Why is my Medicare deposit less than the claims I submitted?

The deposit is one payment run rather than one day of claims. It carries the claims Services Australia had finalised and approved when the run went out, paid at the benefit. Anything declined, still being adjudicated, paid to another payee provider number, or invoiced above the benefit sits outside it.

What should I do if a Medicare claim is rejected?

Read the reason code on the processing report first, because it decides whether the claim goes back out unchanged, goes back out corrected, or has to be billed another way. Leave the invoice open in both systems while that happens. If the invoice was already closed against a payment, the payment comes off before anything else can be edited.

How long should I wait before treating a short deposit as a rejection?

Wait long enough for the claim to be finalised. Tyro Health puts adjudication at one to two business days from submission, Services Australia says reports are available one business day after a claim is finalised, and Zanda says Medicare generates payment status reports 48 hours after a claim is processed. A claim on neither report has not been answered yet.

Should I write the difference off?

A gap that is a declined claim is not a bad debt, because the service was delivered and the claim can usually go back out. A gap that is the practice fee sitting above the Medicare benefit is not a debt at all: bulk billing accepts the benefit as full payment, so nothing above it is owed by the patient. The first needs resubmission. The second needs the item fee corrected in the practice system and the excess taken off the invoice rather than chased.

Why do the charge amount and the paid amount differ on the payment report?

The report shows what you asked for and what Medicare paid as two separate columns. Zanda says the charge amount is the amount charged on the invoice, so it may be higher than the Medicare benefit paid. A claim invoiced at the practice fee can be approved and paid at the lower figure, so it is worth reading down that column before assuming a deposit was short paid.

Problems

Medicare deposit is less than the claims sent

A Medicare deposit is one payment run, not one day of claims, so it pays what Services Australia had finalised and approved by the time the run went out. Four things shrink it: a whole claim declined, a claim that fell into a later run, a run paid to another payee provider number, and a benefit smaller than the amount you invoiced.

Key facts

What a bulk billed service can be charged: Bulk billing means accepting the Medicare benefit as full payment, so nothing above the benefit is billed to the patient⁷
What one deposit covers: One payment run. MedicalDirector defines the deposit amount as the Medicare payment received to the bank account for the payment run⁵
Where a run is paid: The bank account registered with Services Australia for each provider location, which is what a payment depends on¹
Unit of rejection: The whole claim. Tyro Health states that where one service item is rejected the whole invoice is marked as declined²
Where a declined claim is written down: The bulk bill processing report, which shows the claims processed with exceptions and carries a Medicare reason code¹
Where a claim paid below the charge is written down: The payment report. Zanda's Medicare and DVA payment report carries the charge amount and the paid amount as separate columns on the same row³
When the reports can be read: One business day after the claim is finalised, through HPOS with a PRODA login, selected by payee provider number and lodgement date range¹
How long adjudication takes: Tyro Health puts the adjudication response at typically one to two business days from submission²
What a matching total proves: That the payment run landed, not that every claim in it was coded correctly or assigned to the right provider⁶
Where an approved claim is held until the bank line arrives: 100 Medicare clearing, at the BAS Excluded tax rate⁸

What one Medicare deposit covers

The unit Services Australia pays in is the payment run, and the run is not the same shape as your day. Claims that were finalised and approved in time are in it. Claims that were still being adjudicated are not, and claims that failed are not. So the credit in the bank feed is the net of one run, and comparing it against the batch you lodged that morning compares two different things.

Deposit amount refers to the Medicare payment received to the bank account for the payment run.⁵

That is the first thing to settle, because it decides whether there is a problem at all. A run that is smaller than the day's lodgement is ordinary. A run that is smaller than the payment report for the same run is not, and that is a matching question rather than a claiming one.

Four things shrink a Medicare run

Sorting the difference into these four buckets before touching Xero is what keeps the correction to one pass. Each has its own proof, and two of them need no accounting entry at all.

What shrank the run, and the document that proves it¹³

What shrank the run	Where it shows	What you will see
A whole claim was declined	Bulk bill processing report	The claim listed among those processed with exceptions, with a Medicare reason code against it, and absent from the payment report
A claim landed in a later run	Neither report yet, then the next payment report	Nothing at all today, because reports are available one business day after a claim is finalised and this one is not finalised
A second payee provider number was paid	The bank, not a report	A second credit against the other provider number, because bank accounts are registered per provider location
The benefit was smaller than the amount invoiced	Bulk bill payment report	A row where the paid amount column is lower than the charge amount column

A whole claim was declined

Medicare answers a bulk bill claim as one thing. A claim that fails is declined whole rather than trimmed item by item, so a run that is short a declined claim is short by that claim's full amount rather than by a few dollars.

