coreplus Xero sync: one account for all revenue

coreplus connects to Xero from the practice side and pushes in one direction. The help centre is blunt about it: any changes made in your Xero account will not sync back to coreplus. So Xero is the reporting end of the pipe, and a correction belongs in coreplus first.

That is the whole mapping surface: one revenue account, one bank account, one tax setting. Everything the practice bills, and every funder that pays for it, arrives in Xero wearing the same coat.

A practice owner's first question at month end is usually the same one: how much of last month came from each funder. With one revenue account, Xero cannot answer it. Medicare, the private health fund benefit, the plan manager and the corporate contract all land in the same line, and the split has to be rebuilt from the practice system instead.

This is not a coreplus quirk. Cliniko documents no tracking category support either. The difference is depth: Cliniko, Splose and PracSuite each let a billable item, an invoice line or a payment method carry its own account, so the chart of accounts can hold the funder split. coreplus documents one account for the lot.

Plan management revenue, support coordination revenue, and direct provider revenue all sit in one ledger account, hiding margin by service line.¹²

That is a firm of accountants describing what they find in provider files. Their fix is a chart of accounts structured by service line, so each stream can be seen on its own.

The coreplus setting names two Xero tax rates by their Xero names, so it helps to know what each one moves.

The consequences run in both directions. Treatment revenue coded as taxable means the practice hands the Australian Taxation Office one eleventh of money it did not collect, and getting it back means amending a lodged statement. Taxable reports or supervision coded GST free means the GST was not remitted, and collecting it from the payer months later is rarely practical. Revenue coded BAS Excluded leaves total sales understated.

The mapping from these rate names to the activity statement labels comes from Xero Central, which refused an automated read, so it sits in the open questions below.

coreplus publishes a list of sync errors. Three of them are the mapping talking, and they are worth knowing before a month of invoices piles up behind them.

One more is worth knowing about: after a sync has failed ten times it stops trying, and a manual resync has to be requested. Nothing on the coreplus side shouts about it, so a quiet Xero is not proof that invoices are arriving.

The usual answer to reporting by funder is a Xero tracking category. It does not survive contact with an allied health practice. Xero allows two active tracking categories, and both are normally spent on practitioner and location, which are the two cuts a practice owner asks for by name. Funder has nowhere left to go except the account code.

That is why the canonical templates build the chart of accounts around funding source, and why a sync that reaches one revenue account limits what Xero can report, whatever the practice system holds. Tracking categories are not mentioned in any of the four coreplus Xero articles, so whether the sync could carry them is an open question rather than a stated gap.

Ledger Map does not connect to coreplus today, and this page is not going to pretend otherwise. What it does have is the part that is missing above: one standing map for the practice, approved before anything posts, that says which account and which Xero tax rate each funding source and service category takes, with the reason written on the row.

For a coreplus practice that means the drop zone. The reports and remittances you already download go in, the map decides where each line posts, and each deposit becomes one balanced document set that leaves one exact match in the bank feed. Anything the map cannot resolve becomes a question with the options laid out, rather than a silent posting. See how it works for the shape of it.