Envelope Budget Allocation Ledger

How to use Envelope Budget Allocation Ledger

Start with cash and envelope balances, then process dated income, assign/release, transfer, spend and refund rows. Keep earmark movements separate from external cash and inspect both conservation equations after every event.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Start with cash and envelope balances, then process dated income, assign/release, transfer, spend and refund rows. Keep earmark movements separate from external cash and inspect both conservation equations after every event.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–30 distinct envelopes and 1–200 distinct events on nondecreasing dates from openingDate, Gregorian 1900–9999. Opening balances are nonnegative exact cents; transactions are positive exact cents, each up to 1,000,000,000. Initial assigned amounts cannot exceed cash.
• No negative borrowing. Assignments need unassigned cash, transfers/releases/spending need envelope funds, and transfers require different envelopes. A refund must name an earlier spend, return to its original envelope and stay within its unreimbursed amount. Equal-date input order matters.
• Cash-only mathematical ledger, not bank software or budgeting advice. No credit cards, debt, account transfers, planned income, automatic month reset, forecast, investment, real transaction or source-authenticity verification. Assigning or moving earmarks is not spending.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.