A Xero or MYOB integration connects the software that raises your invoices and takes your payments — job system, online store, CRM or point of sale — to the books your bookkeeper keeps, so each invoice, payment and contact is entered once and arrives there on its own. Ozwebnet writes these connections from scratch in Adelaide, South Australia, for businesses across Australia. You receive the source code with the IP assigned to you, for one fixed quote set in writing and staged against milestones.
DETAIL OF SHEET 07 — SYSTEMS INTEGRATION →
It moves the records that end up in your books anyway. When a job is invoiced in your job system, the invoice is raised in Xero or MYOB with the right contact, account code and tax code. When a customer pays in your store or at the counter, the payment is recorded against that invoice. When a new customer is added anywhere, one contact is matched or created, never a duplicate. Xero or MYOB stays the ledger your bookkeeper works in; what stops is the re-keying, the month-end import and the hunt for which invoice a payment belongs to.
Each record type is given one home — invoices raised in the job system, payments taken at the counter or in the store, contacts owned by the CRM — and one direction of travel into or out of Xero or MYOB, agreed before anything is connected.
Every invoice line that reaches the ledger lands on the account code, GST tax code and tracking category or job your bookkeeper expects, from a mapping table you can read and change yourself.
A customer or supplier added in either system is looked up by ABN, name and email before it is created, so Xero or MYOB keeps one contact per business rather than one per spelling.
An invoice approved in your job, sales or store system is created in the ledger the moment it is issued — lines, due date and contact included — and its ledger number written back, so both systems agree on which invoice is which.
A payment taken in the store, at the counter or through your payment gateway is recorded against its invoice in Xero or MYOB, so the debtors list is right without anyone matching receipts by hand.
When the two systems disagree — an invoice edited in both, a contact with two ABNs, a payment with no invoice — the record waits in a list with the reason for a person to decide, and nothing is written over. Every record that moved, and every one that did not, is logged as it happens.
The connection is switched on from an agreed date, with the invoices and contacts already in the ledger matched first, so nothing is raised twice and the month closes the way your bookkeeper is used to.
TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.
Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.
One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.
SEE THE FIVE STAGES ANIMATED →We sit with whoever raises the invoices and whoever keeps the books, and list every record that moves between your systems and Xero or MYOB today, by hand or by import.
The record map, the account and tax code mapping and the rule for every mismatch are specified in writing; the fixed quote is set here, staged against milestones.
Connected one record type at a time — contacts, then invoices, then payments — against a test ledger rather than your live books; each milestone ends with records arriving in Xero or MYOB on their own.
Real invoices, payments and contacts are run through the connection and checked line by line against the ledger, with your bookkeeper, before it touches the live books.
The connection goes live from an agreed date, and you receive the source code with the IP assigned to you.
Yes, if the system lets other software read and write its records — which simPRO, ServiceM8, Cin7, HubSpot, most online store platforms and most points of sale do, as does anything we wrote for you. Which records move, and in which direction, is listed at Survey and set in the record map before the quote.
No. Xero or MYOB stays the ledger, and your bookkeeper keeps working in it as before. What changes is that invoices, payments and contacts arrive already entered, on the account and tax codes they expect, and the month-end import goes away.
It waits. An invoice edited in both systems, a contact with two ABNs or a payment with no invoice is held in a list with the reason, for a person to decide, and nothing is written over. Every record that moved, and every one that did not, is logged as it happens.
One fixed quote, set in writing before the build and staged against milestones. It is set after Survey, so it covers the systems and record types you actually move, and the source code is delivered with the IP assigned to you at handover.
Yes, Australia-wide. The survey, the build and the cut-over can all be done remotely, and Xero and MYOB are connected to over the internet, wherever in Australia your office is.
Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.
