Practice systems
Nookal Xero integration: what a daily total hides
Nookal syncs one way into Xero. A practice sends individual invoices, or one daily summary invoice carrying the day's takings as a total per payment method. The summary mode sends no invoice level detail, so a funder deposit covering several days has nothing in Xero to match against and the reconciliation is rebuilt from the funder's own report.
Key facts
- Direction
- One way, stated by the vendor: data recorded in Xero is not transmitted to Nookal1
- What triggers it
- A frequency chosen at setup. A weekly setting syncs the week as one amount per payment method rather than seven daily takings1
- The two modes
- Invoices, which sends every invoice and entry in the date range, or daily takings, which sends only the total processed for each payment method1
- Account mapping
- A default sales account and bank account on the connection, an optional bank account per payment method, and accounting codes on items in invoice mode1
- Tracking categories
- Not mentioned in the Nookal Xero articles. A Xero App Store review reports they do not work with daily summaries and reach one category rather than two7
- Reference on a daily total
- Reported blank by the same review, so a day's total carries nothing to match on later7
- Bulk deposit handling
- Not described. Daily takings sends one total per payment method, and overpayments and account credit sit outside that amount2
- Listed on the Xero App Store
- Added in 2019, carrying one review when the listing was read7
What the Nookal sync sends to Xero
Nookal's own integration page makes two claims and stops. Invoices raised in Nookal go across to Xero on their own, and Xero is updated when a client pays. Neither sentence names the direction plainly and neither mentions daily takings. The help centre carries both, and says the direction outright.
This integration is one way which means data recorded in Xero will not be transmitted to Nookal. Recording information in Xero and Nookal may lead to synchronisation errors or duplication.1
The help centre article is the one to read. It names the two synchronisation types, warns that recording the same information in both systems leads to duplication, and walks through the setup: which locations sync, which type, how often, and which Xero accounts receive it.
The frequency is a dropdown, not an event. Set it to the end of each week and the week arrives in Xero as one amount per payment method rather than as seven daily takings. What it sends on that frequency is a choice the practice made at setup.
Two modes, and the one that changes month end
The vendor names the two synchronisation types and the difference between them. Invoices sends all invoices and entries added during the date range, payments and adjustments included. Daily takings sends only the total amount processed for each payment method in that range.
| Mode | What Xero receives | What the Xero file can still answer |
|---|---|---|
| Individual invoices | One Xero invoice per Nookal invoice, with a payment against it | Which patient, which service and which payer sits behind a line |
| One daily summary invoice | One total per payment method per day | The day's takings by payment method, and nothing underneath it |
| Either mode, when the funder pays | Nothing about the deposit itself | Only what the funder's own report says |
The mode also decides how far the revenue can be split. In invoice mode an accounting code on a service, class, pass or inventory item sends that item to its own Xero sales account, and the code has to match a sales account id in Xero or the sync fails. Daily takings has no item to hang a code on, so a day of revenue arrives against the default sales account. Both modes leave the same job on the desk: a funder pays a lump covering several days and several patients, and neither has told Xero which claims are inside it.
Where Nookal sits against the other systems
Ten practice systems were read on the same six columns on one day. Nookal sits mid range on direction and near the thin end on depth: one way, a default sales account with a bank account per payment method, tracking categories unmentioned, and bulk deposits handled as totals per payment method rather than as a breakdown.
| Direction | What triggers a sync | Account mapping | Tracking categories | Bulk deposit handling | Cost | |
|---|---|---|---|---|---|---|
| Cliniko | One way, into Xero | Invoice on creation, payment when it is allocated | Default sales account plus overrides by billable item, product and practitioner | Not supported | One payment across many invoices becomes many separate Xero payments | Included in every plan |
| Zanda | A manual batch export into Xero, with a Beta import of reconciled payments coming back | The user exports invoices, then exports payments | One sales account, or the calendar mapped to sales accounts | Up to two, pre-assigned per batch | Payments export to a clearing account, then a receive money entry clears it | Included in every plan |
| Halaxy | Continuous, one way by default, with two way syncing of invoice payments as an option | Automatic | Revenue by fee category, expenses by expense category, payments by payment method | Not mentioned in the Xero articles | One batched payout a day on the bank feed, with each invoice syncing on its own | Platform free, integration cost not stated |
| Splose | Two way | Invoice syncs when a payment is applied or the invoice is sent | Default accounts plus an account on every invoice item line | Locations and practitioners | Reconcile the lump sum in Xero first, then mark the claim upload finalised | Included in the per practitioner price |
| Nookal | One way, stated by the vendor | Invoices, or daily takings totals, on a chosen frequency | A default sales account and bank account, a bank account per payment method, and item level accounting codes in invoice mode | Not mentioned in the Xero articles | One total per payment method per period, excluding overpayments and account credit | Included |
| coreplus | One way | Daily | One revenue account and one bank account | Not mentioned in the Xero articles | Not described | Included |
| PracSuite | One way | Daily totals per payment method, raised as Xero invoices | Defaults plus overrides by business, payment method, schedule and item code | One category, chosen under the Businesses heading and applied to the invoices and payments the sync creates | Built for settlement reconciliation, with provider numbers on the scheme totals | Included |
| Bp Allied | Export report | Manual | One deposit bank account on the connection, plus sales accounts mapped from the Category field | One required, carrying the practitioner, with 100 options given as the vendor's own ceiling | Not described | Included |
| Gensolve | Export with journal posting templates | Manual | Journal templates, which must balance | Not stated | Journal based | Included |
| Jane App | None, there is no native Xero integration | Only through a generic automation tool | None | None | None | Not applicable |
The useful comparison is not which product is better. It is where the splitting of a lump sum happens. PracSuite splits a Medicare or DVA payment per practitioner before it reaches Xero and puts the provider number in the payment description. Cliniko does not split it and sends one Xero payment per invoice. A Nookal daily summary sends a total, and leaves the splitting to whoever opens the bank feed.
The questions one total a day cannot answer
This is the part a setup guide has no reason to cover. Once a day of takings is one line per payment method, a set of ordinary month end questions stops having an answer inside Xero at all.
- Which claims are inside this deposit. A health fund settles a day of claims as one credit, and the total in Xero was built on a different boundary.
- Why the deposit came in short. A declined claim, a claiming fee, or a gap payment taken in the room all move the credit, and none of them is visible in a payment method total.
- Which practitioner or which site earned it. Locations on one connection come together in Xero rather than splitting across sales or bank accounts, so revenue by site means a connection per location, and revenue by clinician is not a dimension the sync carries.
- Which tax treatment the revenue carried. A report written for an insurer and a consultation are both takings, and once they are one payment method total the difference has left the Xero file.
- What a debtor owes. A summary invoice is not the patient's invoice, so the Xero debtors list stops being the record of who has not paid.
Why the daily takings sync stops matching the banking report
Nookal publishes an article named for exactly this question, and it names three causes. All three are about timing: something moved after the total had already gone across, or never went across at all.
- A paid invoice, a paid item or a payment deleted or voided after the sync stays inside the Xero total, because the amount had already been sent. The payments report then reads smaller than Xero.
- A backdated payment posts to Xero on the day it was recorded in Nookal, not the day it was backdated to, so the banking report and the Xero figure disagree on both dates.
- Overpayment and account credit are not synced as part of the daily takings amount, which is why the payments report lands closer to the Xero total than the banking report does.
Tracking categories and the daily summary
The Nookal Xero articles do not mention tracking categories, so the comparison record reads not mentioned rather than not supported. The one public account of them comes from a practice that tried, left as a review on the Xero App Store listing.
Also the tracking codes do not work with daily summaries and appear to work for only one Category not for 2. Example Code1 for Location (Practice 1, practice 2) and Code2 for Profession (Physio, Massage, Exercise)7
Read closely that says two things. Tracking is reported not to travel with a daily summary at all, and where it does travel it is reported to reach one category rather than two. A practice that wants revenue by site and by profession is asking for two dimensions, which is the case the review says did not hold for them.
A blank reference on a day's total
The same reviewer asks for the reference field on daily transactions to be populated rather than left blank, and gives his own example of an EFT total for a day with an item count in it. The request looks cosmetic and is not.
A blank reference is what makes a total unmatchable later. Three months on, a bookkeeper looking at a line in Xero has the amount, the date and the payment method, and no string tying it back to the takings report it came from. The tie has to be rebuilt from the practice system each time somebody asks, and it is rebuilt by hand.
Why reconciling in Xero changes nothing in Nookal
The vendor states it plainly: data recorded in Xero is not transmitted to Nookal. The practitioners describing this integration describe the same one way street.
Nookal and Xero do not communicate properly.... if I mark an invoice off as paid in Nookal, I still have to go into Xero and reconcile.8
That is the shape of a one way sync seen from the user's side. Nookal stays the system of record for what was billed and what was paid, and Xero sits downstream of it. A correction belongs in Nookal first, because a correction made in Xero has no path back and the vendor warns that recording in both leads to duplication.
The pattern that puts one bank line back
None of this is a fault in Nookal, and switching sync mode does not resolve it. The mismatch is between a system that reports a day and a funder that pays a batch. Cliniko's reconciliation article points at the fix for the same problem: payments land in a clearing account, and the bank deposit is matched against that account rather than against a pile of invoices. The canonical allied health template goes one step further and gives each funder its own clearing account.
The two legs are stated separately, because they answer different questions. Revenue is posted when the service is billed and carries its own tax treatment. The settlement leg sits in the clearing account at BAS excluded until the money lands, which is how every clearing component in that template posts, and the account falls back towards nil once the deposit has been matched.
Where Ledger Map fits a Nookal practice
There is no Nookal connector. What there is is the drop zone: the takings export, the funder remittance or payment report and a bank statement export are read there, the rows are matched to what was billed, and the deposit is posted as one balanced document set against the funder's clearing account. That leaves one exact match in the bank feed. It does not auto reconcile, and nothing posts that the practice has not approved.
The accounts and tax rates come from a standing map the practice approves once, drawn from a canonical template rather than chosen by the software. A line the map cannot resolve becomes a question with the options laid out, not a silent posting. You can read the shape of it on how it works.
Which mode a Nookal practice runs changes what the drop zone has to read, not what it produces. Individual invoices hand the matcher line level detail to work from. A daily summary hands it a total, and the funder's own report supplies the rest.
Questions
Why is the Xero daily takings sync not matching the Nookal banking report?
Nookal names three causes. A paid invoice, item or payment voided or deleted after the sync stays inside the Xero total, because the amount had already been sent. A backdated payment posts to Xero on the day it was recorded in Nookal, not the day it was backdated to. Overpayment and account credit are not synced as part of the daily takings amount.
What is the difference between invoices and daily takings in Nookal?
Invoices sends every invoice and entry added in the date range, adjustments and payments included, so the Xero file keeps patient and service detail and item accounting codes can split revenue across sales accounts. Daily takings sends only the total processed for each payment method, so the file is tidy and the detail stays in Nookal. Neither tells Xero which claims sit inside a funder deposit.
Can Nookal split revenue by location or practitioner in Xero?
By location, through a connection per location: the locations selected on one connection come together in Xero rather than splitting across sales or bank accounts, and different locations can be synced to different Xero accounts. By practitioner, no documented route. Tracking categories are not mentioned in the Xero articles, so the sync is not stated to carry them either way, and a Xero App Store review reports they do not work with daily summaries and reach one category rather than two.
Does reconciling in Xero mark the invoice as paid in Nookal?
No. Nookal states the integration is one way, so data recorded in Xero is not transmitted back, and it warns that recording the same information in both leads to synchronisation errors or duplication. A practice manager reviewing the product describes marking an invoice paid in Nookal and still having to go into Xero to reconcile. Corrections belong in Nookal first.
How do you match a funder deposit when Nookal sends one daily total?
From the funder's own paperwork rather than from the total. The remittance or payment report names the claims inside the lump, the bank line gives the amount and the date, and those claims are closed into a clearing account on the funder's paid date. The bank feed then has one line to match against one record.
Read next
- Practice systemsPracSuite Xero sync: daily totals per payment type
- Practice systemsCliniko Xero integration: what syncs, what does not
- Practice systemscoreplus Xero sync: one account for all revenue
- Practice systemsBp Allied and Xero: a manual export, one bank account
- Practice systemsHalaxy Xero integration: sync, fees, duplicates
- Practice systemsSplose Xero integration and the NDIS lump sum
- HubPractice systems
Sources
Open questions
- How a funder deposit covering several days is presented to Xero is not described by the vendor in either mode, so the pattern below is drawn from the funder's own report rather than from anything Nookal states.
- Tracking categories are not mentioned in Nookal's Xero articles. Whether the sync can write to one is unstated rather than ruled out, and the only public account of trying is a single Xero App Store review.
- Whether refunds reach Xero at all in daily takings mode is not documented, so neither answer is stated here as fact.
- Whether the blank reference on a daily transaction is a setting or a fixed behaviour is not documented. The one public account of it is the same App Store review.
- Why is Xero Daily Takings Sync Not Matching Nookal Banking Report?
Nookal. Retrieved 4 Sep 2026. Source updated 2 Apr 2024.
primary
- Can Certain Items be Sent to Specific Sales Accounts in Xero?
Nookal. Retrieved 4 Sep 2026. Source updated 22 Aug 2024.
primary
- Can Xero Synchronise Specific Locations Only?
Nookal. Retrieved 4 Sep 2026. Source updated 25 May 2026.
primary
- Reconcile in Xero when using the Cliniko integration
Cliniko. Retrieved 3 Sep 2026. Source updated 28 Jul 2026.
primary
Review
Last reviewed 4 Sep 2026 by Shane
General information for Australian allied health practices, not tax advice. Confirm a treatment with your BAS agent or accountant before you post it.
Guided onboarding
Run one real month before you go live.
Sign up, connect Zanda and Xero, and replay a month you already closed. The map is reviewed with whoever owns the books, and nothing posts until you approve it.
Every practice starts from a template. Nothing posts until the map is approved.