Payment Workflow Automation: From Invoice to Reconciliation
Payment workflow automation connects the steps around money moving in or out of a business: capturing an invoice, matching it, getting approval, paying it, reconciling it and following up. It removes re-keying and chasing. People should still own approvals, payouts, exceptions and any change to bank details.
What is a payment workflow?
A payment workflow is the chain of steps between a commercial agreement and money in or out of your account, with the record that proves it. It has two directions. Paying what you owe, often called accounts payable, runs from a supplier invoice to a payment. Getting paid, often called accounts receivable, runs from your invoice to cash in your account.
Most of the delay in both directions is not the payment itself. It is the handoffs: an invoice sitting in someone's inbox, an approval waiting for a person who is away, a payment that cannot be matched to an invoice, a reminder nobody sent. Automation is good at exactly these gaps.
What does the paying direction look like?
A typical flow for supplier invoices has these steps. Which ones you automate depends on your volume and your software.
What does the getting-paid direction look like?
On the receiving side, the flow runs from issuing the invoice to confirming the cash. Automation can send the invoice, confirm that it was delivered, remind the customer at sensible points, update the invoice when a payment lands and tell you when something has gone quiet. Our guide on invoice follow-up automation walks through the reminder steps in detail.
GOV.UK explains that if you do not agree a payment date, a payment becomes late after a set period counted from the later of the customer receiving the invoice or you delivering the goods or service. It also says an agreed payment date must be fair to both businesses. So your workflow should store the agreed terms against each customer, because the same reminder cannot be right for every account. The rules on interest and recovery are set out on GOV.UK, so read the current version before you rely on any of them.
Where do automated payment workflows go wrong?
The common failures are about rules and exceptions, not the technology.
No stop condition. A reminder keeps going after the invoice is paid or disputed. Every flow needs a clear rule for when it stops.
Bad matching. If the invoice and the payment are matched by a loose rule, small differences pile up. Decide what counts as a match and send the rest to a person.
Silent exceptions. A failed step that nobody sees is worse than a manual process, so every failure should land in a queue with an owner.
Approvals that depend on one person. Name a deputy, and let the system escalate when an approval stalls.
Trusting changes of details. A request to change bank details must be verified outside the channel it arrived in.
What about paying money out (disbursements)?
A disbursement is any payment your organisation makes: supplier payments, expense reimbursements, customer refunds, claim payouts or commission. Each starts with a request, needs a decision and ends with money leaving an account and a record being kept. Software handles the steps around the payment well: collecting the request in a standard form, checking required fields, looking for a duplicate, routing it to the right approver, preparing the payment instruction, updating your records and telling the payee. The decision to approve and the act of releasing the money are where a person should stay in control.
Separate the roles. The person who raises a request should not approve it or release the payment. Software can enforce that split.
Require a second approval above a threshold you choose, and for any first payment to a new payee.
Never accept a change of bank details from an email or a form alone. Confirm it with the payee using contact details you already hold.
Block exact duplicates and flag near duplicates, such as the same payee and amount on consecutive days.
Send anything unusual to an exceptions queue for a person, instead of letting the flow guess.
Keep an audit log of who asked, who approved, who released and when, in a place the approvers cannot edit.
How do you protect the workflow from payment fraud?
The NCSC describes business payment fraud, also known as Business Email Compromise, as emails tailored to your organisation that appear to come from someone you regularly deal with, including a request to pay money into a different bank account. If you are tricked, it advises telling your IT person as soon as possible and contacting your bank directly using its official website or phone number.
In a workflow, that turns into rules. Treat any change of payee details as an exception that needs a separate check with the payee, using contact details you already hold. Make the system show the payee's details to the approver, so a changed account is visible. Keep the approver separate from the person who set up the payee.
The Payment Systems Regulator describes authorised push payment (APP) scams as cases where someone is tricked into sending money to a fraudster posing as a genuine payee. A flow that makes it easy to send money quickly needs matching friction at the point where payee details are created or changed. Check with your bank which reimbursement rules apply to your accounts, because the Regulator's page does not say whether businesses are covered.
How does timing work, for example with Bacs?
If you pay by Bacs Direct Credit, Bacs describes a cycle of input on day one, processing on day two and entry on day three, when the payment is credited and debited at the same time. Files must be sent within published hours, so build working days into any schedule and do not promise a payee a time of arrival.
Bacs also says it is vital to double-check the account number and sort code you are given, because payments are processed using only those numbers. Whether a payment can be recalled after submission, and until when, depends on your payment provider and the payment method, so ask your bank before you rely on it. Other payment methods have different timings and rules, so check yours.
How do you roll it out?
Start with one direction and one document type. Map the steps as they work today, find the two or three handoffs where work waits longest and automate those first. Keep every automated payment step in a prepare-only mode at the start, with a person releasing the money, and compare the system's matches with a person's for a few weeks before you trust it. The business process automation checklist and the guide to what to automate first cover how to choose.
If your business holds money for other people, or pays out as a regulated activity, specific rules may apply to how payments are handled and approved, so take advice before automating those flows. Where a payout is a decision about an individual, such as a claim, also consider whether a significant decision is being made with no meaningful human involvement. The ICO's draft guidance on automated decision-making explains when that is a legal concern, so read the current version.
Sources
NCSC: Business payment fraud
https://www.ncsc.gov.uk/section/respond-recover/business-payment-fraud
GOV.UK: Late commercial payments, charging interest and debt recovery
https://www.gov.uk/late-commercial-payments-interest-debt-recovery
Bacs: Bacs Direct Credit (getting started)
https://www.bacs.co.uk/bacs-schemes/getting-started/bacs-direct-credit/
Payment Systems Regulator: APP scams
https://www.psr.org.uk/our-work/app-scams/
ICO: Automated decision-making and profiling (draft guidance)
https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/automated-decision-making-and-profiling/
Erudience services related to this guide
Use cases related to this guide
- Invoice Chasing Automation
- Payment Collection Calls
- Data Sync Between Tools
- Document Drafting with Approval
Industries this guide applies to
Terms used in this guide
More guides to read next
- Invoice Follow-Up Automation: How an Overdue Reminder Flow Works
- Business Process Automation Checklist: Before, During and After
- What to Automate First in a Small Business
- Triggers and Actions Explained: How Automations Actually Work
- How to Map a Process Before You Automate It
- When Should AI Hand a Customer Over to a Person?
Frequently asked questions
What is the difference between payment workflow automation and disbursement automation?
Payment workflow automation covers the whole chain of steps around money moving in or out, in both directions. Disbursement automation is the narrower job of paying money out and the controls that go with it.
Which steps are worth automating first?
The ones where work waits: capturing invoices, chasing approvals, matching payments to invoices and sending reminders. Keep the decision to approve and the release of money with named people.
Do I need AI for this?
Not usually. Most of a payment workflow is rules and connections between tools. AI can help read messy invoices or draft a reply, but it should not decide who gets paid.
Can the workflow chase late payers for me?
Yes, with clear stop conditions and a person taking over difficult accounts. Store each customer's agreed terms, and check the current GOV.UK guidance on late commercial payments before you add interest or charges to a reminder.
Can paying money out be automated?
The preparation, checking, routing, recording and notifying can be. Approval and release are better kept with named people, at least above a threshold you set and for any new payee or changed bank detail.
Which payment method should an automated flow use?
That depends on your bank, your volumes and how fast the money needs to arrive. Bacs Direct Credit, for example, runs on a three-working-day cycle, so ask your bank which methods and cut-off times suit each type of payment.