If multiple service items are claimed and one item is rejected the whole invoice will be marked as Declined.²

The proof is the processing report, which lists the claims processed with exceptions and carries a Medicare reason code on each one. The code is the part worth keeping, because it decides whether the claim goes back out unchanged, goes back out corrected, or was not claimable and has to be billed another way. Where the invoice was already closed against a payment, the correction has its own page.

A claim landed in a later run

This is the cause that looks most like a loss and is not one. Tyro Health puts adjudication at typically one to two business days from submission, so a claim lodged late has not been answered by the time the run goes out. It is not declined, it is not short paid, it is simply still travelling.

A claim lodged late in the day may sit outside the current payment run.⁶

You can tell it from a rejection by absence rather than by evidence: a claim that is on neither report has not been finalised yet. The Services Australia guide sets no cut off time for a run, so waiting and reading the next payment report is the honest test. Reversing anything on the day the deposit lands usually creates a second correction two days later. The practice system takes the same position at the moment the claim goes out.

There is no need for you to enter a payment at this point, because the invoice is now awaiting Medicare's approval on this claim.⁴

A second payee provider number was paid

A practice with two payee provider numbers, or one number per site, does not get one deposit that covers everything. It gets one per run per number, and the runs land at their own pace.

You must have your bank account details registered with Services Australia, for each provider location, in order to receive a payment.¹

So the money may not be missing at all. It may be sitting in a second credit that has not arrived yet, or that arrived and was coded somewhere else. The template says the same thing from the posting side, which is why the map holds one Medicare rail rather than one per site.

Medicare pays per payment run per payee provider number, so a practice with several provider numbers can see more than one Medicare deposit a day (docs/research/domain-mechanics.md, section 1.1).⁸

Two credits on the same day are a matching problem rather than a shortfall, and they have a page of their own.

The benefit was smaller than the amount invoiced

The last cause is the quietest, because the claim was approved and paid. It was just paid at the Medicare benefit while the invoice carried the practice fee. Bulk billing assigns the benefit to the practice, and the practice accepts it as full payment for that service, so the amount above it is not owed by the patient and is not a receivable. In the ledger it is an invoice raised above the benefit rather than a payment that went wrong, and the fix is the item fee in the practice system. The Medicare bulk bill page holds the claiming side.

The payment report is built to show this, because it carries the two amounts side by side rather than one net figure.

Charge Amount shows the amount charged on the invoice, so it may be higher than the Medicare benefit paid.³

These are the columns Zanda lists on a Medicare and DVA payment report.

Claim sent, patient, invoice number and claim identifier, which is what joins the row back to the practice system.
Servicing provider name and provider number, which is what tells you whether the claim was assigned to the practitioner you expected.
Charge amount and paid amount, which is where a benefit below the invoiced fee becomes visible.
Run number and date paid, which is what joins the row to the deposit rather than to the day of service.
Payment assigned, which is Zanda's own flag for whether it matched the received payment to the corresponding invoice, rather than anything Medicare sends.

Where the same item code comes back below the charge every fortnight, the fix is the fee on the item in the practice system, not a monthly adjustment in Xero.

One run drawn whole

Here is an illustrative run, built to show all three causes that can shrink one deposit at once. The figures are made up. What is not made up is the shape: the claims that were paid are the deposit, and everything else is somewhere other than the bank.

Plate 1An illustrative payment run. The paid claims add to the credit exactly, and the batch that was lodged that morning was larger for three separate reasons.

The order of work that saves an hour

Reading the reports before opening Xero is the whole trick. Both reports come out of HPOS with a PRODA login, selected by report type, payee provider number, lodgement date range and claiming method, in either a document or a spreadsheet format.

Take the run number off the deposit and pull the payment report for that payee provider and lodgement date range.
Add the paid amounts on that report. If they equal the credit, the run is intact and the difference is entirely outside this deposit.
Pull the processing report for the same range and list the claims carrying a reason code. Those are the declined ones.
Compare the two lists against the batch you lodged. Anything on neither report has not been finalised, so leave it alone.
On the payment report, scan the charge amount against the paid amount row by row. A gap there is an invoice raised above the benefit.
Check whether a second payee provider number has its own run outstanding before treating anything as missing money.
Only then post: approved claims into the clearing account on the paid date, and the deposit matched against that account as one bank line.

What not to do with the difference

The tempting move is to make the numbers agree today: adjust the invoices down to the deposit, or write the gap to a shortfall account and move on. Both destroy the evidence that would let somebody chase the money next month, and a declined claim that has been written off is a claim nobody resubmits.

A bank deposit that agrees to the report total proves the payment run landed, not that every claim was coded correctly, assigned to the right provider, or ready to become revenue.⁶

