Murray-Darling Basin Agreement (Schedule D - Tagging Entitlements for Extraction in another State) Protocol 2010

The Protocol builds around a small set of operational concepts defined in clause 5 and expressed through two schedules.

• Tagging and application. "Application" is a defined term covering an application to tag an entitlement so allocations may be extracted in another State, or to alter or remove a tag; the defined term explicitly excludes an application to transfer an entitlement (clause 5). That distinction separates tagging,an administrative overlay permitting extraction in a different State,from transfers of legal entitlement title, which remain governed by State law and are treated separately (Schedule 2 Step 5).

• State of Origin and State of Destination. The Protocol uses the capitalised terms State of Origin (the State where an allocation is made) and State of Destination (the State where the tagged allocation will be extracted) (clause 5). These labels allocate roles and obligations between the respective retailers, licensing authorities and wholesalers in each State.

• Retailers and wholesalers. "Retailer" is the authority responsible for accounting for transfers of allocations, administering tagging arrangements and accounting for water used pursuant to allocations within a State (clause 5). The Protocol distinguishes SOO retailers (State of Origin retailers) and SOD retailers (State of Destination retailers). "Wholesaler" is the authority responsible for recovering headworks costs from which allocations are supplied in a State of Origin (clause 5). These roles allocate billing, record-keeping and notification obligations.

• Transfer Register, cap, valley accounts and salinity registers. The Authority must record approved tagging on the Transfer Register and make consequential adjustments to statutory or administrative instruments , the cap, valley accounts and salinity registers , as required (Schedule 1 Step 4(1)(a)-(d); Schedule 2 Step 6(2)). These instruments are operational levers that maintain basin-wide accounting and environmental overlays when water is extracted in a different State to where the allocation was made.

• Processes and time limits. The Protocol creates a sequential process for tagging (Schedule 1 Steps 1-6) and separate, but connected, processes for accounting for use of tagged allocations (Schedule 2 Steps 1-7). Examples of time limits include: licensing authorities must provide monthly records to the Authority within 7 days after the end of a month (Schedule 1 Step 5(1)); the Authority must prepare quarterly interstate transfer reports within 30 days after the end of each quarter (Schedule 1 Step 6(1)); licensing authorities must respond to discrepancy reports within 14 days (Schedule 1 Step 5(5)(a)).

• Reconciliation and discrepancy handling. The Authority compares licensing authority records, previous month records and the Transfer Register; it records discrepancies other than "allowable discrepancies" (Schedule 1 Step 5(2)-(4)). Allowable discrepancies are defined narrowly: up to 1 ML per transfer, spelling errors or first-name abbreviations (Schedule 1 Step 5(4)). Unresolved discrepancies are escalated to the Interstate Water Trade Taskforce and an independent auditor (Schedule 1 Step 5(6)).

• Charges and billing. The Protocol instructs State of Origin wholesalers to adopt the principle that bulk water charges be billed directly to the interstate owner of the share as at billing date (clause 7(2)). Schedule 2 Step 7(1) requires SOO retailers to keep wholesalers informed about approvals/deliveries that affect recoverable charges. Schedule 2 Step 7(2) explicitly permits SOD retailers to impose and recover charges it is entitled to under Destination State law.

• Enforcement signals. The Protocol specifies administrative consequences for certain conduct: if an SOD retailer accepts an order when the SOO allocation account lacks sufficient credit and water is nonetheless extracted, the extraction is to be treated by the State of Destination as unauthorised use (Schedule 2 Step 3(4)-(5)). Other enforcement features are administrative: record adjustments, reporting to auditors, and the Authority's adjustments to statutory accounting registers.

These concepts interlock: tagging is an administrative measure that leaves underlying property or entitlement transfers to State law but requires cross-jurisdictional coordination of accounting, delivery capacity checks, charges allocation and dispute-reconciliation procedures. The Protocol foregrounds accounting integrity (Transfer Register, reconciliations), delivery feasibility (SOD determination), and billing allocation (wholesaler and retailer roles).

The Protocol allocates duties and imposes procedural obligations on a defined set of institutional actors; it also imposes practical constraints and potential liabilities on entitlement holders and persons extracting water.

Primary institutional actors:

• The Murray-Darling Basin Authority (the Authority) is the instrument-maker and central recorder. The Authority must determine notice formats in consultation (clause 6(2)), record approved tagging on the Transfer Register and make consequential adjustments to cap, valley accounts and salinity registers when tagging events occur (Schedule 1 Step 4(1)(a)-(d)), examine licensing authority records for discrepancies (Schedule 1 Step 5(2)-(3)), and prepare quarterly interstate transfer reports (Schedule 1 Step 6). The Authority also must review or amend the Protocol when triggered by enumerated events (clause 9).

