Building an IPO-Ready Close Calendar

Most pre-IPO companies we work with have a 12- to 15-business-day close. That's not unusual, and for a private company with annual audits and quarterly board reporting, it's adequate. The problem is that an IPO compresses every downstream deadline at once. The SEC's filing windows for a large accelerated filer — 40 days for a Form 10-Q, 60 days for a 10-K — sound generous until you back out the time required for auditor review, drafting MD&A, legal sign-off, audit committee review, and CEO/CFO certifications under Sections 302 and 906 of Sarbanes-Oxley. The arithmetic forces close to happen in roughly the first business week of the new period.

Here's how we actually get clients there.

Where the days go: a real five-day close

Before talking about how to compress, it helps to see where time goes in a five-day close that's working well. A representative calendar for a public-company-ready accounting team:

• Day 1 (BD+1): Cash, AR aging, AP cutoff, payroll accrual, freight accruals. Subledgers locked.
• Day 2 (BD+2): Revenue cut-off and contract review, deferred revenue roll, inventory and cost of revenue, fixed asset additions and depreciation, lease entries (ASC 842).
• Day 3 (BD+3): Stock-based compensation (ASC 718), credit loss reserves (ASC 326), other estimates and accruals, intercompany eliminations, FX remeasurement.
• Day 4 (BD+4): Income tax provision (ASC 740), earnings per share (ASC 260), segment reporting package (ASC 280), final consolidation, subsequent events review (ASC 855), flux analysis.
• Day 5 (BD+5): Disclosure-committee package, audit committee pre-read, draft MD&A, lock the books.

Notice that the long-pole technical accounting areas — tax, stock comp, EPS, segment reporting, credit losses, leases, and subsequent events — cluster on Days 3 and 4. That's where most close compressions stall. Below is what makes each of those tractable, plus two structural items (expense disaggregation and the S-1 reporting-entity recast) that don't sit on the recurring calendar but that an IPO-track team needs to be solving in parallel.

Tax provision (ASC 740): the most common bottleneck

For most pre-IPO companies, the quarterly tax provision is the single biggest reason close runs long. ASC 740 requires an estimated annual effective tax rate (AETR) applied to year-to-date pre-tax income, with discrete items recognized in the period they occur. That sounds simple, and on a clean U.S.-only entity it is. It is not simple for a multi-entity, multi-jurisdiction structure.

What slows it down: Permanent differences (Section 162(m) compensation limits, meals, GILTI inclusions) and temporary differences (stock comp, depreciation, R&D capitalization under Section 174) all need to be re-estimated. Valuation allowance assessments (ASC 740-10-30-17 through 30-25) can require fresh judgment each quarter — particularly for companies with cumulative loss histories where a deferred tax asset is partially or fully reserved.

How fast-close teams handle it:

• Build a quarterly forecast model that pre-computes the AETR. The provision shouldn't start when close starts. The forecast should be running before quarter-end so that on Day 4, you're updating known data, not modeling from scratch.
• Pre-document the valuation allowance position. If your conclusion is "full VA, all jurisdictions" or "release upon achieving sustained profitability," put that memo in writing once and update it for triggering events — not every quarter.
• Coordinate with your provider's tax team on a working calendar. If you outsource provision, the bottleneck is usually their queue, not yours. A pre-agreed turnaround SLA changes everything.

Disclosure implication: Public companies must disclose the components of the rate reconciliation, deferred tax asset/liability composition, and unrecognized tax benefit movements (ASC 740-10-50). The 2023 amendments under ASU 2023-09 require disaggregated rate-reconciliation categories with quantitative thresholds and disaggregated income tax payments by jurisdiction — both effective for public business entities for annual periods beginning after December 15, 2024. If your provision process doesn't natively track to those categories, you'll be doing the disaggregation by hand at year-end. Build it in now.

Stock-based compensation (ASC 718)

Stock comp is the second-largest close bottleneck for venture-backed companies. The mechanics aren't conceptually difficult — fair value at grant date, recognized over the requisite service period — but the operational complexity adds up.

What slows it down:

• Performance-based awards (PSUs, market-condition awards) require probability assessments updated each period under ASC 718-10-30-12 through 30-14.
• Modifications under ASC 718-20-35-3 — repricings, accelerations, vesting changes — trigger Type I, II, III, or IV modification accounting and an incremental fair value calculation.
• Forfeiture accounting, whether estimated or actual (ASC 718-10-35-1D election), needs a controlled, periodic true-up.
• For pre-IPO companies, the underlying equity valuation (409A) drives grant-date fair value. If 409As lag, your stock comp expense is an estimate sitting on a stale input.

