Month End Close Process: Steps, Owners, Calendar

2026-09-23 · Tommaso Maria Ricci

Nearly eight in ten corporate finance professionals say their month end close process is delayed by waiting for data from other systems or departments. That finding comes from a LiveFlow survey reported by CFO Dive in May 2026, and it matches what I see in almost every finance team I sit with. The same research found that only 16% of respondents close in under three days, while 37% need three to five days, 21% need five to ten, and 16% need more than ten.

Read that first number again. The close is rarely slow because accountants are slow. It is slow because the close is the moment when every other department's unfinished work lands on the general ledger at once: the purchase orders nobody receipted, the sales credits nobody approved, the intercompany charge nobody agreed, the bank feed nobody matched. The accountants inherit the backlog and get blamed for the delay.

This guide treats the close the way the other articles in this series treat order to cash and procure to pay: as a sequence of steps with named owners, a calendar that says who does what on which day, and a short list of handoffs where the time actually disappears. It covers the checklist, the metrics in the order they cause each other, the failure modes, what to automate and what to keep human, a maturity model, a self-assessment and a 90 day plan. If you run a US entity, there is also a section on SOX and internal controls.

What is the month end close process

The month end close process is the set of activities a finance team performs after the last day of a month to make sure every transaction for that period is recorded, reconciled, reviewed and reported. At the end of it, management gets a trial balance and a set of financial statements it can trust, and the period is locked so nobody can post into it by accident.

That is the textbook definition. The practical definition is sharper: the close is the monthly test of whether your operational processes produce accounting data that is complete and correct without human rescue. When purchasing, billing, payroll and treasury run cleanly during the month, the close is a verification exercise that takes a few days. When they do not, the close becomes a reconstruction exercise, and reconstruction has no fixed duration.

This distinction matters because it changes where you look for improvement. Most companies try to speed up the close by working harder inside the close window. The larger gains come from moving work out of the window, into the month, and from fixing the upstream processes that generate the corrections. A team that posts forty manual accruals every month does not have a close problem. It has a procure to pay problem that shows up in the close.

Month end close, quarter end and year end

The monthly close is the base unit. The quarter end close adds disclosures, more rigorous review, often a tax provision and, for public companies, the preparation of the quarterly filing. The year end close adds the audit, full disclosures, impairment testing, and the adjustments that accumulated because nobody wanted to deal with them in October.

A good monthly close makes the year end boring, which is the goal. A weak monthly close pushes work into the quarter and the year, where it costs more because the auditors are watching and the deadlines are external. If your year end takes three times as long as your monthly close, your monthly close is probably skipping steps that the year end then has to do in full.

What "closed" should mean

Teams argue about how many days their close takes because they measure different things. I use one definition: the close is done when the consolidated financial statements for the period have been reviewed by the controller, the period is locked in the system, and the management pack has been sent. Soft closes, flash reports and preliminary numbers are useful, but they are not the close.

Pick a definition, write it down and measure against it every month. Without a fixed finish line, days to close becomes a negotiation, and every team member will quietly count from the day they personally started.

Why the close is slow: the evidence

Three independent data sources point in the same direction, and none of them points at the accounting team's work ethic.

The first is the LiveFlow research above: waiting for data from other systems or departments is the dominant cause of delay, cited by nearly eight in ten respondents, with more than half also naming the work of reconciling information across multiple platforms.

The second is Ledge's 2025 month end close benchmark, a survey of 100 finance professionals at companies with roughly 51 to 200+ employees. Ledge sells close software, so read it as vendor research, but the primary data is useful. Only 18% of teams closed in one to three business days, 32% took four to five, 23% took six to seven, and 27% took more than seven. Asked about blockers, 56% cited cross department dependencies, 50% Excel driven workflows, 40% legacy systems that do not integrate and 37% understaffing. 94% of teams use Excel during the close, and most automate less than 40% of it. Cash reconciliation alone consumed 20 to 50 hours per month.