• SOO retailers (retailer in State of Origin) are the initial contact for applications (Schedule 1 Step 1(1)). They must verify application completeness, ownership, power to deal, restrictions on transferable volumes, and that tagging will not create multiple destination zones (Schedule 1 Step 1(2), Step 2). SOO retailers must ensure fees are paid before tagging takes effect and update records (Schedule 1 Step 4(2)(a)-(b)), debit SOO allocation accounts when transfers occur (Schedule 2 Step 3(3)(a)), and inform wholesalers about charges (Schedule 2 Step 7(1)). They also decide transfer applications in accordance with State of Origin law (Schedule 2 Step 5(2)(a)).

• SOD retailers (retailer in State of Destination) receive notification from SOO retailers and must determine delivery feasibility, may attach conditions to delivery and must notify applicants and the Authority when approved (Schedule 1 Step 3; Step 4(1)). SOD retailers must create SOD allocation accounts (Schedule 2 Step 1(3)), refuse delivery where SOO credit is insufficient (Schedule 2 Step 2(3)), record and adjust orders and SOD accounts (Schedule 2 Step 3(1)-(3)), notify SOO retailers of orders and adjustments (Schedule 2 Steps 3 and 4), report monthly delivered volumes to the Authority (Schedule 2 Step 6(1)), and may impose and recover charges under Destination State law (Schedule 2 Step 7(2)).

• Licensing authorities within States must provide monthly records to the Authority within 7 days after month end (Schedule 1 Step 5(1)), and respond to discrepancy reports within 14 days (Schedule 1 Step 5(5)). They are the record-keepers whose data feed the Authority's reconciliation processes.

• Wholesalers in the State of Origin are responsible for recovering headworks costs; the Protocol directs wholesalers to adopt the principle of billing bulk water charges to the interstate owner as at billing date (clause 7(2)). SOO retailers must keep wholesalers informed of approvals/deliveries that affect such recoverable charges (Schedule 2 Step 7(1)).

Affected private actors:

• Entitlement holders and persons entitled to receive allocations. The Protocol affects holders who wish allocations made under an entitlement to be extracted in another State: they must lodge applications to SOO retailers (Schedule 1 Step 1(1)), ensure any required fees are paid (Schedule 1 Step 4(2)(a)), and be subject to delivery conditions imposed by SOD retailers (Schedule 1 Step 4(1)(b)). If a destination extraction occurs with insufficient SOO allocation credit, the extraction is treated as unauthorised in the State of Destination (Schedule 2 Step 3(4)-(5)), exposing the user to State enforcement under Destination law.

• Water market participants who trade allocations. Although the Protocol excludes applications to transfer entitlements (clause 5), it does govern the accounting for transfers of allocations between tagged entitlements and other entitlements (Schedule 2 Step 5). SOO retailers must decide transfer applications in accordance with State of Origin law (Schedule 2 Step 5(2)(a)).

Who pays and who decides:

• Who pays: billing and recovery mechanisms are split. Wholesalers should bill bulk water charges directly to the interstate owner as at billing date (clause 7(2)). SOD retailers may impose charges under Destination State law on the person extracting the tagged allocation (Schedule 2 Step 7(2)). SOO retailers must ensure fees are paid before tagging takes effect (Schedule 1 Step 4(2)(a)). These provisions create distinct points of cost allocation between owners, origin wholesalers and destination retailers.

• Who decides: SOO retailers make initial eligibility and ownership checks, SOD retailers make delivery feasibility and condition determinations, the Authority records the tagging and adjusts basin-wide accounting instruments, licensing authorities provide the underlying records, and independent auditors and the Interstate Water Trade Taskforce are in place to review unresolved discrepancies (Schedule 1 Step 5(6); clause 9).

In sum, the Protocol affects a concentrated set of institutional actors (Authority, retailers, licensing authorities, wholesalers) who bear ongoing information and accounting burdens, and a dispersed set of entitlement holders and extractors who must comply with application and payment requirements and can be exposed to State enforcement actions for unauthorised extractions.

The Protocol imposes a sequence of duties on institutional actors and establishes rights and expectations for entitlement holders. These duties are primarily administrative, accounting and reporting in nature.

Key duties on SOO retailers (Schedule 1 & Schedule 2):

• Accept and record applications to tag entitlements (Schedule 1 Step 1(1)-(2)). Promptly allocate a transaction identification number and forward the application and identification number to the SOD retailer if not prohibited (Schedule 1 Step 1(2)(d)).
• Verify ownership, power to deal with allocations, transferrable volume restrictions, and that the entitlement will not be tagged to locations in more than one destination zone (Schedule 1 Step 2(1)(a)-(d)).
• Where applications may be approved, notify the SOD retailer (Schedule 1 Step 2(3)). Where they cannot be approved, notify the SOD retailer and the applicant (Schedule 1 Step 2(2)).
• Before finalisation, ensure all relevant fees have been paid, update its records to show tagging, record the date tagging takes effect and advise the SOD retailer and the Authority (Schedule 1 Step 4(2)(a)-(c)).
• Make allocations into the relevant SOO allocation account and, when orders are placed and delivered, debit the SOO allocation account and notify the SOD retailer of reduced credit (Schedule 2 Step 1(1); Step 3(3)(a)-(b)).
• Determine transfer applications of allocations in accordance with State of Origin law and adjust SOO accounts accordingly (Schedule 2 Step 5(2)(a)-(b)).

