Comptroller-General of Customs Instrument of Approval No. 1 of 2017 – Advance Passenger Processing System

The instrument concentrates on three core concepts: (1) approval of an electronic system, (2) the class of reporting entities and flights, and (3) the recipient and content of the reports. The approval is explicitly granted “under subsection 64ACA(2)(b) of the Customs Act 1901 and for the purposes of subsection 64ACA(2) of the Act”, which locates the instrument within a specified statutory framework. The document names the system to be approved as “Advance Passenger Processing”. The approval is limited in scope to operators “of an aircraft that is due to arrive, from a place outside Australia, at an airport in Australia”, and it expressly covers any airport that is the first or any subsequent airport of the flight, thereby including through‑flights and transfers where the aircraft arrives at multiple Australian airports on the same flight sequence.

The reporting obligation, as expressed in the instrument, is similarly narrow and concrete. The system is approved “to report to the Department of Immigration and Border Protection on each passenger who will be on board the aircraft at the time of arrival at the airport.” That phrase establishes three textual elements: the reporting recipient (the Department of Immigration and Border Protection), the object of the report (each passenger), and the temporal reference point for the passenger list (passengers “who will be on board the aircraft at the time of arrival at the airport”). The wording places the focus on passenger presence at arrival rather than at departure or at an earlier point. The instrument does not itself define “passenger” or specify which data elements constitute an acceptable report.

The instrument is procedural rather than substantive. It does not include technical specifications, security or privacy requirements, or operational procedures. Nor does it create express exceptions, transitional arrangements, or enumerated duties beyond the single authorisation. The approving officer is identified by name and office, and the instrument is dated and given a commencement date, which together situate the approval in time and under the delegated function of the Comptroller‑General exercising powers under s 64ACA(2)(b). The phrase “whether it is the first or any subsequent airport of the flight” is a discrete substantive inclusion, confirming coverage of any arrival at any Australian airport on a flight that originates outside Australia and makes one or more domestic stops.

The instrument identifies the primary affected party as “the operator of an aircraft that is due to arrive, from a place outside Australia, at an airport in Australia.” That phrase includes, on its face, any legal or natural person who is the operator of an aircraft in the circumstances described. The approval therefore has immediate operational relevance for aircraft operators conducting international flights to Australia, including those whose aircraft may land at more than one Australian airport during a single inbound flight sequence, because the instrument expressly states it applies “whether it is the first or any subsequent airport of the flight.”

The Department of Immigration and Border Protection is the named recipient of the reports. The instrument therefore affects that Department’s intake channels for passenger information by officially designating “Advance Passenger Processing” as an approved electronic system for receiving those reports. The instrument does not name other agencies, but its approval may have downstream effects on entities that rely on passenger information received by that Department.

Passengers themselves are affected indirectly because the instrument governs the mechanism by which their presence on an arriving aircraft is to be reported to the Department. The instrument explicitly frames the content of reports as information “on each passenger who will be on board the aircraft at the time of arrival.” The instrument does not specify what passenger data fields are required, nor does it specify how passenger consent, privacy or data retention are to be handled; those details, if applicable, must be found in other instruments or statutory provisions not included in the text of this instrument.

Other parties with an operational interest include airports and ground handlers, insofar as they are affected by airline processes for ingesting and transmitting passenger manifests. The instrument does not address their roles explicitly. Finally, the approving officer and the office of the Comptroller‑General of Customs are materially involved, because the document records the Comptroller‑General exercising the power to approve an electronic reporting system under s 64ACA(2)(b). The combination of these named parties and the terse scope of the approval identifies aircraft operators as the principal group that must engage with the approved system and the Department for passenger reporting in the specified circumstances.

The instrument itself establishes a single operative duty in a narrow textual sense: it approves “Advance Passenger Processing” as “an electronic system for the operator of an aircraft ... to report to the Department of Immigration and Border Protection on each passenger who will be on board the aircraft at the time of arrival at the airport.” Read literally, the instrument creates an authorised electronic channel for reporting. It does not, in its own words, create or restate an independent statutory duty to report; rather, it designates an electronic system that can be used for reporting in the context of the statutory provision cited, subsection 64ACA(2) of the Customs Act 1901.

Because the instrument ties the approval expressly to subsection 64ACA(2)(b), the primary legal consequence is that the named system is an approved mechanism for the purposes of that subsection. The instrument therefore confers a right of use or an authorised status on the “Advance Passenger Processing” system in relation to the reporting task described. Whether that confers any particular legal protection, or whether use of the system discharges an operator’s reporting obligations under the Customs Act (if any such obligations exist) will depend on the content of the statutory provisions referenced in the instrument and any subsidiary instruments or departmental directions governing how reports must be made and accepted.

