Ledger repair after BAN-306

Lithic settlements that never debited the customer, GA flows that charged more than Lithic settled, native Lithic flows mis-stated between 22 April and 31 May 2026, and holds stranded on migration day. Each flow was corrected by one be-lithic reconcile message and verified against prod-ledger. Accounts the correction left below zero were then admin credited through Hydra.

Day by day

Ledger repair by tier

One row is one ledger flow. Amounts are the change to the customer's available balance; for a verified flow they are the sum of the preflight values of every batch that carried it.

Admin credits

The write-off segment Finance named was restored: an Active account in it was credited what the fix took from it net, its debits minus its credits. Every other account was credited up to zero, and only by the part of its negative the fix caused. Blocked and Terminated accounts of the segment were credited to zero, through a forced credit.

Not credited, or not debited back

After the credits

Customer communication lists

Lists handed to CRM, one per message. An account already messaged is left off later lists unless the fix debited or credited it again after the message, in which case it goes on that day's list 4.

Closing checks

Held and open

Batches

By category and subgroup

Accounts

Every account the repair touched, with what the fix did, the admin credit it received, its balance at the last read and the lists it was messaged on.

Flows

Click a flow for its Lithic tokens, native flows, RUIDs and the end state the message set.