PBS claim reconciliation: statements and exceptions
A PBS claim reconciliation routine for Australian pharmacies: compare statements, investigate reason codes, track exceptions and confirm claim closure.


Interim and final statements support different reconciliation stages
Source: Services AustraliaRejections, warnings and information messages need different handling
Source: Services AustraliaProcessing a PBS claim does not remove its certification requirement
Source: Services AustraliaIn this article
Pharmaceutical Benefits Scheme (PBS) claim reconciliation connects prescription records with claim statements, exceptions and payment advice. A bank deposit is one piece of that process.
Consider a fictional month-end review. The payment has arrived, but the team still has a warning message and an unresolved missing-prescription entry. Marking the whole period complete would hide unfinished work.
This guide gives Australian community pharmacy owners a management routine around existing claiming processes. It does not replace Services Australia instructions, software guidance or the pharmacist’s professional responsibilities.
Key facts
- Services Australia distinguishes interim statements, final statements and payment correspondence; each answers a different reconciliation question.
- Read the actual reason code and verify the outcome of any correction or support request.
- Keep unresolved work visible and confirm certification and closure separately. A bank deposit alone does not establish that the claim is complete.
What does PBS claim reconciliation cover?
Keep government reimbursement reconciliation separate from supplier invoice reconciliation. The first checks claims and payments; the second checks what the pharmacy owes for purchases.
Assign a responsible person and a backup, with access to the records they need. Decide who handles questions requiring professional judgement. Review at intervals suited to the claim periods and workload; this is a suggested local routine, not a government-prescribed daily checklist.
Start with the approval number, claim-period identifier and the period being reviewed. Similar-looking reports from different periods can create an apparent discrepancy before any claim problem exists.
Which records should you compare?
Services Australia’s claim statement guidance distinguishes payment correspondence available through Health Professional Online Services (HPOS) from statements supplied through dispensing software.
Weekly interim statements support review during a claim period. Final statements follow closure and include prescription details, prices, adjustments, entitlement errors and reason codes.
Use each record for its intended question:
| Record | Question it helps answer | What it does not prove by itself |
|---|---|---|
| Dispensing software records | Which prescription entries belong to this claim? | That every entry has been accepted or paid |
| Interim statement | What needs investigation during the period? | That the period is finally reconciled |
| Final statement | What details and adjustments were recorded after closure? | That every local follow-up task is complete |
| HPOS payment advice | Which payment correspondence relates to the claim? | That certification and closure were completed |
Match the payment advice to the bank receipt. Record any difference for investigation. Staff need their own approved access to do this work; sharing another person’s login is not an access solution.
What does the reason code require?
Services Australia publishes PBS reason and rejection codes. The categories distinguish rejections, warnings, information messages and time-based warnings.
A time-based warning can become a rejection after its warning period. Some messages need no action; others require correction and resubmission.
Record the actual code and read its current explanation. A local label such as “payment error” loses the detail needed to choose the next step.
The claim submission guidance says actionable reason codes must be addressed before supply. Period-end reconciliation is therefore not a substitute for checks required earlier.
If the explanation conflicts with the local record, escalate through the approved software or Services Australia support route. Do not repeatedly resubmit an unchanged entry to see whether it passes.
Keep the original issue and the correction linked. This lets the reviewer establish whether the resubmitted item resolved that issue or created another open task.
Keep a small, controlled exception record
Keep the official reason code and the local follow-up state separate. Services Australia’s code guide explains what a message means. The pharmacy’s exception record answers a different question: who is doing what about it, and what evidence will confirm the outcome?
Keep detailed patient and prescription information in authorised source systems.
A fictional exception at handover
Fictional example: payment has arrived, but a missing-prescription entry remains open. These suggested workflow labels are not Services Australia codes.
- Investigating: Record the approval number, claim period and entry reference. The assigned reviewer checks whether the entry belongs to that claim.
- Action taken: Record the authorised correction or support request and its reference. Keep the original issue linked to it.
- Awaiting evidence: Name the response or statement the reviewer needs to check, and set the next review date.
- Verified or still open: Record what that evidence shows. If the issue remains unresolved, carry its owner and next action into the shift handover.
The bank deposit and support ticket stay in the record. Neither, on its own, closes the exception.
What needs checking before certification and closure?
Services Australia’s submission instructions include reconciling against the missing-script report before closure. Follow its directions for entries that do not belong to the claim and prescriptions listed as missing.
Those instructions concern claim records and serial numbers. They do not authorise indiscriminate deletion of patient or clinical records.
Check the approval and claim-period details, obtain certification from an authorised person and close the claim through the dispensing software.
The separate certification guidance applies to submitted claims, including under-co-payment claims. A processed claim still needs certification; an uncertified claim may require repayment of an advance.
Use the current guidance to establish the applicable certification and closure timeframes. Keep the relevant trigger dates visible instead of treating the bank-payment date as the start of every deadline.
Finish with evidence, not a cleared task list
At the end of the review, document the records compared, who reviewed them and what remains unresolved. Save the relevant statements in the approved location.
Apply the pharmacy’s record retention procedures to the statements and supporting evidence.
If a difference remains, record the reason, owner and next action. An explained open exception is more useful than forcing the totals to match by making an unsupported adjustment.
Ask one practical question at the next review: did the same issue recur? Repeated errors may point to a training, access or workflow problem that deserves separate attention.
Reconciliation is complete when the evidence supports the recorded outcome and ongoing work remains visible. It is not a promise that every rejected claim can be recovered.
Frequently asked questions
- What is PBS claim reconciliation?
- PBS claim reconciliation compares submitted prescription records, claim statements, exceptions and payment advice, then records how differences were resolved.
- Does receiving a payment mean a PBS claim is complete?
- No. Check the relevant statement and exceptions, and confirm the claim's certification and closure requirements separately.
- Should every PBS message be treated as rejected revenue?
- No. Read the exact reason code: rejection, warning, information and time-based warning messages have different meanings and actions.
- Can the pharmacy use a shared spreadsheet for reconciliation?
- Use only an approved, access-controlled record with the minimum necessary information; keep detailed prescription and patient information in authorised systems.
Preparation note
Prepared with AI-assisted drafting, separate Codex reader reviews and primary-source checks on 19 October 2026. Examples and generated images are illustrative; source scope and limitations are stated in the article.
Publisher: Krepko.
Sources
- Get PBS claim statements · Services Australia · Retrieved
- Submit PBS claims for pharmacy · Services Australia · Retrieved
- Manage PBS reason and rejection codes · Services Australia · Retrieved
- Certifying and closing PBS claims · Services Australia · Retrieved


