month-end-close

Topics in the source

• Month-End Close
• Workflow
• The gates block on (exit 4)
• Hard rules
• Scripts
• References and assets

Portability: 3 stdlib scripts, no network, no ERP connection. Export CSV or JSON; the scripts plan, prove and gate. Not accounting or audit advice. Thresholds and aging limits are your policy; the scripts make you state them. A slow close is rarely slow everywhere. One chain of dependent tasks sets the close date, reconciliations "agree" without a proof, and flux review accepts "timing" as a reason. Each script attacks one of those. Step 1 schedules each task as soon as its predecessors finish, then checks the plan against people: one person booked for 1.5 days on WD1 is a plan that will slip. Speed up the critical path, nothing else. Step 2 matches by reference, then by amount within a date window, then pairs digit transpositions (7,980 vs 7,890) into one correcting entry. What is left is a reconciling item: in the GL only (timing) or in the source only (book a journal entry). Opening-balance rows are balances, not transactions: when the two sides open at different amounts, that difference came from last month and blocks sign-off until it is traced there; it is never booked this period. The proof must close to zero. Step 3 marks an account material when it passes your threshold ru

This is an excerpt. Refer to the complete source and its current requirements.