Key textual duties and temporal parameters that the instrument does state are: (a) the obligation to report relates to aircraft “due to arrive, from a place outside Australia, at an airport in Australia”; (b) the reporting covers “each passenger who will be on board the aircraft at the time of arrival at the airport”; and (c) the approval applies to any arrival at any Australian airport on the flight, “whether it is the first or any subsequent airport of the flight.” These are express parameters conveyed by the instrument and therefore define the scope of the approved reporting channel.

The instrument does not specify data content, deadlines, authentication methods, retention obligations, or a mechanism for resolving disputes about whether a particular reporting act using the system fulfils statutory requirements. Nor does it include express rights for operators such as indemnities, fee waivers, or liability limitations. The instrument’s legal effect is therefore primarily to authorise and formalise the use of the named electronic system for the particular reporting function described, leaving ancillary duties and rights to the statutory framework referenced and to separate administrative instruments or operational guidance.

The instrument does not itself set penalties, sanctions, or an enforcement regime. It is an instrument of approval that designates an electronic system for a specified reporting purpose and includes no enforcement language. The text therefore contains no express remedial provisions, penalty schedules, or enforcement processes. Because the approval is made “under subsection 64ACA(2)(b) of the Customs Act 1901 and for the purposes of subsection 64ACA(2) of the Act,” any penalties, enforcement mechanisms, compliance expectations or offences relating to reporting will arise, if at all, from the cited statutory provisions in the Customs Act or from other instruments under that Act which are not included within the text of this instrument.

Practically, this means that a reader of the instrument must consult the provisions of the Customs Act identified in the approval , in particular subsection 64ACA(2) and its related context , to determine whether failure to report via an approved system constitutes an offence, whether reporting in an approved system discharges reporting obligations, whether alternative reporting channels are permissible, and how contraventions would be enforced. The instrument’s silence on penalties leaves open several implementation questions: whether the Department of Immigration and Border Protection has administrative powers to require use of the approved system; whether the operator’s failure to use an approved system attracts civil or criminal penalties; and which officer or agency is responsible for detection and sanction of non‑compliance.

Given this absence, the instrument has a limited enforcement footprint by itself. Enforcement outcomes, and the practical sanctions that might follow from misuse, late reporting, incomplete reporting or non‑reporting, are matters governed by the wider statutory regime and any accompanying administrative instruments, directions or operational arrangements. The instrument does identify the Department of Immigration and Border Protection as the recipient, which situates enforcement and operational follow‑up responsibilities within that Department’s administrative processes, but it does not spell out the nature of those processes or the penalties that may be applied.

The instrument expressly situates itself within the framework of the Customs Act 1901 by citing subsection 64ACA(2)(b) as the statutory authority for the approval. That is the sole statutory cross‑reference within the text. The instrument therefore interacts with the Customs Act to the extent that the Act establishes the legal framework for reporting and for the Comptroller‑General’s power to approve electronic systems. The approval is “for the purposes of subsection 64ACA(2)”, so the instrument’s legal effect is necessarily conditioned on the content and scope of that subsection and any related provisions of the Act.

Beyond the Customs Act, the instrument designates the Department of Immigration and Border Protection as the recipient of passenger reports. That choice inherently engages immigration and border administration functions and suggests an operational intersection between customs reporting channels and immigration data intake. The instrument does not reference privacy, data protection, or information sharing statutes, nor does it reference aviation safety, civil aviation, or international passenger data agreements. Any such legal interactions must therefore be traced in the statutory and administrative materials outside the instrument itself.

Because the instrument approves an electronic reporting system rather than creating a standalone regime, it will interact with other laws and regulations that govern electronic systems, telecommunications, data transmission, and departmental administrative law to the extent those regimes apply to the operation of an approved electronic system. The instrument, however, does not specify these points. Practitioners will therefore need to read the instrument alongside the Customs Act and the Department’s operational directions, which together will determine how the approval interfaces with statutory duties, administrative powers, information‑sharing arrangements, passenger privacy protections, and any international obligations that govern passenger data exchange.

Finally, the instrument’s very narrow scope means its cross‑statutory interactions are limited to the legal question of what using the approved system accomplishes under the Customs Act and any statutory obligations that require reporting of passenger data. The instrument itself does not purport to displace other laws or to create exceptions to statutory obligations outside the context of s 64ACA(2). Users must therefore locate the instrument within the broader legislative and administrative environment to understand fully how it interacts with other laws.

