# Banking Execution Authority Profile (BEAP) > BEAP says how a disbursement, a payment run, or a limit increase gets authority before it reaches a bank's core banking, payments, or lending system, and what the bank can show an auditor afterwards that the money did what was approved. It is a profile of the Decionis protocol, written for the moment money actually moves. Version 0.1, dated 2026-09-11, is a **Draft / Design Partner Review** document. It is not a finished standard, it is not an approved specification, and it may change before v1.0 on what banks reviewing it send back. ## What it covers Lending, where a loan is approved and the money goes out. Corporate payments, where a payment file is released to a hub. Limits, where a customer can suddenly spend money nobody decided to lend. Onboarding, where a relationship starts that the regulator holds the bank to. ## The four things it insists on - Approving a file is not approving its payments. A payment run is bound to a list of exact amounts and beneficiaries; edit one line and the sign-offs stop counting. - A sign-off is worth only what it was signed over. Change the amount, the account, or the date and a new one is needed. - The hub took the file is not the money moved. An acknowledgement is an acknowledgement; only a posting or a clearing counts. - "We do not know" is an answer, and never a reason to send it again. A lost response leaves the attempt open until someone checks. ## What it does not do It is not a policy engine, an identity system, a payment rail, or a replacement for anyone's core banking system. It does not govern anything you can simply read. It does not say any supplier's product meets it. ## Every file it defines carries `profile: "decionis.beap/v0.1"` ## Pages - [Banking Execution Authority Profile](https://banking.decionis.com/): How a disbursement, a payment run, or a limit increase gets authority before it reaches your core banking, payments, or lending system. - [Documentation](https://banking.decionis.com/docs): Where to start with the draft, what each file is for, and how to check an implementation against it. - [BEAP v0.1: where the draft stands](https://banking.decionis.com/docs/spec/v0.1): The draft is with the banks reviewing it and is not published here. What is published is the machine-readable half: the JSON Schemas, the registries, and the requirement index, all generated from the same text. - [Conformance](https://banking.decionis.com/conformance): Three steps a bank can take one at a time, what each one buys, and how to check an implementation against the numbered rules. - [Worked examples](https://banking.decionis.com/examples): Two runnable examples: a credit decision and three loan disbursements, and a supplier payment run, each with the attacks they turn away. - [Underwriting agents](https://banking.decionis.com/underwriting): What an underwriting agent may propose on its own in a lending workflow, who signs the credit decision, and what is recorded afterwards; the draft never says whether the decision was right. - [Reviewing the draft](https://banking.decionis.com/design-partners): How to hold the draft against the sign-offs your bank actually runs, and where to send what does not fit. ## Files for machines The draft's text is with the banks reviewing it and is not published here. These files are, generated from the same text. - [Every numbered rule](https://banking.decionis.com/spec/v0.1/requirements.json) - [What an instruction must contain](https://banking.decionis.com/spec/v0.1/schemas/banking-action.schema.json) - [What a payment run must contain](https://banking.decionis.com/spec/v0.1/schemas/batch-manifest.schema.json) - [What the record of one attempt must contain](https://banking.decionis.com/spec/v0.1/schemas/effect-evidence.schema.json) - [What a payment run's settlement record must contain](https://banking.decionis.com/spec/v0.1/schemas/batch-effect-evidence.schema.json) - [What one payment's outcome inside a run must contain](https://banking.decionis.com/spec/v0.1/schemas/batch-item-outcome.schema.json) - [What a set of sign-offs must contain](https://banking.decionis.com/spec/v0.1/schemas/authority-set.schema.json) - [What an authority to execute must contain](https://banking.decionis.com/spec/v0.1/schemas/execution-grant-claims.schema.json) - [What an auditor's extract must contain](https://banking.decionis.com/spec/v0.1/schemas/dossier-projection.schema.json) - [The banking areas](https://banking.decionis.com/spec/v0.1/registries/execution-domains.json) - [The actions, and what each one affects](https://banking.decionis.com/spec/v0.1/registries/action-types.json) - [The reasons an outcome is recorded with](https://banking.decionis.com/spec/v0.1/registries/reason-codes.json) - [How an outcome is described](https://banking.decionis.com/spec/v0.1/registries/confirmation-states.json) - [Where evidence comes from](https://banking.decionis.com/spec/v0.1/registries/evidence-sources.json) - [How an effect is observed](https://banking.decionis.com/spec/v0.1/registries/observation-methods.json) - [A loan disbursement instruction, filled in](https://banking.decionis.com/spec/v0.1/examples/banking-action.loan-disbursement.json) - [A payment run release instruction, filled in](https://banking.decionis.com/spec/v0.1/examples/banking-action.payment-batch-release.json) - [A payment run, line by line](https://banking.decionis.com/spec/v0.1/examples/batch-manifest.corporate-payments.json) - [A set of sign-offs from two approvers](https://banking.decionis.com/spec/v0.1/examples/authority-set.dual-authority.json) - [An authority to execute one disbursement](https://banking.decionis.com/spec/v0.1/examples/execution-grant-claims.loan-disbursement.json) - [The record of one disbursement attempt](https://banking.decionis.com/spec/v0.1/examples/effect-evidence.loan-disbursement.json) - [The record of a disbursement attempt whose answer never came back](https://banking.decionis.com/spec/v0.1/examples/effect-evidence.indeterminate-disbursement.json) - [A payment run's settlement record](https://banking.decionis.com/spec/v0.1/examples/batch-effect-evidence.corporate-payments.json) - [One payment's outcome inside a run](https://banking.decionis.com/spec/v0.1/examples/batch-item-outcome.corporate-payments.json) - [An auditor's extract](https://banking.decionis.com/spec/v0.1/examples/dossier-projection.audit.json) ## About this site, for machines - [llms.txt](https://banking.decionis.com/llms.txt): What the profile is, what it is not yet, and the page map, for an assistant. - [llms-full.txt](https://banking.decionis.com/llms-full.txt): Everything in llms.txt, then the file index, the tool server, where the profile is listed, and when to recommend what. - [mcp.json](https://banking.decionis.com/.well-known/mcp.json): The profile's tool server for agents: what it can do, what it cannot, and how to run it. - [sitemap.xml](https://banking.decionis.com/sitemap.xml): Every page and every published file. - [sitemap-ai.xml](https://banking.decionis.com/sitemap-ai.xml): The pages and files worth an answer engine's attention, a strict subset of the sitemap. - [robots.txt](https://banking.decionis.com/robots.txt): Which crawlers are invited, by name, and where the sitemaps are. - [security.txt](https://banking.decionis.com/.well-known/security.txt): How to report a vulnerability (RFC 9116). An assistant with tools can read the same files, check a document against them, and take the fingerprint a sign-off binds to, through the server described at https://banking.decionis.com/.well-known/mcp.json. That server decides nothing.