How fast-close teams handle it: Move stock comp to a dedicated equity administration platform (Carta, Shareworks, Pulley) with an integrated expensing module and a maintained option pricing model — typically Black-Scholes for plain-vanilla options, lattice or Monte Carlo for awards with market or performance conditions. Run a parallel model for the first two quarters to validate. Get the modification calculus pre-templated so a repricing doesn't take a week.

Disclosure implication: The ASC 718-10-50 disclosures — weighted-average grant-date fair value, valuation method and assumptions, total compensation cost not yet recognized, weighted-average remaining vesting period — should be auto-generated from the same source system you book the expense from. If they aren't, your 10-Q footnote takes days, not hours.

Earnings per share (ASC 260)

EPS is conceptually a one-line calculation and operationally one of the most error-prone disclosures a newly public company produces. The reason is that a venture-backed capital structure rarely looks like the textbook example.

What slows it down:

• Two-class method. Convertible preferred stock that participates in dividends with common — common in VC term sheets — is a participating security under ASC 260-10-45-60. Net income is allocated between common and preferred based on their respective rights, and basic EPS is computed only on income allocated to common. Most pre-IPO companies don't run this calculation correctly the first time.
• Diluted EPS mechanics. Options, warrants, and RSUs are run through the treasury stock method (ASC 260-10-45-22 through 45-29). Convertible debt and convertible preferred run through the if-converted method. Performance awards are contingently issuable shares under ASC 260-10-45-48 and are included only when performance conditions are satisfied at the reporting date.
• Anti-dilutive sequencing. Each potentially dilutive security is tested individually, in order from most to least dilutive. Forgetting that a security that is dilutive on a fully-diluted basis can be anti-dilutive in a loss period — and must be excluded — produces a wrong number.
• Recapitalizations and stock splits. Any change in capital structure presented in the S-1 (a forward split, a recapitalization at IPO, conversion of preferred at the offering) must be applied retroactively to all periods presented under ASC 260-10-55-12.

How fast-close teams handle it: Build the EPS workbook once, with each share class and each potentially dilutive security as a separate input row, and have it produce both basic and diluted figures plus the reconciliation table required by ASC 260-10-50-1. Update for new grants, exercises, and forfeitures monthly. Have the cap table system feed share counts directly so the weighted-average computation isn't a manual exercise.

Credit loss reserves (ASC 326)

The current expected credit loss (CECL) model under ASC 326 replaced the incurred-loss model in 2020 and remains a meaningful close item — particularly for companies with significant trade receivables, contract assets, or lease receivables.

What slows it down: CECL is forward-looking. The reserve must reflect a current estimate of expected credit losses over the contractual life of the asset, considering historical loss experience, current conditions, and reasonable and supportable forecasts. The most common approaches:

• Aging schedule / loss-rate method. Cleanest for companies with stable customer bases and short collection cycles. Apply historical loss rates to aging buckets, layer a qualitative adjustment for forward-looking conditions.
• Roll-rate method. Better for portfolios where the migration pattern through aging buckets is stable.
• Probability-of-default / loss-given-default. Used by lenders and companies with longer-dated credit exposure; usually overkill for trade receivables.
• Discounted cash flow. Required for purchased credit-deteriorated assets; rarely the right answer for trade AR.

How fast-close teams handle it: Pick the simplest defensible method, document the methodology in a CECL memo, automate the calculation, and only re-evaluate the qualitative overlay when there's a triggering event (significant customer concentration shift, deteriorating macro indicators, recession signals). Quarterly reservation should run in minutes, not days.

Disclosure implication: ASC 326-20-50 requires disclosure of credit quality indicators, the reserve roll-forward, and write-off and recovery activity. For pre-IPO companies, this is also where the SEC frequently issues comment letters — particularly on the qualitative-adjustment methodology and the link to current and forecasted economic conditions.

Lease accounting (ASC 842)

ASC 842 close work shouldn't take long if your lease portfolio is in a maintained system. It frequently does, because the system isn't maintained.