Key duties on SOD retailers:

• On receipt of a notification that an application may be approved, determine whether the SOD retailer can deliver the water comprised in the allocation and whether to approve the application if Step 4 is satisfied (Schedule 1 Step 3).
• When approving, notify the SOO retailer and the Authority and notify the applicant of any delivery conditions (Schedule 1 Step 4(1)(a)-(b)).
• Establish an allocation account in the State of Destination for the person entitled (Schedule 2 Step 1(3)).
• Refuse to deliver water where the SOO allocation account lacks sufficient credit (Schedule 2 Step 2(3)).
• Record orders as first estimates of use, adjust SOD allocation accounts, notify the SOO retailer of orders and adjustments, and perform necessary transfers between SOO and SOD allocation accounts (Schedule 2 Step 3).
• Report to the Authority, within 7 days after month end, the volume delivered pursuant to tagged allocations from each State of Origin (Schedule 2 Step 6(1)).
• May impose and recover charges from the person entitled under Destination State law (Schedule 2 Step 7(2)).

Key duties on licensing authorities:

• Provide copies of records relating to interstate tagging for the preceding month to the Authority within 7 days after the end of a month (Schedule 1 Step 5(1)).
• Respond to discrepancy reports with explanations within 14 days and consult with the Authority to resolve discrepancies (Schedule 1 Step 5(5)).

Key duties on wholesalers:

• Adopt the principle that bulk water charges be billed directly to the interstate owner of the share at billing date (clause 7(2)). SOO retailers must keep wholesalers informed of approvals or deliveries (Schedule 2 Step 7(1)).

Key duties on the Authority:

• Determine the form and content of notices required under the Protocol in consultation with State Contracting Governments and relevant agencies (clause 6(2)).
• Record approved tagging on the Transfer Register and make adjustments to the cap, valley accounts and salinity registers as required (Schedule 1 Step 4(1)(a)-(d); Schedule 2 Step 6(2)).
• Examine licensing authority records for discrepancies, report and record discrepancies other than allowable discrepancies and provide discrepancy reports to licensing authorities (Schedule 1 Step 5(2)-(3)).
• Prepare quarterly interstate transfer reports and distribute them to each Contracting Government and licensing authority (Schedule 1 Step 6(1)-(2)).
• Review the Protocol when triggers in clause 9(2) occur and consider amendments.

Rights and expectations:

• Applicants have a right to be notified if a transfer is prohibited due to another Protocol concerning transfer limits (Schedule 1 Step 1(2)(b)-(c)).
• Entitlement holders have an expectation that tagging will be recorded on the Transfer Register and that the Authority will make consequential adjustments to statutory accounting instruments once tagging is finalised (Schedule 1 Step 4(1)(a)-(d)).
• SOD retailers may attach conditions to delivery and recipients can be charged under Destination State law; applicants are to be informed of those conditions and costs prior to finalisation (Schedule 1 Step 4(1)(b); Schedule 2 Step 7(2)).
• Licensing authorities and retailers are entitled to use the 1 ML allowable discrepancy tolerance per transfer and to correct spelling and abbreviation errors without a formal discrepancy record (Schedule 1 Step 5(4)).

Limitations and cross-references:

• The Protocol does not itself alter entitlement title or State law governing transfers of entitlements; applications to transfer entitlements are excluded from the definition of "application" and transfers are determined by SOO retailers in accordance with State of Origin law (clause 5; Schedule 2 Step 5(2)(a)).
• The Protocol relies on State legal frameworks for enforcement regarding unauthorised use: if a destination user extracts water when SOO credit is insufficient and the SOD retailer cannot prevent extraction, the State of Destination must treat the extraction as unauthorised use under its own law (Schedule 2 Step 3(5)).

In short, the Protocol sets out a matrix of duties that allocate administrative, accounting and reporting responsibilities among the Authority, retailers, licensing authorities and wholesalers, while rights of applicants are largely procedural (notice, conditions, accounting entries) and substantive enforcement remains subject to State law.

The Protocol is primarily an administrative instrument; it does not itself create criminal offences or a discrete penalty regime. It instead establishes administrative mechanisms, cross-jurisdictional reporting, accounting controls and references to State enforcement for unauthorised use. The Protocol therefore relies on a combination of preventive controls, accounting adjustments and escalations to independent audit or State enforcement to manage non-compliance.

Preventive and administrative controls

