Report views vs raw wallet ledger rows

Report views and raw wallet ledger rows look similar in a month-end folder, yet they answer different questions. A report view rolls up delivered, failed, unknown, and spend for product and finance. A ledger row is the prepaid debit or credit line that moved the wallet.

IOSOR keeps the split hard. Export a report when you need product or finance rollups. Open the wallet ledger when you need every hold, debit, refund, and top-up line. Mixing them invents a second money truth.

Report views roll up product and finance truth

A report view answers how the corridor performed: delivered share, unknown share, latency bands, and spend against the prepaid balance. Product uses it for launch reviews; finance uses the same rollup for invoice weeks — not a private sheet with different status labels.

Keep columns tied to shared DLR language. Delivered is a receipt. Submitted is not delivered. Unknown stays unknown until a receipt arrives. When a report folds unknown into “success,” both product and finance will argue with the wallet later.

Raw ledger rows stay under Wallet

Wallet month-end export at 02:00 is the ledger job. It lists holds, debits, refunds, and top-ups as line items. That file proves money moved — not how product charts deliverability. Pasting ledger lines into a product dashboard double-counts refunds or misses multi-segment debits.

Route money disputes to Wallet; deliverability disputes to the report and DLR path. Do not “fix” a missing debit by editing the report CSV. The wallet ledger is the money source; the report reconciles to it without replacing it.

Ops metrics export is a sibling clock, not the ledger

Ops metrics export at 02:00 tracks queue depth, webhook freshness, latency, and error bands. It can share the month-end clock, yet it is not a wallet dump or finance invoice sheet. Use it to explain elevated unknown or latency — then return to the report for rollups and to Wallet for money lines.

White-label DLR latency reporting must stay honest: latency bands explain enterprise tickets without renaming unknown to delivered. Reports cite those bands — they do not invent a parallel ledger.

Refuse hybrid CSVs that paste ledger lines into report packs

A zip that mixes “report_success.csv” with raw debit rows trains the org to treat report views as money proof. Publish two artifacts: the report pack (rollup columns, DLR states, spend totals) and the Wallet ledger export (line items). When a partner asks for “the full money report” in one file, answer with two links: reports for views, Wallet for ledger rows.

Related ops paths

• Wallet month-end export at 02:00
• Ops metrics export at 02:00
• White-label DLR latency reporting truth

Start with IOSOR

Export your monthly report view from the console to verify corridor delivery rates and DLR latency rollups for product reviews. Pull your raw ledger line items strictly from the Wallet section to audit debits, holds, and refunds without double-counting status changes. Deliver the ledger export to finance and the report pack to product leads as distinct artifacts.

IOSOR takeaway

Mixing raw debit line items into aggregated product reports creates distorted spend metrics and double-counts refunded message segments. Report views establish corridor health and delivery truth, while the Wallet ledger provides indisputable proof of financial balance movements.

Do publish two distinct exports at month-end—a report rollup pack for ops and a dedicated Wallet ledger export for accounting. Don't paste raw ledger debit rows into delivery dashboards or treat aggregated report views as line-item bank statements.