Xero bill approvals

Xero accounts payable automation can start with the bill tools you already have. Use Xero's capture, draft bills, permissions and duplicate flags first. Add an approval app when bills need a review sequence those settings cannot cover. Consider a custom workflow when the missing step sits outside Xero, such as checking a completed job or finding who can approve a supplier's work.

For a service business, the useful starting point is one supplier bill from arrival through reconciliation. Write down where staff stop to ask a question, copy a value or chase an approver. That shows which part needs a connection and which part needs a person to decide.

We checked Xero's US bill tools, accounts payable automation guide, Invoices API and OAuth overview on November 3, 2026. The product facts below come from those pages. The proposed approval queue is a design example, with no claimed client result.

Xero's US page documents uploading files or forwarding bills from email. Its document capture extracts details into draft bills for approval. It also describes user roles for creating and approving bills, automatic duplicate flags, bill statuses, planned payment dates and repeating bills.

Test those features with the documents your suppliers actually send. A clear PDF, a revised bill and an email with several attachments may need different handling. Capture gives someone a draft to check; it does not establish that the work was ordered, delivered or priced correctly.

Check your own plan and region before choosing a payment method or assuming every feature is available. The US page describes several payment routes, including exporting a payment file to online banking. A custom approval queue should fit the route your business uses, with payment release kept as a separate authorized step.

Choose an existing approval app when it covers the process with less upkeep than custom code. Ask for a demonstration using an edited bill, an absent approver and a disputed charge. A feature list that says "approvals" does not tell you whether an amount change invalidates an earlier decision.

Our Xero integration page covers authorized accounting data and organization boundaries. The broader accounting firm workflow guide places bill processing alongside document collection, close and reporting.

Xero's Invoices API handles both sales invoices and purchase bills. Its documentation makes a distinction worth checking in any integration: the invoice number for a purchase bill is non-unique. The Xero-generated invoice ID is unique within its organization.

That means a supplier's invoice number alone cannot be your duplicate safeguard. For the workflow we would build, each intake item would retain the authorized Xero organization, supplier match, source document reference, invoice number, dates, currency, amount and the returned Xero bill ID once created.

Before creating a draft, compare the candidate with existing intake items and relevant Xero bills. Matching supplier, number, amount and date can flag a suspect; it should not silently erase a revised bill or assume two legitimate recurring charges are the same. A reviewer needs the original documents and the reason for the flag.

Keep a durable link from the intake item to the bill ID. If creation times out, reconcile the attempted write before creating another draft. A network error can leave the result unknown even when Xero accepted the request. The webhook idempotency guide explains the wider retry problem.

Consider a property-management business receiving a contractor's maintenance bill. This is an illustrative workflow, not a delivered engagement or a claim about a particular property platform.

1. 1Receive the bill through the agreed intake channel and retain its source document.
2. 2Match the supplier and property or job reference. Hold ambiguous matches for staff.
3. 3Compare the charge with the work order and completion evidence available through an authorized connection.
4. 4Prepare a Xero draft and link it to the intake item. Flag missing evidence or possible duplicates before routing approval.
5. 5Show the reviewer the document, job evidence, amount, currency, coding and any exception. Record the decision against that version of the bill.
6. 6Put an approved bill into the business's payment-preparation process. Require the separate authority and checks for releasing payment.
7. 7Read back the accounting result and reconcile it with the payment evidence. Keep an unresolved mismatch assigned to someone.

A completed work order can support review. It cannot prove that an extra charge was agreed. If the bill includes work outside the order, send the difference to the responsible manager with the supporting detail.

The connection also needs an answer for a deleted or missing job reference. An empty lookup should leave the bill waiting for evidence, with a visible reason. It should never be interpreted as confirmation that the work is complete.

Define who may approve each bill using the business's actual authority rules. Include amount, currency, department or property, and a substitute when the usual person is away. An overdue approval should escalate to an authorized substitute; the passage of time should not approve the bill.

Bind the decision to the fields the reviewer saw. If the supplier, amount, currency, bank destination or supporting document changes, hold the item and request the relevant review again. Preserve the earlier decision as history rather than carrying it onto different payment instructions.

Keep these actions separately controlled:

• Creating a new supplier or changing supplier bank details.
• Approving that a bill is valid and correctly coded.
• Overriding a duplicate or evidence exception.
• Preparing a payment batch.
• Releasing money through the chosen payment provider or bank.

The same employee may hold more than one role in a small business, but the software should still record which action they authorized. A draft created by an integration is not evidence of approval. A bill marked paid in an accounting system also needs the appropriate payment and reconciliation evidence before the workflow closes.

Our finance approval guide goes deeper into bank changes, payment release and ledger write-backs.

Give each held bill a reason, an owner and the next action. Useful reasons include an unreadable attachment, uncertain supplier, possible duplicate, missing purchase evidence, disputed amount, absent approver, failed connection or unmatched payment.

The reviewer should be able to open the bill and its evidence from that list. Avoid copying supplier financial details into a general chat alert. A notice can say that review is required and link to the restricted record.

If AI reads a bill or summarizes a supplier email, treat the extracted fields as proposals. Check totals, required references and the supplier match before creating the draft. Tax treatment and unusual coding go to the bookkeeper. Our invoice OCR guide covers document extraction; this approval workflow still has to decide what happens after extraction.

Use Xero's supported authorization rather than asking staff to share their login. Its OAuth documentation describes consent to specific scopes and one or more tenants. Select the permissions needed for the agreed operations and carry the organization identity through each lookup and write.

An accounting firm processing bills for several clients needs explicit access to each organization. A supplier with the same name in two clients' books must not cause a cross-client match. Keep documents, bill IDs and approval history within the correct client's access boundary.

When authorization expires or a required system is unavailable, leave the work pending and alert its owner. The queue should distinguish a connection failure from a bill rejected by the reviewer.

Run a limited set of bills through the proposed process with staff comparing the results. Include a repeated email attachment, a corrected bill with the same supplier number, two suppliers sharing a number, a missing job reference, a changed amount after approval and an approver on leave.

Also interrupt a draft creation, revoke the test connection and check a payment that cannot yet be matched. Confirm that each case either completes with readback or remains visibly held. For ordinary bills, check the source attachment, Xero organization, bill ID and approval history together.

Measure your starting process and the pilot separately: time waiting for approval, manual touches, duplicate suspects and unresolved payment matches. Use your own results to decide whether the extra software earns its running cost.

If Xero's native tools cover capture and a single reviewer handles exceptions comfortably, keep that setup. A new app or integration should address a repeated handoff you can name.

We build systems integrations and workflow automation around those handoffs. For a free automation audit, describe where bills arrive, which tools hold purchase evidence, who approves them and how payment is released. Include approximate volume and an anonymized exception; leave supplier bank details and private documents out of the initial message.