Advance Passenger Processing
Overview
Advance Passenger Processing (APP) is a 2-way interface between an airline’s Departure Control System (DCS) and our immigration databases.
It confirms before boarding to the carrier that a traveller has:
- authority to travel to Australia or to depart Australia
- a valid visa or appropriate travel documents.
Visa applicants and visa holders should tell the department if their passport details have changed.
APP reporting enhances the Australian Government’s ability to target security concerns and streamlines the border clearance process for travellers.
The Migration Act 1958 (the Act) (sections 245L and 245LA) says airlines must report all passengers and crew arriving into and departing from Australia. This includes all transit travellers.
Regular passenger transport airlines operating international flights to and from Australia do this using the APP system or Carrier Portal.
Completing APP reports enables airlines to meet their legislative obligations and confirms whether travellers have authority to travel to Australia.
To see how we handle the personal information we collect before an individual travels through Australia’s border, see the Advance Passenger Processing Privacy Statement.
It is also available in following different languages:
- Advance Passenger Processing Privacy Statement - Arabic
- Advance Passenger Processing Privacy Statement - Cantonese
- Advance Passenger Processing Privacy Statement - Chinese (simplified)
- Advance Passenger Processing Privacy Statement - Farsi
- Advance Passenger Processing Privacy Statement - French
- Advance Passenger Processing Privacy Statement - Hindi
- Advance Passenger Processing Privacy Statement - Indonesian
- Advance Passenger Processing Privacy Statement - Japanese
- Advance Passenger Processing Privacy Statement - Korean
- Advance Passenger Processing Privacy Statement - Malay
- Advance Passenger Processing Privacy Statement - Spanish
- Advance Passenger Processing Privacy Statement - Thai
- Advance Passenger Processing Privacy Statement - Vietnamese
Airline obligations
Airlines must:
- provide advance passenger reports on all passengers and crew, and
- not carry undocumented or inadequately documented passengers to Australia.
Provide advance passenger reports
It is the responsibility of carriers to provide advance passenger reports on all passengers and crew arriving and/or departing (including transiting) Australia. Each missed report may be an offence.
The maximum penalty, upon conviction, for not reporting APP is either AUD43,680 or AUD21,840. This depends on whether the missed reporting is found to be intentional or not. All other instances of failing to report may attract a penalty of AUD3,640 per offence.
Do not carry undocumented or inadequately documented passengers
Airlines must check a passenger’s authority to enter Australia using APP.
When APP is down, you must use the TIETAC check, which is part of the Electronic Travel Authority System (ETAS) to confirm visa status.
If a carrier brings an inadequately documented or an undocumented passenger to Australia, they may be liable, upon conviction, to a fine of AUD36,400. Instead of prosecution, carriers may elect to pay a prescribed penalty of AUD9,100 for an infringement notice.
Note: The airline can be liable for both infringement fines for the same passenger or crew.
See the Advance Passenger Processing (APP) Arrivals and Departures manual.
Avoiding infringements
Airlines can avoid infringements by:
- using APP to confirm that every person has authority to travel to, from and through Australia prior to departure through the 'OK to Board' response. This includes infants and children with or without a separate travel document and boarding pass
- using alternative methods to notify APP when the system is down
- reviewing your ‘Missed APP’ report.
Reporting when Advance Passenger Processing system is down
You still need to complete advance passenger reporting when the system is down (APP system outage).
You must report every flight:
- Planned outages: use the Carrier Portal.
- Unplanned outages: try to resolve through the airline's IT support channels, or if unresolved, email BOC@abf.gov.au.
Reporting using The Carrier Portal
If you need access to Australia’s Carrier Portal to process Crew Travel Authority (CTA), APP, or to run your airline’s APP Transaction report, contact appwebsite@abf.gov.au.
Most airline users are able to have their Carrier Portal account set up by their airlines’ own Carrier Portal Administrators. You should send further requests for password resets and access to the APP website to appwebsite@abf.gov.au.
Emailing the Border Operations Centre (BOC)
Email BOC@abf.gov.au with:
- direction of the flight (arrival or departure)
- flight number
- arrival and departure airports
- arrival and departure date or time
- number of travellers, not APP reported.
The following additional information will also help us when resolving a system down issue:
- expected length of the ‘system down’
- what caused the system down
- any other relevant information.
Refer to the Systems Down Procedure in the relevant APP Manual for more instructions on how to board passengers when the APP is down.
Reviewing your ‘Missing APP’ report
We send daily reports to airlines with advice on their missed APP reports for all of their travellers.
The 'Missing APP' report is an opportunity for your airline to:
- examine your records to determine if any travellers listed were in fact APP reported (and to gather evidence of this).
- investigate the cause of any missing APP report.
- review your processes for potential improvements to APP reporting.
The report will include information on:
- the date of the traveller's movement
- flight number
- family and given name
- date of birth
- gender
- whether the traveller was a passenger or crew
- passport or travel document number
- departmental reference number.
We use these reports to inform infringement processing.
Paying infringements
A carrier has 28 days to either:
- pay an infringement notice, or
- submit a withdrawal request.
Note: The ABF has reduced the number of reasons for the withdrawal of an infringement notice. The ABF will no longer withdraw infringement notices when:
- the failure to APP was due to the introduction or enhancement of IT systems
- there was an IT issue that prevented APP reporting, and the airline took corrective action to fix the cause of the non-reporting.
Paying an infringement
If the carrier cannot complete payment within 28 days, complete Form 1466 – Request for Extension of Payment Date. You should include any relevant evidence.
Ordinarily, we will not grant an extension of the payment date to allow a carrier to investigate the cause of missed APP reports.
Requesting a withdrawal of an infringement
Carriers must submit withdrawal requests by completing Form 1467 – Request for Withdrawal of Infringement Carriers should email this form with any supporting evidence to appinfringements@abf.gov.au
We will consider all withdrawal requests in-line with the guidelines set out in the APP Infringements Manual for Carriers.
If your enquiry is about the infringement regime, contact appinfringements@abf.gov.au.
Responding to a ‘Do Not Board’ (8502) directive
A ‘Do Not Board’ directive means we could not find a valid record based on the information entered. It could mean:
- the passenger or crew genuinely does not have a valid visa for travel to Australia
- the information was not entered correctly.
A check-in agent should:
- check and resubmit the information using accurate data from the bio-data page of the traveller’s travel document. This is important as most mistakes occur in the nationality code, travel document number or the spelling of the names
- then seek assistance from the BOC.
If required, an airline can use TIETAC to apply for an Electronic Travel Authority.
Using the 'A' and 'G' overrides
Airlines can use either an 'A' or 'G' override when they receive '8502 - <DO NOT BOARD>' directive in the Advance Passenger Processing (APP) system.
'A' (airline) override
After an ‘8502 - <DO NOT BOARD>’ directive is generated, an ‘A’ override will allow an airline to submit passenger's information to the APP and board a passenger only in certain circumstances.
Inward APP
An airline may use an ‘A’ override to board a traveller when:
- travellers are transiting Australia and are from a country eligible for Transit Without Visa (TWOV). They must meet the following criteria:
- have a confirmed ticket to leave Australia to travel to a third country within 8 hours of arriving
- have a valid travel document to enter the country of destination
- must not need to clear immigration or leave the airport transit lounge for any reason before boarding their onwards flight.
- military personnel are travelling on military orders and hold military identification (certain countries only). This includes accompanying dependants.
- positioning air crew
- residents of Australia are returning on an ‘Authority to Return’ or ‘Return Endorsement’ - but only under STRICT CONDITIONS. For more details, see Advance Passenger Processing (APP) Arrivals and Departures manual.
Outward APP
An airline may use an 'A' override to board a traveller in certain circumstances when:
- they have a New Zealand passport – current, not expired (not on the system)
- they have an Australian passport – current, not expired (not on the system)
- they have no travel document, however their entry to destination and transit country has been approved
- they are military personnel travelling on movement orders with military ID.
For more detailed information about when you may use an ‘A’ override, see the Advance Passenger Processing (APP) Arrivals and Departures manual.
We recommend that airlines' Departure Control Systems (DCS) have an ‘A’ override capability.
'G' (government) override
An airline should use the 'G' override when:
- BOC has given the airline authority to override an APP response
- APP is unavailable and the airline has contacted BOC to confirm passenger details
- BOC has cleared a passenger’s details after a negative directive from APP, and airline subsequently received a positive boarding directive.
Appropriate use of the 'A' or 'G' overrides could prevent an airline from receiving an infringement.
The rules are different for arrivals and departures APP, Airlines should refer to more specific information about using 'A' and 'G' overrides in the Advance Passenger Processing (APP) Arrivals and Departures manual.
Checking in traveller with a valid visa in an old passport
Passengers may present at check-in with 2 passports – a valid passport and an expired or alternate passport containing a valid Australian visa.
Use the details of the new valid passport for checking in the passenger into the APP system. This applies, even if we issued the person’s visa on the expired or a different passport. All passport information entered into the APP system should only be the current, valid passport.
This applies to all visas, both paper and electronic, except for the Electronic Travel Authority (ETA).
You have a new passport
You need to tell us when you get a new passport so that we can link it to your visa or application. The quickest way to do this is to update your passport details in your ImmiAccount.
Note: This excludes holders of ETA 601. If you get a new passport, you need to apply for a new ETA using your new passport. We cannot transfer your ETA to a new passport.
Update Details - ImmiAccount
- Login to ImmiAccount
- Select your application
- Select ‘Edit’ or ‘View details’ to go to your ‘Application home’ screen
- Select ‘Update details’
- Select 'Change of passport details'
- Select the applicant
- Enter the new passport details
- Enter the reason for the change
- Select Submit
We will link your passport to your visa or application within 72 hours.
If you have not used ImmiAccount before, you can Create an ImmiAccount. You can then import your application to use the online change of passport form.
You can import an application into ImmiAccount if:
- you have an in-progress paper application
- Third part lodged an online application on your behalf, for example, a Migration Agent or Legal Practitioner.
For more information, see Import an application.
Passenger has notified Home Affairs of new passport
The APP system will give an 8501 – ‘OK TO BOARD’ response if:
- we have recorded the APP notification in the person’s record in our systems
- the visa is still valid
- the new passport is issued in the same personal details, including nationality, as the expired or a different passport.
Passenger has not notified Home Affairs of new passport
The APP system will not return an ‘OK TO BOARD’ response if:
- the passenger has not notified Home Affairs of the new passport
- the person’s personal details in the new passport are different.
If the passenger cannot link the new passport to the person’s record, you will need to contact the BOC.
After the details are updated:
- the ‘OK TO BOARD’ message will be generated using the new passport
- airlines will not receive a 'Contact BOC' response whenever the passenger presents this passport for international arriving or departing flights for Australia. This will apply for the life of this travel document.
- the APP system will find the links for Australian dual nationals for their international flight check-in. Linking is available for Australian/foreign and foreign passports of the same nationality.
- advise passengers to use the passport that they used at check-in when using SmartGates. The check-in process will facilitate SmartGate clearance as the APP report will pre-populate the passport and flight details. This will help with faster processing.
Passenger has an ETA
An ETA is lined to an ETA-eligible passport. The passenger must be travelling on that passport to get an 'OK TO BOARD' response. An ETA is not transferable to a new passport. If the passenger is travelling on a new ETA-eligible passport, they should make an application for an ETA using the new passport's details.
Processing passengers utilising transit without a visa facility
To be eligible for transiting Australia without a visa, the person must:
- be TWOV eligible
- enter Australia by aircraft
- hold a confirmed onward booking to leave Australia within 8 hours of the person's arrival in Australia
- hold documentation necessary to enter the country of their destination
- remain in the transit lounge (if they want to clear immigration for any reason, they must obtain a visa in advance of travel).
The APP system allows 2 movement indicators, ‘T’ for transit and ‘M’ for movement.
You should only use the ‘T’ flag for passengers who meet the above transit criteria. Even if the passenger is 'OK TO BOARD', these passengers should not cross the border or stay longer than 8 hours without a valid visa. If they do, or the airline may receive a fine.
Airlines incur fines of AUD8,250 per offence for the carriage of inadequately documented or undocumented passengers to Australia under s229 of the Migration Act 1958.
More guidance for checking-in travellers eligible for TWOV is in the Advance Passenger Processing (APP) Arrivals and Departures manual.
Processing family passports
If all family members are travelling, airlines must submit an APP request and get an 'OK TO BOARD' for each member, using their full details.
Check-in agents should be aware that children on a family passport cannot travel without the primary holder.
If travellers present family travel documents, airlines must submit an APP request for each family member using their full details.
For more information, see the Advance Passenger Processing (APP) Arrivals and Departures manual.
Processing an outward APP report for a dual national
If directed by the APP system, provide both passports' information as requested to BOC@abf.gov.au.
The BOC officer will update departmental records. Once you resubmit, the APP system response will return ‘OK to Board’ for either passport.
Processing crew
Processing crew that are transiting Australia
Operational crew cannot transit Australia.
Airlines must process crew that are transiting Australia as passengers, with the PAX/Crew indicator set to either 'P' for passenger or 'X' for Positioning crew. The airline will receive a 'Do Not Board' directive or a 'Contact BOC' message if the PAX/Crew indicator is not set properly.
Processing APP for Positioning Crew arriving into Australia
Airlines who process positioning crew as passengers using the 'P' (passenger) code may incur the Passenger Movement Charge. To avoid this, airlines should use the 'X' code for positioning crew.
The 'X' for positioning crew works the same as the 'C' code for operating crew. It will allow positioning crew to use their CTA for travel.
Crew holding only a CTA will return a 'Do Not Board' directive from the APP system if airlines process crew using the ‘P’ code. The airline can perform an 'A' override to complete the APP transaction and receive an 'Override Accepted' message.
Processing last minute crew changes
Airlines must report all air crew, both operational and positioning, through the APP system before boarding an arrival or a departure flight. This includes crew with Australian or New Zealand passports.
Many airlines have a crewing function based overseas that processes and schedules crew, and will handle changes.
If there is an emergency crew change without enough time to contact the overseas crewing function, a staff member based in Australia can access Australia’s Carrier Portal. That staff member can submit an APP for a last-minute change.
Most crew are not processed through an airline Departure Control System (DCS) system like passengers, but airlines can process crew through Australia’s Carrier Portal. If airlines process crew through their DCS as either Operational 'C'; or Positioning Crew 'X', we will accept this.
Adding or amending services
Adding or amending scheduled services
Airlines must enter all new flight data into the global communications network – Societe International de Telecommunications Aeronautiques (SITA) – via the Official Airline Guide (OAG).
Loading a flight by an airline via OAG to SITA, and for SITA to load it to the Government Gateway can take up to 2 weeks. Airlines should only use this process if they have enough time before the first flight (that is, 2 weeks prior to first flight).
Adding or amending unscheduled services manually with TIETAYT
If an unscheduled flight will be operating within 2 weeks, airlines must load the flight manually using the TIETAYT command. This option is instant and can be performed at any time.
Airlines must have Electronic Travel Authority System (ETAS) capability to use the TIETAYT command:
- type TIETAYTA to establish a flight schedule
- enter flight data – airlines should ensure that they include all ports at where the flight stops
- type TIETAYTD to confirm that the new flight schedule has successfully loaded.
Note: Penalties may apply when airlines fail to comply with APP reporting obligations. This includes, but is not limited to when:
- the airline fails to make an APP report
- the information for an APP report was incorrect or incomplete at the time of reporting and there was no subsequent APP report made in compliance with APP reporting obligations
- the APP report was not submitted before the legislative deadline.
Airlines should also tell BOC and give the following details:
- flight number
- departure and arrival times
- departure and arrival ports.
They should tell BOC by emailing BOC@abf.gov.au.
If an airline experiences problems loading a flight via the TIETAYT command, they should contact:
SITA Help Desk
Phone: +61 1800 300 043
Email: pss-helpdesk@sita.aero
Contacting the Border Operations Centre (BOC)
The BOC is available to help airlines with boarding issues, including Advance Passenger Processing (APP) for international flights. The BOC is available 24 hours a day, 7 days a week.
Phone: +61 1300 368 126 or +61 (02) 6264 1301 – select '1 EOC/BOC'.
Email: BOC@abf.gov.au
SITATEX: CBRIXCR
Airlines should send SITATEX messages no later than 45 minutes prior to the flight's departure time. This ensures sufficient time for the BOC to respond to enquiries. Our systems require full passport information when updates happen. This includes:
- Family name
- Given name(s)
- Other name(s)
- Date of birth
- Sex
- Flight number
- Country of birth
- Nationality
- Passport number (old or new)
- Date of issue of passport
- Date of expiry of passport
- Issuing authority
- Details of problem.
It is not necessary for airlines to make follow up calls to the BOC after they have sent a SITATEX message.
More information
If your enquiry is about the infringement regime, contact appinfringements@abf.gov.au
Disclaimer: some of the information on this page and in the APP Arrivals and Departures manual may be superseded during a national emergency.
