Skip to content

Systems and records

Treasury payment approval data: why the right amount is not enough

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

A payment approval dataset captures authority by recording, for each approval, the approver's delegated limit and the policy version in force, the separation between initiator, approver and releaser, the approval state of the payee's bank details at release, how any change request was verified, and the bank or ledger record of what happened to the funds. Amount and approver name alone teach a model the wrong rule.

Provenance trail

Treasury payment approval

This page covers treasury payment approval data: why the right amount is not enough.Illustrative

Key takeaways

  • A payment can carry the correct amount and still be approved under the wrong authority.
  • Authority has at least six dimensions: limit, role separation, payee detail status, change verification, routing and release.
  • An approved workflow status is not an outcome; settlement, return or recall records are.
  • Pair each problem case with a clean counterexample so a model cannot rely on amount or approver name.
  • Tokenize bank details instead of deleting them so that changes stay visible.

How should a payment approval dataset capture authority as well as amount?

A payment approval dataset captures authority when every approval row records who approved, under which delegated limit and policy version, whether that person was independent of the initiator, the approval state of the payee's bank details at the moment of release, how any change request was verified, and what actually happened to the money afterward. Amount and approver name alone are not enough.

Without those fields, a model learns a shallow rule: payments under a threshold with a name in the approver column are fine. Real treasury failures do not always look like that. A correctly sized payment can be approved by someone whose delegation lapsed, released to a bank account changed the day before, or approved on the strength of a phone call to a number supplied by the fraudster. Each is a failure of authority, not of amount.

Public payment rules already frame the problem this way. Nacha's fraud monitoring rules define false pretenses as inducing a payment by misrepresenting identity, authority to act on behalf of another person, or ownership of the account to be credited. Two of those three are about authority, and none is about the amount.

The useful unit is therefore not the payment but the approval decision, with its full context. One payment may involve several decisions, such as approving a new payee, approving a bank detail change and approving release, and each can be right or wrong on its own.

Which kinds of authority does a payment pass through before release?

A treasury payment passes through at least six authority checks, and each one lives in a different record. The table maps them to the systems where they usually sit and to the field a dataset should carry.

Which kinds of authority does a payment pass through before release?
Authority checkWhere the evidence livesField to captureFailure it reveals
Delegated approval limitDelegation of authority matrix, policy document, ERP approval setupApprover limit and policy version in force on the approval dateApproval above limit or under a superseded policy
Segregation of dutiesUser roles, workflow historyInitiator ID, approver ID, releaser ID and their rolesOne person controlling initiation, approval and release
Payee master data statusVendor bank account record and its review statusBank detail approval state at release timePayment to unapproved or pending bank details
Change request verificationCall log, ticket, vendor master change formVerification channel and source of the contact numberVerification through a channel the requester controlled
Routing and completion policyWorkflow configuration and instance historyStep, assignment type, completion rule, delegation and escalation eventsApproval satisfied by the wrong person or an expired delegate
Release and settlementBank portal, payment file, bank confirmation, positive pay fileRelease user, rail, release time, settlement or return statusApproved status recorded but funds never settled, or returned

What do ERP approval records actually show about authority?

ERP workflow records show more than most teams use. In Dynamics 365 Finance, for example, an approval step can be assigned by role, by organizational hierarchy or to named users, can carry a time limit with an escalation path, and can complete on a single approver, a majority, a percentage or all assigned approvers. The workflow history records which of these paths a given document took.

Approver actions are also distinct events. Microsoft's documentation lists approve, reject, delegate and request change as the actions an approver can take, and a rejection ends the workflow. A dataset that flattens these into a single approved flag loses exactly the cases where authority moved from one person to another.

Payee data has its own approval trail. With the vendor bank account workflow switched on, a new bank account is not available for use until approved, and edits to protected fields are held as proposed changes until an approver accepts them. The record's review status, such as approved with pending changes, tells you whether a payment released at a given moment used approved details.

How should approval policy versions be stored alongside the rows?

Store the delegation of authority matrix as its own dated table, and join each approval row to the version in force on the approval date. Limits, approver lists and routing rules change through the year as people join, leave or are promoted, and labelling an old approval against today's matrix turns correct decisions into false violations and real violations into apparent compliance.

A simple structure works: one row per role and payment category, with the limit expressed as a ceiling in the company's base currency, an effective-from date, an effective-to date and the document or board resolution that authorized the change. The approval row then carries a foreign key to that version. When a reviewer checks a packet, the applicable rule field is not a summary someone typed later but the exact version the approver was bound by.

