A cross border order can arrive on time and still create a costly finance problem. When VAT is collected at checkout, but the legal seller, the invoice, the import record, and the tax return do not match, the business can face late filings, unrecoverable VAT, customer disputes, or double tax exposure.
VAT remittance is the process of collecting the right tax, keeping the evidence, paying it through the correct entity and channel, and reconciling every amount to the order. To manage it across markets, follow seven controls. Define who the legal seller is for each flow. Store tax data on every order. Separate VAT collected from VAT owed. Keep a filing calendar for each registration. Set tax outcomes for returns. Model VAT before you place stock. Finally, review exceptions before every filing.
This guide walks through each control and shows where ShipSmart products fit. It is general information, not tax advice, so confirm each rule with your tax advisor.
Rule of thumb. Collect the right tax, keep the evidence, remit through the right entity, and reconcile every amount back to the order.
Control 1: Start with the correct VAT liability model
VAT remittance begins with one question: who is legally responsible for the sale and the tax payment? The answer changes by destination, order value, sales channel, Incoterm, and fulfillment location. Therefore, tax, finance, customs, and logistics need one documented answer for every active flow.
€150 is the customs value limit for eligible low value consignments under the EU’s Import One Stop Shop, known as IOSS.
£135 is the value up to which overseas sellers charge UK VAT at the point of sale.
| Flow | How VAT is collected | Where it is reported |
|---|---|---|
| Non EU seller, consignment up to €150 to an EU consumer | At checkout | IOSS return |
| Other consignments into the EU | At the border, or built into a DDP price | By the importer of record, or by the seller under DDP |
| Sale fulfilled from stock held in the EU | At checkout, under local rules | Local registration, and possibly Union OSS |
| UK consignment up to £135 | By the overseas seller at the point of sale | UK VAT return |
| Marketplace sale | By the marketplace, if it is the deemed supplier | By the marketplace |
Do not assume that the checkout setup for direct sales applies to marketplace orders. In some cases, the marketplace is the supplier for VAT purposes. Rules change, so confirm the current thresholds before you decide.
Where ShipSmart helps. Ship Clear issues DDP invoices through a local merchant of record and delivers monthly fiscal reports, so finance gets a clean record of each flow. It works in the markets where Ship Clear operates, so ask the team which ones fit your plan.
Control 2: Build VAT data into the order lifecycle
VAT returns are only as reliable as the data behind them. Treat tax information as core order data, not as a report you assemble later.
For each order, keep the ship to country, the product classification, the VAT rate, the net, VAT, and gross amounts, the currency, the legal seller, the fulfillment location, the shipping method, the Incoterm, the customs reference, and the invoice number. Also keep the date that sets the tax point, which can be the invoice, payment, dispatch, or delivery date.
Example, hypothetical. A US brand sells a €100 jacket to a customer in Germany. The customer pays €15.97 of VAT at checkout, at the 19% German rate. However, the IOSS number is missing from the shipment data, so the carrier collects import VAT again at delivery. The customer pays €15.97 twice, plus a handling fee, and finance must reconcile a tax amount that should not exist.
40% of shoppers who abandon a cart cite extra costs that are too high, according to Baymard Institute.
Where ShipSmart helps. Ship Tax & Duty calculates duties and taxes in real time from cart data and destination. Ship OS then generates labels and customs documents from the same order data, with support for DDP and DDU. As a result, checkout and declaration carry the same numbers.
Our guide to VAT registration workflow automation shows how to keep registrations under control.
Control 3: Separate VAT collected from VAT owed
A common failure is treating the VAT collected from customers as the same figure you must remit. They are related, but they are not always identical. Refunds, cancellations, partial returns, currency rules, credit notes, discounts, marketplace sales, and prior period adjustments all change the amount owed.
Open a VAT control account for each registration or filing scheme. Sales systems should post output VAT, while purchase and import records support input VAT recovery where it applies. Reconcile the balance at least monthly, even if you file quarterly.
This also protects cash planning. VAT collected at checkout is not operating revenue. If it mixes into general cash without a remittance forecast, a fast growing business can look more liquid than it is. Therefore, reserve the expected VAT by country, scheme, and filing period as orders complete.
Where ShipSmart helps. Ship Pay shows inclusive pricing at checkout and supports payment split at the transaction. That can help you keep the tax portion apart from revenue, so ask the team how it maps to your accounts.
Control 4: Keep a filing calendar that reflects reality
VAT compliance fails most often through missed deadlines, incomplete records, or incorrect registrations. It rarely fails because a team misunderstands the concept. A practical calendar turns regulation into repeatable work.
For every registration and simplified scheme, document the filing frequency, the payment deadline, the return currency, the required data, the internal owner, any external advisor, and the source systems. Include dependencies too, such as the date warehouse teams finalize stock movements, or the date carriers return customs evidence.
Close VAT data on a fixed cadence. For example, operations can validate shipment and delivery records weekly. Finance can reconcile collected tax and refunds monthly, and tax owners can review return level variances before submission. This leaves time to fix missing tax IDs, duplicate orders, and shipment records that do not match the checkout value.
It also builds an audit trail. Authorities may ask for invoices, transaction records, proof of transport, customs declarations, or evidence for zero rated treatment. Keep them retrievable for the period each jurisdiction requires, and set one retention policy that meets the strictest standard.
Control 5: Manage returns, refunds, and corrections deliberately
Returns are where VAT processes drift away from the customer experience. A customer may receive a refund at once, while the tax adjustment appears in a later return. That can be fine, if the accounting treatment and the credit documents are correct.
Set clear rules for full refunds, partial refunds, canceled orders, refused deliveries, lost shipments, exchanges, and return to origin movements. Each event should trigger a defined tax outcome. For instance, a refused cross border delivery may require you to reverse the original sale, address import charges, and account for the inventory movement. Do not process it as a routine domestic return.
Trace every correction to the original order and filing period. Avoid manual journal entries that you cannot tie back to the order, the invoice, the credit note, and the logistics record. When manual work is unavoidable, log it, review it, and reduce it over time.
Control 6: Match your VAT model to your fulfillment strategy
Where inventory sits changes your VAT obligations. A brand that ships every order from the United States has a different profile from a brand that holds stock in Germany, the Netherlands, the UK, or several regional warehouses.
Worth knowing. Local inventory can improve delivery speed and cut last mile cost. However, it can also trigger registration, domestic reporting, stock transfer documents, and local invoicing. For EU businesses using centralized reporting, stock moving between countries can still create obligations that OSS alone does not solve.
Therefore, do not approve fulfillment expansion on shipping cost and delivery time alone. Model the tax impact before you place stock. The right answer depends on order volume, margin, destination mix, return rate, B2B versus B2C demand, and your capacity to maintain local registrations.
Where ShipSmart helps. Ship Fulfillment places inventory in hubs across Latin America, the United States, and Europe. Use it together with the VAT model above, because the hub you choose changes the registrations you need. Our guides on when to use regional fulfillment and multi country inventory planning explain the trade off.
Control 7: Use exception reporting before every filing
The strongest VAT process runs on exceptions, not on blind trust in totals. Before each filing, review orders with a zero VAT rate, missing destination data, manual tax overrides, unusual refund values, tax amounts that differ from expected rates, duplicate invoices, and shipments delivered under a different service than selected.
Then compare three views of the business: checkout transactions, financial postings, and physical shipments. If the totals differ, find out whether the cause is timing, cancellations, unshipped orders, returns, or a data failure. A small variance can be normal. A recurring variance is a process issue that is about to become a compliance issue.
As coverage grows, standardize these controls by country instead of relying on individual knowledge. Ownership can stay local, but the discipline should stay the same: documented rules, reconciled data, retained evidence, approval before filing, and a clear escalation path.
Which ShipSmart product supports which VAT control?
| VAT control | Product | What it contributes |
|---|---|---|
| Liability model and invoicing | Ship Clear | DDP invoices through a local merchant of record, and monthly fiscal reports |
| Tax at checkout and in the declaration | Ship Tax & Duty | Real time duties and taxes from cart data and destination |
| Shipping documents from the same data | Ship OS | Labels and customs documents, with DDP and DDU support |
| Inclusive price and tax separation | Ship Pay | Inclusive pricing, multi currency payments, and payment split |
| Stock location and VAT exposure | Ship Fulfillment | Hubs in Latin America, the United States, and Europe |
Frequently asked questions about VAT remittance
What is VAT remittance?
VAT remittance is the payment of collected VAT to the tax authority through the correct entity and channel. It also includes the records and the reconciliation that support each amount.
Is VAT collected at checkout the same as VAT owed?
Not always. Refunds, cancellations, credit notes, currency rules, and adjustments change the amount owed. Therefore, reconcile collected and owed VAT every month.
Who remits VAT on cross border sales to the EU?
It depends on the model. The seller may remit through IOSS, Union OSS, or a local registration, while the importer of record pays import VAT at the border. A marketplace remits when it is the deemed supplier.
What is IOSS?
IOSS is the EU’s Import One Stop Shop. It lets sellers charge VAT at checkout on eligible low value consignments, up to €150, and report it in one return.
Do I need a VAT registration if I hold stock in the EU?
Often yes. Local stock can trigger registration, domestic reporting, and local invoicing. Confirm the rules for each country with your tax advisor.
How often should I reconcile VAT?
At least monthly, even if you file quarterly. A monthly rhythm leaves time to fix exceptions before the return.
VAT remittance becomes manageable when you design it into the commercial model before orders scale. The brands that move fastest internationally treat tax as part of the operating system, not as a filing task after the fact. To see how these controls would run in your markets, book a call with ShipSmart and bring your list of registrations and flows.