What Ledger Map does with a short run

Ledger Map holds one standing map for the practice, approved before anything syncs. Paid claims resolve through that map into the Medicare clearing account on the date Services Australia paid them, the run is posted as one balanced document set, and one exact match is left in the bank feed for the credit.

A claim that was declined resolves to no posting at all, because the canonical template says so on the rail itself rather than in a note somebody has to remember. A claim that cannot be read as paid, declined or still in flight from the reports the practice has becomes a question with the candidate postings laid out, not a silent entry. The account and the tax rate are the practice's own template. The learn hub carries the rest of the Medicare reconciliation questions, and how it works shows the map itself.

Questions

Why is my Medicare deposit less than the claims I submitted?
The deposit is one payment run rather than one day of claims. It carries the claims Services Australia had finalised and approved when the run went out, paid at the benefit. Anything declined, still being adjudicated, paid to another payee provider number, or invoiced above the benefit sits outside it.
What should I do if a Medicare claim is rejected?
Read the reason code on the processing report first, because it decides whether the claim goes back out unchanged, goes back out corrected, or has to be billed another way. Leave the invoice open in both systems while that happens. If the invoice was already closed against a payment, the payment comes off before anything else can be edited.
How long should I wait before treating a short deposit as a rejection?
Wait long enough for the claim to be finalised. Tyro Health puts adjudication at one to two business days from submission, Services Australia says reports are available one business day after a claim is finalised, and Zanda says Medicare generates payment status reports 48 hours after a claim is processed. A claim on neither report has not been answered yet.
Should I write the difference off?
A gap that is a declined claim is not a bad debt, because the service was delivered and the claim can usually go back out. A gap that is the practice fee sitting above the Medicare benefit is not a debt at all: bulk billing accepts the benefit as full payment, so nothing above it is owed by the patient. The first needs resubmission. The second needs the item fee corrected in the practice system and the excess taken off the invoice rather than chased.
Why do the charge amount and the paid amount differ on the payment report?
The report shows what you asked for and what Medicare paid as two separate columns. Zanda says the charge amount is the amount charged on the invoice, so it may be higher than the Medicare benefit paid. A claim invoiced at the practice fee can be approved and paid at the lower figure, so it is worth reading down that column before assuming a deposit was short paid.

Sources

Open questions

The Services Australia guide sets no cut off time for a payment run, so whether a claim lodged late in the day falls into the next run cannot be predicted from a published rule. The page states it as an observed cause and points at the next payment report as the proof.
The Services Australia guide says reports are available one business day after a claim is finalised, while Zanda says Medicare generates payment status reports 48 hours after processing. Both are stated here rather than merged, because they are measured from different events.
How long a payment run takes to reach the bank is not stated here. The figure in circulation, two to three working days, was found only on a vendor blog and no published Services Australia service standard for it was located, so the page names no arrival time.
The bank narration Services Australia uses for a payment run is not confirmed by any primary source in the corpus. Zanda documents the run number as the identifier that joins a report to a credit, which is a join key rather than a narration string, so no descriptor string appears here.
Only Zanda's documentation was verified to show the charge amount and the paid amount as separate columns. The Cliniko and MedicalDirector help topics read on this pass describe neither those two columns side by side nor what happens when a claim is declined.

How to access Medicare Bulk Bill reports in Health Professional Online Services (HPOS)
Services Australia. Retrieved 3 Sep 2026. Source updated Jul 2024.
primary
Medicare claims processing flows
Tyro Health developer portal. Retrieved 3 Sep 2026.
primary
Medicare and DVA payment reports
Zanda. Retrieved 3 Sep 2026.
primary
Process bulk bill claims for Medicare
Cliniko. Retrieved 3 Sep 2026. Source updated 18 Jun 2026.
primary
Medicare Claim Payment (Bulk Bill / DVA) Report
MedicalDirector Bluechip knowledge base. Retrieved 3 Sep 2026.
secondary
Reconcile Medicare bulk bill and DVA payments in allied health
Invoice Data Extraction. Retrieved 3 Sep 2026. Source updated 14 May 2026.
secondary
Medicare billing in Australia
Pabau. Retrieved 4 Sep 2026.
secondary
Allied health by funding source, the canonical template
Ledger Map. Retrieved 3 Sep 2026.
primary

Review

Last reviewed 3 Sep 2026 by Shane

General information for Australian allied health practices, not tax advice. Confirm a treatment with your BAS agent or accountant before you post it.

Guided onboarding

Run one real month before you go live.

Sign up, connect Zanda and Xero, and replay a month you already closed. The map is reviewed with whoever owns the books, and nothing posts until you approve it.

Start your map

Every practice starts from a template. Nothing posts until the map is approved.