Ireland-UK Invoicing After Brexit: GB and NI Guide

If you are trying to handle Ireland UK invoicing after Brexit, start with one split. Goods between Ireland and Great Britain are third-country movements, so the invoice usually has to support customs declarations with EORI details, goods descriptions, values, and classification data. Goods between Ireland and Northern Ireland still follow EU VAT rules, so the invoice logic stays much closer to intra-EU trade. Services involving Northern Ireland do not follow that goods carve-out, so the invoice treatment usually reverts to UK VAT logic, often with reverse charge treatment for B2B services supplied from Ireland.

That split matters because finance teams are rarely dealing with theory. They are deciding whether an invoice needs customs-ready data, which VAT number should appear on it, and which reporting system the transaction should feed. The topic is large enough to justify a practical workflow view. According to InterTradeIreland's cross-border trade statistics, cross-border trade in goods between Ireland and Northern Ireland reached EUR10 billion, or GBP8.6 billion, from January to November 2025, so these are routine operating issues rather than edge cases.

Use this matrix as the quick-answer version before you review individual scenarios in more detail:

Transaction path	Customs position	VAT number or identifier to check	Invoice treatment cue	Main reporting trail
Ireland to Great Britain goods	Export from EU to a non-EU territory	Irish seller's IE VAT and EORI details where relevant	Commercial invoice should support customs declarations with goods data	Export and customs records
Great Britain to Ireland goods	Import from a non-EU territory into Ireland	Irish importer EORI and import records	Invoice should align with import entry and customs value data	Import VAT and customs records
Ireland to Northern Ireland goods	No standard third-country customs workflow for the goods movement	Irish supplier IE VAT number, customer validation where relevant	Intra-EU style goods treatment	VIES and, where applicable, Intrastat
Northern Ireland to Ireland goods	Goods still within the Northern Ireland Protocol framework for EU VAT purposes	Northern Ireland trader's XI VAT number for EU goods trade	Intra-Community goods logic rather than GB customs logic	EC Sales List or VIES-style reporting and, where applicable, Intrastat
Ireland to UK or Northern Ireland B2B services	Customs not the core issue	Customer VAT details, but not an XI prefix simply because the customer is in Northern Ireland	Reverse charge often applies if place of supply sits with the business customer	Service VAT reporting based on place-of-supply rules

The rest of this guide follows that structure. First, separate Great Britain from Northern Ireland. Then separate goods from services. Once you do that, the invoice rules become much easier to apply consistently across Revenue Commissioners guidance, HM Revenue & Customs notices, and your own posting controls.

Goods Between Ireland and Great Britain Need Customs-Ready Invoices

Once goods move between Ireland and Great Britain, you are no longer in an intra-EU invoicing workflow. The invoice becomes part of an import or export file, which means it has to support customs declarations as well as normal accounting records. That is the practical change many teams feel after Brexit: the commercial invoice is no longer just evidence of sale. It is also a customs document support layer.

For Ireland to Great Britain shipments, the Irish seller needs an invoice that helps customs authorities understand what is moving, who is trading, and how the goods should be valued and classified. For Great Britain to Ireland purchases, the same discipline matters from the import side because the invoice values and descriptions will be checked against the import declaration. If the invoice is vague, clearance slows down and the downstream VAT and landed-cost records become harder to reconcile.

At a minimum, finance teams should expect the invoice or related customs pack to carry these details clearly:

• Seller and buyer name and address
• VAT number where relevant
• EORI number where relevant
• A clear goods description that explains what the product is, not just an internal code
• HS code or commodity code data
• Quantity, weight, and package information where needed for the shipment
• Value details that support customs valuation

Irish businesses trading with Great Britain also need to think about EORI registration early. An Irish EORI is the operational identifier customs systems use for imports and exports with non-EU countries. If the business is moving goods between Ireland and Great Britain, an invoice review process should include a check that the right EORI number is available and consistent with the rest of the customs file.

The wording of the goods description matters more than many teams expect. "Parts" or "samples" is rarely enough. Customs authorities want enough detail to identify what the goods are, what they are used for, and how they should be classified. That is why HS code accuracy and invoice wording should be reviewed together instead of as separate tasks handled by different teams.

Supporting declarations sit alongside the invoice rather than inside it, but the data still has to match. Depending on the route and mode of transport, that can include an Entry Summary Declaration and a Pre-Boarding Notification for RoRo traffic. The invoice should not try to replace those filings. It should give them reliable underlying data on value, goods description, and trading parties.