• Preconditions for tagging: SOO retailers must verify ownership, the power to deal, and that transfers do not breach transfer limits or protocol-imposed zone restrictions prior to approving tagging (Schedule 1 Step 2(1)(a)-(d)). SOO retailers must also ensure all relevant fees have been paid before updating records to show an allocation is tagged (Schedule 1 Step 4(2)(a)-(b)). These checks operate as administrative gatekeeping to prevent unauthorised or non-compliant tagging.

• Delivery feasibility and conditions: SOD retailers must determine whether they can deliver the water and may attach conditions to delivery (Schedule 1 Step 3; Step 4(1)(b)). That power reduces the risk that extraction occurs in a manner the destination system cannot support.

• Account sufficiency rule and unauthorised use: A key enforcement mechanism is the rule that an SOD retailer must not deliver water unless the SOO allocation account credit is sufficient to meet the volume ordered (Schedule 2 Step 2(3)). If an extraction occurs notwithstanding insufficient credit, the Protocol requires the State of Destination to treat that extraction as unauthorised use under Destination State law (Schedule 2 Step 3(4)-(5)). The Protocol does not specify the sanctions that apply to unauthorised use; it leaves those to Destination State law and enforcement mechanisms.

Accounting, reconciliation and escalation

• Reconciliation and discrepancy reporting: Licensing authorities must send monthly records to the Authority within 7 days after month end (Schedule 1 Step 5(1)). The Authority must examine records for discrepancies and record any discrepancy other than permissible ones (Schedule 1 Step 5(2)-(3)). A licensing authority must provide explanations within 14 days and consult to resolve discrepancies (Schedule 1 Step 5(5)). These reconciliation duties act as an early-detection mechanism to surface accounting anomalies that may indicate non-compliance or systemic data issues.

• Escalation to taskforce and independent auditor: If a discrepancy is not resolved within the month it was reported, the Authority must inform the Interstate Water Trade Taskforce and report the discrepancy to the independent auditor referred to in subclause 16(5) of Schedule D for the year (Schedule 1 Step 5(6)). Clause 9(1) also allows the independent auditor to consider the operation of the Protocol and recommend that the Authority review it. These escalation paths provide institutional oversight but do not themselves impose penalties.

Charging and commercial remedies

• Recovery of charges: The Protocol assigns charge-recovery rights. SOD retailers may impose and recover charges against the person entitled to receive a tagged allocation under Destination State law (Schedule 2 Step 7(2)). SOO retailers must keep wholesalers informed about approvals or deliveries that may affect charges recoverable from entitlement holders (Schedule 2 Step 7(1)). Wholesalers are expected to bill bulk charges to the interstate owner as at the date of billing (clause 7(2)). These provisions create commercial enforcement levers: unpaid charges can trigger State-based debt recovery or billing remedies under State law.

Absence of express sanctions in the Protocol

• No express civil or criminal penalties are specified. The Protocol relies on State law where sanctioning power is required, for example in relation to unauthorised use (Schedule 2 Step 3(5)) or in transfer determinations that are to be made "in accordance with the law of the State of Origin" (Schedule 2 Step 5(2)(a)). The Protocol's enforcement architecture therefore delegates sanctions to existing State regimes and uses accounting, notice, and reporting obligations to support State enforcement.

Practical enforcement risks and uncertainties

• The Protocol's enforcement effectiveness depends on co-ordination among retailers, licensing authorities, wholesalers and the Authority. If an SOD retailer cannot practically prevent extraction in the Destination State when SOO credit is insufficient, the Protocol simply requires the Destination State to treat the extraction as unauthorised , it does not create an interstate remedy or prescribe cross-border sanctioning mechanisms. Similarly, dispute resolution or sanctions for data discrepancies are channeled to independent auditing and taskforce escalation, rather than immediate statutory penalties.

In sum, the Protocol focuses on administrative controls and accounting integrity as the primary means of preventing and responding to non-compliance, deferring specific penal measures to State law and to independent audit processes and intergovernmental oversight bodies for systemic or unresolved issues.

The Protocol is an instrument made under the Murray-Darling Basin Agreement and the Water Act 2007 and expressly cross-references other statutory instruments, State law regimes and existing administrative registers. It does not displace State property or transfer laws; it overlays inter-state administrative coordination. Key interactions spelled out in the text are as follows.

Foundational legal basis

• The Protocol is made under clause 6 of Schedule D to the Murray-Darling Basin Agreement and section 18E of the Water Act 2007 (preamble). It therefore operates within the federal Agreement and Water Act framework, and its legal force derives from the Authority's powers under those instruments.

Interaction with State laws on transfers and unauthorised use

• Transfers of entitlements: The Protocol's definition of "application" excludes an application to transfer an entitlement (clause 5). For transfers between allocations and tagged entitlements the SOO retailer must determine applications in accordance with the law of the State of Origin (Schedule 2 Step 5(2)(a)). This explicitly preserves State law primacy over entitlement transferability and means disputes about title or transferability will be settled under State law, not by the Protocol.