The third is ISG's Ventana Research. In a March 2023 analyst perspective, Robert Kugel reported that 88% of organizations using extensive automation in their close finish within six business days, against 40% of those using little or no automation. The same piece noted that 40% of midsize and larger organizations still handle consolidation exclusively in standalone spreadsheets.

The older benchmark everyone still quotes

The most cited benchmark on days to close is APQC's, from its General Accounting Open Standards Benchmarking survey. As reported on CFO.com, with 2,300 organizations answering, the top quartile closed in 4.8 calendar days or less, the median needed 6.4, and the bottom quartile needed 10 or more. That data was published in March 2018, so treat it as a historical reference point, not a current benchmark. It is still useful for one reason: it measures from running the trial balance to completing consolidated statements, which is a clean definition.

Put the sources together and the picture is consistent across eight years and several methodologies. Somewhere between a third and a half of companies need more than five business days. A minority close in three or fewer. And the teams that close fast differ from the slow ones mainly in two things: how much of the upstream data arrives clean, and how much of the matching and checking runs without a person.

What slowness costs

Days to close sounds like an internal efficiency metric. It is really a decision latency metric. If your books close on the tenth business day, management is looking at last month's margin in the third week of this month. Pricing, hiring and spend decisions get made on intuition in the meantime, and the finance team spends the second half of every month explaining numbers that are already stale.

There is also a quality cost. A Gartner survey of 497 accountants in controllership roles, published in February 2024 and conducted in July 2023, found that 59% make several errors every month, and it linked the errors to capacity constraints: misinterpreted data, manual work, reopened books and weak reviews. A compressed, chaotic close is exactly the environment in which reviews become weak.

Month end close process steps and owners

A close checklist without owners is a wish list. Every step below has a function that owns it and, in a working team, a person's name next to it. The function is a starting point. The name is what makes it happen.

Step 1: subledger cutoff. Accounts payable, accounts receivable, payroll, inventory and fixed assets are closed for the period so no new transactions land in the old month. Owner: the manager of each subledger, individually. Nobody owns "the subledgers" collectively.

Step 2: cash and bank reconciliation. Every bank, card and payment processor account is matched to the ledger, and differences are explained. Owner: treasury or the general ledger accountant responsible for cash.

Step 3: revenue and receivables review. Billing is complete for the period, deferred revenue is rolled forward, credit notes are posted, and the receivables aging supports any allowance. Owner: the revenue accountant, with sales operations confirming that all billable events were captured.

Step 4: accruals and prepaids. Expenses incurred but not invoiced are accrued, prepaids are amortized, and last month's accruals are reversed or confirmed. Owner: the general ledger accountant, with budget holders providing the inputs.

Step 5: payroll and benefits. Payroll expense, taxes, bonuses and commissions accruals are posted and reconciled to the payroll provider. Owner: payroll, reviewed by the controller.

Step 6: inventory and cost of sales. Where relevant, inventory is counted or rolled forward, reserves are updated and cost of goods sold is reconciled. Owner: cost accounting, with operations confirming physical quantities.

Step 7: fixed assets and leases. Additions, disposals and depreciation are posted, and lease schedules are updated. Owner: the fixed asset accountant.

Step 8: intercompany. Charges between entities are agreed on both sides, eliminated and settled or scheduled for settlement. Owner: a single intercompany coordinator, not each entity separately.

Step 9: balance sheet reconciliations. Every balance sheet account has a reconciliation with supporting evidence, a preparer and a reviewer. Owner: each account's assigned preparer, with the controller or assistant controller as reviewer.

Step 10: consolidation and FX. Entities are translated, eliminations are posted, and minority interests or other adjustments are recorded. Owner: the consolidation or group reporting lead.

Step 11: flux analysis and review. Variances against prior period and budget are explained, significant items are investigated, and the controller signs off. Owner: FP&A for the business explanations, the controller for the accounting ones.

Step 12: reporting and lock. Financial statements and the management pack are produced, reviewed and distributed, and the period is locked. Owner: the controller, with the CFO as final approver.

