PracSuite Xero sync: daily totals per payment type

PracSuite does not push a patient invoice into Xero. It summarises the payments entered in PracSuite and sends the summary, and the vendor is direct about the trade: payments are synced to Xero as daily totals per payment method, and individual invoices are not mirrored. Sync a single date and Xero receives one invoice for cash, one for EFTPOS, one for bank transfer, and so on for every method that took money that day.

That is a deliberate design rather than a missing feature, and it is the opposite choice to the one Cliniko makes. Pushing every invoice gives Xero the detail and leaves the bookkeeper with hundreds of payments no bank line matches. Pushing daily totals gives Xero something that looks like a bank statement and takes the patient level detail away. Which one is easier depends entirely on who pays the practice.

One sentence in the vendor documentation explains why PracSuite reads as the most settlement aware of the native integrations: Medicare payments are automatically separated per provider to best match how payments appear on bank statements, and DVA works the same way. Services Australia pays per payee provider number, so a per provider total is a total that can meet a bank line.

The consolidation toggles do the same job for cards and funds. Split credit card totals by card type and the Xero side lines up with a merchant statement that settles Visa and Mastercard separately. Split health fund totals by entry method and terminal claims stop being mixed with claims lodged online. That does not remove the matching work. It does make the matching possible.

This is the part no vendor page addresses. The daily total is built from the payments entered in PracSuite on that date. A scheme deposit does not arrive on that date. Medicare bulk bill pays a run of claims days after they were lodged, and NDIS agency managed pays a batch days after the bulk payment request went in.

So the Xero invoice and the bank line are dated differently and grouped differently. One deposit can cover claims receipted across several days, and one day's total can hold claims that three separate deposits will eventually pay. If the payment account on the connection is the real bank account, those totals land in an account whose statement does not show them. If it is a clearing account, they wait there until the deposit arrives, which is the whole reason the pattern exists.

PracSuite uploads a payment total for each day per payment method, and it uploads on payments received rather than all revenue billed in a period. For a practice reporting on a cash basis that is the right answer and the story ends there. For an accrual practice the vendor documents a monthly routine.

Steps three and four are the ones to read twice. A practice on accrual is stripping and re-adding GST on synced transactions every month, which is a fair amount of exposure for a step only one help article describes.

A clearing account per settlement source turns a daily total from a problem into a queue. The pattern is not unusual and it is not a Ledger Map idea: SimpleClinic documents the same thing for its own users, a BAS excluded current asset account that holds transactions before they are allocated to other accounts in Xero, with a bank rule per merchant and per HICAPS settlement line.

Read on the same six columns as the other nine practice systems, PracSuite is at the thick end of the range: overrides at four levels below the default, per provider scheme totals, and consolidation toggles built for how money actually settles. Bp Allied is at the thin end, with a manual export and one bank account on the connection. Zanda sits between them, with a documented clearing account pattern behind a manual batch export.