Invoice Automation for Small Business with n8n, QuickBooks and Xero

How does supplier invoice capture work, step by step?

This is the flow we would normally propose. Your own version depends on how invoices reach you and who signs them off.

1. Trigger. An accounts mailbox receives the invoice. n8n's Email Trigger (IMAP) node can watch a mailbox and download attachments, and its Gmail Trigger node starts a run when a message arrives. A rule discards anything with no PDF or image attached.
2. File intake. The attachment is saved to storage you control, and a fingerprint of the file is written to a log so the same file cannot be processed twice.
3. Extraction. An AI model reads the document and returns structured fields: supplier, invoice number, issue and due dates, currency, lines, tax and total. Fields it cannot read confidently are flagged rather than guessed.
4. Checks. The workflow runs the tests in the table below.
5. Human approval. A message goes to the approver with the key fields and a link to the file. n8n's WhatsApp Business Cloud node, for example, offers a send-and-wait step that pauses the run until someone replies, and other nodes can do the same by email or chat.
6. Posting. On approval, the bill is created as a draft. The QuickBooks Online node lists create, get and update operations for bills and vendors. In the Xero API a bill is an invoice of type ACCPAY, and the API's statuses include Draft, Submitted and Authorised. n8n's Xero node page lists contacts and invoices, so bill handling may go through the HTTP Request node with your Xero credential, which n8n documents as the route for anything a node does not cover.
7. Attachment and log. Both APIs accept files linked to a transaction (QuickBooks through its attachment upload, Xero through invoice attachments, which cover purchase bills). The log row is updated and your bookkeeper is told it is waiting.

What does the workflow check before anything is posted?

Most of the value is in the checks, not the AI read. Each one has a defined outcome, so a failure never ends as a silent bad entry.

Check	How it works	If it fails
Same file seen before	Fingerprint compared with the log	Stop, tell the approver, post nothing
Same supplier and invoice number	Search existing bills in QuickBooks or Xero (Xero's API can filter by invoice numbers)	Send to review marked “possible duplicate”
Unknown supplier	Match against your vendor or contact list	Ask a person to pick or confirm; no new supplier is created silently
Arithmetic	Lines, tax and total must agree	Review with the mismatch highlighted
Dates and currency	Due date after issue date, no far-future dates, currency matches supplier history	Review
Changed bank details	Compared with the supplier's previous invoice	Hold; confirm by phone using a number you already had, never one printed on the new invoice

What can go wrong, and how is it handled?

• The AI misreads a figure. The approver sees the original file next to the values, and totals are cross-checked, so a misread normally shows up as an arithmetic mismatch. It cannot be ruled out, which is why approval exists.
• A scan is blurry or the invoice is a statement. The item goes to a manual queue instead of being forced through.
• A connection expires. n8n lets you assign an error workflow, started by its Error Trigger node, which receives the failed run's details. We would use it to alert a person with a link to the run.
• The accounting system is down or rejects the bill. The invoice stays in the queue as unposted. It is only marked done once the system returns a record ID.
• The same email arrives twice. The file fingerprint catches it.

Can it chase customers for payment and help with reconciliation?

Reminders. A scheduled run lists unpaid customer invoices from QuickBooks (the node can get invoices and has a send operation) or Xero, then groups them by due date: a courtesy note shortly before, a polite nudge on the day, and firmer notes after. Before each send it re-checks the invoice status, so a customer who paid this morning is not chased this afternoon. Customers you mark as in dispute are skipped, and large balances can wait for a person to approve the wording. Your accounting software may already have built-in reminders; custom rules are worth it only when you need logic those do not offer.

Reconciliation. The workflow does not mark anything as reconciled. It helps matching by keeping supplier names consistent, putting the invoice number in the reference, attaching the file, and producing a weekly list of approved bills with no payment and payments with no matching bill. The final match stays with your bookkeeper.

What does it not replace, and how is the data protected?

It does not replace an accountant. Tax treatment, sales tax or VAT coding decisions, year-end work, filings and advice stay with a qualified person. The AI can suggest an account code, but it is a suggestion.

Invoices contain names, addresses and bank details, so treat them as sensitive. As general information, not legal advice: collect only what you need, limit who can open the review queue, decide how long files are kept, and read your AI provider's terms on how submitted data is used and where it is processed. Self-hosting n8n keeps workflow data on infrastructure you choose; our self-hosted versus cloud comparison covers that trade-off. Confirm your obligations with your own adviser.

What decides the scope of an invoice automation project?

Every project is quoted individually. The main drivers are monthly invoice volume, how many different supplier layouts you receive, how many companies or accounting files are involved, multi-currency handling, the number of approval steps, and any custom coding rules. Separate running costs, such as n8n hosting or a plan, AI model usage and your accounting subscription, are paid to those vendors and change over time. For tool choice see our n8n and Zapier comparison, and for pricing models the n8n and Make pricing guide.

Website Prism's founder has 8+ years behind them and 800+ projects delivered, mostly on Fiverr, and Website Prism Ltd was incorporated in 2026; that is general build experience, not a claim about invoice projects specifically. To discuss your set-up, see AI automation with n8n or contact us.