• Unauthorised use: Where a person extracts water in the State of Destination despite insufficient credit in the SOO allocation account, the Protocol requires the State of Destination to treat that extraction as unauthorised use under its law (Schedule 2 Step 3(4)-(5)). The Protocol thus depends on Destination State enforcement regimes for sanctions and remedies when extraction occurs improperly.

Registers and basin accounting instruments

• Transfer Register, cap, valley accounts, salinity registers: The Authority must record tagging on the Transfer Register and make any consequential adjustments to the cap, valley accounts and salinity registers as required (Schedule 1 Step 4(1)(a)-(d); Schedule 2 Step 6(2)). These are instruments maintained under the broader Agreement or the Water Act framework; the Protocol requires coordination so that interstate tagging is reflected in basin-wide statutory accounting and environmental instruments.

Electronic notices

• Clause 6(1) and the accompanying note refer to section 9 of the Electronic Transactions Act 1999 for written notices being given electronically. The Protocol therefore envisions notices may be properly given by electronic means under that Act.

Interaction with intergovernmental oversight and audit

• Independent auditor: Clause 9(1) references the independent auditor appointed under subclause 16(5) of Schedule D to the Agreement; the auditor may consider the operation of the Protocol and recommend a review. Schedule 1 Step 5(6) requires escalation of unresolved discrepancies to this same independent auditor. The Protocol thus operates in a multilevel oversight environment with intergovernmental audit mechanisms.

Limits on revocation and prior protocols

• Clause 3 revokes prior protocols made under paragraph 6(1)(f) of Schedule D to the Agreement before 1 December 2009 that apply only to interstate tagged trade, and partly revokes protocols made before this Protocol where those earlier instruments covered interstate tagged trade alongside other matters. The Protocol therefore supersedes earlier interstate-tagging-only protocols but leaves intact prior instruments to the extent they dealt with non-tagging matters.

Interaction with State billing and charging laws

• Charging and recovery: Clause 7(2) instructs State of Origin wholesalers to adopt the principle of billing bulk water charges directly to interstate owners at billing date, while Schedule 2 Step 7(2) permits SOD retailers to impose and recover charges under Destination State law. The Protocol does not create a uniform billing law; instead it directs behaviour and leaves enforceability to State legal frameworks for billing and debt recovery.

In short, the Protocol functions as an inter-jurisdictional administrative overlay that preserves State sovereignty over entitlement transfer law and enforcement of unauthorised use, while binding retailers and the Authority to common accounting and reporting processes so that basin-wide registers and caps remain coherent after interstate tagging events.

The instrument text itself contains limited chronological metadata and express revocation language that informs its immediate amendment history and status relative to predecessor instruments.

• Making and authentication: The Protocol was made by the Murray-Darling Basin Authority, in consultation with the Basin Officials Committee and after consideration of advice from persons nominated by Contracting Governments under subclause 6(3) of Schedule D to the Agreement (preamble). It was authenticated by Rob Freeman, Chief Executive of the Authority, who signed and dated the Protocol authentication on 30 August 2010 with a signature block dated 7 September 2010 (preamble). The Protocol commences on the day after it is registered (clause 2).

• Revocation of prior protocols: Clause 3(1) revokes all protocols made under paragraph 6(1)(f) of Schedule D to the Agreement before 1 December 2009 that apply only to interstate tagged trade of entitlements. Clause 3(2) provides that any earlier protocol that dealt with interstate tagged trade alongside other matters has no application insofar as it dealt with interstate tagged trade. Those clauses thus expressly retire earlier, exclusively interstate-tagging protocols and carve out the tagging parts of mixed prior instruments.

• Review triggers and amendment obligation: Clause 9 provides a mechanism that can lead to review and potential amendment. An independent auditor appointed under subclause 16(5) of Schedule D may consider the Protocol's operation and, where appropriate, recommend a review by the Authority (clause 9(1)). Clause 9(2) imposes a duty on the Authority to review, and if appropriate consider amending, the Protocol in specified circumstances: if the Agreement is amended in a way relevant to interstate transfers (clause 9(2)(a)); if Commonwealth or State legislation or instruments are made or amended in ways that may affect interstate transfers (clause 9(2)(b)); if reports about the operation of Schedule D or the markets for interstate transfers prepared under clause 18 of Schedule D indicate a review is appropriate (clause 9(2)(c)); or if an independent auditor recommends a review in connection with their appointment (clause 9(2)(d)). These are the only express amendment or review triggers contained in the Protocol text.

• No further textually recorded amendments: The Protocol as provided contains no other amendments, schedules, or subsequent variations. It explicitly contemplates future amendment following the processes described, but no later variations or replacement instruments are contained within the supplied text.

