Direct answer
Use a native app from the Xero App Store when one exists for your other tool and it handles your invoices the way you raise them. Use Zapier or Make for one or two simple steps the app doesn't cover. Pay for a custom integration when line items, part-payments, currencies or exceptions need rules that someone on your team currently applies by hand.
Whichever you choose, decide first which system owns each piece of information. Re-keying usually starts with two systems that both think they hold the customer, the job or the price.
Who this is for
Owners and office managers who type the same job, customer or invoice details into Xero and another tool: job management, CRM, booking, e-commerce or a spreadsheet. If what you need is Xero's own invoice reminders, start with How to chase unpaid invoices in Xero. If you want to ask Claude or ChatGPT questions about your Xero data, read Connecting Claude or ChatGPT to Xero.
The three options compared
Swipe or scroll to compare the columns.
| Native app (Xero App Store) | Zapier or Make | Custom integration (Xero API) | |
|---|---|---|---|
| Best for | A standard flow your other tool's vendor already supports | One or two simple "when this, do that" steps | Your own rules across several systems |
| Typical example | Finished jobs sent to Xero as draft invoices | A paid invoice in Xero posts a message to the team chat | Accepted quote → deposit invoice → reminder → job released when paid |
| Where it usually stops | When your process differs from the vendor's: fields you can't map, sync in one direction only | A varying number of invoice lines, finding the right contact, retries without duplicates, part-payments and credit notes | When nobody owns it after launch |
| Who keeps it working | The app's vendor | Whoever built it, often you | You, your developer, or a support plan |
| Typical cost | The app's subscription, sometimes included in your other tool's plan | A plan priced by monthly task or credit volume, plus setup time | A build fee plus upkeep; see "What it costs" below |
| Time to set up | Hours to days | Hours to days | One to six weeks |
Three questions that decide it
Does a native app already do it? Search the Xero App Store for your other tool first. If an app syncs the records you need, in the direction you need, and your team can live with how it maps the fields, stop there. You pay a subscription, and the vendor keeps it working when either product changes.
How many steps, and how many exceptions? Zapier and Make are good at "when this happens, do that". Zapier's Xero integration, for example, can start a Zap when a sales invoice is created, updated or goes overdue, and can create an invoice, find a contact or add items to an existing invoice. It gets fiddly when one event needs a varying number of invoice lines, a lookup to find the right contact, or a different path for part-payments and credit notes. If you've ever searched "zapier xero multiple line items", you've met the usual sticking point.
What happens when it fails? Every integration fails sometimes: a contact doesn't match, a call to Xero times out, or a bulk sync runs into Xero's daily API call limit. A custom integration should come with an exception queue, retries that don't create duplicates, and an alert to a named person. If nobody would notice a failed sync for a week, plan for that before you plan the build.
What it costs
A native app costs its subscription. Zapier and Make charge by plan and monthly volume. As of October 2026, Zapier's free plan includes 100 tasks a month and only two-step Zaps (one trigger, one action), and its paid plans add multi-step Zaps (Zapier's pricing page). Make bills in credits: most actions use one credit, and its free plan includes 1,000 credits a month (Make's pricing page). Count how many invoices, contacts and payments you'd push through in a busy month before you pick a plan.
A custom build also has a Xero side. Xero's developer pricing, in force since 2 March 2026, has a free Starter tier limited to five connections and 1,000 API calls per organisation per day; paid tiers raise both limits and are priced in Australian dollars on Xero's developer pricing page. A small business connecting its own Xero organisation will usually fit in Starter, but check before you commission anything that syncs in bulk.
For the build itself, published UK prices vary. Generativ, a UK consultancy, publishes £3,000–£5,000 excl. VAT for a single contained process and £8,000–£10,000 for a multi-system workflow (its own pricing guide, dated 28 September 2026). Our Pilot, at £15,000 excl. VAT, covers one workflow across up to three systems, including exception paths, an audit trail, documentation, handover and a 30-day defect period. The cost guide lists more published prices. If a native app or a few hours in Zapier does the job, that is the better buy.
Worked example: from accepted quote to paid deposit
This example is our PaxBespoke project, and it doesn't run on Xero. PaxBespoke makes bespoke wardrobes, and its accounts side uses QuickBooks, with deposit invoices raised through PayPal. We include it because the shape is the same whichever accounts software sits at the end, and it shows where the rules live.
- A customer books a consultation in Calendly. The booking, or a cancellation or reschedule, updates the customer's record in Monday.com.
- The team measures each room and agrees the price. A person approves the proposal before it goes anywhere.
- The approved proposal goes to the customer for e-signature.
- When the signed document comes back, a rule works out the 40% deposit from the approved price and creates the deposit invoice.
- After a set window, the workflow checks whether the deposit has been paid and applies the business's rule for holding a provisional date.
- Reminders go out by stage (consultation, quotation, signature, deposit), and each one is recorded so no customer gets two at once.
No generative AI is involved. The deposit, the stage changes and the reminder timing are all fixed rules, and n8n runs them between the services. People own measurements, prices, exceptions and any conversation outside the reminder sequence. The PaxBespoke case study describes the system; it publishes no measured results.
To do the same with Xero, step 4 would create the invoice in Xero, and step 5 would read the payment back from Xero. The hard parts don't change: matching the right contact, keeping one owner for the price, and deciding what happens when a payment only covers part of the deposit.
Before you commission a custom build: a ten-point checklist
Write down an answer to each of these. Any you can't answer is a question for the scoping call, not for the developer to guess.
- System of record per field: for the customer, the job, the price and the invoice status, which system wins when two disagree?
- Identifiers: what links a record in your other tool to the contact and invoice in Xero? A name is not an identifier; an account number or ID is.
- Line items: how many lines does a typical invoice have, and where does each line's description, quantity and price come from?
- Tax codes: which VAT rates and account codes apply to which items, and who sets them?
- Currencies: do you invoice in more than one currency? Multi-currency is only on Xero's Comprehensive and Ultimate plans in the UK (Xero's UK pricing page, October 2026).
- Part-payments: what happens when a customer pays half? Does the job still go ahead?
- Credit notes and refunds: who raises them, and should they flow back to the other system?
- Who gets the alert: when a sync fails or a record doesn't match, which named person hears about it, and how?
- The manual fallback: if the integration is down for a day, how does the team keep working, and how do you catch up without duplicates?
- Who maintains it: who changes it when Xero, your other tool or your prices change, and what does that cost each year?
If most of your answers are "the vendor's app already does that", you don't need a custom build. If several are "it depends, and only one person knows", that knowledge is what the integration has to capture.
Sources and dates
Checked 24 October 2026: Zapier's Xero integration page and pricing page; Make's pricing page; Xero's developer pricing page and remote MCP FAQ (API limits per organisation); Xero's UK pricing page (plan features); Generativ's AI integration cost guide (dated 28 September 2026). Prices and plan limits change, so check the source page before you rely on a figure.
