Reconcile WorkCover and CTP Payments for Allied Health

To reconcile WorkCover and CTP claim payments for an allied-health clinic in Australia, extract the claim number, patient or worker name, service date, item code, invoice number, billed amount, paid amount, rejection reason, and EFT reference from each payment notice. Match those rows to the clinic invoice register, then investigate short-paid or rejected lines against the relevant state fee schedule, approval record, and portal payment status.

Workers compensation and CTP are different payer streams, but both produce claim-based payment notices or remittance advice that must be matched back to the invoice the clinic originally raised.

A clean reconciliation row usually needs more than the bank amount. Build the match around scheme identifiers, the invoice number, service details, billed and paid amounts, exception reason, approval status, EFT reference, and the ledger or customer account where the revenue should land.

This is a bookkeeping workflow, not legal advice about scheme entitlements. Scheme portals, fee schedules, and provider guidance remain the source for rule changes.

Map each claim to the right scheme, portal, and code family

Before matching dollars, identify the scheme that paid them. The payer determines the portal record, the code family, the approval evidence, and the fee schedule you will use to explain a mismatch.

In NSW, a clinic may be working through icare and SIRA requirements, including claim references, approval details, and SIRA payment classification codes. Do not match an icare payment only by patient name and service date; the claim reference and payment classification code should agree with the invoice register.

For Victoria, separate WorkSafe worker claims from TAC CTP claims. WorkSafe matching usually turns on the claim, service details, and item code; TAC matching uses the client claim, TAC item number, and any HICAPS Digital or TAC invoicing record.

For Queensland, keep WorkCover claims separate from MAIC CTP work because the portal status fields and document language differ. The same clinic may treat both workers compensation and motor accident clients, but the document vocabulary is not interchangeable.

For other state, territory, and federal schemes, apply the same rule: identify the payer first, then match against the identifiers that scheme actually recognises.

Build an invoice register that can survive scheme differences

The invoice register is the control point. If the clinic records only invoice number, patient name, and total, reconciliation becomes guesswork as soon as a payment notice uses a scheme code or approval reference that is missing from the billing record.

At a minimum, keep columns for invoice number, claimant or worker/client name, claim number, payer or scheme, date of service, practitioner, item code or payment classification code, billed amount, approval reference, approval expiry, treatment-plan status, and submission channel. For clinics posting by case, include the matter ledger, customer account, or claim ledger that receives the revenue.

Approval status belongs in the finance workflow, not only in clinical admin. Missing approval, an expired treatment plan, or a session cap can turn into a short-paid or rejected line even when the service was delivered and invoiced correctly. Allied Health Treatment and Recovery Plan (AHTRP) status, approval-before-service evidence, and provider portal notes should be visible before the next invoice is sent, not discovered only after the payment fails.

Preserve the original billed amount and code. If the payment notice later shows a different paid amount, a different item description, or a rejection reason, that difference is the evidence you need to identify a fee-schedule issue, code mismatch, or approval problem. The same register should then reconcile into Xero, MYOB, or the practice-management export without replacing the original billing facts.

Extract payment notice rows before you start matching

The extraction step should produce one row per claim line, not one row per PDF or one total per remittance. A payment notice total is useful for agreeing to the bank deposit, but the clinic still needs line-level detail to explain which invoice was paid, short-paid, rejected, or left open.

For each payment notice or remittance advice, extract the claim number, patient or worker/client name, service date, item code or payment classification code, invoice number, billed amount, paid amount, rejected amount, rejection reason, EFT reference, source file, and page number. If the original invoice PDF is available, extract the same identifiers from that file as well so the notice row and invoice row can be compared side by side.

A practical prompt for this workflow asks for one row per claim payment line, with the identifiers, amounts, rejection detail, EFT reference, source file, and page number kept explicit. With invoice data extraction for claim payment notices, the clinic can upload payment notices, remittance PDFs, and related invoice PDFs, describe the fields it needs in plain language, and export the results to Excel, CSV, or JSON.

That structured output does not decide whether the scheme was right to reject or short-pay a line. It gives the bookkeeper the rows needed to match against the invoice register, check the relevant portal record, and preserve a source-file reference for review.

Investigate short-paid and rejected lines by failure mode

Treat every mismatch as a failure mode until the evidence says otherwise. A short-paid or rejected row might come from an obsolete item code, a fee-schedule transition, expired or missing approval, a session or treatment-plan limit, an unaccepted claim, an invoice date before the service date, a missing claim number, duplicate resubmission, or a provider/practitioner identifier mismatch.

Fee-schedule transitions deserve special attention because the invoice can look correct under the clinic's old billing setup and still fail against the current scheme rules. TAC Victoria says its new physiotherapy fee schedule applies to services delivered to TAC clients across Australia from 1 February 2026, with updated item codes and rates; providers using old item codes may receive outside service definition date remittance advice and need to resubmit with the new codes, according to the TAC 1 February 2026 physiotherapy fee schedule.

For a short-paid line, start with the invoice row and compare the code, duration or quantity, and amount against the current schedule, fees order, or gazetted rate. Then check the portal payment status and approval record. If the code and amount are right but the approval expired, the next action is different from a simple rate correction. If the claim has not been accepted or the provider identifier is wrong, resubmitting the same invoice may only create another rejection.

SIRA payment classification code reconciliation works the same way in principle: the classification code on the invoice, the scheme record, and the payment notice need to describe the same service. When they do not, record the exception reason before deciding whether to amend, resubmit, query the scheme, or write off the balance.

Reconcile one bulk EFT back to many claim lines

A bulk EFT is not reconciled when the bank feed total is coded to income. One deposit may cover several claimants, multiple invoice numbers, and payment notices that appeared in a portal on a different day from the bank transaction.

Start with the bank deposit and collect every related notice, portal remittance line, or practice-management payment report. Total the notice lines by EFT reference, settlement date, or payer batch reference, then compare that total to the bank amount. Once the deposit agrees to the remittance total, match each claim line back to the invoice register by claim number, service date, item code, invoice number, and amount.

Unmatched lines should stay visible. A paid line with no invoice match may be using a different claim identifier or patient spelling from the practice-management system. An invoice row with no payment line may be unpaid, rejected, delayed, or included in a different batch. A payment line with a lower paid amount belongs in the exception list rather than being posted silently as a discount.

Keep WorkCover and CTP deposits separate from other allied-health AR streams even when the same clinic reconciles them in the same week. HICAPS terminal settlements have their own deposit pattern, so clinics should separately reconcile HICAPS daily settlement reports. Medicare and DVA also have their own remittance logic; use a separate workflow to reconcile Medicare bulk-bill and DVA rebates. Plan-managed NDIS remittances belong in a separate NDIS remittance advice extraction workflow as well.

Once a claim line is matched, post the paid amount to the right customer, matter ledger, claim ledger, or clearing account. Keep rejected and short-paid rows in a review queue with the scheme, invoice number, claim number, exception reason, and next action. Do not bury them in a general debtor balance where the approval or code issue will be hard to reconstruct later.

The evidence trail should be boring and complete: original invoice, payment notice or remittance advice, portal status export or screenshot where used, extracted row, matching notes, resubmission or query outcome, and the final accounting entry.