AoB is a workflow, not just a form
The updated Medicare Assignment of Benefit (AoB) process is often described in terms of forms, signatures and consent.
Those things matter.
But in a real medical practice, AoB is a workflow.
A practice staff member may need to start the agreement. The patient or assignor may need to complete it. The completed agreement may need to return to the practice. Billing staff may need to know whether the agreement is complete. The record may need to be retained and retrieved later.
If the workflow does not fit the way the practice operates, the process will create friction.
That is why AoB readiness should not be limited to choosing a document template.
It should include the practical question:
How will this work inside our practice?
What the official guidance says
Services Australia states that from 1 July 2026, Assignment of Benefit can occur either before or after the service has been rendered to the patient.
This flexibility matters.
A pre-service AoB workflow may work well where the service is predictable and the required details can be provided before the appointment.
A post-service AoB workflow may be more suitable where the actual service, MBS item, practitioner or billing details are only confirmed after the consultation.
The Department of Health, Disability and Ageing has also confirmed a 12-month transition period to support implementation of the new Assignment of Benefit requirements.
That gives practices time to build a workflow that works properly.
The basic AoB workflow
A practical AoB workflow usually has four steps.
1. Practice starts the agreement
The practice initiates the AoB agreement and enters the known details.
This may include the patient, provider, practitioner, service category, location, appointment context or other required information.
2. Patient or assignor completes and signs
The agreement is sent or presented to the patient, or to the correct assignor.
They review the information, complete any required fields, agree to assign the Medicare benefit and provide their signature or agreement.
3. Completed agreement returns to the practice
Once completed, the agreement returns to the practice workflow.
Staff can confirm completion and proceed with the next administrative or billing step.
4. Record is stored, retrieved and shared if needed
The completed agreement is retained by the practice. It can be retrieved later for patient copy requests, internal checks, or compliance review.
This is the workflow that matters.
The timing may differ. The channel may differ. The patient scenario may differ.
But the core work still needs to be started, completed, tracked and evidenced.
Why one fixed process may not be enough
Not every AoB situation is the same.
A standard GP consultation may be predictable. A specialist consultation may change after clinical assessment. A patient may complete an agreement remotely. A carer may need to act as assignor. A service may be delivered by a different practitioner from the one expected.
That is why practices should avoid designing an AoB process around only the simplest scenario.
A practical workflow should support:
- pre-service assignment
- post-service assignment
- in-practice completion
- remote completion
- patient or assignor signing
- changed service details
- changed practitioner details
- incomplete agreements
- record retrieval
- patient copy requests
The workflow should guide staff through those situations rather than leaving them to decide manually each time.
Why this matters for GP practices
GP practices need AoB workflows that are fast, repeatable and easy for staff to manage.
Reception and billing teams do not need another disconnected administrative burden. They need a process that fits the rhythm of the practice.
For GPs, an effective AoB workflow can help:
- reduce front desk congestion
- support digital completion before or after appointments
- make patient or assignor completion clearer
- reduce paper handling
- show which agreements are complete
- support retrieval if the practice needs the record later
For eligible patients, enduring assignment may also become relevant. Services Australia explains that enduring assignment can apply to certain eligible GP patients, including MyMedicare patients, residents of aged care homes, and patients of ACCHOs and AMSs.
Even then, practices still need clear workflows for episodic AoB, exceptions, incomplete agreements and patient copy requests.
Why this matters for specialist practices
Specialist practices need flexibility.
In specialist rooms, the service may not always be known in advance. The final MBS item may depend on what occurs during the consultation. The rendering practitioner may change. The patient may need a different billing pathway after the appointment.
This makes post-service workflows particularly important.
For specialist practices, a good AoB workflow should help staff handle:
- service variation
- practitioner variation
- procedure-specific details
- post-consultation completion
- assignor scenarios
- multiple appointment or service contexts
- accurate record storage and retrieval
A generic form process may struggle with that variation.
A workflow-based approach is better suited to the real administrative environment of specialist practice.
Tiikr’s workflow approach to AoB
Tiikr has always been strongest where work needs to move between people, steps and outcomes.
The Tiikr Medicare Assignment of Benefits solution helps practices treat AoB as structured work.
The practice can start the agreement. The patient or assignor can complete their part. The completed agreement can return to the practice. The record can be retained and retrieved.
This is more than sending a form.
It is a way of making the AoB process visible, trackable and provable.
Pre-service and post-service should be timing options, not separate administrative worlds
One useful way to think about AoB is this:
Pre-service and post-service are timing options in the same underlying workflow.
The practice still needs to create the agreement, collect the required information, obtain the patient or assignor agreement, store the completed record and retrieve it later.
The difference is when the agreement is completed and what information is known at that point.
A well-designed digital workflow should support both timing models without forcing staff into a completely different process every time.
Frequently asked questions
What is the best Medicare AoB workflow?
The best Medicare AoB workflow is one that allows practice staff to start the agreement, allows the patient or assignor to complete and sign it, returns the completed agreement to the practice, and stores the record so it can be retrieved later.
Should AoB be completed before or after the service?
It depends on the practice workflow and service context. Services Australia says Assignment of Benefit can occur before or after the service. Pre-service may suit predictable services, while post-service may suit situations where final service details are only known after the consultation.
Do GP and specialist practices need different AoB workflows?
They may need different configurations of the same workflow. GP practices often need speed and repeatability. Specialist practices often need flexibility for changed service, practitioner or item details.
A practical next step
Map one common AoB pathway in your practice.
Start with a simple scenario:
- who starts the agreement?
- when is it sent or presented to the patient?
- who signs it?
- how does the practice know it is complete?
- where is the completed record stored?
- how would staff retrieve it later?
Then map the exceptions.
That is where many paper and basic e-signature processes start to struggle.
Book an AoB readiness review with Tiikr and see how a structured AoB workflow could fit your practice.