Automate customer invoicing from job completion to checked reconciliation, with UK invoice fields, approval rules, payment matching and exception handling.
18 June 2026 · 9 min read · Daniel Stevens
Last updated 31 August 2026
Make your accounting platform the invoice system of record, then connect one approved business trigger to a controlled draft, validation, send, reminder and reconciliation flow. The routine path runs without re-keying. Missing fields, disputes and unmatched payments enter a named review queue.
This guide covers sales invoices you issue to customers, also called accounts receivable. Supplier invoices you receive are accounts payable and need a different flow for document capture, approval and payment. The custom AI integration reference flow shows how one supplier-PDF route can work.
Research published by the Office of the Small Business Commissioner on 31 July 2025 found that 22% of surveyed businesses spent staff time chasing late payments. Among businesses affected by late payment, that averaged 86 hours per year. A scheduled reminder ladder can return the routine follow-up to the workflow while finance keeps the decisions that need judgement.
Create and number each invoice in your accounting platform. Xero, QuickBooks, FreeAgent and similar products already cover recurring invoices, email delivery, reminders and bank or payment connections on some plans. Use those native controls where they fit. Add a connected workflow when the trigger or required data lives in your job, booking, CRM or e-commerce system.
Record the accounting invoice ID back against the source job or order. That gives both systems one shared reference.
Choose the event that makes work ready to invoice. Examples include:
approved for billingUse a stable source key such as job-1842:final or contract-72:2026-08. Before creating anything, the workflow checks whether that key already has an invoice ID. A retry then returns the existing record instead of raising a duplicate.
Write down where each field comes from before connecting the systems:
| Invoice field | Approved source | Review condition |
|---|---|---|
| Customer legal name and address | Accounting customer record | Missing or unverified customer record |
| Description, quantity and price | Approved job, order or timesheet | Unapproved line or price override |
| Supply date and invoice date | Job record and accounting clock | Missing completion or supply date |
| Payment terms and purchase order | Customer terms record | Required PO absent |
| VAT code and rate | Accountant-approved item or customer mapping | New or conflicting tax treatment |
| Currency | Contract or customer terms | Currency differs from the approved contract |
The accounting platform should calculate VAT from an approved tax-code mapping. The workflow moves the agreed inputs; it does not invent tax treatment.
Check the required customer details, line totals, dates, VAT mapping, currency, payment terms and source key. Then apply a written approval rule.
For example, standard repeat work under an agreed value can move from validated draft to send. A first invoice, price override, new VAT treatment or missing purchase order stays in draft for finance approval. The threshold and reviewer belong in the workflow specification.
Send the approved invoice from the accounting platform and include the payment route agreed with the customer. Store the invoice ID, delivery status, due date and payment reference. If delivery is rejected, keep the invoice open and route the customer details for correction.
Build the reminder sequence around the current invoice state, not a date alone. Immediately before each message, query the open balance and status.
An open invoice can receive the approved pre-due, due-date and overdue messages. A paid, disputed, voided or credited invoice leaves the sequence. A partial payment follows the rule agreed for its remaining balance. The automated invoice-chasing playbook shows the customer-facing part of this workflow.
| Reminder stage | Live-state check | Approved action |
|---|---|---|
| Before due | Invoice is open, delivered and has a balance | Send the agreed heads-up with the invoice and payment route |
| On the due date | Balance remains open and there is no hold | Send the due-date reminder in the approved voice |
| Overdue | Balance remains open at the agreed interval | Send the next reminder and record the message against the invoice |
| Escalation | The invoice reaches the agreed threshold | Present the invoice, correspondence and approved next action to the named reviewer |
The schedule, intervals and wording belong in the workflow specification. For a professional-services example, see the invoice-chasing schedule for consultants. That example remains part of the same parent playbook, with the live balance and status checked before every message.
Treat payment collection and reconciliation as separate events. A successful payment event proves that a provider accepted the payment. Reconciliation decides which accounting invoice and balance it belongs to.
An automatic match should use an agreed combination of invoice ID or payment reference, customer, currency and amount. It should also check that the payment event has not already been processed. Partial payments, batched settlements, processor fees, foreign exchange differences, refunds, chargebacks and missing references enter the review queue with the candidate invoice attached.
| Stage | Input | Output | Review route |
|---|---|---|---|
| Trigger | Approved job, order, timesheet or billing date | Stable billing key | Trigger has missing approval or was already processed |
| Draft | Customer, lines, dates, terms and tax codes | Accounting draft with invoice ID | Required field or mapping is absent |
| Send | Validated or approved draft | Sent invoice and delivery record | Delivery rejected or recipient needs correction |
| Remind | Open balance and reminder schedule | Approved message and event log | Dispute, hold, credit or customer-specific rule |
| Reconcile | Unique payment event and open invoices | Exact match and updated balance | Partial, batched, fee-adjusted or unmatched payment |
| Report | Invoice and payment states | Outstanding, overdue and exception measures | Source totals do not reconcile |
The Automate workflow ends with reliable invoice and payment events. From there, Turing BI can analyse outstanding balance, overdue balance, time from billing approval to send, reminder events and the review-queue age in a governed dashboard.
| Test | Expected evidence |
|---|---|
| The same billing event arrives twice | One invoice exists and both runs point to the same invoice ID |
| A required address, PO or VAT mapping is absent | The invoice stays in draft and the named reviewer receives the reason |
| An API timeout happens after invoice creation | The retry finds the existing invoice by its stable source key |
| Payment arrives before the next reminder | The fresh balance check removes the invoice from that reminder run |
| A customer makes a partial payment | The paid amount and open balance remain distinct and follow the agreed rule |
| A settlement contains fees or several invoices | The settlement enters review with candidate matches rather than closing the wrong invoice |
| A dispute, credit note or refund is recorded | The reminder state and accounting balance follow the approved handling rule |
Keep a short parallel run before handing the routine path over. Compare invoice counts, gross and VAT totals, open balances and payment matches between the old and new process.
As at 31 August 2026, GOV.UK says an invoice must include a unique identification number, supplier and customer details, a clear description, supply and invoice dates, amounts, applicable VAT and the total owed. Sole traders and limited companies have additional identity requirements. VAT invoices carry further fields, and HMRC says electronic VAT invoices must contain the same information as paper versions.
Making Tax Digital for Income Tax applies from 6 April 2026 to qualifying sole traders and landlords with more than £50,000 of self-employment and property income. HMRC requires compatible software and digital records, with digital links where more than one product is used. An invoice workflow should preserve that record route; automation on its own does not confirm tax compliance.
Have your accountant approve VAT codes, tax-point handling, credit notes and record-retention rules before launch. The workflow then enforces that approved map.
As at 31 August 2026, the Commercial Payments Bill is proposed legislation, not law. It was introduced in the House of Lords on 19 May 2026 and has not received Royal Assent. The proposal includes maximum payment terms and mandatory interest measures, but those proposed measures are not yet in force.
Use the current GOV.UK guidance on late commercial payments for the rules that apply now. Keep any interest or debt-recovery wording behind a named approval step, and have an accountant or legal adviser confirm the entitlement, calculation and message before it enters an automated sequence. The Commercial Payments Bill overview and UK Parliament bill page show the proposal and its progress.
Start with the accounting platform's own features when the invoice begins there, the schedule is recurring, the reminder sequence is standard and its bank or payment connection covers reconciliation. This keeps the fewest moving parts.
A connected workflow automation earns its place when billing begins in another operational system, several records form the invoice, approval rules vary by customer, or payment and reconciliation need a defined route across systems.
Tell us where billing starts and which accounting platform holds the invoice. We will map the trigger, fields, approval path, reminder states and reconciliation rule into a fixed-scope plan and quote for you to review.
Want this handled end to end? It’s part of Workflow & Process Automation: we design it, build it and hand it over.
The routine path can run from an approved trigger through draft, send, reminders and an exact payment match. Finance keeps the review queue for missing fields, new tax treatments, disputes, credits and unmatched payments. Define both paths before launch.
Get started
Tell us what you want to automate. You get a free plan and a fixed quote to approve before anything gets built.
Fixed price you approve firstYou own everything we buildPause or cancel anytime