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

Straight-line depreciation journal: salvage exclusion · case 03

Monthly charges are too high for assets with salvage value.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

x = {'cost', 'salvage', 'life_months', 'start_month', 'convention': 'full_month'|'mid_month'|'next_month', 'through': last month to post}. Depreciable base = cost - salvage. The first charge month is start_month (start_month + 1 for next_month). Charges use cumulative rounding: target accumulated after the j-th charge month is round(base*j/life) or, for mid_month, round(base*(2j-1)/(2*life)), half-up and capped at base; each month posts target - accumulated. Posting stops after 'through' or once accumulated reaches base. Return {'schedule': [[month, amount]], 'accumulated', 'book_value': cost - accumulated}.

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: salvage exclusion	`{"accumulated": 100000, "book_value": 0, "schedule": [[2, 14286], [3, 14285], [4, 14286], [5, 14286], [6, 14286], [7, 14285], [8, 14286]]}`	`{"accumulated": 88000, "book_value": 12000, "schedule": [[2, 12571], [3, 12572], [4, 12571], [5, 12572], [6, 12571], [7, 12572], [8, 12571]]}`	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.