As published by Irish Revenue, goods arriving in Ireland by roll-on/roll-off (RoRo) ferry from a place outside the EU customs territory have to be imported in accordance with section 12B of the Customs Act 2015. The declarations are lodged before arrival at the ferry port of departure, and their Movement Reference Numbers (MRNs) go into a Pre-Boarding Notification (PBN) submitted to Revenue before arrival at that port. For outbound movements, the MRNs must be in a PBN that Revenue has cleared before departure from the Irish ferry port. One PBN covers one commercial vehicle or trailer and can hold several MRNs, it is required even for an empty commercial vehicle or trailer, and it is completed by the carrier, a term that includes persons providing haulage or logistical services. Revenue's PBN User Guide states that failure to comply with the requirement is an offence, and Revenue's page states that without a valid PBN at the "Good to proceed to Check-In" status the vehicle will not be allowed to board (as published — confirm current requirements with your adviser). Revenue's national electronic import system, AIS, handles the validation, processing, duty accounting and clearance of the declarations themselves.
LATYNEX Digital builds custom logistics software around the movement record that holds those references. This page covers that work for Dublin businesses. The general service is at Logistics Software Development, and the market overview is at LATYNEX Digital for businesses in Dublin. Delivery is in English, and this page names no client.
Typical industries
- Road hauliers running trailers and vehicles on RoRo ferry routes
- Freight forwarders and clearance agents lodging declarations for others
- Importers and exporters whose goods travel on a haulier's vehicle
- Logistics providers coordinating several declarants for one vehicle
- Dispatch and back-office teams planning ferry bookings and check-in
Common lead-handling problems
- Declaration references (MRNs) held by several parties with no single record per vehicle or trailer
- No view, before the vehicle reaches the ferry port, of whether every MRN is on the PBN
- Empty trailers and repositioning movements forgotten because there is no goods declaration to prompt anyone
- Delegation between haulier and declarant tracked in email threads
- No record of which party supplied which reference, and when
Direct answer
If your Dublin business moves goods on RoRo ferry routes between Ireland and a place outside the EU customs territory, LATYNEX can build software that holds each vehicle or trailer as one movement record, collects the declaration references from everyone involved, and shows what is still missing against the ferry check-in cut-off, so a gap is found at dispatch rather than at the port.
Why the global page and the Dublin hub are not enough
The global Logistics Software Development page has no Irish customs step to design around, and the Dublin hub is broad discovery for the market. As published, the PBN gates boarding on declaration references for every commercial vehicle on the in-scope movements, and the haulier carries responsibility while the declarations may come from other parties. The design point is therefore a record per vehicle or trailer that gathers references from several parties and exposes what is missing before check-in.
What we configure and build
The software sits around your movement records and the parties' own submissions, not in place of them.
- A movement record per vehicle or trailer, with the ferry booking and check-in cut-off alongside it
- Every declaration reference (MRN) captured against the record, with who supplied it and when
- A pre-check that flags a movement with no references, or references still to arrive, ahead of the cut-off
- Empty and repositioning movements held as records too, so they are not skipped
- Delegation between haulier, declarant and clearance agent recorded on the movement, plus a written handover
Technical considerations
As published, Revenue's AIS developer pages describe XSD and WSDL files, REST endpoints, SOAP web services and ROS integration. Whether and how any of that applies to your set-up depends on your own Revenue access and on technical review. Confirm current technical details with Revenue and your adviser.
What stays with you and Revenue
Lodging declarations, completing and submitting the PBN, ROS and AIS access, the choice of who is the declarant, and every dealing with Revenue stay with you, your clearance agent and your adviser. We build the record and the reference checks; we do not submit anything to Revenue.
What needs API support or custom scope
Any live exchange with Revenue's systems would depend on your own approved access and is scoped per project, after technical review and subject to Revenue access approval. LATYNEX claims no AIS or PBN integration and holds no Revenue credentials. Connections to your TMS, ERP or ferry-booking tools are scoped separately where they add value.
What we do not do, and where LATYNEX is not the right fit
LATYNEX does not file declarations or PBNs, does not act as a customs agent or declarant, gives no customs or legal advice, and does not certify compliance. This page makes no claim about Northern Ireland, EU-to-EU routes, or air and container sea movements, none of which the sources above address. It has no Dublin office or named clients, and delivery is in English only. If a clearance agent already handles every reference and you need no shared record, this page is not for you.
How delivery actually works
LATYNEX Digital has no office in Dublin and does not claim one. We work with Dublin businesses remotely, over video calls and written updates, in English, with the same team and process as in every other market.
Questions
Do you have an office in Dublin?+
No. We work with businesses in Dublin remotely, over video calls and written updates, in English, and we do not imply a local presence.
Which movements does the PBN apply to?+
As published, goods arriving in Ireland by RoRo ferry from a place outside the EU customs territory, and outbound movements through an Irish ferry port, with one PBN per commercial vehicle or trailer. We do not extend that to other routes or modes. Confirm whether a given movement is in scope with your adviser.
Do you submit PBNs or declarations to Revenue for us?+
No. Submission stays with the haulier, your declarant or your clearance agent, using your own Revenue access. We build the record and the reference checks around it.
Does this make our ferry movements compliant?+
No. We give no customs or legal advice and cannot say a movement meets the requirements. Revenue's own guidance states that failure to comply is an offence, so confirm requirements with your adviser; we build to the data and references they specify.
Do you have an AIS or PBN integration?+
No. Revenue publishes developer specifications for AIS, and any exchange would be scoped per project after technical review and subject to Revenue access approval.
How are you invoiced, and in what currency?+
In EUR, by Latynex Trade OÜ, a company registered in Estonia (EU). Tax treatment for a client in Ireland is confirmed on the quote, and we do not give tax advice.
What happens next
- 01
We talk through what you need
The problem, the people who will use it and what runs it today.
- 02
We write the scope
What is built first, what is deliberately left out and what needs a decision from you.
- 03
Price agreed in writing
One price for that scope, approved by you before any work starts.
- 04
We build in stages you can review
You see working software along the way, not a reveal at the end.
- 05
Test, hand over, document
Your code, your accounts and your domain, with documentation that lets someone else run it.
Who you would be working with
- Company · Who you would be working with
- LATYNEX Digital is a service line of Latynex Trade OÜ, a company registered in Estonia (EU). Contact: info@latynexdigital.com.
- How we work · Delivery
- Remote, in English, with the person who would run the project. No local office is implied in any market.
- How we work · Commercial terms
- One scope and one price, agreed in writing before work starts. Your accounts, code and domain stay yours; any access we use is granted by you and can be withdrawn.
There are no client case studies on this page, and none are implied. What LATYNEX has built and runs itself is on the portfolio, each system labelled by stage. Published prices are on the pricing page; anything not listed there is scoped and quoted after review.