The instrument text contains a single dated action, and the document records no amendment history within its own text. It was signed by Roman Quaedvlieg, Comptroller‑General of Customs, and is dated 22 March 2017. The instrument also records an effective commencement date: 1 April 2017. There are no further entries in the text indicating modifications, revocations, or prior approvals replaced by this instrument. The instrument’s title, “Comptroller‑General of Customs Instrument of Approval No. 1 of 2017 - Advance Passenger Processing System”, implies it is an instrument produced in the 2017 instrument series, but the document itself contains no history of amendment.

Because the instrument is confined to a single approval act, any amendment or repeal would typically occur by subsequent instrument issued under the same or related statutory powers, or by legislative amendment to the underlying statutory scheme. The present text, however, contains no such subsequent actions. Users seeking an amendment history should therefore consult official instrument registers or the public administrative records that catalogue legislative instruments and their amendments, but those records are not part of the instrument text provided.

In short, the instrument’s internal amendment history is nil: the document records the approval and commencement date, and no later modifications appear within the text. For practical purposes, practitioners should treat the instrument as a discrete approval made on 22 March 2017 with effect from 1 April 2017 and proceed to locate any later instruments or statutory amendments outside the text supplied if they need to establish whether the approval was amended or superseded.

The instrument contains no record of litigation and does not reference any judicial consideration. There are no cases, proceedings, or legal challenges mentioned in the text. Because the approval is an administrative instrument, any litigation that might arise would occur after the approval in the courts or tribunals as a result of enforcement actions, challenges to administrative decisions, or disputes about the meaning, scope or legality of the instrument or the underlying statutory power. None of those matters are recorded in the instrument itself.

Users requiring litigation history will need to search judicial and tribunal databases, or administrative law records, for any proceedings that refer to or challenge this particular instrument, its application, or the statutory powers under subsection 64ACA(2)(b) of the Customs Act 1901. The instrument’s silence on litigation means that, within the four corners of the document, there is no judicially authorative interpretation of its terms available. Any subsequent court decisions interpreting the approval, its scope, or the interplay between the instrument and the Customs Act would be external to the instrument text and are not included here.

Until and unless such external materials are located, the instrument should be treated as having no recorded litigation history within its own text. Practitioners should therefore supplement this instrument‑centric review with targeted searches of case law and tribunal decisions if litigation risk or precedent is material for compliance strategy or legal advice.

The instrument’s brevity gives rise to several practical limitations and potential pitfalls that arise from what the text includes and, notably, what it leaves unspecified. The first textual “gotcha” is the temporal definition of who must be reported: the approved system is for reporting “each passenger who will be on board the aircraft at the time of arrival at the airport.” The instrument does not address last‑minute passenger changes, diversionary arrivals, or variations between boarding and arrival manifest. Those operational contingencies are material in practice but are not dealt with in the instrument. Operators must therefore be alert to the fact that the instrument fixes a point of reference for reporting but provides no further operational guidance in circumstances where passenger composition changes between reporting and arrival.

Second, the instrument expressly includes arrivals that are the “first or any subsequent airport of the flight.” That phrase brings within scope any inbound international flight that touches down at multiple Australian airports during the same flight sequence. Operators may misread a narrower scope and neglect to report passenger presence at subsequent Australian landings; the instrument’s text specifically removes any such ambiguity by including subsequent airports, but it does not supply procedural detail on how to report when an aircraft conducts multiple arrivals on a single itinerary.

Third, the instrument approves an electronic system by name, but it does not provide technical specifications, message formats, transmission protocols, authentication requirements, or timing deadlines. The absence of technical detail is consequential: operators must rely on separate operational directives or system documentation from the Department of Immigration and Border Protection to know what to transmit and when. The instrument therefore creates an approved channel without specifying how to use it in practice.

Fourth, the instrument names the Department of Immigration and Border Protection as the recipient, which may seem unusual to some readers expecting customs agencies to be sole recipients of passenger manifests. The instrument makes no attempt to explain the interagency relationship or data‑sharing arrangements, nor does it address privacy, data retention, or overseas transfer issues. Practitioners should not assume that the approval resolves data governance concerns; the instrument is silent on those matters.

Fifth, the document does not state whether use of the approved system is mandatory or merely permissive. It approves a particular system “as an electronic system for” reporting, but it does not say whether an operator who uses that system will be taken to have fulfilled all statutory reporting obligations, or whether operators may instead use alternative approved channels. The legal consequences of using the approved system versus alternative means of reporting are not explained in the instrument.

