
A revised deadline creates a useful preparation period
Ireland's Revenue deployed AIS V2 on September 15 and initially provided a three-month transition. Its November 5 notification extends migration until January 27, 2027. From that date, the notice says new import declarations must use AIS V2. The announcement addresses the busy trading period; it does not remove the migration requirement. Revenue notification 24/2026
For a US seller supplying Ireland, the immediate question is usually how its commercial information reaches the party making the declaration. A software transition can expose weaknesses in that exchange even when the seller never operates Irish customs software itself.
The extra time is useful when it supports realistic preparation. A statement that a provider is upgrading its product is a starting point. The importer also needs confidence that its own transactions can be handled by the people and systems involved.
Follow a real order through the information chain
Consider a hypothetical order involving several product lines, a commercial invoice, packing information, and a later correction to one quantity. Different employees may maintain those records. The customs representative receives the resulting information through an agreed channel.
Following that order reveals where a migration question belongs. The seller can establish who prepares product information and who communicates corrections. The importer can confirm what its representative requires. The software provider can explain how its interface handles the relevant information.
These responsibilities should connect without being confused. A software supplier cannot verify an unfamiliar product's commercial description merely by accepting a message. An exporter cannot confirm the performance of a customs system it does not use. Each organization contributes a different part of the evidence.
This approach also makes questions more useful. Instead of asking whether everything is ready, the importer can describe a normal transaction and ask how it will be processed after the change. That gives its provider something concrete to explain or demonstrate.
Outsourcing declarations does not eliminate coordination
Revenue's preparation guidance distinguishes internally supported software from an external provider's software. It also tells traders using customs agents to ensure the agent's software can interface with AIS V2. The guidance highlights declaration content, data elements, message types, and code lists. Revenue preparation guidance
For an importer using an agent, the practical preparation can begin with that existing relationship. The agent can identify whether the information it requests from the importer is changing and explain how questions will be resolved during transition.
The importer should then connect those requests to the right internal owner. Product information may sit with purchasing, invoice information with finance, and packing information with the warehouse. Sending every request to a general logistics inbox can obscure who is able to provide a reliable answer.
A US supplier can help by maintaining a clear commercial contact for the affected orders. This is particularly valuable when a correction needs input from the person who understands the product rather than the person who booked its transportation.
Test the awkward transaction as well as the routine one
A simple transaction may not reveal the problems that consume the most staff time. A practical preparation exercise should include the variations the business actually encounters, using the provider's authorized testing arrangements and appropriate handling of commercial data.
Examples might include an order with multiple product descriptions, a replacement item, or a correction received after the initial information package. These are illustrative business situations, not claims that any specific AIS field has changed or that a particular customs treatment applies.
The useful result is an understood process. Who recognizes that information is incomplete? Who contacts the supplier? Who updates the record, and who confirms that the representative received the change? A technically successful message does not answer those organizational questions.
Staff should also understand what a demonstration does and does not establish. One successful example supports confidence in that example. It should not be represented as proof that every possible transaction or exception has been validated.
Older declarations need their own continuity plan
The November notification says declarations previously lodged in AIS V1 can still be amended or invalidated beyond January 27, with the end date for that facility to be confirmed. That distinction matters: the rule for a new declaration is not the same question as access to an older record.
A business should discuss its outstanding historical work with its representative. The relevant issue may be how staff locate an earlier declaration, identify who handled it, and preserve the supporting commercial documents. There is no need to assume that an older transaction disappears when a new system becomes mandatory.
For example, an employee responding to a later inquiry should be able to distinguish an original invoice from a corrected version. That information discipline remains useful regardless of the particular software used. It also reduces dependence on the memory of the employee who managed the shipment.
Connect migration readiness with customer communication
Importers can explain the transition to suppliers in terms of actual requirements. A concise request identifying the affected order, required information, responsible contact, and needed response is more useful than forwarding an unfamiliar technical notice without context.
Maritime providers should likewise avoid making delivery assurances from the extension alone. The notice concerns customs-system migration. It does not confirm a vessel schedule, terminal availability, or the status of an individual import transaction.
Zeaclub members supporting Irish trade can use the announcement to start focused discussions with their commercial partners. Describe the import workflow being prepared and the role for which help is needed. Do not imply that a community discussion replaces the importer, representative, or Revenue's current instructions.
The extension's commercial value lies in the work completed before the revised deadline. A business that understands its information chain, normal transactions, exceptions, and older records will be better placed to use its provider's new arrangements effectively.
Sources
- Irish Revenue, eCustoms notification 24/2026, November 5, 2026
Checked November 15, 2026; revised migration date takes precedence over older December references.
- Irish Revenue, preparing for AIS V2
Checked November 15, 2026; business and software preparation guidance.