Description

Toll receipts at highway barriers present a unique challenge: they are documents that qualify as invoices (mentioning VAT rate, amount, and a sequential number) but the buyer is typically not identified at the point of transaction. This means the toll operator cannot determine whether the buyer is a taxable person (B2B) or a consumer (B2C).

The administrative tolerance treats anonymous toll transactions as B2C operations. The toll operator declares sales through B2C e-reporting (Flux 10.3 daily cumulative sales). This lets the PPF pre-fill the seller's collected VAT but not the buyer's deductible VAT. The taxable buyer processes toll receipts independently for their VAT deduction, which may create a discrepancy with pre-filled data.

When the toll operator identifies the buyer through a subscription or accreditive card, a proper B2B periodic invoice (typically monthly) must be issued through the e-invoicing flow.

Key characteristics

• Anonymous barrier tolls: treated as B2C, declared in Flux 10.3 e-reporting.

• PPF pre-fills seller collected VAT only; buyer deductible VAT not pre-filled.

• Buyer declares deductible VAT independently (potential discrepancy with pre-fill expected).

• Subscription or accreditive card tolls: buyer identified — periodic B2B invoice (e-invoicing).

• Parking automates: similar treatment, transitional B2C until automates updated.

• No mandatory automate adaptation requirement at reform launch.

Relationship to other use cases

Use case 27 shares the B2C e-reporting mechanism with use case 6 (Employee Expenses B2C) and use case 28 (Restaurant Notes). The subscription model producing periodic B2B invoices is a standard e-invoicing scenario. Use case 30 (VAT Already Collected) may apply if a buyer requests a B2B invoice after an anonymous toll transaction declared in e-reporting.

Business and tax context

Legal and regulatory framework

Administrative tolerance lets toll receipts serve as valid invoices. The key practical issue is that automated barriers cannot identify whether the client is a taxable person, leading to the B2C treatment by default. Subscription-based services resolve this by identifying the buyer upfront.

Common business scenarios

Highway tolls

Anonymous passage, receipt at barrier, B2C e-reporting.

Toll subscription

Monthly invoice for corporate fleet (B2B e-invoicing).

Parking

Anonymous ticket, transitional B2C treatment until automate upgrade.

Tax and accounting implications

The buyer's deductible VAT on anonymous toll receipts will not match the PPF pre-fill (which only reflects the seller's collected VAT). The buyer must declare this deductible VAT directly, creating an expected discrepancy that the tax administration acknowledges.

Key data requirements

Anonymous toll (B2C e-reporting):

Subscription toll (B2B periodic invoice):

Implementation considerations

Seller considerations

Anonymous tolls

Declare in Flux 10.3 (B2C daily cumulative sales).

Subscription tolls

Issue periodic B2B invoices through standard e-invoicing.

Buyer considerations

Anonymous toll receipts

Process independently for VAT deduction (discrepancy with pre-fill expected).

Subscription invoices

Standard B2B invoice processing.

General considerations

• The issuer's Plateforme Agréée (PA-E) must support both e-reporting (anonymous) and e-invoicing (subscription) flows.

SCI mapping

Standard SCI mappings apply for subscription-based periodic B2B invoices. Anonymous toll transactions use e-reporting (no SCI invoice format).