Twelve steps sounds like a lot. In a small company several collapse into one person's afternoon. The point of listing them separately is that each one has a different upstream dependency, and each dependency is a place where the close can stall.

The close calendar: day by day, with owners

The calendar is the single most useful artifact in the close. It turns a checklist into a schedule, which means it turns vague responsibility into a deadline that someone can miss. Below is the calendar I start from with a mid-sized, multi-entity company. Day 0 is the last calendar day of the month; positive days are business days after it.

Before the month ends: Day -3 to Day 0

Day -3. Procurement and budget holders confirm goods and services received but not yet invoiced, so accruals can be prepared from real information rather than memory. Sales operations confirms any billing events expected before month end. Owner: the general ledger accountant sends the request; budget holders own the answers.

Day -2. Intercompany charges for the month are calculated and sent to counterpart entities for agreement. Recurring journal entries are staged. Payroll confirms the final run and any off-cycle payments. Owner: intercompany coordinator and payroll.

Day -1. Pre-close reconciliations for stable accounts (prepaids, fixed assets, most liability accounts) are prepared using month-to-date balances, so only the final days remain. Owner: each account preparer.

Day 0. Cutoff. Accounts payable stops entering invoices dated in the period after a fixed hour. Billing issues the final invoices. Inventory counts, if any, happen. Owner: each subledger manager confirms cutoff in writing.

After the month ends: Day +1 to Day +5

Day +1. Bank and card feeds are pulled and matched. Subledgers are closed and their totals are tied to the general ledger. Accruals are posted. Payroll is posted. Owner: treasury, subledger managers, GL accountant.

Day +2. Revenue is finalized, deferred revenue is rolled forward, intercompany balances are confirmed by both sides and disagreements are escalated. Inventory and cost of sales are finalized. Owner: revenue accountant, intercompany coordinator, cost accounting.

Day +3. Balance sheet reconciliations are completed and submitted for review. Consolidation and FX translation run. A first flux analysis identifies unusual movements. Owner: account preparers, consolidation lead.

Day +4. Reviewers clear reconciliations. FP&A and budget holders explain operating variances. Late adjustments are posted only through the controller. Owner: controller, FP&A.

Day +5. Financial statements and management pack are finalized, approved and sent. The period is locked. A short retrospective records what slipped and why. Owner: controller and CFO.

A five day calendar is realistic for a mid-sized company with clean subledgers and a working reconciliation discipline. A company with complex consolidation or manufacturing cost accounting may need seven. A small single-entity business can often close in three. What matters is less the number than the fact that every line has a day and a name, and that the calendar is published where everyone who feeds the close can see it.

The rule that makes the calendar hold

Every input from outside finance has a deadline, and late inputs are handled by a published rule: finance estimates the number, posts the estimate and adjusts next month. The budget holder who misses the Day -3 accrual deadline does not get to hold the close open. This rule feels harsh the first month and saves the calendar forever after. Without it, the close ends when the slowest department finishes, which is the definition of an unmanaged process.

The handoffs where close time gets lost

The steps are not where days disappear. Days disappear at the boundaries between steps, where one team's output is another team's input and nobody owns the gap. These are the five I find most often.

Late accruals: operations to finance

The general ledger accountant needs to know what was received and not yet invoiced. The people who know are in operations, marketing, IT and facilities. They are not in the close, they do not feel its deadline, and they answer the accrual request on Day +3 when the accountant chases them for the second time.

The fix is upstream. If purchase orders are raised before spend and goods receipts are recorded when services are delivered, most accruals become a system report instead of an email chain. That is the procure to pay discipline described in the guide on procure to pay process design and controls. Where purchase orders do not exist, a standing monthly accrual template sent to budget holders on Day -3, with a Day -1 deadline and a default estimate rule, recovers most of the lost time.

Intercompany: entity to entity

Intercompany is where multi-entity groups lose the most time, and it is almost entirely avoidable. Entity A books a management fee. Entity B has not received the invoice, disagrees with the amount, or booked it at a different exchange rate. The difference surfaces at consolidation on Day +3, both controllers email each other, and the elimination waits.

