Skip to main content
01 / The problemFor allied-health clinics managing NDIS and insurer payments

Still juggling inboxes, PDFs, Cliniko and Xero just to match insurer payments to the right patient?

Every insurer payment sends your team searching through remittance emails and PDFs, Cliniko records and Xero payment lines to work out where it belongs. When one deposit covers several invoices, the search becomes slower and mistakes become easier to make.
Request a workflow walkthrough

Takes about one minute. No phone number required.

One paymentEvidence arriving from three directions
Source 01

Email / PDF

The insurer's remittance report

Source 02

Cliniko

The clinic invoice record

Source 03

Xero

The accounting context

The payment arrived. The explanation didn’t.

Your team still connects the dots.

There should be one place where the whole payment makes sense.

02 / The solution

Match NDIS and insurer payments without the pain.

Reconexa brings the remittance, invoice details, Cliniko record, and relevant Xero evidence into one workspace—so your team can see what belongs together, handle payments covering multiple invoices, and approve what happens next.

Workflow / 01–03

From remittance to a review-ready match.

Each stage adds context to the same payment instead of starting the search again in another system.

01 / Collect

Collect the payment evidence.

Supported Gmail and Microsoft 365 mailboxes sync on a schedule. Reconexa can process supported email bodies and PDFs, retrieve compatible YourRemittance links, and accept a manual PDF upload when another portal still sits in the way.

Evidence carried forward

  • Email body
  • PDF report
  • Manual upload

02 / Match

Understand and match the payment.

Reconexa creates Remittance Invoices, checks invoice numbers and amounts in Cliniko, finds relevant Xero Bank Statement Lines, and groups multi-invoice deposits into Batch Payments where appropriate.

Evidence carried forward

  • Cliniko invoice
  • Xero evidence
  • Batch Payment

03 / Approve

Approve and complete the work.

Your team reviews or corrects the evidence, confirms Batch Payments, creates the approved Xero output and supporting PDF when ready, records the approved Cliniko payment, and completes bank reconciliation in Xero.

Evidence carried forward

  • Operator review
  • Approved output
  • Visible history

One trail. The clinic keeps the final decision.

Product proof

See the whole payment story as one connected system.

The evidence, match, review state, and operator decision remain visible together—so the layout itself feels like the answer to the fragmented workflow above.

One review surface

The evidence stays attached to the decision.

Remittance details, Cliniko records, and relevant Xero evidence remain visible in the same comparison.

Connected evidence

  • Source remittance and attachments
  • Extracted payer, dates, and amounts
  • Matched Cliniko invoice and status
  • Relevant Xero payment evidence
  • Edits, notes, and review history

The control boundary

Reconexa prepares it. Your team approves it.

Operators review clear and uncertain matches, confirm Batch Payments, approve downstream work, and complete bank reconciliation in Xero.

Batch Payments and exceptions

Because one payment does not always mean one invoice.

Related invoices stay grouped while uncertain, mismatched, or failed work stays visible until someone reviews it.

  • Matched
  • Review
  • Mismatched
  • Failed
03 / Why Reconexa exists

Reconexa began inside a clinic—not on a software whiteboard.

Caroline runs a large physiotherapy clinic. Her team was tracing insurer payments across three separate sources: a PDF report received by email, the invoice record in Cliniko, and the corresponding accounting context in Xero.

That often meant three windows across three monitors just to understand where one payment belonged. Every manual step introduced another opportunity to select the wrong patient, overlook a payment, or spend more administrative time correcting the records.

Pete and Caroline started Reconexa to bring that scattered payment story into one reviewable workflow—reducing the work required to understand each payment while keeping the final decision with the clinic.

Less time tracing payments. Fewer opportunities for human error.

Pete

CEO

Building Reconexa around the operational realities of insurer-payment work.

Caroline

Physiotherapist and clinic operator

Bringing first-hand experience of clinic operations and payment administration.

04 / Talk to us

Show us how your payments arrive. We’ll show you where Reconexa fits.

Tell us which systems you use, how remittance information reaches your clinic, and where the process creates the most administrative work. We’ll review it before we speak and tailor the walkthrough around your actual payment workflow.
  1. 01Complete the one-minute form
  2. 02We review your workflow
  3. 03We tailor the walkthrough
  4. 04You learn whether Reconexa fits
About one minute · no phone number
Before requesting a walkthrough

The questions that usually decide whether a conversation is worthwhile.

What systems and remittance formats are supported?
Reconexa currently supports Gmail, Microsoft 365, Cliniko, Xero, compatible email content and PDFs, YourRemittance links, and manual PDF uploads. Other applications and portal formats can be assessed against your workflow before support is promised.
Does Reconexa reconcile Xero automatically?
No. Reconexa prepares and matches the supporting work, can create the approved Xero output with its attachment, and keeps the status visible. Your team completes bank reconciliation in Xero.
What happens when a match is uncertain?
The record remains visible for review. An operator can correct extracted fields, inspect the source, select the relevant evidence, upload a PDF, or retry failed processing. Uncertainty is not silently treated as success.
Can Reconexa work with another application?
Possibly, after assessment. Tell us what your workflow requires and Reconexa can assess whether additional support is technically and commercially appropriate. Unlisted applications are not presented as plug-and-play integrations.