Logistics & freight
Freight invoicing is high in volume and unusually detailed at line level. A single shipment invoice can carry freight, handling, customs charges, demurrage and disbursements paid on the customer's behalf — each with a different tax treatment. Structured invoicing requires every one of those lines to be explicit and correct.
Amounts paid on a customer's behalf are treated differently from your own service charges. That distinction has to be represented properly at line level, and it is one of the most common sources of error in this sector.
When a business issues thousands of invoices a month, a validation error affecting one percent of them is not a minor issue — it is a daily operational workload. Getting the mapping right matters more here than almost anywhere else.
Demurrage, storage and detention are often known only after the shipment has moved, producing supplementary invoices and adjustments against work already billed.
Jobs, shipments and charges live in an operational system; the invoice is produced from or alongside the accounting package. The mapping has to bridge both.
Customer-specific tariffs applied at billing time, sometimes manually, which affects how reliably invoice data can be generated automatically.
Agents, overseas principals and local shippers require different handling in structured invoices.
Establishing, per charge type, what the correct treatment is and how it is expressed in the structured format. This is scoping work done with your tax advisor, before any integration.
Testing three invoices proves very little at this scale. Validation needs to run across a representative volume, including the awkward charge combinations.
At high volume, rejections need a defined resolution process and an owner from day one, not an ad hoc response when someone notices.
Per-invoice pricing models from providers behave very differently at this volume. Reviewing the commercial terms properly is part of the work, not an afterthought.