Practical point for users: because clause 9 obliges the Authority to review the Protocol in response to changes in the Agreement, Commonwealth or State law, or relevant reports, parties should monitor amendments to the Murray-Darling Basin Agreement, the Water Act 2007 and relevant State legislation, along with audits and reports prepared under Schedule D, to identify when formal reviews or amendments may be initiated.

The Protocol text contains no references to judicial decisions, litigation, or case law. It does not incorporate or cite any court determinations, nor does it record challenges to its provisions or to prior protocols. The Protocol instead contemplates administrative oversight and independent audit processes (clause 9(1); Schedule 1 Step 5(6)) and leaves disputes involving entitlement transfers and unauthorised use to State law (Schedule 2 Step 5(2)(a); Step 3(5)).

What the absence means in practice:

• No case law precedent embedded in the instrument. Because the Protocol establishes administrative procedure rather than creating new substantive rights or offences, the text relies on institutional compliance mechanisms and State enforcement, which are the likely loci of any litigation. Any litigation that might arise in future would almost certainly involve State law issues , for example, disputes over entitlement transfers, billing disputes under State charging regimes, or State enforcement actions for unauthorised use , rather than direct challenges to the Protocol itself, unless a party could mount a public law challenge to the Authority's exercise of power under the Water Act or the Agreement.

• Dispute resolution channels are administrative and intergovernmental. The Protocol provides for reconciliation, reporting to the Interstate Water Trade Taskforce and referral to the independent auditor (Schedule 1 Step 5(6)). These channels suggest a preference for administrative resolution and systemic oversight rather than litigation as a first resort.

For legal practitioners and researchers, the absence of litigation referenced in the Protocol means analysis of how these provisions operate in real disputes will require sourcing State-level case law and any decisions touching on inter-jurisdictional tagging in water markets, which are not contained in the Protocol itself. Within the Protocol’s text, there is no litigation history to summarise or rely upon.

The Protocol contains many procedural details and cross-jurisdictional dependencies that can generate traps for practitioners and market participants. Below are concrete operational "gotchas" drawn from the text and the mechanisms they create.

1. "Application" excludes entitlement transfers

• The Protocol’s definition of "application" expressly excludes an application to transfer an entitlement (clause 5). Practically, an applicant who intends to change legal ownership of an entitlement must pursue State transfer mechanisms separately. Failing to distinguish tagging (administrative permission to extract elsewhere) from transfer (title change) can cause process failure and mismatched records.

2. Multiple destination zones prohibited at tagging

• The SOO retailer must verify that, if approved, the entitlement will not be tagged to a location in more than one zone of destination (Schedule 1 Step 2(1)(d)). This prevents simultaneous multi-zone extraction under one tagged entitlement. Applicants or brokers who expect flexible multi-zone extraction may find this restrictive and must structure contracts accordingly.

3. Fees must be paid before tagging takes effect

• The SOO retailer must ensure that all relevant fees have been paid prior to updating records to show an entitlement is tagged and recording the effective tagging date (Schedule 1 Step 4(2)(a)-(c)). If fees are outstanding or billing is ambiguous, the tagging may not be recorded, with consequent effects for delivery and cap adjustments.

4. Delivery can be refused for lack of SOO credit, and extraction becomes "unauthorised"

• An SOD retailer must not deliver water unless SOO allocation account credit suffices (Schedule 2 Step 2(3)). If water is nevertheless extracted in the Destination State when SOO credit is insufficient, the Protocol requires the Destination State to treat the extraction as unauthorised use (Schedule 2 Step 3(4)-(5)). The practical risk: where physical control over extraction points is limited, extractors may inadvertently or intentionally take water without matching SOO accounts, exposing them to State enforcement. Responsibility for preventing extraction lies with the SOD retailer but enforcement/punishment is under State law.

5. Reconciliation timelines are tight and discrepancies can escalate rapidly

• Licensing authorities must send records within 7 days after month end (Schedule 1 Step 5(1)); the Authority then has 14 days to report discrepancies, and licensing authorities have 14 days to explain them (Schedule 1 Step 5(3)-(5)). If unresolved within the month they must be escalated to the Taskforce and independent auditor (Schedule 1 Step 5(6)). Failure to meet these deadlines can lead to escalation and audit scrutiny. The 1 ML allowable discrepancy per transfer tolerance (Schedule 1 Step 5(4)(a)) is narrow , in high-frequency, low-volume trades small misallocations can trigger reports.

6. Different charging points and potential double-charge confusion

• The Protocol envisages SOO wholesalers billing bulk charges to interstate owners (clause 7(2)) and SOD retailers recovering charges from destination recipients under Destination State law (Schedule 2 Step 7(2)). Parties must be explicit about which actor is responsible for which charge to avoid double billing or under-recovery. The SOO retailer’s duty to advise wholesalers (Schedule 2 Step 7(1)) is an important notification step; missing it may leave wholesaler billing based on older ownership records.

7. Authority adjustments have multiple downstream effects