Three rules remove most of this. First, one person owns intercompany for the whole group. Second, the charging entity books and the receiving entity mirrors automatically, or at least from the same document on the same day. Third, a fixed rate for the month is agreed before month end. Groups operating across the US and Europe add a currency and tax layer that makes this even more important, since the transfer pricing documentation depends on the same numbers.

Bank reconciliation: treasury to accounting

Cash should be the easiest account to reconcile, because the bank provides an independent record. In practice it is often the slowest, because of volume: card transactions without receipts, payment processor settlements that net fees and refunds, and customer payments without remittance detail. Ledge's respondents reported 20 to 50 hours a month on cash reconciliation alone, across three to five systems.

The answer is to reconcile daily or weekly, not monthly. Bank matching rules handle the recurring patterns, exceptions are cleared as they occur, and the month end reconciliation becomes a confirmation of a balance that was already agreed on the 28th. The receivables side of this, cash application against open invoices, is covered in the guide on the order to cash process, steps and owners.

Subledger cutoffs: operations to the ledger

A subledger that stays open after month end keeps generating transactions dated in the old period. An invoice from the 30th arrives on the 4th and accounts payable enters it with the original date. A shipment from the 31st is invoiced on the 2nd. Each of these moves the trial balance after the close team has started reconciling it, which forces rework.

The fix is a written cutoff policy that states which document date governs, what happens to items received after cutoff (they go through the accrual, not a backdated entry), and who confirms that each subledger is closed. The confirmation should be a named person saying "closed" on Day 0 or Day +1, recorded in the checklist.

Review queues: preparers to the controller

The last hidden handoff is inside finance. Reconciliations are prepared on Day +3 and the controller reviews them on Day +4, all at once, while also answering the CFO's questions and posting late adjustments. The review becomes a bottleneck and, worse, a weak control, because the reviewer does not have time to look.

Spread the review. Stable accounts reconciled on Day -1 get reviewed on Day +1. High risk accounts get a reviewer assigned in advance. Materiality thresholds decide what needs full review and what needs a glance. The Gartner finding about weak reviews and reopened books describes what happens when this handoff is left to chance.

The close checklist

A useful close checklist is short enough to be read, specific enough to be tested and structured by day. Below is a condensed version you can adapt. Each line needs an owner's name, a due day and a completion flag.

Pre-close (Day -3 to Day 0)

1. Accrual request sent to budget holders with deadline and default rule.
2. Expected billing events confirmed with sales operations.
3. Intercompany charges calculated and sent for agreement at the month's fixed rate.
4. Recurring journals staged and reviewed.
5. Stable account reconciliations prepared on month-to-date balances.
6. Payroll final run confirmed.
7. Cutoff time communicated to accounts payable, billing and inventory.

Core close (Day +1 to Day +3)

1. All bank, card and processor accounts reconciled, differences explained.
2. Each subledger confirmed closed and tied to the general ledger.
3. Accruals and prepaids posted, prior month reversals checked.
4. Revenue finalized, deferred revenue rolled forward.
5. Payroll, bonus and commission accruals posted.
6. Inventory and cost of sales finalized where relevant.
7. Fixed asset additions, disposals and depreciation posted.
8. Intercompany balances agreed on both sides and eliminated.
9. Consolidation and FX translation completed.
10. All balance sheet reconciliations submitted with evidence.

Review and report (Day +3 to Day +5)

1. Reconciliations reviewed, sign-off recorded.
2. Flux analysis against prior month and budget, with explanations above threshold.
3. Late adjustments posted only with controller approval, and logged.
4. Financial statements and management pack approved.
5. Period locked.
6. Retrospective: what slipped, why, which owner, what changes next month.

Line 23 is the one teams skip, and it is the one that makes the close faster over time. A fifteen minute retrospective, with the list of items that slipped and the name of the upstream owner, is how a seven day close becomes a five day close without buying anything.

Metrics for the month end close process, in causal order

Days to close is the metric everyone reports, and it is the wrong one to manage directly. It is an outcome. It moves when the inputs move. Manage the inputs in the order they cause each other and days to close follows.

