Check Supplier Invoice Prices Before Creating Xero Bills

To check a supplier invoice against agreed prices, match each line to the right purchasing record. Check the supplier, item, unit of measure, currency and applicable agreement. In the workflow below, differences or missing evidence go to a named reviewer before a Xero draft is created. Your team still decides whether to approve and pay the bill.

This becomes harder when the invoice arrives as a PDF but the purchase order and agreed prices live in an inventory system, purchasing application or spreadsheet. Reading the PDF gives you the supplier's figures. You also need the records that establish what your business agreed to buy.

Start by mapping those records and the decisions people make today. You may be able to improve an existing Xero or purchasing workflow. A custom integration deserves consideration only after you can identify the gap it would need to fill.

The records needed for a meaningful price check

A total that looks reasonable can hide a difference on one line. Match the supplier and purchase first, then compare the line details on the same basis.

For each source, establish who maintains it, how you can read it and when it was last updated. A weekly export may be suitable for a weekly process. It cannot establish the current state of a purchase amended after that export.

Agree how to handle tax-inclusive versus tax-exclusive values, discounts, delivery charges and rounding before comparing totals. Your finance team should define the treatment for its own records. An unexplained difference should remain visible for review.

A fictional invoice with a price difference

This example is invented to show the decision process. It is not a client result or a claim about savings.

A supplier sends invoice INV-2048 for 120 individual units of item PACK-01. The purchasing system holds approved order PO-318. Both records use EUR, exclude tax and have no discounts or delivery charges in this example. The applicable agreed price is €10 per unit.

The invoice is €120 higher than this purchasing record, a 10% price difference. That is a discrepancy to investigate. It does not yet establish an overcharge: perhaps an approved price change has not reached the record being checked.

The review entry should show the invoice, the order, both prices, the calculated difference, the source's update time and the person responsible for investigating. A clear reason might read: "Unit price €11.00; agreed order price €10.00. Review the €120.00 difference."

The reviewer can confirm a valid amendment, seek a corrected invoice or leave the item on hold while evidence is collected. Record that decision and check the updated records again. Keep the original supplier document; do not silently rewrite its amount to make it match.

If your policy also requires a receipt check, perform it separately. The prices can match while the delivered quantity remains unresolved.

Decide what happens when the records disagree

Define the routine path and the exceptions before choosing software. A practical starting point is:

• The required checks pass: prepare an unapproved Xero draft, retaining the supplier document and a reference to the checks performed.
• A value differs: hold it for the person authorised to resolve that kind of difference. Show the actual and expected values.
• Evidence is missing or unclear: identify the missing order, unreadable line or stale export. Request the evidence needed to continue.
• The invoice appears to have been processed already: investigate the existing record before creating another bill.

Your team should set any price tolerance explicitly. A small difference may be legitimate rounding in one workflow and a contractual issue in another. Record who agreed the rule, what it covers and when it changes. A tolerance should not turn missing evidence into a match.

Also decide who covers an absent reviewer, how unresolved items are found and what happens when a source system is unavailable. If a transfer times out, check whether a draft was created before retrying. Otherwise a temporary connection problem can become a duplicate bill.

Test these requirements with representative examples before connecting live records. Confirm which checks and exception paths your chosen product or integration supports.

Check what your existing products already support

If your purchase orders already live in Xero, examine its current purchase-order-to-bill workflow first. Xero's 17 June 2026 update confirms that creating a bill from a purchase order records a link and history references between the transactions.

Established apps also support matching. For example, ApprovalMax documents bill-to-purchase-order matching for approved orders with the same supplier and currency, when the feature is enabled. Check the matching behaviour, subscription and configuration against your requirements. Ask whether it can compare your external price records and apply your particular line-level rules.

Bring a small set of representative invoices to a product review: an ordinary match, a price change, a partial delivery, a missing order and a possible duplicate. Ask the product provider or your advisor to show how each is handled, including the state of the bill created in Xero.

Compare the ongoing burden of maintaining a custom connection with the alternatives. Include who will look after it when a supplier changes its invoice layout or the purchasing system changes. Reducing repetitive work is useful; the records still need to support the decision.

A draft bill is separate from approval and payment

People sometimes use "posting to Xero" to mean any transfer into the system. Be precise about the destination and status you want.

Xero distinguishes draft bills from bills awaiting approval or payment. Its bill approval instructions explain how a draft is approved. Saving a draft does not complete approval or make a payment.

In the proposed workflow, the integration produces an unapproved draft bill or an exception awaiting review. Your authorised team approves bills and controls payment. Check the configuration of any product you evaluate, because another workflow may use different states or approval rules.

Prepare a useful first discussion

You do not need a complete technical specification. Start with the names of the systems, approximate invoice volume, who checks invoices and a description of the recurring exceptions. Establish where the agreed prices live and whether a reliable export or supported connection is available.