Cash-basis thinking is tempting in a collections inbox. Accounting is not a collections inbox.
A sent invoice creates a billed amount. Whether that amount is revenue yet depends on the product: over the term, as delivered, point in time, usage accrued through the period and settled on invoice, commitments, forfeits.
Sonic posts from the documents you already sent. Every journal line can walk back to a source. Debits equal credits or the batch does not publish. Consolidated product blocks exist so a finance reader sees one product, not a row per account unless they ask.
Freight is stricter about dates. The haul owns recognition. If you billed later, you still recognise on the shipment date — waiting for the invoice-day leg when billing was in advance, then posting the recognised amount to the haul date. If both happen on the same calendar day, the journal can say so in one breath. If they do not, they stay two stories. Deferred revenue is not used on freight; unbilled revenue is the bridge when the haul is first.
We do not print ASC 606 or Ind AS 115 certification on a marketing page. Your policies remain yours. The product’s job is to apply the methods you configured and to keep the trail an auditor can follow without a forensic reconstruction of Slack.