If your team also needs the mirror-image perspective from the UK side, it helps to compare your controls with the UK-side customs invoice checklist for post-Brexit exports. The core point remains the same from either side of the Irish Sea: goods between Ireland and Great Britain now need customs-ready invoices, not just ordinary sales invoices.

Northern Ireland Goods Still Follow EU VAT Rules, but the XI Prefix Matters

Northern Ireland is where many post-Brexit invoice mistakes begin, because businesses often apply Great Britain rules to a Northern Ireland goods transaction. For goods, that is the wrong starting point. Under the Northern Ireland Protocol framework, goods moving between Ireland and Northern Ireland continue to follow EU VAT rules rather than the third-country customs model used for Great Britain trade.

That means an invoice for goods moving from Ireland to Northern Ireland is usually handled more like intra-EU trade than an export to Great Britain. The practical implications are familiar to VAT teams: validate the customer's VAT status, check the relevant IE or XI number through VIES where appropriate, document the transaction in a way that supports intra-Community treatment, and make sure the reporting trail aligns with VIES and, where applicable, Intrastat rather than a standard Great Britain customs workflow.

The XI VAT number is the most distinctive feature in this corridor. A Northern Ireland trader may hold both a normal UK VAT registration and an XI-prefixed VAT number. The XI prefix is the one that matters for goods trade with Ireland and the wider EU. If a Northern Ireland business is buying or selling goods across the border, finance teams should check whether the invoice should carry the XI number instead of treating the counterparty as a standard UK customer or supplier.

That dual-prefix reality is why invoice controls need to verify the nature of the transaction before they verify the tax treatment. If the movement is goods between Northern Ireland and Ireland, the invoice logic usually points toward EU VAT treatment. If the transaction is something else, the answer may change. Teams that skip that first classification step often end up using the wrong customer identifier, the wrong reporting path, or both.

In practice, the useful question is not just "What is an XI number?" It is "When should that number appear on the invoice, and what does that choice imply for reporting?" XI matters when a Northern Ireland trader is participating in EU-facing goods trade, and that choice connects directly to VIES, intra-Community VAT logic, and any Intrastat obligations that still apply to the business.

So if the transaction is goods and the counterparty is in Northern Ireland, do not jump straight to the Great Britain customs model. Check the VAT prefix, confirm the invoice supports intra-EU treatment, and treat the XI number as an operational control point rather than a minor formatting detail.

Services With Northern Ireland and the UK Use a Different VAT Logic

The biggest conceptual trap in this topic is assuming Northern Ireland always follows the same rules. It does not. Northern Ireland's special post-Brexit treatment is mainly about goods. Once the transaction is a service, the invoice logic usually follows UK VAT treatment instead of the Northern Ireland goods regime.

For many B2B services supplied from Ireland to a customer in the UK or in Northern Ireland, the place of supply is where the business customer is established. In practice, that often means the Irish supplier does not charge Irish VAT and instead issues the invoice on a reverse charge basis. The important control point is not whether the customer happens to be in Northern Ireland. It is whether the transaction is a service and whether the place-of-supply rules shift the VAT obligation to the customer.

That is why finance teams should classify the transaction before they validate the invoice fields. A consulting engagement, software subscription, freight management service, or advisory project should not inherit the invoice treatment used for a shipment of goods just because the customer is in Belfast. If it is a service, customs-style invoice data is not the main issue. The core questions are whether reverse charge VAT applies, whether the customer's VAT number has been verified, and whether the invoice wording makes the tax treatment clear enough for both parties' records.

Operationally, a reverse charge UK Ireland services invoice should usually do three things well:

• Identify the business customer clearly
• Carry the VAT information needed to justify the treatment, including the customer's business VAT details where relevant
• State clearly that the customer accounts for VAT under the reverse charge so both sides' records point to the same treatment

This is also where the XI point often causes confusion. The fact that Northern Ireland uses XI identifiers for certain goods transactions does not mean every Northern Ireland service customer should be treated through that lens. The goods regime and the services regime split apart after Brexit, and the invoice needs to follow that split.

