Get your store, job system or custom app posting to Xero correctly, so the payouts reconcile and nobody retypes an order.
If someone in your business copies online orders, bookings or job invoices into Xero by hand, or a connector is doing it for you and the books still won't match the bank, that is the work we do. CodeDrips is a Melbourne software studio. We build Xero integrations, we repair the ones that leave the accounts slightly wrong, and we'll tell you when an off-the-shelf connector is all you need.
What we build around Xero
- Shopify and WooCommerce to Xero: online sales landing in Xero the way your bookkeeper wants them, as individual invoices or as summaries, with GST, shipping, discounts, refunds and gift cards each treated consistently. We work on both Shopify and WooCommerce stores.
- Job and booking systems to Xero: a finished job or a paid booking becomes an invoice in Xero, and the payment status comes back so your team can see who has paid without opening the accounts.
- Custom apps that raise invoices: if you run a portal, a quoting tool or a piece of custom software, there is no ready-made connector for it. We connect it to Xero through Xero's API, using rules written for your business.
- Payment gateway payouts that reconcile: card sales, fees and refunds recorded so each payout in your bank feed has a matching entry waiting for it.
- Repairing a setup that doesn't reconcile: duplicates, wrong tax codes, rounding differences, refunds that never reached Xero. We find where the numbers drift and fix the cause.
When a connector is the right answer
Often it is. Shopify, WooCommerce and most established booking and job management products already have a Xero connector, built by the platform or by a third party. If your sales are reasonably standard and the connector summarises them in a way your bookkeeper is happy with, a custom integration would be money spent for nothing. The useful work in that case is choosing the connector, setting up its account and tax mapping with care, and testing it with a week of real orders, awkward ones included.
Custom work earns its cost in a few situations:
- Your website or app is custom, so no connector exists for it.
- Your rules don't fit a connector's assumptions: trade customers on account alongside retail, deposits and part payments, staged invoices, or sales split by location or product line.
- Several systems feed the same Xero file and need to land consistently.
- You have enough volume that small errors add up to real hours every month.
Our guide to Xero integrations for websites and stores goes through that decision in more detail. If a connector will do the job, we'll say so.
Payments and reconciliation
Most Xero integration trouble is really payment trouble. When a customer pays by card, the money doesn't reach your bank as that one sale. The payment gateway collects many payments, takes its fees, deducts any refunds and pays you a net lump sum later. Xero's bank feed shows the lump sum. Your sales show the individual orders. If the integration marks each invoice as paid straight into the bank account, nothing will ever match.
The pattern we usually set up, with your bookkeeper's agreement, is a clearing account for each gateway. Sales are paid into it, fees and refunds are recorded against it, and each payout moves the net amount across to the bank. Done properly, the clearing account returns to zero after each payout and reconciling becomes a quick check.
We build the payment side as well as the accounting side. See our Stripe integration work for checkout, subscriptions and invoicing, or read our comparison of Stripe, Square and Tyro for Australian sites if you haven't settled on a gateway yet. For trades and service businesses, booking and payment integrations for trades covers getting from booking to paid invoice.
How we scope the work
- Start with your bookkeeper. How should sales appear? Which contacts matter? How are payouts, fees and refunds recorded, and which lines carry different GST treatment? Their answers are most of the specification.
- Review what's there. We look at the store or system, any connector already installed, and what is actually landing in Xero, then tell you whether you need a settings fix, a different connector or something custom.
- Pick one owner for each record. Data flows one way wherever possible, and each Xero record carries a reference back to the original order or job so nothing can be posted twice.
- Test the awkward cases. Mixed GST orders, discounts, partial refunds, gift cards, part payments and edited orders, checked by the person who does your books before anything goes live.
- Make failures visible. A readable log, and an alert to a person when a record doesn't go through. An integration should never fail quietly.
What it costs
Work starts from $500. That covers small jobs such as reviewing a setup that won't reconcile, or correcting the mapping on a connector you already have. A custom integration is scoped and quoted individually. In our website cost guide we put a typical integration at $2,000 to $8,000, depending on the quality of the other system's API and how deep the connection goes.
We're developers, not accountants. Your bookkeeper or accountant makes the calls on how things should be recorded, and we make the systems do it reliably.
Related integration work
Xero is rarely the only system involved. Our API development and integration page covers CRMs, email platforms and the rest, and our guide to API integrations for business explains the approach in plain terms.
Tell us what should land in Xero.
Tell us what you run, what should reach Xero and where the numbers drift. Work starts from $500, and a senior developer will reply within one business day.
Xero integration questions
Work starts from $500, which covers small jobs such as reviewing a setup that won't reconcile or correcting the mapping on an existing connector. A custom integration is quoted individually. Our published website cost guide puts a typical integration at $2,000 to $8,000 depending on its depth.
For a standard online store or an established booking product, a well-configured connector is usually the right answer and we'll tell you so. Custom work makes sense when your system is custom, when your invoicing rules don't fit a connector's assumptions, or when several systems need to post to the same Xero file.
Yes. We look at the store, the connector and what is landing in Xero, find where the numbers drift, and fix the cause. That is commonly duplicates, tax mapping, rounding, or refunds and fees that were never recorded against the payout.
Yes. If the product already has a Xero connector, we start there and check it handles your deposits, part payments and refunds. If your system is custom or the connector can't express your rules, we build the connection through Xero's API.
Yes, and we prefer to. They decide how sales, fees, refunds and GST should be recorded, and those decisions become the specification. We're developers, not accountants, so nothing we say is accounting or tax advice.
The approach is the same for any gateway that pays out in batches. Each gateway gets its own clearing account, with sales, fees and refunds recorded against it so the payout in your bank feed matches. We also build the payment side, including custom Stripe checkouts and invoicing.
Yes. Our studio is in Carlton and we work with businesses across Australia. Integration work rarely needs anyone in the same room.
Books and bank not agreeing?
Talk to us directly. No commitment required.