Ireland splits customs declarations across two systems. AIS (Automated Import System) processes inbound declarations and AES (Automated Export System) processes outbound ones. Both are electronic-only, UCC-compliant and run on Irish Revenue infrastructure, but each follows its own AIS and AES declaration workflow and lifecycle. Here is how the two pipelines differ and where automation helps most.
The Data Layer
AIS is built on the EU Customs Data Model (EUCDM). Its declaration types include:
- H1: standard release into free circulation (the most common)
- H2 to H7, I1 and I2: scenarios such as customs warehousing, temporary admission and low-value consignments AES covers three pieces of data: the export declaration, the exit confirmation and, depending on destination and goods, a safety and security dataset.
The AIS Lifecycle
An AIS declaration is submitted electronically, registered by Revenue and passed through risk assessment. It then moves through a defined sequence of statuses until it reaches one of two outcomes: release, or a hold for documentary or physical checks. For the business side of this split, see the Automated Import System vs Automated Export System comparison.
The AES Lifecycle
An AES declaration is lodged before or at departure. Revenue or the exit point then confirms the goods have left, and an exit certification is generated. Side by side, the two flows look like this:
AIS: submit > register > risk assessment > status updates > release OR hold for checks
AES: lodge (before or at departure) > exit confirmed > exit certification issued
The key difference is timing. AES data must be in place before goods leave Ireland, so export paperwork has to be ready early.
Automating Both Directions
Running two separate tools means duplicate data entry and two places to check status. A shared validation layer fixes that. iCustoms runs commodity classification, EORI validation and declaration submission through the same automated checks for imports and exports, from one interface, with one status view across both.
Troubleshooting tip
If software handles AIS, don't assume it handles AES. Confirm both workflows before integration.
Building or reviewing a customs workflow for Ireland? Watch a demo to see both pipelines run side by side.
Top comments (0)