Keep recurring supplier transfers aligned with current authority, contract terms and bank instructions. Separate the approval of a repeating instruction from proof that each payment was correct.
A supplier’s monthly charge changes, but the standing order keeps paying the old amount. Alternatively, a replacement instruction starts while the original is still active. Both problems can survive a perfectly tidy invoice-approval process because the bank instruction repeats independently of the next AP payment run.
For a UK finance team, the control object is therefore two things: the standing instruction and each payment it produces. This guide covers payer-initiated, fixed recurring supplier transfers, not supplier-collected Direct Debits, recurring card charges or ACH arrangements. The controls below are recommended company practices; your bank’s channel rules, authority arrangements and contract terms still govern the actual action.
Control the instruction, not just the next invoice
A standing order tells the bank to send a fixed amount at regular intervals. Lloyds’ business payment guidance distinguishes this payer instruction from a Direct Debit, where a company has permission to collect. Its setup information includes the recipient, amount, frequency and first payment date.
That difference changes the review. Do not wait for a supplier’s collection notice: finance must maintain the expected schedule itself. Conversely, an approved standing order does not prove that a particular invoice is valid or that cash reached the intended supplier.
- Instruction lifecycle: proposed → authorized → bank-confirmed active → change pending → superseded or retired.
- Payment cycle: expected → bank outcome checked → allocated → posted → reconciled, with a separate exception for any difference.
Closing September’s payment does not retire the instruction. Retiring the instruction does not, by itself, extinguish an unpaid invoice or settle a contract dispute.
Build a versioned standing-order register
AP owns the commercial linkage; treasury owns verification of the bank instruction. Keep one stable internal instruction ID and a new version for every approved change. Do not overwrite the old amount or effective date and lose the explanation for earlier payments.
- Identity: buying entity, supplier ID, contract reference, bank instruction reference and masked funding-account reference. Keep full banking details only in the approved secure record.
- Schedule: fixed amount and currency, frequency, first date, next expected date, final date or other end condition, and payment reference.
- Authority: business owner, preparer, approver, authorized bank operator, approval evidence and backup owner.
- Version boundary: old version’s last intended payment, new version’s first intended payment, change reason and bank-confirmed effective outcome.
- Accounting linkage: invoices or service periods covered, allocation basis, posting references and treatment of any balance paid on account.
- Review: next review date, evidence checked, exception owner and current instruction status.
Set the review frequency according to risk and company policy. Also trigger a review when the contract price, beneficiary, funding account, service status or responsible owner changes. A register marked “inactive” is not evidence that the bank instruction has stopped.
Put an evidence gate at every financial transition
| Trigger and owner | Evidence and control | Exception and next state |
|---|---|---|
| New request — AP and business owner | Confirm valid obligation, fixed schedule, entity, supplier and approved payment route. Treasury checks beneficiary and funding account before authorized bank setup. | Missing contract or unverified payee: keep proposed. Resume only after evidence and policy approval. |
| Setup submitted — treasury | Compare bank-confirmed amount, dates, reference and instruction status with the approved version. Retain the bank reference and confirmation time. | Submitted or awaiting approval is not active. Resolve rejection or incomplete bank authorization before relying on the schedule. |
| Price or date change — AP, approver and treasury | Approve the revised commercial basis and exact old/new payment boundary. Verify what the bank actually changed and when. | Effective period uncertain: change pending. Escalate before releasing any parallel top-up or replacement. |
| Payment expected — treasury and AP | Check actual bank activity against the active instruction and the amount due for that period. Exclude the same obligation from a manual payment run. | Missing, duplicate or wrong amount: investigate bank status, allocate an owner and block an automatic replacement. |
| Cash recorded — accounting | Link the bank line, approved allocation and posting reference. Explain differences and identify any still-open liability or recoverable amount. | Do not force a match with an unsupported expense or credit. Reconcile after approved classification or keep a linked residual case open. |
| Service ends — business owner and treasury | Retain the commercial decision and bank cancellation result. Check the final payment period and later bank activity. | Retire only on verified instruction closure; separately own final invoices, credits and recovery. |
Bank permissions are not identical to internal approval policy. Bank of Scotland’s business setup guidance describes required account access and roles, and configurable approval methods. Check your actual bank configuration rather than assuming every instruction receives an independent second approval.
Change one version without funding two schedules
Approve the boundary before the bank action
Write the instruction change as a before-and-after decision: current amount, proposed amount, last period under the old version and first period under the new version. Include any one-off adjustment separately. An instruction change is not permission to pay an extra amount for every prior period.
Lloyds’ standing-order amendment guidance covers changing amount, date and frequency, with different instructions by banking channel. Confirm which changes your account supports. If the bank requires cancellation and replacement, link the two instructions and verify their date boundaries rather than creating an overlapping schedule.
A beneficiary change deserves its own verification, not just a new version label. Follow the vendor bank-account change control before authorizing changed payment details. Keep independent verification and the resulting approval linked to the instruction change.
Use the bank’s actual timing, not a universal cutoff
Record the applicable bank channel, action deadline, request time and confirmation. Leave enough time for your internal approval as well as the bank action. An internal “cancelled” status is not a bank result.
For example, NatWest’s business standing-order guide says Bankline cancellation can take two business days and directs customers to support when a payment is due within that window. The page also gives channel-specific timing information. Confirm the rule for your own account and channel; do not turn one bank’s example into a UK-wide promise.
If the next payment may already be processing, keep its status unresolved until treasury establishes the outcome. Use the separate vendor payment cancellation process for a particular payment that needs stopping or recovery. Do not assume retiring future instructions retrieves cash already sent.
Worked example: a price increase misses the cutover
Illustrative example, GBP: a supplier’s approved fixed monthly fee increases from £1,200 to £1,350 from November. There are no fees, currency differences or tax adjustments in this illustration. The contract owner supplies the agreed change; finance authorizes version 2 with November as its first intended period.
Treasury discovers that the bank still sent £1,200 for November. The instruction change did not govern that payment. AP must record the actual outcome, not change the register retrospectively to make it look successful.
- Establish the difference: £1,350 valid November obligation − £1,200 confirmed payment = £150 still to resolve. Check allocation and any credits before authorizing further cash.
- Separate the correction: authorize a £150 one-off payment only after treasury rules out another pending transfer covering the same difference. Link its payment reference to November, not to a second recurring instruction.
- Verify the next cycle: treasury confirms the bank’s active instruction is £1,350 for the next intended date, with no duplicate old instruction. Record the actual effective boundary for version 2.
- Reconcile: accounting checks the £1,200 and £150 bank lines against the £1,350 obligation and approves the posting treatment. The difference is zero only after the second payment is confirmed and allocated.
If both a £1,200 old instruction and a £1,350 replacement were paid for the same £1,350 obligation, the £1,200 excess would need a separately controlled recovery or approved application. Do not classify the extra transfer as another month’s expense simply to clear the bank reconciliation.
Close the recurring arrangement and the balance separately
Use two completion tests. Instruction closure needs the bank cancellation or end-state evidence and review of the relevant subsequent activity. Financial closure needs the final obligation, actual payments, credits, allocation and posting references to agree, with any residual assigned an approved disposition.
Stopping a payment method is an operational action, not a substitute for determining contractual entitlement. The business owner resolves termination and final charges under the actual agreement. Accounting decides classification, period and entries under the organization’s policies; this guide does not prescribe a universal journal.
Review unmatched payments, overdue change requests, instructions without a current business owner, and instructions continuing beyond their approved end condition. Use counts and outstanding amounts from your own records; do not assume a control has worked merely because no supplier has complained.
Where Workhint fits
The coordination problem is the handoff between AP’s commercial evidence, a finance approver’s decision, treasury’s bank action and accounting’s reconciliation. Workhint’s Workflow Engine describes role-based approval routing and required details, files or approval steps before work advances. Those capabilities are relevant to a standing-order change packet with an old/new schedule and required bank evidence.
The Finance Leaders solution describes connecting approved work with invoicing and tracking payout status. For this use case, treat the article’s register and closure gates as a proposed operational design to validate in your implementation, not as proof of a ready-made standing-order integration.
The cited pages do not establish native standing-order creation, bank cancellation, live bank-status import or automatic ledger reconciliation for this workflow. Keep those execution steps in the authorized bank and accounting systems and require their evidence before closing the coordination task.
Frequently asked questions
Does invoice approval change a standing order?
No. It is an internal decision, not evidence that the authorized bank action has happened. Compare the bank-confirmed instruction with the approved schedule.
Should a missing payment be replaced immediately?
Not solely because it is absent from an imported statement. Treasury should establish whether the bank rejected, delayed or is still processing it, then authorize an alternative only when duplication risk is resolved.
Can one-off adjustments be added to the recurring amount?
Only if that is genuinely the approved future schedule. Keep a single-period shortfall separate so it does not become an accidental permanent increase.
When is the case complete?
When the instruction’s actual state is evidenced and the relevant payments and obligations reconcile. An open final invoice or recovery remains a separate owned case even after the instruction is retired.

Leave a Reply