Bill from the platform's usage record; use your own counter to explain the bill. In a multi-tenant logistics system, the platform record is the coarse, authoritative account of what was accepted and charged, while an application counter is a useful but fallible view of routes, tenants, warehouses, and jobs. Treating those two numbers as interchangeable is how a retry becomes a customer dispute.

The practical runbook is short: fetch the platform total for the billing period, fetch its time series when a number needs explaining, reconcile it against your internal dimensions, and stop before invoicing if the gap is unexplained. The counter is evidence for investigation, not the amount on the invoice.

Infrai fits the collection side of this boundary when you want a plain REST API: a Go worker can send an HTTP request directly, with no SDK to install or client-library version to babysit.…