What is payment approval? Definition, example, and how it works
Accounts payable and procure-to-pay
Payment approval is an authorization step, often by amount threshold, in which a designated person approves a payment before funds are released to a supplier. It comes after the supplier bill is recorded and approved, creates no journal entry of its own, and is the last internal check before cash leaves the bank.
- Type
- Authorization step
- Comes after
- Bill recorded and approved
- Journal entry
- None of its own
- Routed by
- Amount threshold
What is the purpose of payment approval?
Payment approval stops cash from leaving for the wrong payee, the wrong amount, or a bill already paid.
The FBI's 2025 Internet Crime Report (IC3) logged 24,768 business email compromise complaints with $3,046,598,558 in reported losses for 2025. That is one scheme approval exists to catch: a routine-looking request that sends cash to an impostor.
How does payment approval work?
Payment approval usually works on a batch: AP proposes which approved bills to pay, an approver reviews each item, and often a second person releases the file to the bank.
- Select: AP pulls approved, due bills into a payment proposal or run
- Review: The approver checks payee, amount, due date, bank details, and duplicates
- Approve: Routing follows the approval matrix below
- Release: Someone other than the approver sends the payment file or authorizes the wire
How long approval takes depends on routing. In QuickBooks Online Advanced or QuickBooks Bill Pay Elite, payment release workflows send bill payments to the approver's Pending Approvals tab, and payments not reviewed within 30 days are automatically denied. With vendor payment approval routing turned on in NetSuite, a typical setup has a Payment Clerk create payments and an AP Payment Manager approve them. In SAP S/4HANA Cloud, the Approve Bank Payments app approves payment batches.
How do you set payment approval thresholds?
You set payment approval thresholds from your delegation of authority: dollar bands decide who approves, and risk triggers send certain payments up regardless of amount. The bands below are illustrative.
| Payment | Approver | Released by |
|---|---|---|
| Up to $5,000 | AP manager | Treasury or a second user |
| $5,001 to $25,000 | Controller | Treasury or a second user |
| Over $25,000 | Controller and CFO | Treasury or a second user |
| Any wire, new vendor, changed bank details, or off-cycle payment | Controller, whatever the amount | Treasury or a second user |
In a sound design, no one approves a payment they requested, and the approver doesn't release it.
Payment approval example
Alder Robotics runs its weekly payment run on Thursday, October 29, 2026, with three approved bills. The $42,000 bill waits for the CFO, who approves it Monday, November 2. All amounts are illustrative.
| Date | Account | Debit | Credit |
|---|---|---|---|
| Oct 5, 2026 | Consulting expense | 18,400 | |
| Accounts payable | 18,400 | ||
| Oct 12, 2026 | Software expense | 3,200 | |
| Accounts payable | 3,200 | ||
| Oct 14, 2026 | Equipment | 42,000 | |
| Accounts payable | 42,000 | ||
| Oct 30, 2026 | Accounts payable | 21,600 | |
| Cash | 21,600 | ||
| Nov 2, 2026 | Accounts payable | 42,000 | |
| Cash | 42,000 | ||
| Total | 127,200 | 127,200 |
Nothing posts on October 29, approval day. Treasury releases the two smaller payments Friday, October 30, inside their net 30 terms.
| Payment run, October 29, 2026 | Amount | Approver | Approved | Open in AP, Oct 31 |
|---|---|---|---|---|
| Consultant | $18,400 | Controller | Oct 29 | $0 |
| Software | 3,200 | AP manager | Oct 29 | 0 |
| Equipment | 42,000 | Controller and CFO | Nov 2 | 42,000 |
| AP aging total, these vendors | $42,000 | |||
| General ledger AP, these vendors | $42,000 | |||
| Difference | $0 |
Does payment approval create a journal entry?
No. Approval is a control, not a transaction: the entries are the bill (debit expense or asset, credit accounts payable) and the payment (debit accounts payable, credit cash) when funds are released.
What is payment approval confused with?
Payment approval is most often confused with invoice approval, a payment hold, and the payment run itself.
| Term | What it is | How it differs from payment approval |
|---|---|---|
| Invoice approval workflow | Routing of a supplier invoice to the right approvers, based on amount, department, or cost center, before it is released for payment | Approves the bill and the cost; payment approval approves the cash |
| Payment hold (payment block) | Block placed on an invoice or vendor that prevents payment until a dispute, mismatch, or compliance question is resolved | Stops payment until cleared; approval permits it |
| Payment run | Scheduled batch in which a company selects approved, due supplier invoices and pays them together by ACH, wire, check, or card | The batch; approval is the sign-off on it |
| Segregation of duties in AP | Internal control that splits tasks such as vendor setup, invoice entry, approval, and payment among different people to prevent fraud and errors | The rule that keeps approver and releaser apart |
"Payment approval percentage" in card processing means something else: the share of a merchant's card transactions that get authorized.
Quick test: if you're deciding whether cash should leave today, it's payment approval.
Payment approval vs invoice approval
Invoice approval authorizes the liability; payment approval authorizes the movement of cash. The first confirms the bill is real and coded, the second that this payee should get this amount today.
Payment approval at month end
At month end, you confirm that only released payments reduced AP and that every payment above threshold has approval evidence, as part of the month-end close.
- Cutoff: Record payments on the release date; approved but unreleased bills stay in AP
- Pending list: Clear bills stuck in approval before late fees or missed discounts
- Evidence: Match approver, date, and amount to the released payment file
- Tie-out: Agree the AP aging total to the general ledger
For cash flow, the pending approval list is next week's outflow forecast. Our AP Agent posts each bill only after your team approves it, approvers can't approve their own request, and payment stays with your team.
Common payment approval mistakes
The most common payment approval mistakes are trusting the invoice approval and approving the batch total without reading it.
- Treating an approved invoice as approved cash: Bank details can change between bill approval and payment
- Approving and releasing as one person: One user can then create and send a payment alone
- Signing off on the batch total: A changed bank account hides inside a long run
- Dollar thresholds only: Wires, new vendors, and bank changes need review at any amount, and split payments dodge the bands