Sixth, the instrument contains no enforcement or penalty provisions. The lack of express sanctions means that enforcement mechanisms must be sought in the Customs Act or other instruments. Relying solely on the instrument to understand legal exposure for non‑reporting or incorrect reporting would therefore be incomplete.

Finally, the approval is dated 22 March 2017 and commences 1 April 2017. Operators should be wary of assuming immediate operational readiness; the instrument gives a commencement date but no transitional guidance. Practical readiness for operators with different IT architectures, or for aircraft that operate to multiple jurisdictions with differing passenger data regimes, may require lead time that the instrument does not address.

Each of these gaps is a “gotcha” in the sense that the instrument, while creating an approved channel, leaves numerous implementation and legal questions unresolved. Practitioners and operators must therefore pair this instrument with the relevant statutory provisions and any operational guidance issued by the Department of Immigration and Border Protection to achieve full compliance.

The instrument itself specifies only that the “Advance Passenger Processing” system is approved “as an electronic system” for operators to report passenger information to the Department of Immigration and Border Protection in respect of aircraft “due to arrive, from a place outside Australia, at an airport in Australia.” Compliance therefore has two distinct dimensions: (1) the legal dimension of ensuring an operator is meeting any statutory reporting obligations under the Customs Act and related law; and (2) the operational dimension of using the approved electronic system in a way that aligns with departmental requirements.

Legal due diligence steps

• Locate and read subsection 64ACA(2) and related provisions of the Customs Act 1901 to determine whether reporting is mandatory and whether reporting via an approved system discharges any statutory duty. The instrument cites s 64ACA(2)(b) as the approving authority and links the approval to the purposes of s 64ACA(2), so those statutory provisions must be consulted to interpret legal obligations.
• Confirm whether any other legislative provisions, regulations or instruments impose timing, data field, privacy or retention obligations in connection with passenger reporting, including whether there are penalties or administrative mechanisms for non‑compliance.
• Identify any interagency memoranda of understanding that govern how the Department of Immigration and Border Protection uses or shares data received via the approved system, and assess any obligations that arise from those arrangements.

Operational steps

• Establish access to the “Advance Passenger Processing” system: contact the Department of Immigration and Border Protection to obtain official registration procedures, user credentials, technical documentation, and onboarding requirements. The instrument names the system as approved, but it contains no access process, so the Department will be the operational point of contact.
• Implement system integration and test data flows. Because the instrument contains no technical specifications, obtain and implement the Department’s technical message formats, authentication requirements, encryption and transmission protocols, and error handling procedures, and conduct end‑to‑end testing prior to relying on the system for live reporting.
• Ensure manifest accuracy at the relevant temporal point: the instrument requires reporting “on each passenger who will be on board the aircraft at the time of arrival at the airport.” Operators should establish internal processes to reconcile boarding lists, last‑minute changes, and diversion scenarios to ensure the passenger data reported corresponds to the arrival‑time composition.
• Cover multi‑stop itineraries: where a flight’s itinerary includes multiple Australian airports, ensure procedures capture passenger presence at each arrival and that the system is used as required for subsequent airports, pursuant to the instrument’s explicit inclusion of “whether it is the first or any subsequent airport of the flight.”
• Maintain logs and records: retain copies of transmissions, acknowledgements from the Department, and any error reports. The instrument does not specify retention obligations; however, retaining operational records will assist in responding to queries and in demonstrating compliance with reporting processes.
• Verify privacy and data governance compliance: because the instrument is silent on data governance, operators should ensure that internal handling, storage, and onward sharing of passenger data meets applicable privacy and security obligations under law and under any contractual arrangements with the Department.
• Review contingency arrangements: establish fallback procedures for system outages or communications failures, including protocols for re‑transmission or alternative approved reporting channels if those are permitted by the statutory scheme or departmental instructions.

Practical timing

• Note the commencement date in the instrument, 1 April 2017, and align operational on‑boarding and testing so that the approved channel is available if required by statute or departmental direction from that date. The instrument itself gives no transitional relief.

Engage legal and operational counsel

• Because the instrument does not specify whether use of the approved system discharges statutory obligations or how enforcement is to be applied, operators should obtain legal advice to clarify the legal effect of reporting via the approved system and to design operational processes that align with both the instrument and the statutory environment referenced (subsection 64ACA(2) and surrounding provisions).

In summary, the instrument identifies an approved electronic channel and a defined reporting subject and recipient; compliance requires pairing this approval with statutory provisions and departmental technical and procedural instructions. Operators should prioritise legal verification of obligations under the Customs Act, secure access and technical integration with the Department’s system, and implement operational controls to ensure accurate reporting of passengers “who will be on board the aircraft at the time of arrival.”