System of record & ledger

Several records describe what an agent did, and they disagree by design.

A trace isn't a ledger: a ledger is complete, append-only and kept; traces are sampled, expire, and become personal-data stores once content capture is on. AWS says observability explains activity but isn't a billing report, and OpenAI warns that its usage and cost data may not reconcile.

Logs become evidence. On May 13, 2025, a US court ordered OpenAI to preserve API output logs it would otherwise have deleted (zero-retention customers exempt), an obligation lifted going forward on September 26, 2025. The EU AI Act makes deployers of high-risk systems keep logs at least six months. Keep eval results outside any console that can close.

Sources: AWS harness, OpenAI's usage API (search result), Duane Morris, AI Act Art. 26.

The system acted on is the ledger and the trace is the explanation: stamp every write with the agent's identity and run ID so the two can be joined.

Ask an expert: when the trace says the agent issued a refund but the payments system disagrees, which wins, and who reconciles?

Every fact has an owner, and the payout company owns fewer than its dashboard suggests.

A public remittance company's filing says it may keep prefunding balances with disbursement partners, earns no interest on them, and could lose them if a partner fails to disburse: the money you count isn't in your bank. So each currency needs a three-way reconciliation (ledger, partner statement, rail confirmation). The classic breaks: FX rounding, partner fees netted from balances, returns in pesos against a dollar payout, statements cut in different time zones.

Regulators test the ledger. Model state laws require permissible investments at least equal to outstanding obligations; the UK's safeguarding rules (PS25/12, since May 7, 2026) require daily reconciliations and a resolution pack retrievable within 48 hours; Canada's RPAA requires end-user funds in trust or insured. When ledger and banks disagree, end users lose: the 2024 collapse of a banking-as-a-service middleware company (see spend management) left a gap estimated at up to $95M, and the CFPB allocated $46.2M, about half.

Sources: FCA, Bank of Canada; the remittance company's 10-K under "Cited without links".

The partner's statement says what money exists, your ledger says whose it is, and the rail says whether it moved: reconcile all three, per currency, every day.

Ask an expert: what breaks your reconciliation most often (FX rounding, netted partner fees, returns or time zones), and how long do breaks stay open?

Every fact has an owner, and few of them are you.

The classic breaks: card deposits arrive net and batched against gross invoices; a lockbox deposits one total for fifty checks; an ACH return arrives after the cash was applied; a payer deducts its wire fee. Book fees, returns and corrections as their own entries, never edits. When the ERP and the bank disagree, the bank wins for cash and the ERP for what's owed.

The ledger also carries the loss reserve. CECL (ASC 326) applies to trade receivables: lifetime expected loss from day one, pooled by risk, never zero on current balances, with price concessions and credit memos stripped from loss history. ASU 2025-05 (July 2025) lets any company assume current conditions persist for current receivables, and private companies may also count collections after the balance-sheet date, for years beginning after December 15, 2025.

Nobody is the system of record for remittance or for deduction reasons, so whoever captures them best owns the matching and a clean loss history.

Sources: Deloitte on CECL, KPMG on ASU 2025-05 (July 2025).

Ask an expert: when CRM contract terms and ERP customer terms disagree, which wins, and who fixes it?

Every fact has an owner, and the buyer's ERP owns fewer of them than it seems.

The classic breaks:

• Tool and ERP disagree. The AP tool shows an invoice paid; the ERP still shows it open.
• Received, not invoiced. Goods arrived, the invoice hasn't, and the accrual is a month-end chore.
• Outstanding checks. The ERP says paid; the bank hasn't seen the check.
• Card timing. A virtual card was issued, not yet charged, and nobody can say where the cash sits.

As on the seller's side, the bank wins for cash and the ERP wins for what's owed; corrections post as journal entries, never edits. For audit, the approval trail matters as much as the payment record: auditors test who approved and who released, not only whether the money moved.

Ask an expert: when the AP tool and the ERP disagree on an invoice's status at close, which one wins, and who posts the fix?

Every fact has an owner, and few of them are the platform.

The classic breaks: processor and bank disagree on what settled; card spend is still uncoded at close; unsubmitted out-of-pocket spend is accrued as a guess, or ignored. And pooled funds stop adding up. Synapse, a banking-as-a-service middleware company, failed in April 2024 with its ledger out of step with its banks'. Shortfall estimates ran from $60M to $95M; after suing and reaching a stipulated judgment in 2025, the CFPB allocated $46.2M from its Civil Penalty Fund to those affected. Prepaid cards and spend-platform cash accounts use the same pooled structure.

The FDIC proposed daily reconciliation of custodial accounts in 2024; its agenda lists the final rule as "To Be Determined". Banks demand it by contract anyway: a law firm's August 2026 summary lists real-time, auditable ledger reconciliation among sponsor banks' standard asks.

Sources: American Banker and Banking Dive on Synapse, FDIC proposal and agenda, National Law Review (Aug 2026).

Four ledgers describe one purchase: the bank's wins for what's owed, the expense tool's for why, the ERP's for the books, and someone has to reconcile them every day.

Ask an expert: what daily reconciliation break do you watch most, and who wins when the processor and the bank disagree?

Your inventory database is a copy. Nearly every fact a customer cares about is owned by someone else.

Sources: NANPA 2025 annual report, iconectiv, Somos TSS, Google billing FAQ.

One ledger is only yours. Consent records are the sender's own system of record, and in a lawsuit or a carrier audit they're the only defence. CTIA's short code handbook expects opt records kept six months after an opt-out. The reassigned-number safe harbor protects only callers who can prove they checked the Reassigned Numbers Database, so keep those query logs too.

Ask an expert: when your inventory disagrees with the NPAC, TCR or Meta, which one do support agents trust, and how often do you reconcile against each?