Monthly close agreements: the dates and deliverables to put in writing

A close agreement should identify what management receives, not only when a task is marked complete. Name the statements, reconciled accounts, material schedules, adjusting-entry support, and unresolved questions included in the package.

Specify the entity and reporting basis. A consolidated report and separate entity statements are different deliverables. Confirm whether payroll, inventory, subscription revenue, and processor balances are covered where they affect the business.

List the reports and approvals the provider needs and the date each must arrive. Assign an internal owner for payroll changes, receipts, customer contracts, warehouse records, and unusual transactions. Explain how late information affects the agreed timetable.

For example, a proposed tenth-business-day close may depend on payroll and processor reports reaching the team by the third business day. The agreement should show that dependency rather than leave the founder to discover it after a missed date.

Agree how material unresolved items are evaluated and escalated. A missing receipt and an unexplained large cash balance should not receive identical treatment. Ask the reviewer to establish the basis for releasing statements with known exceptions.

Require an open-items list with amount, owner, next action, and expected resolution. Keep those items visible in the next close. Carrying a balance forward without review is different from an explained timing difference.

Confirm who prepares reconciliations and who reviews the balance sheet and adjustments. Establish how management questions are raised and when the firm responds.

If a closed month needs correction, preserve the adjustment, approval, and impact on reports already distributed. Determine who updates the management pack and any tax handoff. A corrected ledger alone does not guarantee that the board or lender received the new figures.

Track delivery dates, incomplete inputs, repeated exceptions, and corrections. Discuss patterns at a proportionate cadence rather than escalating every minor delay.

Use the agreement to improve the workflow when a recurring report arrives late or an integration posts incorrectly. The expected result is a dependable package with named responsibilities, plus an honest record of the assumptions needed to deliver it.