FA-58267 / Double-entry ledger accounting / Member archive

Receivables subledger tie-out: difference orientation · case 02

Reconciling differences are reported with the opposite sign.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

x = {'control': [[day, amount]], 'sub': {customer: [[day, amount]]}, 'as_of': day}. Only rows dated on or before as_of count. The subledger total nets every customer balance, including credit (negative) balances. Return {'control', 'subledger', 'difference': control - subledger, 'credit_balances': customers with negative balance sorted by name, 'open_customers': count of nonzero balances}.

Why this case matters

Ledger software must keep debits equal to credits and apply normal-balance, period and cutoff rules exactly; small sign or boundary slips silently misstate financial statements.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
regression: difference orientation	`{"control": 400, "credit_balances": [], "difference": 1350, "open_customers": 4, "subledger": 1750}`	`{"control": 400, "credit_balances": [], "difference": -1350, "open_customers": 4, "subledger": 1750}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.