Why this session exists
Before you build tools that read a client’s paperwork, you need to know what the paperwork is. After this session you should be able to:
- Read a close checklist and recognize what kind of work each line is.
- Follow the vocabulary in a discovery conversation without a glossary tab open.
ClearSky is starting with the accounting close because it is the hub: lots of finance work flows into it, and lots of reporting flows out. Show value here, then expand. More processes = more automation ROI.
The finance department, briefly
Orientation only — not a competency to master. The artifacts you will process were written by specific teams, for specific jobs, and that shapes how they look.
Controllership / Accounting
Owns the close. Records things accurately.
FP&A
Planning and forecasting. Eats close output. In real life they get a tiny window before pre-close for the next month starts (~5 days before month-end).
AP / AR
Payables = what we bought. Receivables = collecting what we sold.
Payroll
Salary, benefits, equity/options.
Tax
Not the close owner, but tax calcs feed the close and close output feeds filings. Multinationals file in many countries.
Treasury
Cash and banks. Exchange rates must be one published source for everyone (example: Bloomberg on BD1).
Scale example from the call: a listed multinational ~$500M revenue can have ~60 finance people. Another client example: ~30–40.
Three audiences (Barry said the slide is wrong and will be redone)
CFO
Is the close on time? Any surprises? Close is talked about in business days, usually BD5–BD7. Earnings call might be BD12. Two days late compresses the story-crafting window. Markets punish a $0.03 miss harder than a small beat.
Controller
Day-to-day owner. Hunts bottlenecks: one late Jakarta bank statement can stall five downstream tasks. Always: what is late, what is at risk.
Operator
Does the work. Example used on the call: one clerk reconciling ~70 multi-page bank statements on a single BD. Cares about: what’s on my list today, what’s blocking me, what am I blocking.
Buyers are CFO/Controller. Users who must not hate the tool are operators. Pitch automation as “your 10-hour day becomes 30 minutes,” not “you are replaceable.”
Just enough vocabulary
| Short | One line, as taught in the room |
|---|---|
| GL | System of record for all financial transactions (Workday or NetSuite in the examples). |
| JE | The unit of work that updates the GL. Most close tasks resolve to “post a JE” or “review one.” |
| CoA | The categorization scheme. You will see account numbers constantly. |
| Subledger | Detail ledger (AP, AR, fixed assets, payroll) that rolls up into the GL. |
| Accrual | Record the expense/revenue in the period it happened, even if cash moves later. Not the same as debt. Laptop in August, pay Apple in 90 days → August expense. |
| Rec | Confirm two numbers that should match, do. The single most common checklist task. |
| Entity / company code | Large companies close each legal entity, then consolidate. Same task repeats 12 times. Debit/credit mechanics are out of scope for this session. |
| PO / net 30 | Big companies route a purchase order, get invoices, pay in batches. Net 30 = 30 days to pay. You still accrue the commitment now. |
A JE in real life (from the transcript)
Not “Mom’s flight to Cairo.” One travel JE is many rows: flights, hotels, food, mileage, cars, Ubers for the whole company for the period. AP fills an Excel template (they often cannot log into NetSuite). Accounting Operations uploads. Someone else approves. Posting = approved in the GL.
Orchestration problem: if the JE is late you do not know whether the template was never filled, or filled and never uploaded. Completion signals: file in SharePoint with this month’s timestamp, email, or NetSuite API status on that CoA account. Then unlock dependent tasks.
What “the close” is
The recurring, time-boxed process (monthly inside, quarterly for public reporting) of finalizing the books so the company can report. Speed matters because forecasting, board packs, and SEC filings wait on it.
Not a rigid waterfall. Different departments/regions finish when their data exists so you do not pile everything on BD7. Subledgers often sit around BD−1 / BD1. Collection + rec ~ BD1–3. Approvals want to be done by BD5–7. Pre-close starts ~5 days before month-end. AP itself is continuous (weekly payments), not time-boxed like the close.
Public companies report quarterly because of SEC rules. There is a live debate about allowing semi-annual reporting; Barry’s take: markets will still want quarterly, and most exchanges already are quarterly. Internally they still close monthly.
Why the close is hard
1. Manual & spreadsheet-native
Checklists live in Excel, Wrike, SharePoint, email, and someone’s memory. Export / recon / upload between systems that do not talk.
2. Hidden dependencies
Handoffs happen at the coffee machine. “File is on SharePoint” never hits a system. Point72 idea: drop a Slack/Symphony note in a dedicated channel. Manual “mark done” should ask for a justification if the system cannot see it.
3. Varies wildly by client
Team names, task grain, tooling, risk posture — none of it standardized. Same-size companies can have totally different workflows. Product fits their process first; “optimal process” later.
Stakes: errors become restatements and audit findings. Rework across time zones burns whole business days (Singapore fills a template Monday night NY time; NY rejects it Tuesday; Singapore sees it Wednesday).
What they said ClearSky is building (context, not a second course)
- Nudging as a Service — internal auto-chases first; external messages maybe drafted for a human to send.
- Validate JE templates before send, so the timezone rework loop dies.
- Agents that pull 70 bank statements and line up “statement vs system.”
- Node map: task, owner, approver, upstream deps.
- Atomic tasks that can live in more than one process (tax sees a standalone task; close sees the same atom).
- One core UI; per-client tasks/KPIs/schema. “Flight Plan” = dynamic schema.
- Connectors to Workday/NetSuite; hope clients grow MCP layers so you can filter (e.g. Symphony trading chats stay invisible).
- Target: large public or private companies whose process pain is expensive. Private still reports to PE/shareholders.
Related SOX pages (the auditor docs Barry promised): JE · policies · TFN
Originals
Meeting notes (Gemini): Google Doc. Fireflies: Intro to Finance Processes · 18 Aug 2026 · id 01M0864P3HRTHJJ6VVG7XF1VYX · open in Fireflies.
Every short form
Hover any dotted term in the page. Or search here. One line each.