Month-End Close Engine

Closing a month is not one operation but a chain: cancel the previous close, set correct document timestamps, repost the period, resolve duplicate invoices, and only then close. An accountant triggered each step by hand, and any of them could fail with "document posting sequence violated" — sending them back to square one.

The processor runs the whole chain in one go and clears the usual causes of failure along the way. It widens the reposting window automatically when the sequence boundary has slipped into the previous month — precisely what kept breaking the depreciation routine, in the accountant's words "every single time, in every company". It flags duplicate invoices. It backfills missing counterparty tax registration codes from the state register by tax ID, where a tax authority or network failure is logged but never halts the close. A readiness check runs first: if closing isn't possible, the processor names the reason and the offending document up front instead of failing midway.

The second mode closes the period with a work-in-progress calculation, for a manufacturing client. That chain is longer: cancelling material transfers and WIP inventories, an initial close, the WIP calculation with automatic inventory creation, a final close, and reversal entries. The calculation methodology itself was written up as a formal appendix to the accounting policy, fit to be presented during a tax audit.

Running in production across five client databases: standard mode on four, WIP mode on the manufacturing one. In WIP mode the history from January 2023 through June 2026 was recalculated and re-closed — 42 consecutive months, each with its own pair of WIP control entries.