Delegations need the same treatment. A temporary delegation should have a start, an end, a delegator, a delegate and a scope, because the worked case below turns entirely on whether a delegation was still active. Workflow systems usually record the delegation event, but the business reason and intended end date often live in an email or calendar entry, and that record belongs in the packet too.

What should the authority and approval constraint task packet include?

Each packet is one payment decision, frozen at the moment of release approval, with the evidence a careful approver would have had and the outcome that proves whether approval was right. Use the fields below as the packet template.

What should the authority and approval constraint task packet include?
Packet fieldContentsSource recordReviewer check
Starting statePayment request as submitted: payee, purpose, due date, amount, currency, railPayment journal or request ticketNothing dated after the decision point
Applicable ruleDelegation matrix entry and policy versionPolicy repository, ERP approval setupVersion matches the approval date
Approval chainEach step with assignee, action, timestamp, delegation or escalationWorkflow instance historyCompletion rule satisfied by eligible people
Role separationInitiator, approvers and releaser with rolesUser role assignments on the dateNo single person holds conflicting steps
Payee detail statusBank detail review status and last change dateVendor bank account record and change historyRelease used approved details
Change verificationChannel, contact number source, verifier, timeCall log or ticketNumber came from records on file, not the request
Supporting documentsInvoice, contract, purchase order or board resolution IDsDocument management systemPurpose and amount trace to support
Decision labelApprove, reject, hold or escalate, with the reasonReviewer annotationReason cites a field in the packet
Verified outcomeSettled, returned, recalled or recovered, with dateBank confirmation, return notice, reconciliationOutcome comes from the bank or the ledger, not the workflow status
Evidence labelReal or illustrative, and screen statusPacket metadataIllustrative cases are marked as such

Worked case: a correct amount with broken authority (illustrative)

This case is illustrative and not drawn from any company. Starting state: an accounts payable clerk submits a supplier payment that matches an approved invoice and purchase order exactly. The supplier's bank details were edited two days earlier. The first approver is a regional controller acting as delegate for the treasurer, and the payment is 20 percent above the controller's own limit.

Linked evidence: the workflow history shows the delegation was created for a two-week absence that ended the day before approval. The vendor bank record shows the edit was approved, but the change ticket shows the verification call went to a number quoted in the supplier's email. FBI business email compromise guidance advises verifying payment changes in person or through a known telephone number, not one supplied in the request.

Decision: the correct label is hold and escalate, for two independent reasons that have nothing to do with the amount. The delegate lacked authority on the approval date, and the bank detail change was verified through a channel the requester controlled.

Verified outcome: in the illustrative case the treasurer rejects the payment, the supplier confirms through its known contact that its details never changed, and the bank detail change is reversed. The outcome record is the reversal entry and the vendor's written confirmation, not the rejected status in the workflow.

Counterexample: a second payment in the same week goes to a long-standing supplier, under the approver's limit, with no bank changes in a year and a clean two-step approval. Every authority field is satisfied, and the bank confirmation shows settlement. Pairing the two cases teaches that identical amounts and similar approver names can carry opposite answers.

Which records prove approval, and which prove what happened to the funds?

The decision is proven by the workflow instance and the policy in force; the outcome is proven only by records outside the workflow. Treat any packet whose outcome field points back to the approval status as incomplete.

At a glance

Which records prove approval, and which prove what happened to the funds

Timing matters because some rails cannot be reversed. On the Fedwire Funds Service a payment is final and irrevocable when the receiving participant's account is credited or the payment order is sent to it, whichever is earlier. Once that happens, the record of interest becomes a recall request or recovery effort rather than a cancellation, and the packet should say so.

Returns deserve special attention. A returned payment can mean a closed account, a mismatched name or a fraud flag at the receiving bank, and the return reason changes what the case teaches. Keep the bank's return reason as a field rather than a free-text note.

  • Decision proof: workflow history, delegation record, policy version, role assignments.
  • Settlement proof: bank confirmation or statement line matched to the payment ID.
  • Return or recall proof: the bank's return notice, recall request and response.
  • Check payments: the positive pay file and the bank's hold or clear decision, since banks compare presented checks against the issued list and hold mismatches.
  • Ledger proof: the cash and payable entries that cleared, or the reversal entries.

What has to be removed before payment approval records leave treasury?

