Monthly close, certified by the fifth

If the close date moves every month, you do not have a close. You have a negotiation.

Monthly close is the core of the Tarient engagement. A dedicated CFO and analyst pair own the calendar, the reconciliations, and the certification. You do not learn a new stack to get there. You get a finished pack on a published date, with the supporting work already reviewed inside Oversight.

The founder stays in the review seat. The pair executes. Cutoffs are public before month end. Critical anomalies block certification instead of getting waved through in a Slack thread at midnight. The standing target is the fifth business day, every month, unless the board calendar forces an earlier freeze.

Most growth-stage companies already know the pain: bank recs finish late, flux waits on a spreadsheet someone forgot to update, and the board pack is rebuilt the night before. The work is not mysterious. It fails because nobody owns the sequence, and because the founder quietly becomes the backup preparer for every missing receipt. Tarient installs ownership and a calendar that survives contact with a messy week.

Who owns which lane

Ambiguity is what turns a five-day close into a fifteen-day ordeal. We assign lanes before the month starts and keep them stable. When a lane is empty, the delay is visible the day it happens—not discovered in a board preview.

• Client ops: bank feeds complete, payroll locked, revenue system exports available, AP inbox cleared of orphan invoices.
• Tarient analyst: reconcile cash, AR, AP, and payroll; draft flux notes; queue anomalies with evidence.
• Tarient CFO: approve material judgments, certify the pack, brief the founder on what changed and why.
• Founder or CEO: review the pack, decide open policy questions, unblock vendors or systems when access stalls.

That split is not bureaucracy. It is how you get a close you can defend. Preparer and reviewer stay different people on every critical control. If you want the pair staffed against your systems, start from monthly close or contact Tarient.

What the pack contains when we say closed

Closed means more than a P&L that looks roughly right. The monthly pack includes ownership for every material account, bank reconciliations, a revenue rollforward that ties to the billing system, AP aging that matches the ledger, payroll tie-outs, and flux versus last month and versus forecast. Material judgments get a short note, not a buried footnote. Critical anomalies are either cleared or explicitly carried with a named owner and due date.

Work lives in Oversight: the checklist, the anomaly queue, and the board pack in assembly. You can see status without asking for a status email. When something blocks certification, it is visible as a blocker with an owner, not a vague delay. Certification is a written event. A verbal “looks good” is not a close.

1. Business days −3 to −1. Cutoff memo goes out. Soft close of AP. Confirm payroll calendar and any mid-month equity or debt events that need ledger treatment. Silence in this window is a risk signal.

We do not begin flux before cash is reconciled. Explaining variance on unreconciled cash invents a story you later walk back. Day one belongs to the bank.

1. Business day 1. Cash and credit card feeds reconciled. Obvious duplicates and missing deposits flagged. Revenue export pulled and hashed against the prior control total.

2. Business day 2. AR and AP aging tied. Accruals drafted. Payroll and benefits posted. Anomaly queue triaged into certify-blockers versus next-month cleanup.

By the end of day two the mechanical spine should be intact. What remains is judgment: what moved, what is strange, and what the business still owes.

1. Business day 3. Flux draft complete. Balance sheet scrub for odd balances. Intercompany or related-party items reviewed if they exist. Material movement gets a sentence a board member could understand without a glossary.

2. Business day 4–5. CFO review, founder briefing, certification. Pack frozen. Forecast inputs updated from closed numbers, not from last month’s estimate. An explicit delay with a reason beats a quiet slide to day twelve.

When something breaks—a missing feed, a late invoice, a payroll exception—the pair absorbs it inside the calendar. You get status without becoming the escalation path for every missing document. That rhythm is the product. Tools change. The calendar and the ownership model do not.

Deliverables you can point at

• Published close calendar before month end
• Certification memo the CFO seat can stand behind
• Anomaly log that survives the month, not a thread that dies
• Operating pack ready for the reporting cadence the same week
• Handoff into the thirteen-week forecast from certified numbers

Where closes fail in the wild

A late close is not a calendar inconvenience. It is an operating tax. The forecast waits. Hiring and vendor decisions get made on gut while finance says the month is “almost done.” Board materials scramble because the close pack arrived too late to reuse.

• Revenue recognition debates postponed until “after we close,” which means they never resolve.
• Bank feeds that look complete but miss a subsidiary account or a new processor.
• Accruals invented without invoices, then reversed next month without a trail.
• One person both preparing and reviewing the same control—speed without a reviewer is just fast fiction.
• Board packs rebuilt from memory because certification slipped past the freeze date.

A late close does not just delay accounting. It poisons the forecast, the board conversation, and every vendor timing decision that depends on certified cash.

You stop rebuilding the month from memory. You stop asking “are we closed?” in the meeting where you should be reading the forecast. Over a few cycles: fewer heroics, clearer owners, and a pack that leaves when it says it will. That boring reliability is the product.

This is financial operations. It is not investment advice, tax advice, an audit opinion, lending, insurance, or brokerage. Licensed specialists still sit beside the work when the question requires them. If you want the operating standard behind the calendar, read the close calendar playbook and the close by the fifth method.