1. Upstream input timeliness

Share of inputs from outside finance (accrual confirmations, billing confirmations, intercompany agreements, payroll data) received by their calendar deadline. If this is below 80%, nothing else you do inside finance will produce a fast close, because you will be waiting. Track it by department and publish it. Visibility does most of the work.

2. Subledger close on time

Number of subledgers confirmed closed and tied to the general ledger by Day +1. Each late subledger shifts every downstream step.

3. Reconciliations completed on time

Share of balance sheet reconciliations submitted by their due day, and share reviewed by their review day. Measure both. A team that prepares on time and reviews late has moved the bottleneck, not removed it.

4. Unreconciled and aged items

Number and value of reconciling items older than 30, 60 and 90 days. Old reconciling items are small problems that nobody has resolved, and they compound. This metric also tells auditors a lot about your controls.

5. Manual journal entries per close

Count of manual journals, split into recurring and non-recurring, with the value of each. High recurring manual volume means automation candidates. High non-recurring volume means upstream processes are generating corrections.

6. Post-close adjustments

Number and value of entries posted after the books were declared closed, including those that reopen a locked period. This is the quality metric that balances days to close. A team that closes in three days and then posts twenty adjustments did not close in three days.

7. Days to close

Business days from month end to the finish line you defined. Report it last, as the result of everything above. When it gets worse, the first six metrics will tell you why.

Why the order matters

The order is causal. Late inputs cause late subledger closes, which cause late reconciliations, which leave aged items unresolved, which get patched with manual journals, which generate post-close adjustments, which extend the close. Teams that target days to close directly usually compress the review step, because it is the only one fully under finance's control. The result is a faster close with more adjustments and weaker controls, which is worse than the slow close it replaced.

Failure modes I see repeatedly

These are the patterns that keep a close slow even after a team has a checklist and a calendar.

The heroic controller. One person holds the close together through personal knowledge. The close takes five days when they are present and nine when they are on holiday. The fix is documentation of each account's reconciliation method, a second trained person for every critical step and a calendar that does not depend on anyone's memory.

The spreadsheet consolidation. Consolidation runs in a workbook with linked tabs that only one person understands. ISG's finding that 40% of midsize and larger organizations still consolidate exclusively in spreadsheets tells you how common this is. Spreadsheets are fine for a two entity group. Past five entities or two currencies, they become a control risk and a single point of failure.

The reconciliation that is a signature. A reconciliation that shows the ledger balance equal to the ledger balance, signed by the preparer and the reviewer, with no independent evidence. It passes the checklist and catches nothing. Every reconciliation should tie to something outside the ledger: a bank statement, a subledger report, a third party confirmation, a calculation with visible inputs.

Closing into the next month. The team is still correcting March when April begins, so April's daily work is neglected, which makes April's close slower. This spiral is common after a system migration or a staff departure, and it only breaks with a deliberate decision to accept estimates, close, and fix in the following period.

Flux analysis as decoration. Variances are explained with phrases like "timing" or "higher activity" that nobody challenges. The analysis exists to catch errors before the numbers leave finance. If it never catches anything, either the books are perfect or nobody is really looking.

Automating the chaos. A company buys close software to fix a process that has no owners and no calendar. The tool faithfully tracks tasks that are still late for the same upstream reasons. Software amplifies a working process. It does not create one.

The management pack nobody reads. The close produces a sixty page pack, and the CEO looks at two numbers. The extra fifty eight pages consume days of finance time each month. Ask the readers what decisions they make from the pack and cut the rest.

What to automate, and what to keep human

The ISG data gives a clear direction: teams with extensive automation are much more likely to close within six business days. The question is which automation, in which order. My rule is the same as for accounts payable and order to cash: automate what you can describe in plain language on one page, and keep judgment with people.

Continuous accounting first

Continuous accounting means moving close work into the month. Bank matching runs daily, intercompany is agreed weekly, reconciliations for stable accounts are prepared before month end, accruals are captured as goods are received. It is less a technology than a calendar change, and it is the single largest lever. A close that starts on Day +1 with half the reconciliations already done is structurally faster than one that starts from zero.