What slows it down: New leases, modifications, reassessments, impairment indicators, and incremental borrowing rate (IBR) updates all need to flow into the right-of-use asset and lease liability roll. ASC 842-10-25-1 through 25-3 distinguish between modifications that are accounted for as new leases versus modifications of existing leases — the answer drives whether you remeasure the liability or recognize a new one. Variable lease cost, common-area maintenance, and short-term lease elections all sit in the disclosure footnote.

How fast-close teams handle it: A single lease accounting system (LeaseQuery, Visual Lease, Nakisa, or an in-house spreadsheet model only if the portfolio is genuinely small) with a disciplined intake process — every new lease signed is logged within five business days of execution. The IBR is refreshed quarterly using a documented methodology (typically a synthetic credit rating against benchmark yield curves at appropriate tenor), not annually.

Disclosure implication: ASC 842-20-50 requires the maturity analysis, weighted-average remaining lease term, weighted-average discount rate, and a roll-forward of lease cost components. Each one should be a system output, not a manual schedule. The maturity table is also required to reconcile to the lease liability on the balance sheet — a frequent source of audit findings when the system isn't authoritative.

Segment reporting (ASC 280)

Segment reporting starts with a deceptively simple question — who is the chief operating decision maker (CODM), and what financial information do they actually use to allocate resources and assess performance? In practice, identifying the CODM and operating segments under ASC 280-10-50-1 through 50-9 takes serious work, particularly for companies whose internal reporting has evolved organically.

What slows it down:

• CODM identification. Often the CEO, but it can be a management committee or a function leader if that's where resource allocation actually happens. The conclusion has to be evidenced by board materials, internal management packages, and budgeting workflows — not asserted.
• Operating segment vs. reportable segment. Operating segments are determined first; reportable segments are then identified using the 10% quantitative thresholds (revenue, profit/loss, or assets) under ASC 280-10-50-12, with aggregation criteria available under ASC 280-10-50-11 only when economic characteristics and other qualitative factors align.
• ASU 2023-07 expanded disclosures. Effective for fiscal years beginning after December 15, 2023 (interim periods one year later), public entities must disclose significant segment expenses regularly provided to the CODM, plus the title and position of the CODM. Even single-reportable-segment companies must comply. This is a real change for most newly public filers, and the categorization needs to be built into the close package — not assembled from the GL after the fact.

How fast-close teams handle it: Document the CODM analysis and segment determination in a standing memo, refreshed annually or upon a triggering event (acquisition, reorganization, change in management reporting). Build the CODM management package as the source-of-truth segment view, so the 10-Q footnote ties to a document that already exists.

Expense disaggregation (ASU 2024-03)

The FASB's ASU 2024-03, Disaggregation of Income Statement Expenses (DISE), issued November 2024, will require public business entities to provide tabular disaggregation of relevant expense captions — including cost of revenue, SG&A, and research and development — into specified natural categories: purchases of inventory, employee compensation, depreciation, intangible asset amortization, and depreciation/depletion of oil-and-gas-producing assets. Other expenses within the caption are then quantitatively reconciled to the total. The standard is effective for annual periods beginning after December 15, 2026, and interim periods one year later, with early adoption permitted.

Why this is a close-calendar problem: Most companies' general ledgers code expenses by functional caption (COGS, S&M, G&A, R&D) but not consistently by natural category within that caption. A salary expense sitting in S&M needs to be tagged as employee compensation; an amortization charge inside COGS needs to be separable. Without that dimensionality in the GL, the disaggregation table is built quarterly by hand — which won't survive a five-day close.

How fast-close teams handle it: Restructure the chart of accounts now to capture natural-category dimensionality alongside functional caption — typically through a secondary segment or sub-account hierarchy. Build the disaggregation report as a system output. Companies that wait until adoption will find themselves either delaying close or doing the work outside the system, which is an internal control problem in addition to a calendar problem.

Subsequent events (ASC 855)

Subsequent events review is a small line item on a close calendar but a category that the SEC reads carefully. Two types under ASC 855-10-25:

• Type I (recognized): Conditions that existed at the balance sheet date — settlements of pre-existing litigation, customer bankruptcies confirming pre-existing collectibility issues. These adjust the financial statements.
• Type II (non-recognized): Conditions that arose after the balance sheet date — material acquisitions, capital raises, debt issuances. These don't adjust the statements but require disclosure if their omission would make the financial statements misleading.

