United States / Blog / The month-end close: what actually gets checked, in what order
United States · noteThe month-end close: what actually gets checked, in what order
"The software shows a P&L" is not "the month is closed"
Every accounting platform will generate a profit and loss statement for any date range, on demand, whether or not a single account behind it has been checked against anything. That is what makes "closed" a slippery word — the software never refuses to produce a report just because nobody reconciled the bank feed that fed it. A P&L that opens cleanly and a P&L that has been closed are two different claims, and only one of them means the numbers can be trusted for a decision.
A closed month is one where every balance sheet account has been tied to an independent source — a bank or card statement, a loan schedule, a payroll register — and every income statement line reflects what was actually earned or incurred in that period, not just what cash moved. Closing is a sequence of checks with a specific order, because later checks depend on earlier ones being right. Doing them out of order, or skipping the ones that do not throw a visible error, is how a business ends up with twelve tidy-looking months that were never actually verified.
Step one: reconciliations, because everything downstream depends on them
The close starts with bank and credit card reconciliation — matching every transaction in the ledger against the actual statement, account by account, until the ending balance in the books agrees with the ending balance on the statement to the penny. This step comes first because almost every other close task reads from the same transaction feed: a duplicate charge, a missed refund, or a transaction booked to the wrong account shows up in reconciliation before it has a chance to distort revenue, expense, or a schedule further downstream.
A reconciliation that "mostly" balances is not a reconciliation. A $40 unexplained variance sitting in a plug account is a decision deferred, not a problem solved — and it compounds, because the next month's reconciliation starts from that same unexplained balance. The discipline that matters here is not sophistication; it is refusing to move to the next step until every account ties, including loan and line-of-credit balances against the lender's statement, not just operating and card accounts.
Step two: revenue schedules, because cash timing and earned revenue are not the same fact
Once the transaction feed is verified, the next dependency is revenue recognition — confirming that what shows up as revenue in the period is what was actually earned in that period, not what happened to be invoiced or collected. For a subscription or contract business, this means walking the deferred revenue schedule forward: what was collected, over what service period, how much of that period has elapsed this month, and how much of the liability should have released into revenue as a result.
This step depends on reconciliation being finished first, because a deposit that has not yet been matched to its bank entry cannot be reliably tied to the contract it belongs to. Skipping straight to "does revenue look about right" without the schedule underneath it is how a company ends up recognizing a full year's prepayment as revenue in the month it was collected — a number that looks fine on a dashboard until the person reading it needs it to mean what it claims to mean.
Step three: payroll tie-out, because the ledger and the processor are two separate records
A payroll processor and the general ledger are independent systems recording the same activity, and nothing forces them to agree without someone checking. The payroll tie-out matches every pay run posted to the ledger — gross wages, each tax withholding, employer-side payroll tax expense, and any benefits deduction — against what the processor actually reported and remitted for that period.
The most common failure here is a payroll liability account that grows every month instead of resetting to zero: withholdings get booked as owed, but the remittance that should clear them never gets matched against the liability, so the balance climbs quietly for months before anyone notices it no longer means anything. Clearing that account back to a verified balance, and confirming quarter-to-date wage and withholding totals match what will eventually be reported on Form 941, is a mechanical check — but it only works as a check if it happens every month, not once a quarter when the return is already due.
Step four: accruals and prepayments, the entries that turn cash-basis activity into an accrual-basis month
With transactions verified, revenue scheduled, and payroll tied out, the close moves to accrual entries: expenses incurred in the period but not yet paid (a utility bill that arrives next month for this month's usage, a contractor invoice still outstanding), and prepayments being expensed over the period they cover rather than the month the cash left (an annual insurance premium, a prepaid software license). Both entries exist to make the income statement reflect economic activity in the period, independent of when cash actually moved.
This step comes last among the entries — after reconciliation, revenue, and payroll — because accruals are frequently small corrections layered on top of a transaction set that needs to already be verified. Estimating an accrual against an unreconciled account just adds an estimate on top of an unknown, and the two errors do not cancel out; they stack.
The close calendar runs on business days, not calendar dates
A close calendar built around calendar dates — "books close on the 5th" — breaks the first month a bank statement posts late, a holiday falls mid-week, or a payroll run lands on a weekend. A close calendar built around business days after month-end is more resilient: reconciliations complete by business day 3, revenue and payroll tie-outs by business day 5, accrual review and adjusting entries by business day 7, and management review of the finished package by business day 10, adjusted case by case for a fiscal year-end or a quarter that also needs Form 941 prepared.
The specific day counts matter less than the ordering being fixed and repeated the same way every month. A close that finishes on a different day count each month, in a different order, is not actually a process — it is a set of tasks performed under whatever pressure exists that particular month, which is exactly the condition under which a step gets skipped and nobody notices until a diligence request or a tax filing surfaces it.
What a reviewer actually signs off on
When someone signs off on a closed month, the sign-off is a specific, checkable claim, not a general impression that the numbers "look right." It means: every bank, card, and loan account reconciles to its statement; the deferred revenue schedule has been rolled forward and agrees with the balance on the books; the payroll clearing account is at zero (or explained if not) and ties to the processor's reports; accrual and prepayment entries for the period have been posted and reviewed; and any variance that could not be resolved is documented — what it is, why it exists, and what would resolve it — rather than absorbed into a plug.
That last point is what separates a real review from a formality. An unexplained variance that gets written off to "miscellaneous" every month is not closed; it is deferred every month, indefinitely, until something forces the question — a bank running out of patience with a reconciling item, an investor's diligence team, or a filing deadline. A documented gap, by contrast, is something a reviewer, a lender, or a CPA can actually work with.
How a closed month feeds the quarterly and annual filing cycle
The close is not an end in itself — it is the input the tax cycle depends on. Form 941, the employer's quarterly federal tax return, asks for exact totals on wages, withholding, and Social Security and Medicare tax; those totals should trace directly back to the payroll tie-out performed each month of the quarter, not get reconstructed from scratch during filing week. A quarter where all three months closed cleanly hands the preparer numbers that already agree with the processor's records. A quarter where the payroll liability account was never cleared hands the preparer a reconciliation project with a filing deadline attached to it.
The same logic runs through to the annual corporate return. A calendar-year C corporation's Form 1120 is generally due by the 15th day of the 4th month after its tax year ends — April 15 for a calendar-year filer — and that return is built from twelve closed months, not one large reconstruction done in March. A business that treats each month as closed only in the loose sense — the P&L opened, nobody complained — is doing the real closing work retroactively, under a filing deadline, instead of monthly, without one.
CapEasy's bookkeeping support runs the reconciliation, revenue-schedule, and payroll tie-out steps described above on a fixed monthly cadence, so the accrual entries and the closed package are built on numbers that already agree with their source statements. Revenue recognition judgment calls, the corporate and payroll tax returns themselves, and any position taken with the IRS stay with your CPA, working from books that were actually closed each month rather than assembled once a filing deadline made it necessary.
Reading about it is optional. The books aren’t.
A named accountant, software underneath, licensed partners where the law wants them.