Reconciliation automation second

Transaction matching for bank, card, processor and intercompany accounts is the most mature automation in the close, and the most repetitive work. Rules match the obvious items, exceptions go to a person with the context attached, and the reconciliation report is generated rather than assembled. This is where Ledge's 20 to 50 hours of monthly cash reconciliation comes back. The same logic applies to supplier invoice matching, which is covered in the guide on how to automate the accounts payable process.

Recurring journals and allocations third

Depreciation, prepaid amortization, standard accruals, cost allocations and recurring intercompany charges follow rules that do not change month to month. They should post from schedules, with a review of the output rather than a manual entry of the input. Every recurring manual journal is a risk of a keying error and a use of close time that adds nothing.

AI for variance commentary, with limits

This is where the conversation in most finance teams is right now. Gartner's 2025 finance survey, reported by CFO Dive in November 2025, found 59% of finance functions using AI, barely changed from 58% in 2024, with 91% of users reporting only low or moderate impact so far. Error and anomaly detection was among the top three use cases, at 34%.

Language models are good at drafting first pass variance commentary from structured data: this account moved by this much, driven by these transactions, compared with this pattern. They are also good at flagging unusual entries for review. They are not good at knowing why the business did something, and they will write a confident explanation for a variance that is actually an error. Use them to draft and to flag. Keep the explanation's owner human, and never let generated commentary reach management without someone who knows the business reading it. The broader view on where AI helps finance and where it does not is in the guide on AI for CFOs.

What stays human

Judgment on estimates (bad debt reserves, inventory obsolescence, bonus accruals, revenue recognition on unusual contracts), the review and sign-off of reconciliations, decisions on late adjustments, and the conversation with budget holders about why their numbers moved. These are the steps where accountability matters, and where auditors expect to see a person's name.

If you want a second pair of eyes on which parts of your close are ready for automation and which need fixing first, send a consultation request through the site with your current calendar and the number of days you close in today. That is usually enough to find the first two days.

SOX and internal controls for US companies

If your company is listed in the US, or is preparing to be, the close is not only an efficiency topic. The Public Company Accounting Oversight Board's auditing standard AS 2201, which governs audits of internal control over financial reporting, requires the auditor to evaluate the period-end financial reporting process "because of its importance to financial reporting". The standard defines that process to include the procedures used to enter totals into the general ledger, to initiate, authorize, record and process journal entries, and to record recurring and nonrecurring adjustments.

In practice, this means the close checklist is also your control framework. Three areas get the most attention.

Journal entry controls. Who can post, who approves, what thresholds require a second approval, and how manual and top-side entries are reviewed. Segregation between preparer and approver is the baseline. AS 2201 specifically names controls over journal entries and adjustments made in the period-end process among the antifraud controls the auditor considers.

Reconciliation evidence. Each reconciliation needs a preparer, a reviewer, a date and supporting documents. A reconciliation reviewed without evidence of the review is, for audit purposes, a reconciliation that was not reviewed.

Period locking and post-close changes. Who can reopen a period, with what approval, and how the reopening is logged. Post-close adjustments are a control indicator as much as a quality metric.

The external deadline also shapes the calendar. According to the Deloitte Accounting Research Tool, Form 10-Q is due 40 days after quarter end for large accelerated and accelerated filers and 45 days for non-accelerated filers. A monthly close that takes ten business days leaves little room for review, disclosures and audit committee sign-off within that window.

Private companies are not subject to SOX, but the same logic applies when you raise capital, take on bank covenants or prepare for an acquisition. Investors and lenders do their own diligence on the close. For European founders operating a US entity, as many of the companies I work with between Rome and Miami do, it is worth building the close to SOX-like standards early: documented owners, evidenced reconciliations, approved journals. It costs little at small scale and a great deal to retrofit later.

Maturity stages of the close

Most finance teams sit at one of five stages. The stage matters more than the tool set, because each stage has a different next move.

