Does Bp Allied sync with Xero automatically?

No. The vendor documents a Xero connection made inside Bp Allied and an export report that a person runs. There is no documented schedule and no documented event that pushes an invoice as it is raised, which is why the Xero file can look current and be weeks behind.

Can Bp Allied send to more than one Xero bank account?

No. The vendor states that only one bank account can be used, and it is the account payments are saved into. Revenue is a different question: a Category on each product or service maps to its own Xero Sales Code, so income splits during the export even though the money does not. Split the money afterwards, with a clearing account per funder.

How do you reconcile a HICAPS or Medicare deposit from a Bp Allied export?

The deposit is reconciled from the funder's own paperwork, not from the export. The remittance or payment report gives the claims inside the lump, the bank line gives the amount and date, and the invoices are closed into a clearing account on the funder's paid date so the single bank line matches one record instead of dozens.

Does the Bp Allied export carry tracking categories?

It requires one. The export creates a Practitioner tracking category and puts the practitioner who created the invoice on it, which uses one of the two categories Xero allows active at a time. Best Practice Software states that a practice with more than 100 practitioners cannot use the export at all, and reads the figure as a cap. Xero's own set up article puts 100 options per category as a guide for report speed and states four categories with two active as the limits. An invoice covering several practitioners is attributed to the one on the first appointment invoiced.

What should a practice leaving Bp Allied keep for its Xero file?

The invoice and payment history as a file the practice holds, every remittance and fund statement for periods still open, a bank statement export covering the same dates, and a note of which Xero accounts the practice was coding out of the one bank account on the connection.

Practice systems

Bp Allied and Xero: a manual export, one bank account

Bp Allied's Xero link is a manual export report, not a continuous sync. The practice makes a Xero connection from inside Bp Allied and sets one bank account on it. Best Practice Software has set an end of service date of 31 July 2026, so the export is a wind down path rather than a platform to build a month end on.

Key facts

Vendor: Best Practice Software, the publisher of Bp Premier⁶
How data reaches Xero: An export report from a Xero connection made inside Bp Allied¹
What triggers it: A person, each time. No scheduled or event driven sync is documented¹
Account mapping: One deposit bank account on the connection, with sales accounts mapped from the Bp Allied Category field to the Xero Sales Code and tax rates from the item's GST Code²
Bulk deposit handling: Not described in the vendor documentation²
Tracking categories: One is required, and it carries the practitioner on the invoice. Xero allows two, so the export consumes one of them³
What the export carries: Clients as Contacts, Products and Services as Items, then Invoices and Payments, in that order, with refunds and overpayments handled at the payments step²
The ceiling on the export: Best Practice Software states that a practice with more than 100 practitioners cannot use the export, reading 100 options as a hard limit on a Xero tracking category³
What Xero's own article puts at 100: A guide for keeping reports quick rather than a cap. The limits Xero states outright are four tracking categories in an organisation and two of them active at a time⁴
When the integration shipped: With v6, announced by the trade press in Sep 2018⁷
End of service: 31 July 2026, after which the vendor says the product receives no updates, improvements or technical support⁵

What the connection actually is

Bp Allied does not push an invoice into Xero as it is raised. The practice creates a Xero connection from inside Bp Allied, authorises it against one Xero organisation, and sets a single bank account on that connection as the deposit account. From then on the accounting data leaves Bp Allied as an export report somebody runs, in a fixed order: Clients as Xero Contacts, Products and Services as Xero Items, then Invoices, then Payments.

The one bank account is a deposit limit, not a mapping limit. Revenue does split: a Bp Allied Category maps to a Xero Sales Code, so different types of income can be tracked against different accounts, and the item's GST Code sets the tax rate. What arrives in one place is the money. Every payment method and every funder lands in the same bank account, so the split a bank reconciliation needs is made after the export rather than during it.

A manual export is not a sync

The distinction carries more weight than it sounds like it should. A sync has a trigger, a queue and a retry. An export has a person, and a person has a busy week.