Account numbers, routing details and employee payee information come out first. Microsoft's own positive pay documentation warns that those files contain sensitive payee and amount information, and the same is true of payment journals and bank portal exports. Replace account identifiers with stable tokens so that a change in bank details is still visible as a change.

Then separate four questions that are easy to blur. Access is whether the team can export the records at all. Privacy covers personal data about employee payees, individual vendors and approvers. Ownership asks whether the company created the records or a bank or vendor did. Licensing rights depend on bank agreements, vendor contracts and confidentiality clauses that may limit reuse. De-identification helps with privacy and nothing else, so counsel reviews the agreements before records are shared outside the company.

When does payment approval history teach the wrong lesson?

Approval history misleads when the recorded process is not the real one. Five patterns recur, and most can be caught by comparing the workflow record to other evidence.

At a glance

When does payment approval history teach the wrong lesson

  • Policy drift: limits or routing changed mid-period, and rows are labelled against the current policy instead of the one in force on the approval date.
  • Shadow approvals: real sign-off happened in email or chat and the system shows a single user approving on someone's behalf.
  • Emergency paths: urgent payments bypassed normal routing and were ratified later, so the record shows approval after release.
  • Collapsed roles: small teams where one person legitimately initiates and approves under a documented compensating control, which should be labelled rather than treated as a violation.
  • Public sector rules: federal certifying officials carry personal responsibility for the legality of a proposed payment under 31 U.S.C. 3528, so government payment data follows a different authority model from corporate treasury and should not be mixed without a label.

Preparing treasury approval packets for a licensing conversation

A company with several years of linked approval, payee change and settlement records has the raw material for authority-aware payment tasks. Treasury and AP teams licensing records like these can work with SourceX, which handles qualification, rights review, contracting, preparation, delivery and payment. The company signs, on scope and terms it has approved, before any delivery, and fit is checked through a short assessment that needs no data.

Frequently asked questions

What is treasury payment approval data?

It is the record of how payments were requested, approved, released and settled: workflow histories, delegation records, payee bank detail changes, verification logs and bank confirmations. For AI use, its value is in linking those records so each approval can be judged against the authority that applied at the time.

Why is the amount not enough to judge a payment approval?

A payment can carry the correct amount and still be sent under the wrong authority, such as an expired delegation or an unverified bank detail change. Nacha's definition of false pretenses centers on misrepresented identity, authority and account ownership, which an amount field cannot capture.

Is an approved status a valid outcome label?

No. Approved means the workflow finished, not that the payment was right or that it settled. The outcome should come from the bank confirmation, a return or recall notice, or the ledger entries that cleared.

Should segregation of duties exceptions be removed from the dataset?

Keep them and label them. A documented compensating control in a small team is a legitimate case, while an undocumented one is a control failure, and a model needs to see both to learn the difference.

Do we need to remove bank account numbers?

Yes, before records leave treasury. Replace them with consistent tokens so that changes to a payee's bank details remain visible without exposing the details themselves.

Sources

  • In Dynamics 365 Finance, the vendor bank account approval workflow can require approval for new bank accounts and for edits to selected fields; a new account is not available for use until approved, and protected field changes are not applied until approved. Source
  • Dynamics 365 approval steps can be assigned by role, organizational hierarchy or named user, carry a time limit with an escalation path, and use a completion policy of single approver, majority, percentage or all approvers. Source
  • In Dynamics 365 workflows an approver can approve, reject, delegate or request a change, and a rejection ends the workflow process. Source
  • Positive pay files list issued checks so the bank can compare presented checks and hold mismatches for review, and Microsoft notes the files contain sensitive payee and amount information. Source
  • Nacha's fraud monitoring rules define false pretenses as inducing a payment by misrepresenting identity, authority to act for another person, or ownership of the account to be credited, and from Phase 2 apply to all non-consumer Originators regardless of volume. Source
  • The FBI's business email compromise guidance advises verifying payment changes in person or through a known telephone number rather than contact details supplied in the request. Source
  • GAO's Standards for Internal Control in the Federal Government describe segregation of duties as separating authority, custody and accounting to help prevent fraud, waste and abuse. Source
  • A Fedwire Funds Service payment is final and irrevocable when the receiving participant's account is credited or the payment order is sent to it, whichever is earlier. Source
  • Under 31 U.S.C. 3528, a federal certifying official is responsible for the legality of a proposed payment as well as the correctness of the certificate and the computation of the voucher. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies