RIFT - billing leak detection RIKO - the AI front desk RISE - social media (coming soon) Is it for me? Security Philanthropy Blog Login Cart Free leak report
← Back to Help centre RIFT

RIFT leaks explained

Each leak type and follow-up group in plain words, the Leaks tab filters, what "worth checking" coding flags mean, and how an item is resolved or dismissed.

This article explains every group RIFT sorts its findings into, how the Leaks tab is filtered, what the coding flags mean, and what happens when you mark an item done or dismiss it.

How RIFT sorts what it finds

RIFT splits its findings into three places in the sidebar:

Each group on the Leaks and Follow-ups tabs is a collapsible section with a count, a subtotal and a ? that explains it. Click the section heading to open it.

The five leak groups on the RIFT Leaks tab

Sub-groups inside a RIFT leak group (who pays)

Some groups split into a second level so the right person is chased:

A group with only one sub-group shows flat, without the extra heading.

The follow-up groups on the RIFT Follow-ups tab

On the Follow-ups tab the Update menu offers only Paid in full, Called / no answer and Dismiss.

Filters and sorting on the RIFT Leaks tab

Across the top of the Leaks tab (and Follow-ups):

The figure in the tab header is the total of whatever is currently shown. Each item row shows the title, the client and date, the amount, any history, and buttons for what you can do with it.

"Check first" warnings on a RIFT item

Some items carry a warning line starting with a triangle. RIFT adds it when your own records suggest the money may already be in: a reception note on the appointment or invoice that reads like a payment, a client with a payment noted against them, a partly paid amount that does not match either share of a funded split, or an invoice whose own note mentions payment. The header shows the total of these as "flagged, check first" and keeps it out of the leak estimate. An item with this warning is never emailed automatically, whatever your sending settings say - a person must look first.

Billing codes worth checking (RIFT coding flags)

RIFT runs three automated coding checks and lists the results under Billing codes worth checking on the Follow-ups tab:

Every finding is "worth checking", never "you billed this wrong". The dollars never join your leak estimate or your recovered total; they get their own "worth checking" figure. The disclaimer that travels with them everywhere they appear: coding findings are automated estimates only - not billing, financial or legal advice. Medicare and NDIS rules depend on details no practice-software export can see (referrals, plans, entitlements, what was actually delivered). Verify each one against the scheme's current rules before making or changing any claim.

Resolving a RIFT item: Done versus Recovered

There are two ways to say "handled", and RIFT keeps them separate on purpose:

If an item you marked Done is still there at the next sync, it stays Done rather than being counted as recovered. If a cleared item reappears in your data later, RIFT reopens it.

Dismissing a RIFT item, and why RIFT dismisses some itself

Choose Update > Dismiss and say why (for example "fee waived" or "invoiced elsewhere"). The item moves to the Dismissed tab with your reason, and will not be chased. Click Reopen on a dismissed item to put it back on the Open list. A dismissed item that later disappears from your data stays dismissed - a deliberate ignore is never counted as recovery.

RIFT also dismisses items itself when your rules say they are not actionable, and states the reason on the row: within payment terms, within the invoicing grace period, excluded by clinic policy, client marked do-not-chase, not a real patient, billed externally, superseded by a Medicare claim item, or dated after the export snapshot. RIFT may undo its own dismissals when the reason goes away (for example after a settings change), but it never undoes a dismissal a person made.

Two shortcuts on a row: Paid outside Zanda (or Cliniko) on a "Verify uninvoiced" item dismisses it with that reason, and Billed externally marks the client as billed by someone else, so all their sessions move to the Externally billed bucket and stop counting as leaks.

The RIFT Buckets view

Buckets shows the raw data behind the lists, one table per bucket: Outstanding invoices, Medicare claims, Uninvoiced appointments, Possibly pack-covered, No-shows / late cancellations, Unallocated payments, Session packs, Referrals, Group appointments (check) and Externally billed. Each tab shows a row count; type in Filter rows... to narrow the table, click a column heading to sort, and the caption shows the total of the money column for what is shown. Rows older than your write-off setting appear dimmed, and a triangle in the Outstanding invoices table marks a "check first" warning (hover to read it).

Data confidence warnings in RIFT

After each sync RIFT checks whether your data fits the way it analyses (for example, whether appointments are marked as attended). Anything it is unsure about appears in a Data confidence - review before trusting the numbers banner under the header, naming which lists are affected. It also shows on the Home view under Needs attention. Fix the cause in your practice software, or adjust the matching setting in RIFT, and the warning clears at the next sync.

Still stuck?

Ask RIKO Help, the chat bubble in the corner of this page - it answers from these articles. If it cannot help, use the support form in your dashboard or email support@rapidintelligence.com.au. Please do not include patient names or details.