Nothing moves until somebody runs it, so a quiet Xero file and a broken connection look the same from the outside.
Editing an invoice after it has gone across is the case Xero itself pushes back on. Zanda's export documentation states the constraint plainly: once payment is applied, no further changes to that invoice are permitted. Bp Allied says the same from the other side: a change made in Bp Allied after the export has to be replicated in Xero by hand.
A record that has crossed carries a Xero identifier written back to it, so choosing New rather than All sends only what has not gone yet. Choosing All re-sends everything and updates names and prices in Xero.
The export is a point in time. A fund or a funder that pays three weeks later is left to whoever reconciles the bank account.
There is a budget on it. Xero allows 5000 API calls a day at one call a second, and Bp Allied sends clients, items, invoices and payments in batches of 50 while spending one call on each payment allocation, so a large first transfer is planned rather than run at 4pm on a Friday.

Where Bp Allied sits against the other systems

Ten practice systems were read on the same six columns on the same day. Bp Allied sits at the thin end of that range: an export report, run by hand, with one deposit bank account, a required tracking category and nothing stated about bulk deposits. PracSuite sits at the thick end, with daily totals per payment method and provider numbers on the scheme totals. Zanda is the closest neighbour, also a manual batch export, but with a documented clearing account pattern behind it.

As at 29 Aug 2026
	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

Plate 1The native practice system to Xero integrations, read on one day. Bp Allied is the eighth row.

The useful comparison is not which product is better. It is how much of month end each one hands back to the bookkeeper. PracSuite hands back the least, Zanda hands back the payments side, and an export report with one bank account hands back nearly all of it.

What the documentation leaves out

Take a bookkeeper's questions to the vendor material and some come back answered, some come back as limits, and the ones about a funder deposit come back empty. That is worth setting out row by row, because a directory listing that says only integrates with Xero reads as an answer when it is not one.

What month end needs, and whether the export answers it²³⁸

What month end needs	In the Bp Allied documentation	Where the answer comes from instead
Revenue split by funder	A Category on each product or service maps to a Xero Sales Code	The export itself, once the categories are set up to match the chart of accounts
Revenue split by practitioner	One required tracking category, carrying the practitioner on the invoice	The export, up to the 100 practitioners the vendor gives as its ceiling
Revenue split by location	Not stated. The tracking category slot the export needs is taken by the practitioner	Journals, or a report outside Xero, or Xero's second tracking category
One bank line per funder deposit	Bulk deposit handling is not described	The funder's remittance, matched by hand or by a tool
Merchant and claiming fees	Not described	The payout or fund statement, coded as its own line
A comparable settlement aware export	Not offered	PracSuite documents daily totals per payment method with provider numbers on the scheme totals

The end of service date changes the question

Best Practice Software's Bp Allied page now leads with a sunset rather than with features. It gives an end of service date of 31 July 2026 and says that from that date the product receives no updates, improvements or technical support, and that associated services conclude. The vendor's home page leads with Bp Premier, Best Health Booking, Best Practice Mobile and Bp Comms, and does not list Bp Allied.

So the question a practice types into a search box is usually the wrong one. How do I set up the Bp Allied Xero integration matters much less than what do I keep when this file stops being maintained. The rest of this page is written for the second question.

One bank account, and one bulk deposit

Allied health money does not arrive one invoice at a time. A health fund settles a day of claims as one credit, Medicare pays a run of claims as one transfer, and a plan manager pays a batch of invoices with one payment. The bank shows one line. The export has produced many payments into the one account the connection points at.

That mismatch is the whole of the work. The bank account inside Xero fills with small payments that do not appear on a statement, the reconcile tab grows, and a deposit that comes in short because whole claims were declined turns into a difference somebody has to explain. None of that is a fault in the export. It is what an export without a clearing account produces.

What month end looks like, and what it could look like

The pattern that keeps the trail intact is a clearing account per funder: the payment is posted against the invoice into the funder's clearing account on the date the funder paid, the bank line is matched as one transfer, and the clearing balance returns to nil once the deposit has landed. In the canonical templates that clearing leg posts as BAS excluded, because the revenue was recognised when the invoice was raised. Bp Allied does not do that on its own, so the second column below is the practice's own chart of accounts doing it.

Plate 2The Xero state one bank account on the connection produces, next to the state a clearing account per funder produces.

What to keep if the practice is moving

A practice leaving a sunsetting system usually loses the reconciliation trail first, because the trail lives in reports rather than in the export. Keeping these makes the Xero file defensible after the practice system is switched off.

The invoice and payment history out of Bp Allied, exported to a file the practice holds rather than left in the product.
Every funder remittance and fund statement for the periods still open, because they are what proves a deposit was split correctly.
A bank statement export covering the same periods, so a deposit can be tied to a date and an amount without the bank feed.
A written note of what the one bank account on the connection was, and which Xero accounts the practice was coding out of it, so the opening balances make sense to whoever looks next.

What Ledger Map does with a Bp Allied practice

There is no Bp Allied connector, and with the end of service date set, none is planned. What there is is the drop zone: the export file, the funder remittance and a bank statement export are read there, the rows are matched to invoices, and the deposit is posted as one balanced document set against the funder's clearing account, which leaves one exact match in the bank feed.

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. Nothing posts until that map is approved, and anything the map cannot resolve becomes a question with the options laid out rather than a silent posting. That is how Ledger Map works whichever system the file came from, which is the useful property when the system it came from is being turned off.

Questions

Does Bp Allied sync with Xero automatically?
No. The vendor documents a Xero connection made inside Bp Allied and an export report that a person runs. There is no documented schedule and no documented event that pushes an invoice as it is raised, which is why the Xero file can look current and be weeks behind.
Can Bp Allied send to more than one Xero bank account?
No. The vendor states that only one bank account can be used, and it is the account payments are saved into. Revenue is a different question: a Category on each product or service maps to its own Xero Sales Code, so income splits during the export even though the money does not. Split the money afterwards, with a clearing account per funder.
Is Bp Allied still supported?
Best Practice Software's own product page gives an end of service date of 31 July 2026 and says that from that date the product receives no updates, improvements or technical support. Bp Allied is also absent from the product list on the vendor's home page as at 3 Sep 2026.
How do you reconcile a HICAPS or Medicare deposit from a Bp Allied export?
The deposit is reconciled from the funder's own paperwork, not from the export. The remittance or payment report gives the claims inside the lump, the bank line gives the amount and date, and the invoices are closed into a clearing account on the funder's paid date so the single bank line matches one record instead of dozens.
Does the Bp Allied export carry tracking categories?
It requires one. The export creates a Practitioner tracking category and puts the practitioner who created the invoice on it, which uses one of the two categories Xero allows active at a time. Best Practice Software states that a practice with more than 100 practitioners cannot use the export at all, and reads the figure as a cap. Xero's own set up article puts 100 options per category as a guide for report speed and states four categories with two active as the limits. An invoice covering several practitioners is attributed to the one on the first appointment invoiced.
What should a practice leaving Bp Allied keep for its Xero file?
The invoice and payment history as a file the practice holds, every remittance and fund statement for periods still open, a bank statement export covering the same dates, and a note of which Xero accounts the practice was coding out of the one bank account on the connection.

Sources

Open questions

The knowledge base pages behind the export no longer answer on their own host, so this page cites Internet Archive captures. The Xero Limitations capture is older than the Set up and Send to Xero one, and whether the API budget it states has since changed cannot be checked at the vendor.
How a funder deposit covering several days reaches Xero is not described in any of the three knowledge base pages, in either direction.
Whether a Bp Allied listing remains in the Xero App Store could not be settled: the search returned a results page with nothing rendered, which may mean a withdrawn listing or a page that does not render for an automated fetch.

Create a Xero connection and set a bank account
Best Practice Software. Retrieved 4 Sep 2026. Source updated 27 Sep 2022.
primary
Set up and Send to Xero
Best Practice Software. Retrieved 4 Sep 2026.
primary
Xero Limitations
Best Practice Software. Retrieved 4 Sep 2026.
primary
Set up tracking categories
Xero Central. Retrieved 4 Sep 2026.
primary
Bp Allied, carrying the end of service notice
Best Practice Software. Retrieved 3 Sep 2026.
primary
Best Practice Software, the current product list
Best Practice Software. Retrieved 3 Sep 2026.
primary
Best Practice launches v6 of Bp Allied with improved private health claiming
Pulse+IT. Retrieved 3 Sep 2026. Source updated 26 Sep 2018.
secondary
Enabling the Xero integration
PracSuite. Retrieved 29 Aug 2026.
primary
Exporting to Xero
Zanda. Retrieved 3 Sep 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.

Start your map

Every practice starts from a template. Nothing posts until the map is approved.