INDIRECT TAXMONITOR

Follow the mandate. Reconcile the transaction.

Coverage desk

VAT invoice authority

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

HMRC self-billing needs agreement-to-invoice continuity

HMRC allows a VAT-registered customer to issue invoices for a VAT-registered supplier only within an agreed arrangement. Each invoice therefore needs a dated trace to the supplier identity, agreement, covered transaction, required statement, and later change or expiry.

UK VAT groups need a member-period ledger

HMRC treats eligible VAT-group members as one taxable person while membership, intra-group treatment, and exceptions can change by date. A transaction record therefore needs the exact member set and treatment that applied when the supply occurred.

A Pagero network connection needs an exit-ready route register

The registered Pagero page now resolves to Thomson Reuters Europe and presents ONESOURCE Pagero network reach, system connectivity, and e-invoicing automation. A connection is governable only when every sender-to-recipient route can be changed or retired without losing document identity, mandate context, acknowledgements, exceptions, or reconciliation evidence.

A Basware handoff needs invoice-format and recipient lineage

Basware documents network interoperability around e-invoicing. A reviewable handoff still needs the sender, recipient, document identity, source format, target format, mapping version, transport event, validation response, exception, and archive record that belong to the same invoice.

A Comarch delivery status is not invoice acceptance

Comarch documents multi-channel invoice distribution and delivery monitoring. The status still needs an exact document identity, recipient evidence, authority state, and exception history.

An SAP DRC submission status is not tax-authority acceptance

SAP documents real-time document submission, statutory reporting, monitoring, corrections, and public-agency integration in Document and Reporting Compliance. A platform status can show what SAP processed, but only the named authority response and the taxpayer's reconciled record can establish what happened after submission.

An EDICOM e-invoice archive does not set the retention rule

EDICOM documents electronic invoicing, authority connectivity, signatures, and archiving in one international platform. The archive can preserve transmitted records and evidence, but the controlling retention period, required form, accessibility, and legal effect still come from each jurisdiction and the taxpayer's own obligations.

Texas separates remote-seller collection from marketplace-provider collection

Texas Comptroller guidance assigns different permit, collection, rate, and record duties according to the seller’s Texas presence and sales channel. A marketplace certificate can change who collects on marketplace sales without resolving the seller’s other Texas transactions.

ATO eInvoicing changes invoice exchange—not the tax treatment

The Australian Taxation Office describes eInvoicing as structured invoice exchange through the Peppol network. That transport path does not decide whether a document is a valid tax invoice, which GST treatment applies, or whether the underlying transaction record is complete.

EN 16931 support does not make every EU invoice legally valid

The European framework supplies a common semantic model for structured public-procurement invoices. Country profiles, tax rules, validation, routing, reporting, recipient acceptance, and archives remain separate evidence layers.

Streamlined guidance keeps remote-seller nexus state-specific

The multistate chart is a useful orientation layer, but its own warning is decisive: thresholds, measurement periods, sales bases, and effective dates remain matters of individual state law and current state guidance.

VIES validates a VAT number—not transaction tax treatment

The European Commission service checks a VAT number against the relevant national record for the current day. That result is one identity fact, not a conclusion about place of supply, liability, rate, exemption, invoicing, or reporting.

Wayfair ended physical-presence nexus—not state-by-state review

The U.S. Supreme Court rejected physical presence as the constitutional shortcut for sales-tax collection. It did not create one national economic-nexus threshold, so tax systems still need a dated state-by-state rule and transaction record.

HMRC’s MTD rules make VAT record aggregation a governed control

HMRC permits specific VAT records to be summarized or adjusted without rewriting every underlying supply record. The permission is bounded by transaction type, value, return period, tax rate, and retained source information, so aggregation belongs in the tax-control design rather than a generic data-compression setting.

ZATCA keeps FATOORA integration wave-aware

Saudi Arabia's second phase remains a taxpayer-notified integration program with structured formats, authority connectivity, and invoice-type-specific controls.

Peppol BIS is an exchange profile—not a tax conclusion

The maintained specification supplies business terms and validation artefacts, while country rules still determine legal invoice, tax, reporting, and archive obligations.