Finance playbook · AI Employee: Fin

Month-End Close Coordination

Close completes on schedule; blockers surface early

Install this playbookBack to marketplace
The problem

Month-end close is the finance team's monthly emergency. Accruals from every department, JEs from AP, revenue recognition from RevOps, variance analysis, controller sign-off. Every close depends on inputs from people whose day job isn't close. Every missed input is a delay. Every delay compounds.

At a glance
Trigger
Cron (per month)
Approvals
Controller approves close checkpoints
What it does
Writes to your systems
Systems
NetSuite · Ironclad · Ticketing · Slack
How it feels in production

An hour-by-hour walkthrough.

Day 25 of the month. Fin fires the close-kickoff playbook. Sends personalised checklists to each accrual owner (Marketing accruals to CMO's team, IT accruals to CIO's team, etc.), tags each item with a due date (Day 2 of following month) and the specific data needed. Day 27. Fin checks in: 60% of accruals submitted. Sends a friendly nudge to the 40% outstanding, this time listing the specific missing items rather than a generic "still need your accruals". Day 1 of next month. Fin escalates: any accrual still outstanding pings the owner's manager. Any accrual estimated at above a materiality threshold (default $10k) gets an extra reminder to the controller. Day 2. Controller reviews the assembled accrual package with variance flags per line item, JE aggregation from AP, revenue recognition from CRM. Sign-off in Slack. Day 3. Close published. Post-close retro: which owners were on time, which weren't, what were the escalations, what got materially estimated (bad sign for next month's forecast). Retro post to finance leadership.
How it works

Step by step.

  1. 01

    Send close checklist

    Day 25 of month, Fin sends personalised checklists to each accrual owner via Slack DM. Each checklist lists specific line items expected from that owner, due date, data source (which spreadsheet or system to pull from).

    Slack · Email · Close template
  2. 02

    Collect accruals + JEs

    Owners submit via Slack reply, portal form, or direct upload to shared drive. Fin ingests, validates against templates, flags anomalies (accrual is 3x prior month → flag).

    Slack · Google Drive · NetSuite · Journal Entry system
  3. 03

    Escalate blockers

    Late items nudge owner Day 27, escalate to manager Day 1, escalate to controller Day 2. Material items ($>10k default) get extra nudge cadence.

    Slack · Teams
  4. 04

    Aggregate for controller

    Fin assembles all accruals, JEs, and revenue recognition into the controller's review package. Variance analysis auto-generated per line item vs. prior month / budget.

    NetSuite · Excel · Controller dashboard
  5. 05

    Publish close + retro

    Controller sign-off in Slack triggers close publication. Post-close retro auto-generates: on-time %, escalation count, material estimates, forecast implications.

    NetSuite · Slack · Finance leadership
Systems and wiring

What you connect to make this run.

NetSuite · QuickBooks · SAP · Oracle

read+write

GL integration. Read prior-period balances for variance; write JE aggregations on approval.

Slack · Teams

write

Personalised checklists per owner; nudges + escalations; controller sign-off.

Google Drive · SharePoint

read

Where accrual owners upload spreadsheets. Fin ingests, validates, and normalises into standard format.

Salesforce · CRM

read

Revenue recognition inputs — closed-won deals in period, subscription changes, deferred revenue schedules.

What changes

Before and after, honestly.

Close completion time
Before
Day 5-7 of following month
After
Day 2-3
Close-related Slack messages between finance + owners
Before
~200 messages per month across chase-ups
After
~30 (structured requests + confirmations)
Material estimates in accruals
Before
10-20% of accrual items estimated due to missing data
After
Under 3% (real data collected via structured process)
Finance team overtime on close week
Before
20-40 hours across the team
After
5-10 hours (review + judgment work only)
Related

Playbooks that pair with this one.

Finance

Weekly Finance Digest

The pre-close visibility that surfaces close-blocking issues before Day 25.

Finance

AR Aging & Collections

AR aging feeds revenue recognition in the close.

Finance

Bill Payment Approval

AP cutoff at close; approved bills post to the closing period.

Finance

License Cost & Renewal Tracking

SaaS accruals for the month tie to renewal / usage tracking.

Frequently asked

Answers about this playbook.

What if an accrual owner is on vacation during close?

Owners designate a delegate in the approval-policy config. Delegate gets the checklist automatically if primary is on approved leave. Never blocks the close on an out-of-office owner.

How does it handle variance thresholds?

Configurable per line item + per period. Variances above threshold get flagged in the controller review with the underlying detail. Below threshold, just tracked for post-close analysis.

Can we do a soft close mid-month?

Yes — the playbook can be triggered on any date with a soft-close template (lighter checklist, no controller sign-off). Useful for weekly / bi-weekly financial reviews.

What about multi-entity consolidations?

Fin runs the close per entity in parallel, then rolls up to consolidation. Each entity has its own owner group + templates; consolidation happens after all entities close.

Does this replace our ERP's close functionality?

No — it orchestrates around it. Your ERP still does the actual GL work (period lock, JE posting, financial statement generation). Fin coordinates the humans and inputs that feed the ERP.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore Finance playbooks