Mixed businesses make this especially important. A supplier may sell equipment and maintenance to the same Northern Ireland customer in the same month. One invoice may belong in the goods workflow, while the other belongs in the services workflow. If AP, billing, or bookkeeping teams do not classify the transaction first, they can easily apply the wrong VAT identifier or add invoice fields that do not belong there.

Windsor Framework Changes the Supporting Documents More Than the Core Invoice

The Windsor Framework matters, but not in the way many searchers first assume. It is best understood as a change to the supporting document and customs environment for certain Northern Ireland-bound goods movements, not as a complete rewrite of the invoice rules across every Ireland-UK transaction.

In practical terms, the Framework introduced differentiated treatment for some goods moving into Northern Ireland. Where goods are staying in Northern Ireland and meet the relevant conditions, the movement can fall into a simplified route. Where goods may move onward into the EU single market, fuller customs treatment applies. That is where businesses encounter ideas such as green lane versus red lane handling and the role of the UK Internal Market Scheme.

For invoice reviewers, the key question is not "Does Windsor Framework language appear somewhere in the file?" It is "Does the invoice line up with the declared movement and the rest of the customs pack?" If a shipment is being handled under a simplified Northern Ireland route, the commercial paperwork, product descriptions, and consignee details should support that position. If the goods are treated as at risk of entering the EU, the supporting declarations and customs data burden will be heavier.

This is also the right place to keep postponed VAT accounting in perspective. For Irish importers, postponed VAT accounting changes how import VAT is accounted for, because the VAT is recognized through the VAT return rather than paid upfront at the border in the ordinary way. It does not remove the need for accurate import documentation, and it does not turn a Great Britain goods movement back into an intra-EU invoice.

That distinction matters when teams design controls. The invoice still needs the right customs-supporting data for the import. Postponed VAT accounting then affects how the business books the import VAT and manages cash flow after the goods arrive. If you want the UK-side comparison, how postponed VAT accounting works on the UK import side is a useful companion piece, but the Ireland-side lesson is straightforward: postponed VAT accounting is an import VAT accounting method, not an alternative invoice regime.

So treat the Windsor Framework as a document-handling and routing layer on top of the underlying rules, not as a shortcut that replaces the need to classify the transaction correctly in the first place.

Use a Finance-Team Checklist for Currency, Reporting, and Record Matching

Once you separate Great Britain from Northern Ireland and goods from services, the last job is control design. The businesses that handle this corridor well usually rely on a short review checklist rather than trying to remember every edge case from memory.

Before an invoice is posted or sent, check these points:

1. Classify the transaction first. Is it goods or services? Is the counterparty in Great Britain or Northern Ireland? That single decision determines most of the rest.
2. Check the VAT identifier. For Northern Ireland goods trade, confirm whether an XI VAT number should appear. For Great Britain goods trade, focus on the customs and import or export file instead of assuming intra-EU logic still applies.
3. Review customs-supporting data for Great Britain goods. Make sure the invoice description, value, quantities, and classification details are strong enough to match the customs declaration.
4. Validate reverse charge treatment for services. If the transaction is a B2B service, confirm the place-of-supply logic, customer VAT information, and invoice wording before posting it.
5. Match the invoice to the right reporting channel. Northern Ireland goods may connect to VIES and, where applicable, Intrastat. Great Britain imports and exports feed customs and import VAT records. Services follow their own VAT reporting logic.
6. Check currency handling from the Irish side. Ireland uses the euro, while many counterparties in Northern Ireland and Great Britain invoice in sterling. If the business bills or receives an invoice in GBP, make sure the euro value used for Irish VAT records is documented and consistent with the exchange-rate policy used by the business.
7. Reconcile to the full document set. For goods, that means matching the invoice to transport records, declarations, and import evidence. For services, it means matching the invoice to the contract, VAT treatment, and customer details that support the reverse charge position.

The most common errors are predictable: treating a Northern Ireland service like a goods movement, missing an XI prefix on Northern Ireland goods trade, carrying weak customs descriptions on a Great Britain shipment, or posting invoice values that do not tie back to import records. Those are process failures more than tax-theory failures.

A good closing step is to turn these checks into a standard review sheet for AP or bookkeeping staff. That way the rule split becomes part of everyday document handling rather than something only a specialist remembers. Keep that workflow separate from broader digitization projects such as Ireland's separate 2028 e-invoicing and Peppol preparation timeline, because the Brexit question is about current cross-border invoice treatment, not the future domestic e-invoicing mandate.