Allied health financial workflow

HICAPS, Halaxy and Xero: Follow the Claim All the Way to the Bank

Connecting HICAPS Digital to Halaxy is only one part of the job. The claim, invoice, payment, Xero record and bank deposit still need to form one financial story that your practice can follow and reconcile.

The short version: Halaxy records the service, invoice and claim workflow. HICAPS Digital communicates with the supported funding scheme. Xero records the accounting result. The bank confirms what money actually arrived. A successful connection does not remove the need for correct setup and review.
HICAPS Digital, Halaxy and Xero workflow for allied health practices

Do not treat them as one system

HICAPS, Halaxy and Xero have different jobs

The integration becomes easier to understand when each system is given a clear responsibility.

HICAPS Digital

Handles the supported digital claim pathway between the practice and the relevant scheme. It provides claim status and payment information for that claiming process.

Halaxy

Holds the operational story: the client, practitioner, appointment, service, invoice, claim and payment application. It is where practice activity is connected to the amount owing.

Xero

Holds the accounting story: invoices and payments sent from Halaxy, account classifications, bank-feed activity and the final reconciliation used for financial reporting.

The goal is not three identical screens. The goal is a traceable path in which the claim and payment can be followed from the service in Halaxy, through HICAPS Digital, into Xero and finally to the bank.

Current Halaxy scope

Which HICAPS claims can Halaxy process?

HICAPS offers several products and integration pathways. The connection documented by Halaxy is HICAPS Digital Claims, formerly LanternPay. Halaxy currently documents this connection for:

  • agency-managed NDIS claims;
  • Transport Accident Commission (TAC) claims; and
  • WorkSafe Victoria claims for supported disciplines and services.

For NDIS, Halaxy states that HICAPS Digital Claims supports agency-managed claims. Plan-managed and self-managed claims are not supported through this connection. Activation with HICAPS Digital and the relevant eligibility requirements still apply.

Do not confuse HICAPS Digital with every HICAPS service. A general HICAPS capability list may mention private health, Medicare, DVA or other schemes. That does not mean every capability is available through the Halaxy connection. Confirm the current Halaxy integration, scheme and practitioner eligibility before designing the practice workflow.

Official setup and eligibility information changes over time. Check the current Halaxy HICAPS Digital Claims guide and HICAPS requirements before activating claiming.

The complete transaction path

From consultation to Xero reconciliation

The integration does not begin with the bank deposit. It begins with the practice activity that created the amount owing.

1Halaxy

The correct service is recorded

The practitioner, client, payer, fee and service details need to reflect what actually occurred. Incorrect information at this stage can flow into the invoice and claim.

2Halaxy

The invoice is created

Billing turns the delivered service into an amount owing. The invoice should identify the correct payer, fee, practitioner and any information required for the claim.

3Halaxy to HICAPS Digital

The claim is submitted from the invoice

For an eligible connection, the claim is initiated from Halaxy and passed to HICAPS Digital. A connection existing in Settings does not prove every invoice is claim-ready; the underlying details still matter.

4HICAPS Digital

The claim is assessed and its status returned

The claim may be accepted, rejected, held or require further action. Rejected and unresolved claims should remain visible rather than being treated as expected cash.

5HICAPS Digital to Halaxy

Payment information updates the practice record

Halaxy states that claims processed through its HICAPS Digital connection appear in the HICAPS practitioner portal and payments are usually received in the nominated account the next business day. Confirm the payment and status for the actual claim.

6Halaxy to Xero

The relevant invoice and payment data syncs

With the Halaxy–Xero connection configured, Halaxy invoices and payments can be replicated in Xero. Which records sync, their status and the accounts used depend on the chosen Xero sync preferences.

7Bank to Xero

The bank deposit appears

The bank feed shows the money that reached the nominated bank account. Its date or amount may not mirror one individual invoice if timing, batching or adjustments are involved.

8Xero

The accounting record is reconciled

Only after the Xero record and bank activity exist can the bookkeeper match them and confirm that the deposit is properly explained.

Paid, synced and reconciled are not synonyms. “Paid” describes the invoice or claim status. “Synced” describes information moving between systems. “Reconciled” confirms that the Xero accounting record agrees with bank activity.

Connection design

Set the HICAPS connection at the right level

Halaxy allows a HICAPS Digital Claims connection to be applied at group, clinic or individual-practitioner level. This is not simply an administrative choice. It affects which practitioners can use the account and where payments are processed.

Connection levelHow Halaxy describes itFinancial question to answer
GroupPractitioners in the group use the same HICAPS Digital account, with payments processed to one account.Is the group genuinely operating through the same entity and nominated bank account?
ClinicThe connection applies to selected practice locations and can support different biller accounts and payment destinations.Do clinic locations use different entities, provider arrangements or bank accounts?
IndividualThe connection applies to a particular practitioner, at selected locations or across their locations.Is the practitioner receiving the income personally or through a separate business arrangement?

Before authorising the connection, document which legal entity earns the income, which provider makes the claim, who owns the receivable and which bank account should receive settlement. If these do not align, the software may work technically while the accounting remains wrong.

The accounting hand-off

How the Halaxy–Xero settings affect HICAPS transactions

HICAPS Digital does not replace the Halaxy–Xero setup. Halaxy remains the operational source sending invoices and payments into the accounting file.

Connection level

Match the Xero organisation to the same group, clinic or practitioner structure used by the practice. Do not send one entity’s income into another entity’s Xero file.

Sync starting date

Choose the date deliberately. Turning on pre-existing transaction sync without a cut-over plan can create duplicates or push old, unresolved records into Xero.

Which invoices sync

Halaxy can sync all invoices or only invoices with a payment. Unpaid invoices may sync to Draft, Awaiting Approval or Awaiting Payment depending on preferences.

Revenue mapping

Map Halaxy fee categories to appropriate Xero revenue or liability accounts. Defaulting everything to one account can hide meaningful reporting differences.

Payment mapping

Halaxy can route invoice payments to selected Bank-type accounts based on payment method. The destination should support the actual settlement and reconciliation process.

Invoice numbers

Enable invoice-number syncing where it will help identify payments and reconcile batched deposits. An amount alone is weak evidence where many services share the same fee.

Patient privacy

Halaxy offers a setting to hide patient names in the accounting package and use an HX identifier. Choose the privacy approach deliberately and restrict access appropriately.

One-way or two-way sync

Halaxy describes the default as one-way from Halaxy to Xero, with optional two-way payment syncing. Decide which system owns each change before staff start editing in both.

Do not manually “fix” both systems at once. Halaxy warns that manually editing an invoice or payment in Xero can break the link to the Halaxy record. First identify where the error began, understand the sync status, then correct it in a controlled order.

Where the story is tested

Reconciling HICAPS-related payments in Xero

Bank reconciliation should be the last confirmation—not the first guess. By the time the deposit reaches Xero, the practice should be able to explain the payer, claim, invoice, payment date, amount and account mapping.

  1. Confirm the claim status in Halaxy and HICAPS Digital. Do not assume submission means approval or payment.
  2. Confirm the correct Halaxy invoice was updated. A payment against the wrong invoice can make one account look settled and another remain overdue.
  3. Open the Halaxy Xero sync history. Check whether the invoice and payment synced successfully and review any error message.
  4. Find the matching record in Xero. Use the invoice reference, payment date, payer and amount—not the amount alone.
  5. Compare the nominated settlement account. Confirm the money arrived in the bank account expected from the HICAPS connection.
  6. Investigate timing or grouping differences. A settlement date may differ from the service or claim date. Several items may need to explain one deposit.
  7. Reconcile only when the complete amount is explained. Do not create an unrelated transaction merely to make the bank-feed line disappear.

When a clearing account is useful

A correctly designed clearing account can hold payments between the point they are recorded and the point the bank settlement arrives. It can be useful when individual payments in Halaxy or Xero need to be matched against a combined settlement.

However, a clearing account is a control account, not a dumping ground. Its balance should represent identifiable transactions still moving through the process. An old balance means something has not cleared and needs investigation.

If the deposit does not match

  • check for multiple claims grouped into the deposit;
  • check whether the payment was directed to a different practitioner or clinic bank account;
  • check claim and settlement dates;
  • check rejected, adjusted or partially paid claims;
  • check for duplicate or missing payments in Halaxy;
  • check Xero sync history and payment-account mapping; and
  • check whether someone manually changed the Xero invoice or payment.

Controls that prevent clean-ups

What the practice should review regularly

Daily or frequent

  • rejected and held claims;
  • unidentified receipts;
  • payments applied to the wrong invoice;
  • sync errors; and
  • unexpected settlement accounts.

Weekly

  • outstanding HICAPS-related invoices;
  • claims awaiting action;
  • payments recorded but not banked;
  • clearing-account movements; and
  • unreconciled deposits.

Monthly

  • Halaxy outstanding invoices against Xero receivables;
  • old clearing-account balances;
  • revenue-account mapping;
  • duplicate contacts or invoices; and
  • differences between practice and accounting reports.

Whenever the practice changes

  • new practitioner setup;
  • new clinic or entity;
  • changed bank account;
  • new fee categories; and
  • changed claiming eligibility or funding arrangements.

Common failure points

Why a technically connected workflow can still be wrong

  • The wrong scope was assumed. Staff treat every HICAPS product or scheme as available through Halaxy.
  • The connection level does not match the business structure. Group, clinic and practitioner income is sent to the wrong bank or Xero organisation.
  • The invoice is wrong before the claim begins. The payer, fee, practitioner or service details do not reflect the real transaction.
  • Expected income is treated as received. A submitted or approved claim is marked paid before settlement is properly evidenced.
  • Old transactions are synced during setup. A poorly planned start date creates duplicate or historical records in Xero.
  • Payments go to an unexplained account. Xero mapping does not match the settlement path.
  • Staff edit Xero without understanding the link. The Halaxy–Xero relationship breaks and later changes no longer flow as expected.
  • The bank feed is forced to reconcile. A clearing difference or missing payment is hidden instead of resolved.

Frequently asked questions

HICAPS, Halaxy and Xero FAQs

Does Halaxy integrate directly with HICAPS?

Halaxy documents an integration with HICAPS Digital Claims, formerly LanternPay. The connection is added in Halaxy under Settings and Integrations, then authorised through the HICAPS Digital login.

Which HICAPS Digital claims can I process through Halaxy?

Halaxy currently documents HICAPS Digital Claims support for agency-managed NDIS, TAC and WorkSafe Victoria, subject to activation, discipline and other eligibility requirements. Check the current Halaxy and HICAPS documentation before relying on a scheme being available.

Can I process private health claims through the Halaxy HICAPS Digital connection?

Do not assume so. HICAPS offers different integration pathways, but HICAPS lists Halaxy as a HICAPS Digital partner for TAC, WorkSafe Victoria and NDIS. A HICAPS terminal and private health claiming are separate capabilities and should be confirmed directly for the practice software and setup.

Does a HICAPS payment go straight into Xero?

The accounting path is generally understood through Halaxy. The claim and payment relate to the Halaxy invoice, and the Halaxy–Xero connection sends the relevant invoice and payment records according to the chosen sync preferences. The bank feed separately brings the actual deposit into Xero for reconciliation.

Does “paid” in Halaxy mean the bank transaction is reconciled?

No. Paid is an invoice or payment status. Reconciliation occurs in Xero after the accounting record can be matched to the bank activity. The payment can be recorded in Halaxy and synced to Xero while the bank deposit is still waiting to arrive or be reconciled.

Why is the HICAPS deposit not matching the Xero payment?

Possible causes include timing differences, grouped settlements, partial or adjusted claims, incorrect bank-account mapping, a payment applied to the wrong invoice, a sync error or manual changes in Xero. Follow the item backwards from the bank to Xero, Halaxy and the claim rather than guessing.

Should HICAPS payments go through a Xero clearing account?

That depends on how individual payments and bank settlements appear. A clearing account can be useful where several accounting payments must be matched to a combined deposit, but it needs a documented clearing process. The account should not retain unexplained old balances.

Should I turn on two-way syncing between Halaxy and Xero?

Only after deciding which system will own payment changes and training staff accordingly. Halaxy describes the default sync as one-way from Halaxy to Xero, while the optional two-way setting can allow payments added or assigned in Xero to update Halaxy.

What happens if someone edits a synced invoice in Xero?

Halaxy warns that manually editing a Xero invoice or payment may break the link between the records. Paid Xero invoices also become locked. Review the sync history and understand the correct correction sequence before changing either system.

Can My Great Bookkeeper help fix an existing HICAPS–Halaxy–Xero workflow?

Yes. We can follow claims and payments through Halaxy and Xero, review account mapping, investigate clearing balances and identify where the accounting story stopped matching the bank. HICAPS or Halaxy technical support may still be required for product activation or platform faults.

Continue the workflow

Related Halaxy guides

When the systems disagree

Do not force the reconciliation. Follow the transaction.

If HICAPS, Halaxy, Xero and the bank are telling different stories, the problem may have started with the invoice, claim, payment, sync settings or account mapping. We work through the complete path and find where it stopped making sense.

đŸ„• Talk to a Halaxy bookkeeper đŸ„• Book a free consultation