Skip to content
CodelessOps

Grounded · Use cases · Finance partner

Run the close

"Kick off the May 2026 month-end close."

Who this is for, and the moment

Working day one to working day eight. Same steps every month, same documents, same three people. And the same place it goes wrong: a figure moved after the ledger cut, and nobody re-ran the sheet that depended on it.

The question, as typed

“Kick off the May month-end.”

The answer

Kick off the May 2026 month-end close.
Ran 7 toolsShow steps ›

The May-26 pack is already issued: the May Monthly Reporting Pack shows reporting period “May-26,” issued on 10 June 2026, with status “Final” 2021. I’ll therefore frame this as a re-run of the May close checks and verification of the issued pack, not as a first-time close. The calendar says the WD8 issued Monthly Reporting Pack is the governing pack, and any later copy marked FINAL supersedes prior versions 27.

May-26 close checklist — table of record

WDTaskOwnerOutputStatus
WD1Sales ledger and despatch cut-off; order-line despatch data frozenDev Patel, AR & Credit LeadFrozen revenue subledgerNot started in this re-run
WD2Purchase ledger close; agency labour and carrier & freight accruals postedMarta Kowalska, AP Lead · Ben Tranter, Management AccountantAccruals in GLNot started in this re-run 16
WD3FLASH: headline revenue and gross margin issued to CEO & CFOPriya Nair, FP&A AnalystFlash email — not a governing documentNot started in this re-run 5
WD4Segment reviews: GMs confirm revenue by channel and flag one-offsHelen Drummond + segment GMs, with FP&AConfirmed segment viewOwner step — not automated 24
WD5CLOSE COMPLETE: manual journals posted and approved; GL lockedJames Whitfield, Financial ControllerLocked GL for the periodNot started in this re-run 17
WD6Pack drafting: Consolidated P&L, Revenue & KPIs, Opex by Department, Balance Sheet, Cash FlowPriya Nair, FP&A AnalystDraft Monthly Reporting PackNot started in this re-run 25
WD7Controller review; commentary drafted with segment GMs; checks tab clearedJames Whitfield + Priya NairReviewed pack, commentaryOwner step — not automated 26
WD8MONTHLY REPORTING PACK ISSUED — Status: FinalIssued by FP&A after Controller sign-offGoverning pack — PDF + xlsxAlready issued; to verify 27
WD9Variance follow-ups with department budget ownersBen Tranter, Management AccountantActions listOwner step — not automated 28
WD10Quarter-ends only: KPI & Commentary Pack and board deck preparation begins; covenant certificate preparedFP&A · Financial ControllerQuarterly outputsNot applicable unless quarter-end close output is requested 6

Close board

WD1 · Sales cut-offWD2 · AP close + accrualsWD3 · FlashWD5 · Journals + GL lockBank reconciliationWD6 · Variance packWD8 · Pack issued

The board is a visual of the cited checklist above. Bank reconciliation is included as a skill-added close check; it is not shown as a separate row in the close calendar.

Runnable close steps mapped to skills

Calendar stepSkill
WD2 / WD5 accrual completenessaccrual-completeness-sweep
WD3 flashwd3-flash-report
WD5 manual-journal approvalsjournal-approval-check
Bank reconciliationbank-reconciliation-close
WD6 variance pack + commentarymonth-end-variance-pack

The other calendar steps stay with their named owners.

Shall I run these in order? I’ll stop for your sign-off at each gate.

Document · Month-End Close & Reporting Calendar.xlsxDocument · Monthly Reporting Pack - May-26.xlsx
The close checklist as the app returned it, re-set for this page: the company's own calendar with its owners, a gate between each runnable step. Real app, fictional company, 12 October 2026.

The checklist reads the company’s own close calendar and shows the steps with their owners: WD1 sales-ledger cut-off, WD2 accruals, WD3 flash to CEO and CFO, WD5 close complete with journals approved, WD6 pack drafted, WD7 Controller review, WD8 pack issued FINAL. The runnable steps are offered in order, and each stops at a reviewer gate before the next starts. Chips: Month-End Close & Reporting Calendar · Monthly Reporting Pack May-26, Executive Summary.

The steps, each its own skill

The skills page: Drive and ERP connected, and the eight platform skills including the six close skills and reconciliation

Real app, fictional company, captured 12 October 2026.
  • WD3 flash. Revenue £21,063k against £20,753k budget; operating profit £(12)k against £(51)k. Top variances called out. One page, every figure cited. The flash is an early indication; the issued pack governs, and the skill says so.
  • Journal approvals. Manual journals of £50,000 or more need the Financial Controller. One qualifies in May: JNL-508295, £285,000, the Ridgway Freight accrual. It is presented for approve or query, and the decision is written to the approval log with who and when.
  • Accrual sweep. What posted after the ledger cut: £333,173 in June against May, dominated by the £285k accrual; the department export that missed it; the invoice that evidences it.
  • Bank rec. Statement £9,882,613.23 to cashbook £8,911,388.92 to pack £8,911k, three unpresented and two uncleared items verified, one stale cheque flagged for a person to decide.
  • Variance pack. Every P&L line against budget, material variances investigated to their drivers, commentary drafted for sign-off.

The citation clicked

Any figure on any step opens its source. The gate screenshot shows the reviewer’s approve-or-query control next to the cited figure.

The trust chain

Every step’s figures go through the same guard a chat answer does. A step with an untraceable figure doesn’t close its gate.

What to notice

  • The calendar is the company’s own, read from the document. There’s no template underneath.
  • A person decides at every gate. The skill prepares the step; it doesn’t approve anything.
  • Each decision is logged with its evidence, so the close records who signed as well as what happened. That log is what the auditor reads.
  • I want to be straight about what’s built and what isn’t. The variance pack skill drafts the commentary today. Generating the approved pack as a file is still backlog, and the page says so.

Video

Watch one $2.1 million travel through an entire close (the biotech corpus).

Use cases: Check the board pack · Hard queries · The audit trail.

Series: Continuous close for FP&A. Post: The $2.1 million that was only in one of your reports.

Hiring?

Need this kind of build on your team?

I take contract roles in finance automation and FP&A systems. Ask me anything about how Grounded works; I'm happy to walk through the parts that broke as well as the parts that worked.