Month-end close in finance outsourcing: calendar and reconciliations

Month-end close rarely slips because of one major mistake. More often, small dependencies accumulate: a document arrives late, a cost owner does not respond, a reconciliation has no assigned owner, or an adjustment reaches a period that has already been closed. Outsourcing adds another challenge: the client and provider must work from the same calendar, definitions and version of the data.

Start by defining what “month closed” means for your organisation. It may mean a completed set of reconciliations, a management report or approved data handed over for further reporting. Scope and dates depend on systems, contract, accounting policies, group requirements and reporting deadlines. There is no universal schedule suitable for every business.

Set the period boundary and cut-off rule first

Cut-off defines the period to which a transaction belongs and how to handle documents received after the deadline. Agree cut-off dates for invoices, costs, inventory receipts and issues, accruals, adjustments, and data from entities or locations. For each type, document the source, decision owner and route for late items. A provider can register, compile and route exceptions, but should not independently change the client’s accounting policies.

Build the calendar backwards from the reporting deadline

Allow time not only to perform each task, but also for data owners to respond and for differences to be corrected. A sample cadence can be tailored: before month-end, confirm the calendar and missing documents; D+1, register incoming items and run initial checks; D+2–3, reconcile bank, supplier, customer and clearing accounts; D+4, resolve exceptions and review changes; D+5, obtain client approval of the close pack. D is the last day of the period; business-day offsets should reflect actual volume and reporting deadlines.

Give every task an owner and evidence

For each step, record the preparer, approver, deadline, source system, input, output and evidence. Avoid vague entries such as “finance to check”. Instead write: “provider team prepares the supplier account reconciliation by D+2; client controller decides items above the agreed threshold by D+3; the variance report is saved in the shared register.” Separating preparation from approval is especially important for payments, manual journals and exceptions.

Reconcile differences, not just closing totals

Matching ending balances does not always mean every item is correct. Define identifiers, date range, currency, tolerance, source and expected balance. For each variance, record the amount, cause, owner, due date, status and decision to adjust or carry forward. Bank reconciliations compare transactions with statements; receivables and payables analysis reviews open items and ageing; inventory work links quantities, valuation and movement records under the applicable policies.

Create an exception queue and controlled cut-off

After the cut-off, do not silently delete or overwrite prior results. A late document or adjustment should enter a controlled queue with its receipt date, relevant period, proposed action and authorised decision-maker. Agree which items block close, which may remain open and which require manager approval. Every post-close change should retain a history: who requested it, who approved it, what changed and which report must be refreshed.

Measure process quality with a short scorecard

Track task timeliness, the share of reconciliations completed on time, number and value of unresolved variances, post-close adjustments, time spent waiting for client input, and completeness of evidence. Metrics should locate bottlenecks, not shift blame. Review recurring delays monthly and agree one or two process improvements.

What a simple close calendar can look like

Divide the roles: provider prepares, client decides

A provider may support Accounts Payable, balance reconciliations, data compilation for Record to Report, exception registers and process documentation, subject to the contract and access rights. The client retains ownership of its accounting policies, decisions on unusual events, approval of journals and reports, and approval of financial statements. The contract and RACI should define the boundary clearly; role labels do not replace permissions and controls.

Start with one pilot period

Before transferring the full scope, select one period or a limited set of accounts. Test the calendar, file formats, tolerance thresholds, exceptions, cover arrangements and close report. Compare results with the previous process, clarify instructions, and then expand. Also agree how to handle absences, system outages and changes to the close deadline.

BackOffice Outsourcing lists Accounts Payable, balance reconciliations, Record to Report, month-end close support, Inventory and Cost Accounting, internal controls and process documentation among its finance and accounting process services. If you are planning to improve this part of your operation, review the finance and accounting process scope and contact the team to align responsibilities with your policies and systems.

Sources and further reading

• IFRS Foundation — IAS 1: Presentation of Financial Statements
• IFRS Foundation — IAS 10: Events after the Reporting Period
• IFRS Foundation — IAS 21: The Effects of Changes in Foreign Exchange Rates
• IFRS Foundation — IAS 8: Basis of Preparation of Financial Statements
• COSO — Internal Control