Stage 1: reactive

No written checklist. The close is done by whoever knows how, in the order they remember. Days to close varies widely month to month. Reconciliations exist for cash and not much else. Next move: write the checklist, assign owners, set a target day for the management pack.

Stage 2: documented

A checklist exists with owners. A calendar exists but upstream inputs arrive late and the close ends when the last one arrives. Most reconciliations are done, often without independent evidence. Next move: enforce input deadlines with the estimate rule, add evidence standards to reconciliations, start measuring the causal metrics.

Stage 3: managed

The calendar holds most months. Metrics are tracked and reviewed. Reconciliations are evidenced and reviewed on schedule. Manual journals are still high and consolidation may still be in spreadsheets. Next move: move stable work before month end, automate bank and intercompany matching, turn recurring journals into schedules.

Stage 4: continuous

Significant work happens during the month. Matching runs daily. Recurring entries post automatically. The close is mostly review, judgment and reporting, and takes three to five business days. Next move: reduce post-close adjustments to near zero, introduce AI assisted variance drafting under human review, shorten the management pack.

Stage 5: integrated

The close is a byproduct of well-run operational processes. Upstream systems produce clean data, exceptions are rare and resolved in the month, and finance spends close week on analysis rather than assembly. Very few mid-sized companies are here, and it is not necessary to be. Stage 4 is the realistic target for most.

Self-assessment: score your close in ten minutes

Answer each question with 0 (no), 1 (partly) or 2 (yes). Be honest; the score is for you.

Ownership and calendar

1. We have a written close checklist where every step has a named person, not a department.
2. We have a published close calendar with a due day for every step, including inputs from outside finance.
3. Late inputs from other departments are handled by a written estimate rule, and the close does not wait for them.
4. Every subledger is formally confirmed closed by a named person by Day +1.
5. Bank and card accounts are reconciled at least weekly during the month.
6. Intercompany charges are agreed by both entities before month end, at a fixed rate, by one owner.

Evidence, measurement and automation

1. Every balance sheet reconciliation ties to independent evidence and has a recorded reviewer.
2. We track manual journal entries per close, split into recurring and non-recurring.
3. We track post-close adjustments and their value every month.
4. Recurring journals and allocations post from schedules rather than manual entry.
5. Consolidation runs in a system rather than a linked spreadsheet (score 2 if single entity).
6. We hold a short retrospective after each close and change something as a result.

Scoring. 0 to 8: Stage 1 or 2. Your close is limited by ownership and calendar, not tools, and buying software now would be premature. 9 to 16: Stage 3. The foundations exist; the next gains come from moving work into the month and automating matching. 17 to 24: Stage 4 or close to it. Focus on post-close adjustments, review quality and the usefulness of what you report.

Look at which questions scored zero rather than at the total. A zero on question 3 alone can explain two days of close time.

A 30/60/90 day roadmap

This is the sequence I use when a company wants a measurably faster close within a quarter, without a system replacement.

Days 1 to 30: measure and assign

Run one close with a stopwatch. Record when each step actually started and finished, and when each upstream input actually arrived. Write the twelve step checklist with a name on each line. Draft the calendar from Day -3 to your target day. Define "closed" in one sentence. Start tracking the seven metrics, even in a spreadsheet. Agree the estimate rule for late inputs with the CFO and publish it to budget holders before the next month end.

Expected result: no dramatic change in days to close yet, but a clear picture of where the time goes. In most companies, two or three handoffs account for more than half the delay.

Days 31 to 60: fix the handoffs

Attack the two or three largest delays you measured. Typically that means the accrual request moves to Day -3 with a default rule, intercompany gets a single owner and a fixed rate, and bank reconciliation moves to weekly. Prepare stable reconciliations before month end. Spread reconciliation review across the close rather than concentrating it on one day. Hold the first retrospective and publish input timeliness by department.

Expected result: one to three business days removed from the close, mostly by eliminating waiting.

Days 61 to 90: automate the routine