• The Authority must make consequential adjustments to the cap, valley accounts and salinity registers on tagging (Schedule 1 Step 4(1)(b)-(d); Schedule 2 Step 6(2)). Changes in cap or valley accounting following tagging can affect entitlements, accounting in other valleys, and salinity obligations. Parties negotiating trades must anticipate that tagging will prompt these administrative changes, and that those changes can affect other users' rights and environmental compliance metrics.

8. Notices are in writing, but may be electronic under a separate Act

• Clause 6(1) requires notices in writing, but the accompanying note points to s9 of the Electronic Transactions Act 1999. Parties must ensure their notice systems comply with both the Protocol’s written requirement and the Electronic Transactions Act’s criteria for valid electronic notices, including identification, integrity, and record-keeping.

9. The Protocol delegates unresolved enforcement and sanctions to State law

• Because the Protocol does not itself specify penalties for many breaches (see "Penalties and enforcement"), parties cannot rely on the Protocol to provide a cross-border remedy. For example, where an unauthorised extraction occurs, the remedy is to be found under Destination State law (Schedule 2 Step 3(5)). Before trading or tagging, market participants must understand relevant State sanctions for unauthorised use, debt collection, and transfer refusals.

10. Transaction identification numbers and record integrity

• The SOO retailer must allocate a transaction identification number and forward it to the SOD retailer when an application is not prohibited (Schedule 1 Step 1(2)(d)). Failure to correctly use or communicate transaction IDs can complicate reconciliation, create apparent discrepancies, and increase the risk of audit escalation.

11. "Tagging takes effect" is a recorded date with practical consequences

• SOO retailers must record the date on which tagging takes effect and advise SOD retailer and the Authority (Schedule 1 Step 4(2)(c)). That effective date triggers Authority entries and cap/valley/salinity adjustments. Parties should confirm effective dates in writing and ensure fees and conditions are observed as of that date.

Mitigation approach for practitioners: maintain clear checklists aligned to Schedule 1 and Schedule 2 steps, confirm the legal framework in both Origin and Destination States (including charging and unauthorised use regimes), negotiate allocation of fees and charges in contracts, and build procedures for quick monthly reconciliation and rapid response to Authority discrepancy reports.

The Protocol is a procedural instrument: compliance consists of observing the steps and timelines in Schedule 1 (processing applications and reconciliation) and Schedule 2 (accounting for tagged allocations), and meeting the obligations set out in clauses 5-9. Below is a practical, step-by-step compliance roadmap grounded in the Protocol’s text.

Pre-application preparation (applicants and brokers)

• Distinguish tagging from transfer. Prepare separate processes for an application to tag (protocol application) and any application to transfer entitlement title (State transfer process). The Protocol’s definition of "application" excludes entitlement transfers (clause 5).

• Documentation and fees: ensure ownership evidence, proof of power to deal with allocations, and readiness to pay relevant fees in accordance with State of Origin requirements. SOO retailers will verify ownership and the power to deal (Schedule 1 Step 2(1)(a)-(b)) and must ensure fees are paid before tagging is recorded (Schedule 1 Step 4(2)(a)).

Application lodging and initial checks (SOO retailer duties)

• Applicants must lodge tagging applications with the SOO retailer (Schedule 1 Step 1(1)). SOO retailers must immediately note the application, verify it is not prohibited by any protocol concerning transfer limits (Schedule 1 Step 1(2)(a)-(c)), allocate a transaction ID and forward a copy and the ID to the SOD retailer (Schedule 1 Step 1(2)(d)).

• SOO retailers must promptly do substantive checks: ownership, power to deal, transfer limits for the trading zone, and ensure not tagging an entitlement to more than one destination zone (Schedule 1 Step 2(1)(a)-(d)). If the SOO retailer determines the application may not be approved, it must promptly notify the SOD retailer and the applicant (Schedule 1 Step 2(2)).

Destination assessment and conditions (SOD retailer duties)

• Upon receiving notification that an application may be approved, the SOD retailer must promptly determine whether it can deliver the water and whether, in view of relevant matters, it will approve the application subject to Step 4 (Schedule 1 Step 3). If the SOD retailer approves, it must notify the SOO retailer and the Authority and notify the applicant of any delivery conditions (Schedule 1 Step 4(1)(a)-(b)). Ensure that any conditions attached to delivery are documented and communicated to applicants in writing.

Finalisation, record updates and Authority entries

• After SOD approval and confirmation that fees are paid, the SOO retailer must update its records to show the allocation is tagged, record the effective tagging date and advise the SOD retailer and the Authority (Schedule 1 Step 4(2)(b)-(c)). The Authority must record approved tagging on the Transfer Register and adjust the cap, valley accounts and salinity registers as required (Schedule 1 Step 4(1)(a)-(d)).

Monthly reconciliation and discrepancy handling

