Home › Guides

Route cross-border invoices and domestic tax reports correctly

Select the required legal outputs before choosing the network. A customer in another country can receive a document through Peppol while a domestic authority requires a separate report. A domestic customer can also fall outside the ordinary business-invoice route because of transaction or customer status.

Use the invoice routing decision worksheet for each approved transaction pattern. The method below recommends controls. It does not replace the place-of-supply, establishment and national reporting decisions that determine which outputs apply.

Identify the transaction facts

Record the legal seller and buyer, relevant establishments, registrations, goods or service classification, customer status and place-of-supply conclusion. Keep physical delivery, tax jurisdiction and message destination in separate fields.

Do not classify from a postal address or VAT number alone. Establish which legal person issues the invoice and which establishment is relevant. Where facts are unresolved, route the case to tax rather than assigning the most common country code.

Assign billing responsibility for the customer document, tax responsibility for output scope and integration responsibility for implementing the route. AP owns incoming-document handling. The controller reviews the reconciliation across the complete population.

Define a customer-delivery path and an authority-reporting path for each pattern. Either can have several steps, and one can be inapplicable. Record the required document, profile, recipient identifier, reporting data and evidence of completion.

Australia provides a clear boundary. The ATO states that it does not receive copies or view the contents of business eInvoices exchanged through its Peppol arrangements. Exchange success should therefore not be labelled tax-return submission. ATO, eInvoicing for software developers.

France separately distinguishes domestic electronic invoicing and transaction-data reporting according to the parties and operations. A foreign transaction needs its applicable scope decision rather than automatic copying into the domestic exchange route. DGFiP, discover electronic invoicing.

Singapore's GST InvoiceNow requirement includes invoice-data submission to IRAS. This is a national arrangement using InvoiceNow, not an inference that all Peppol traffic reaches a tax authority. IRAS, GST InvoiceNow requirement.

These examples establish why the paths differ. They do not permit you to apply one country's reporting scope to another company's invoice because both providers use the same network.

Define one transaction with several controlled outputs

Keep the commercial transaction ID stable across the customer invoice, provider submission and authority records. Store each output's identifier and result separately. A reporting extract must not create another sales transaction when imported back for status reconciliation.

If an output aggregates several transactions, retain the membership of the aggregate. If one transaction produces several reports, keep the purpose of each. A flat expectation that invoice count equals every reporting-message count will generate false exceptions.

For profile selection, record the implemented release and counterpart capability. Confirm that recipient identifiers include their scheme. If the intended network route is unavailable, follow the legally approved alternative. Do not default to email where a required exchange or reporting channel remains mandatory.

Work a ten-transaction routing test

Consider a synthetic test group with two legally separate companies. Its tax owner has independently approved all classifications and national scope. Each of ten sales has net value 1,000 in the test's common comparison currency. Tax amounts are excluded from this routing exercise.

The Australian company has three business invoices, each reachable through its agreed Peppol provider. The test expects three customer-exchange cases representing net value 3,000. It does not expect three invoice copies to arrive at the ATO. The company's tax-return process remains a separate task.

The French company has seven transactions. Assume it is already in the applicable issuance/reporting phase. Three domestic business transactions qualify for its electronic-invoicing route. Two international transactions and two consumer transactions qualify for its approved transaction-reporting population. No special exemption applies in this example.

The French domestic exchange population therefore contains three transactions worth 3,000 net. The separately classified transaction-reporting population contains four transactions worth 4,000 net. Customer delivery for those four follows the approved arrangement for their category. It does not turn them into additional domestic B2B exchange cases.

The group sales population is ten transactions worth 10,000 net. The routing record explains all ten: three Australian exchanges, three French domestic exchanges and four French transaction-reporting members. French domestic invoice data may also pass through the authority-data process associated with that invoice flow. Count that evidence by purpose rather than creating another sale.

The number of actual reporting messages can differ from four if an approved process aggregates records. Retain all four membership references so the controller can prove completeness without assuming one message per sale.

Handle a changed buyer or establishment

Suppose one French transaction originally classified as consumer is confirmed to involve a business customer. Reassess the actual operation and national scope. Changing the master-data label alone does not determine whether to replace a document, adjust reporting or change a future route.

Preserve the original classification, evidence, effective date and correction decision. The tax owner approves the revised route and the permitted remedy for any completed output. Integration prevents the correction from producing a second sale.

Apply the same control when a warehouse, supplier establishment or buyer registration changes. Effective dates matter. A new customer address should not silently reroute historical invoices awaiting response.

Recover a partially completed route

If customer delivery succeeded but reporting failed, investigate the failed reporting case. Do not send a second commercial invoice solely to obtain a new technical result. Preserve the successful path and the outstanding obligation separately.

If the reporting result is unknown, query the existing attempt before replaying it. If the recipient cannot accept the required document profile, investigate capability and the permitted alternative rather than removing the obligation from the route.

At close, reconcile source transactions to all required outputs in both directions. Record exclusions with evidence. Check amounts by purpose, currency and period, and distinguish transport timing from the legally relevant reporting date.

Approve the route before automating it

Use the services VAT guide for UK/EU service classification and the status guide to interpret outcomes. Keep route ownership in the existing obligation register.

Sources checked 17 October 2026. The synthetic populations are approved assumptions for a control exercise, not a classification of every Australian or French sale.

Worksheet: Cross-border invoice route decision

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Show the worksheet

Use with the routing guide. Complete one decision for each approved transaction pattern and effective period.

Record the facts

Define each required output

Copy this block for customer delivery and each authority-data obligation.

Reconcile the synthetic pattern

Three Australian exchange cases represent 3,000 net. Three French domestic exchange cases represent 3,000 net. Four separately scoped French transaction-reporting members represent 4,000 net. The source population is ten sales worth 10,000 net. Additional reporting evidence does not create more sales, and an aggregate can represent multiple members.

Tax approval and date: ____

Finance/integration acceptance and date: ____

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: · Markdown version

Newsletter – monthly digest of mandate and ERP support changes. Subscribe on the home page.