How to Automate Invoices with the Xero API

Manual invoicing is one of the most reliably solvable inefficiencies in a business. The information needed to create an invoice — who the customer is, what they bought, how much it cost, what tax applies — already exists somewhere in your systems. The work of opening Xero, creating an invoice, entering that data and sending it is pure overhead. The Xero API makes it possible to automate that entirely: the order is placed, the event fires, the invoice is created in Xero with the correct data, and the customer receives it — without anyone touching anything.

How automated Xero invoice creation works

The integration connects an event in your system to the Xero invoice creation API. The event could be anything that should generate an invoice: an order placed on your ecommerce platform, a subscription payment confirmed, a job marked complete in your project management system, a contract signed in your CRM, a timesheet approved in your time-tracking tool.

When the event fires, the integration retrieves the relevant data — customer details, line items, amounts, tax treatment — and makes a POST request to the Xero API’s invoices endpoint. Xero creates the invoice and returns a confirmation including the Xero invoice ID, which the integration stores against the original record for future reference (payments, updates, void operations).

The invoice arrives in Xero in the correct status for your workflow. If invoices need approval before sending, they’re created in Draft or Submitted status for review. If they should go straight to the customer, they’re created in Authorised status and Xero can send them automatically using its own email templates.

Getting tax right

Tax handling is where invoice automation either works correctly or creates accounting problems. The common mistakes — hardcoding tax rates, assuming all products are standard rated, not handling exempt or zero-rated items — produce invoices that look right but have incorrect VAT. Fixing incorrect VAT on Xero invoices after the fact is tedious; preventing it from the start is the job of the integration.

A properly built Xero invoice integration retrieves the tax rates configured in the connected Xero organisation at startup and maps your platform’s products to the correct Xero tax codes. Standard rated products map to the 20% VAT rate. Zero rated products map to zero rate. Services sold outside the UK map to the appropriate no-supply or reverse charge rate. The mapping is explicit and configurable — not guessed.

For businesses with complex tax requirements — partial exemption, mixed supplies, distance selling to EU customers — the tax mapping is a key part of the scoping conversation. Getting it wrong in an automated system at volume creates compliance problems. Getting it right means every invoice is correct from the moment it’s created.

Line item structure and account mapping

Every Xero invoice line item needs to specify the account code it posts to in the chart of accounts. An order containing a physical product, a digital product and a shipping charge might need to post to three different accounts: product sales, digital sales and delivery income. The integration maps each line item type to the correct Xero account automatically.

Account codes differ between Xero organisations. An integration that hardcodes account code “200” works for one organisation and fails for another. A well-built integration retrieves the accounts from the connected organisation and uses account names or a configurable mapping rather than hardcoded codes — making it portable across different Xero setups.

Tracking categories — Xero’s system for departmental or cost centre reporting — can also be applied to invoice lines automatically. If your platform knows which department or project an order relates to, that context can be passed to Xero and applied to the invoice line, keeping management reporting accurate without any manual coding.

Handling the invoice lifecycle

Invoice automation isn’t just creation. A complete integration handles the full invoice lifecycle.

Updates. If an order is amended after the invoice is created — a quantity changed, a line item added, a discount applied — the integration updates the existing Xero invoice rather than creating a new one. Updating is straightforward for invoices in Draft or Submitted status. Authorised invoices require voiding and recreating, or creating a credit note and a new invoice, depending on your accounting requirements.

Payments. When a payment is received — through Stripe, GoCardless, bank transfer or any other channel — the integration applies the payment to the Xero invoice automatically. The invoice moves from Awaiting Payment to Paid status in Xero without manual reconciliation. See Xero and Stripe integration for how this works with Stripe specifically.

Credit notes. Refunds generate credit notes in Xero automatically, applied against the original invoice. The credit note references the original invoice, keeps the audit trail clean, and adjusts VAT correctly.

Voids. Cancelled orders void the corresponding Xero invoice automatically, keeping Xero’s outstanding invoice list accurate without manual cleanup.

Duplicate prevention

One of the most important requirements for automated invoice creation is idempotency — ensuring the same invoice isn’t created twice if the event fires more than once. A webhook retry mechanism, a system restart after a failure, or a manual re-sync can all cause events to fire twice. Without idempotency handling, each duplicate event creates a duplicate invoice in Xero.

The standard approach is to store the Xero invoice ID against the originating record in your system. Before creating an invoice, check whether a Xero invoice ID already exists for that record. If it does, skip creation (or update if the order has changed). If it doesn’t, create the invoice and store the returned ID. This check adds one database query per event but prevents a category of error that’s time-consuming to clean up.

For the full Xero integration service and pricing, see the Xero API integration service. For the complete guide to how the Xero API works, see Xero API integration guide. For WooCommerce invoice automation specifically, see Xero WooCommerce integration. For what the build costs, see the Xero API integration cost guide.

Related posts

• Xero API integration: a complete guide
• Xero and Stripe integration: automating payment reconciliation
• Xero WooCommerce integration: how it works
• Xero API integration cost

Batch invoice creation for high-volume platforms

For platforms processing high transaction volumes — ecommerce sites with hundreds of daily orders, subscription platforms with large customer bases — real-time per-event invoice creation can run into Xero’s rate limits. Xero allows 60 API calls per minute per organisation. A spike of 200 orders in one minute would exhaust that limit immediately if each order triggered an immediate API call.

The solution is a queued batch approach. Orders are added to a processing queue as they arrive. A background job processes the queue at a controlled rate — up to 60 items per minute — creating invoices in Xero as fast as the rate limits allow. During normal volume, the queue clears quickly. During spikes, it absorbs the burst and processes everything without errors. The queue also provides resilience — if Xero is temporarily unavailable, records stay in the queue and are processed when the connection recovers.

Xero also supports batch invoice creation through a single API call with multiple invoices in the payload, which is more efficient than one call per invoice for bulk operations like end-of-day reconciliation runs.

Error handling and visibility

Automated invoice creation will encounter errors in production. The most common: Xero validation errors when an invoice payload has incorrect data; rate limit errors during high-volume periods; network timeouts; token expiry. Each needs a defined handler.

Validation errors should log the full Xero error response alongside the invoice payload that caused it, flag the record for manual review and send an alert. This makes it fast to diagnose what went wrong and fix the underlying data issue. Network timeouts and rate limit errors should trigger automatic retries with backoff. Token expiry should trigger the token refresh flow and re-queue the failed request.

A dashboard or admin page that shows sync status — last run time, records processed, errors flagged, queue depth — gives whoever manages the integration visibility into what’s happening without needing to read logs. For business-critical invoice sync, this kind of visibility is worth building from the start rather than adding later when something goes wrong.

If you need help with a custom API integration for your website or business application, I can help. I build bespoke API integrations for UK businesses. See API integration pricing or get in touch to discuss your project.