Now that the process has owners and a calendar, automate the parts whose rules are stable: bank and card matching, recurring journals, standard allocations, intercompany matching. Review the manual journal list and eliminate or schedule every recurring item. Pilot AI drafting of variance commentary on a subset of accounts, with a named reviewer for each. Tighten journal approval thresholds and period locking if you are, or plan to be, subject to SOX.

Expected result: a stable close calendar that holds most months, fewer manual journals, and the capacity to spend close week on analysis. For the wider view on sequencing AI and automation across the accounting function, the guide on AI for accounting goes deeper.

Where this connects to the rest of finance

The close sits at the end of every other finance process. Order to cash determines how clean revenue and receivables are when the month ends. Procure to pay and its sourcing front end, described in the guide on source to pay stages and owners, determine how many accruals you need and how reliable they are. Payroll, treasury and inventory each contribute their own subledger.

This is why a fast close is so rarely achieved by the close team alone. The companies I have seen close in three to four days did not get there by asking accountants to work faster. They got there by making every upstream owner accountable for the quality of the data they hand to finance, and by giving finance the authority to enforce deadlines. That is an organizational decision, and it has to come from the CFO or the CEO.

If you are at the point where the close calendar exists but keeps slipping for reasons outside finance, that is usually the moment an outside view helps most. Send a consultation request through the site with a short description of your entities, systems and current days to close, and we can look at where the handoffs are costing you time.

FAQ

What is the month end close process?

The month end close process is the set of steps a finance team completes after each month ends to record, reconcile, review and report every transaction for that period. It typically includes subledger cutoff, bank reconciliation, revenue and accruals, payroll, inventory, fixed assets, intercompany, balance sheet reconciliations, consolidation, variance review and reporting. It ends when reviewed financial statements are distributed and the period is locked in the system so no further entries can be posted to it without approval.

What are the month end close process steps and owners?

A practical close has twelve steps, each with a named owner. Subledger managers own cutoff. Treasury owns cash reconciliation. The revenue accountant owns revenue and receivables. The general ledger accountant owns accruals and prepaids, with budget holders supplying inputs. Payroll, cost accounting and the fixed asset accountant own their areas. One coordinator owns intercompany. Each balance sheet account has a preparer and a reviewer. The consolidation lead owns consolidation and FX, FP&A and the controller own variance review, and the controller and CFO own reporting and the period lock.

How long should the month end close take?

For a mid-sized company, three to five business days is a realistic target, and five to seven is common. Ledge's 2025 survey of 100 finance professionals found half of teams need more than five business days, and only 18% close in three or fewer. A LiveFlow survey reported in May 2026 found 16% closing in under three days. Complex multi-entity groups may need longer, while a small single-entity business can often close in two or three days with clean subledgers.

How can we shorten the month end close?

Stop waiting for inputs and move work into the month. Set deadlines for accruals, billing confirmations and intercompany agreements before month end, and publish a rule that late inputs are estimated and adjusted next period. Reconcile bank accounts weekly, prepare stable reconciliations before month end, and spread review across the close rather than concentrating it at the end. Measure upstream input timeliness and post-close adjustments, not only days to close. Most teams remove one to three days this way before buying any software.

What should we automate first in the close?

Start with bank, card and payment processor matching, because it is high volume, rule based and one of the most time consuming tasks in the close. Next, turn recurring journals, depreciation, prepaid amortization and standard allocations into scheduled entries. Then automate intercompany matching. Use AI to draft variance commentary and flag unusual entries, but keep a named person responsible for every explanation. Leave estimates, reconciliation sign-off and late adjustment decisions with people, because those steps carry judgment and accountability.

Does SOX change how the month end close process should work?

For US listed companies, yes. PCAOB auditing standard AS 2201 requires auditors to evaluate the period-end financial reporting process, including how journal entries are initiated, approved and recorded and how adjustments are made. That means documented owners, segregation between preparer and approver, evidenced and reviewed reconciliations, controlled period locking and a log of post-close changes. Private companies are not subject to SOX, but building to similar standards early makes fundraising, lending diligence and a future audit considerably easier.