How fast-close teams handle it: A standing subsequent-events checklist owned by the controller, populated jointly with FP&A, treasury, legal, and HR, executed on Day 4 of close. For SEC filers, the evaluation period extends through the date the financial statements are issued or available to be issued — not the close date — so the checklist needs to be re-run before filing.

What SOX 404 demands of speed

Compressing close without breaking controls is the hard part. A close that runs on heroics — one person knows the spreadsheet, manual journal entries get rubber-stamped, account reconciliations are signed but not actually performed — won't survive an integrated audit under PCAOB AS 2201.

The controls that hold up at speed:

• Account reconciliations completed and reviewed within close, not after. Reconciliation is a control. If it's done on BD+10 but the books closed on BD+5, the financials were issued without an effective control over those balances.
• Journal entry approval thresholds aligned to risk. A flat "all JEs over $10K" rule produces noise. Tier by risk — non-standard entries, top-side adjustments, estimates — and require dual review for the high-risk tiers.
• Manual key controls that produce reviewable evidence. A flux review isn't a control if the only artifact is "reviewed by JS." It's a control if the artifact is the actual variance schedule, the threshold methodology, the explanations, and the reviewer sign-off with date.
• Information used in controls (IUC) tested for completeness and accuracy. The system-generated reports feeding your reconciliations and reviews are themselves subject to control testing. Document the IUC the first time, not the tenth.

The companies we see fail an integrated audit aren't the ones with slow closes. They're the ones with closes that look fast but don't have evidence behind the controls.

The S-1 wildcard: change in reporting entity

One item that doesn't fit a recurring close calendar but consumes enormous time on the first S-1: a change in reporting entity. Many IPOs involve a pre-offering reorganization — inserting a new holding company, converting from an LLC or partnership to a C-corporation, executing an Up-C structure, or contributing operating subsidiaries up to a newly formed issuer. Each of these is a change in reporting entity under ASC 250-10-45-21 and requires retrospective application to all periods presented.

For an S-1, that typically means recasting three years of annual financial statements plus interim periods on the new reporting entity basis, including all footnote disclosures, EPS, segment reporting, and tax provision. Predecessor/successor presentation may apply if the reorganization is treated as a transaction between entities under common control versus a true acquisition. Stock splits and reverse splits effected before the offering also receive retroactive presentation under ASC 260-10-55-12.

How to manage it: Identify the reporting-entity question early — ideally before legal structure is finalized — and build the recast in parallel with the S-1 drafting cycle, not after. Document the technical analysis (common-control vs. acquisition, predecessor period, basis of presentation) in a memo that the auditor and SEC reviewer can follow. The recast itself is a one-time effort, but a poorly documented one will surface in SEC comments and delay effectiveness.

The disclosure controls layer

Item 307 and Item 308 of Regulation S-K require quarterly evaluation of disclosure controls and procedures and an annual assessment of internal control over financial reporting. The disclosure-controls evaluation is broader than ICFR — it covers the controls that ensure information required to be disclosed is recorded, processed, summarized, and reported within the required time periods.

In practice, this means a disclosure committee that meets in close week, reviews a draft of the 10-Q or 10-K, and signs off on completeness. The committee needs a documented charter, a member roster (typically CFO, controller, GC, head of IR, and a representative from each material business unit), and meeting minutes. Build the disclosure committee process before you go public, not after.

What to do this quarter

If you're 12+ months from a target IPO date, three actions move the calendar more than anything else:

• Time-stamp every close task in your next two closes. When did the bank rec actually get done. When did revenue cut-off finish. When did the tax provision arrive. You can't compress what you can't measure.
• Pick the two longest-pole technical areas and re-engineer them. For most clients, that's tax and stock comp. The fixes — pre-built quarterly forecast models, automated equity admin platforms, pre-templated modification accounting — pay back across every subsequent close.
• Run a mock 10-Q close on a private quarter. Pick a real period, set a 40-day clock, draft the full disclosure document end-to-end. Where it broke is your roadmap.

None of this is about working harder. It's about pre-committing to decisions, automating the calculations, and ensuring the controls produce real evidence. If you'd like a second set of eyes on your close calendar or a benchmark against where peer companies sit at filing readiness, we'd be glad to help.

This article is for general informational purposes and should not be relied on as accounting, tax, or legal advice for any specific transaction. Please consult with your advisors.