As published by HMRC, the Goods Vehicle Movements API is version 1.0 beta. It covers creating, updating, getting, listing and deleting goods movement references, uses user-restricted access for organisation users, and states that references created through the API should not subsequently be accessed through HMRC's own online service, or vice versa. HMRC's GVMS guide says hauliers can link references online or through a direct link from their own software (as published — confirm current requirements with your adviser). GOV.UK's guidance lists Great Britain to Northern Ireland and Northern Ireland to Great Britain among the movement directions it covers, and says to include declaration references for all goods carried.
LATYNEX Digital builds custom logistics software around your own record of each crossing. This page covers that for Belfast businesses. The general service is at Logistics Software Development, and the market overview is at LATYNEX Digital for businesses in Belfast.
Typical industries
- Northern Ireland hauliers
- Freight forwarders moving trailers to and from Great Britain
- Groupage and consolidation operators
- Manufacturers and distributors running their own fleet
- Agents handling references for hauliers
- Transport back offices
Common lead-handling problems
- Crossing references keyed by hand for each trailer
- Declaration IDs pasted in from email
- Trailer and driver records kept apart from crossing records
- A missing reference found only at the port
- Status notices read on one person's screen
Direct answer
If your Belfast business moves trailers between Northern Ireland and Great Britain, LATYNEX can build an internal tool that holds one record per crossing: trailer, driver, direction, the linked declaration references and every status notice received, with an owner for anything that needs action. Whether it can create or update references directly depends on API access, described below.
Why the global page, the Belfast hub and the Southampton page are not enough
The global Logistics Software Development page has no crossing-level reference or notice design. The Belfast hub is written about software and cybersecurity teams. The Southampton page is about vehicle-compound inspection, not a per-crossing reference workflow. This page is about the record for one crossing and everything linked to it.
What we configure and build
The tool follows how your dispatch team already works.
- A crossing record linking trailer, driver, direction and declaration references
- Required fields that differ between unaccompanied and accompanied movements, following what HMRC's documentation specifies
- A notice inbox: status changes logged, assigned and closed
- A list of crossings with a missing reference, visible before departure
- Roles, an audit trail and a written handover
What stays with you and HMRC
Registration, your Government Gateway account and authorisation are yours. As published, user-restricted access needs the haulier's own HMRC registration, and software acting as an agent has its own separate registration pathway. Declarations, customs treatment and any Northern Ireland trading arrangements stay with you and your adviser.
What needs API support or custom scope
The API is in beta, so it may change. Any link to it is scoped per project through the documented API if access is permitted, after technical review. Because references created through the API should not also be handled in HMRC's online service, we decide with you which route each record uses before building. Without API access the tool still holds your own record, updated by your team.
What we do not do, and where LATYNEX is not the right fit
LATYNEX gives no customs, tax or Windsor Framework advice, does not say a haulier is compliant, holds no HMRC approval, and has no integration with any port or port-community system. It has no Belfast office or named clients. Delivery is in English only. If you use a customs or forwarding system that already links references to HMRC, this page is probably not for you.
How delivery actually works
LATYNEX Digital has no office in Belfast and does not claim one. We work with Belfast 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 Belfast?+
No. We work with businesses in Belfast remotely, over video calls and written updates, in English, and we do not imply a local presence.
Can the software create goods movement references for us?+
Possibly. That depends on API access, which needs your own HMRC registration and is in beta. It is scoped per project after technical review.
Does this make us compliant with customs requirements?+
No. We give no customs, tax or Windsor Framework advice. Confirm requirements with your adviser; we build the fields and notices they specify.
Can we mix HMRC's online service and your software?+
As published, references created through the API should not subsequently be accessed through HMRC's online service, or vice versa. We settle which route applies per record during scoping.
Is this stable long term?+
The API is currently beta, so it may change. We build the record and notice handling to be independent of it, and any API link is a separate, reviewed piece of scope.
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 the United Kingdom 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.