INDIRECT TAXMONITOR

Follow the mandate. Reconcile the transaction.

Coverage desk

UK VAT invoice calculation

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

HMRC VAT invoice rounding needs a method-and-total control

HMRC VAT Notice 700 permits different invoice, line, and unit rounding treatments within defined scopes and distinguishes invoice traders from retailers. A tax and billing team should therefore version the chosen method, apply it consistently, and reconcile displayed lines, invoice VAT, accounting, and return totals without treating a small difference as automatically permitted or erroneous.

CFDI cancellation needs request-to-status reconciliation

Mexico's SAT describes cancellation as a workflow with a reason code, a replacement folio when applicable, a receiver-response path in some cases, and a resulting invoice status. Tax and finance teams should preserve those events as a linked record instead of treating a submitted request or an ERP void as final cancellation.

Esker shared e-invoicing needs AP–AR role separation

Esker presents one platform for supplier invoice receipt and customer invoice delivery. Tax and finance buyers should test whether each legal entity, invoice direction, approval, and exception remains separately owned when both flows share technology.

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.

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 TaxCloud rate result needs address, item, and configuration lineage

TaxCloud presents real-time, item-level sales-tax calculation based on customer address and jurisdiction. The returned amount can support checkout, but a reviewable determination still needs the transaction inputs, taxability mapping, effective configuration, response, and downstream treatment that produced it.

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 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.

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.