• Licensing authorities must send copies of all records relating to interstate tagging for each preceding month to the Authority within 7 days after month end (Schedule 1 Step 5(1)). The Authority will compare records with previous months and the Transfer Register and must record discrepancies other than allowable ones (Schedule 1 Step 5(2)-(3)). Licensing authorities have 14 days to explain discrepancies and must consult with the Authority to resolve them (Schedule 1 Step 5(5)). If unresolved within the month, the Authority will inform the Interstate Water Trade Taskforce and report the discrepancy to the independent auditor (Schedule 1 Step 5(6)). To comply: maintain robust monthly record-keeping, designate a point of contact for discrepancy responses, and ensure explanations and corrective steps can be provided within 14 days.

Quarterly reporting

• The Authority will issue quarterly interstate transfer reports within 30 days after the end of each quarter (Schedule 1 Step 6). Organizations should be prepared to provide requested data to the Authority and to review those reports for accuracy.

Accounting for tagged allocations (Schedule 2 compliance steps)

• When an allocation is made, the SOO retailer must make the allocation into the SOO allocation account and promptly advise the relevant SOD retailer of the consequent credit (Schedule 2 Step 1(1)-(2)). The SOD retailer must establish an allocation account in the State of Destination for the entitled person (Schedule 2 Step 1(3)).

• Orders: persons entitled in the Destination State must place orders with the SOD retailer (Schedule 2 Step 2(1)). The SOD retailer must check SOO allocation account credit and must not deliver unless sufficient credit exists (Schedule 2 Step 2(2)-(3)). Implement controls to validate SOO account balances before delivery and to refuse delivery where credit is insufficient.

• Recording and transfer mechanics: SOD retailers must record orders as first estimates of use and adjust SOD accounts; they must notify SOO retailers promptly. Once notice is given, the SOO retailer must debit its allocation account, notify the SOD retailer of reduced credit, and the SOD retailer must credit the SOD allocation account equivalently (Schedule 2 Step 3(1)-(3)). Ensure systems can synchronise debits/credits within these notification sequences and support first estimates being corrected post-meter readings.

• Metering and revisions: If an order is altered before delivery or meter reads indicate usage that should have been attributed to a tagged allocation, the SOD retailer must revise estimates, adjust its allocation account, promptly advise the SOO retailer, and adjust delivery and SOO allocation accounts accordingly (Schedule 2 Step 4). Maintain metering accuracy and billing reconciliation processes to reconcile estimates to actuals.

• Transfers between allocations: Applications to transfer allocations from tagged entitlements to another person or vice versa must be made to the SOO retailer and decided in accordance with State of Origin law (Schedule 2 Step 5(1)-(2)). SOO retailers must notify SOD retailers of approvals and account adjustments (Schedule 2 Step 5(3)-(4)). Coordinate transfer applications with State transfer registries and legal counsel to ensure compliance with State law.

• Monthly delivery reporting: SOD retailers must, within 7 days after the end of a month, notify the Authority of the volume of water delivered pursuant to all tagged allocations from each State of Origin in the preceding month (Schedule 2 Step 6(1)). SOO and SOD retailers must be prepared to provide and reconcile these monthly reports.

Charges and billing compliance

• SOO retailers must keep wholesalers informed of tagged allocations that may affect recoverable charges (Schedule 2 Step 7(1)). Wholesalers should adopt the principle of billing bulk water charges directly to interstate owners as at billing date (clause 7(2)). SOD retailers may impose and recover charges under Destination State law from the person entitled to receive the tagged allocation (Schedule 2 Step 7(2)). To comply, clarify contractual allocation of billing responsibilities and ensure State law charge recovery mechanisms are understood and in place.

Notices and record format

• Notices under the Protocol must be in writing (clause 6(1)), though the Protocol acknowledges written notices may be given electronically consistent with s9 of the Electronic Transactions Act 1999. Ensure notice practices (electronic or paper) meet statutory requirements for identification and record integrity under that Act.

Audit readiness and review triggers

• Be aware that an independent auditor may review the Protocol’s operation and recommend a review (clause 9(1)), and the Authority must review the Protocol where specified triggers occur (clause 9(2)). Maintain auditable records and internal controls so that any audit or review can be supported.

Practical checklist for implementation

• Establish documented procedures mapping to Schedule 1 Steps 1-6 and Schedule 2 Steps 1-7.
• Implement control systems for transaction IDs, effective tagging dates, and synchronous debiting/crediting between SOO and SOD accounts.
• Maintain metering accuracy processes and capacity to revise first estimates promptly.
• Ensure billing systems are aligned with State law responsibilities for wholesalers and retailers; document who pays what.
• Appoint liaison officers for Authority reconciliation queries and auditor inquiries; ensure monthly records are prepared and sent within 7 days after month end.
• Confirm statutory notice formats and electronic notice compliance under the Electronic Transactions Act.

Following these steps will align operational practice with the Protocol’s specified duties, timelines and required cross-jurisdictional coordination.