AI accounting
Review the current close, evidence, and journal-entry capabilities alongside early-access surfaces.
Budget vs actuals, versioned forecasts, and board memos — read from the mirrored ledger, not last month’s export. Every figure drills to the entries behind it. Sebastian drafts the explanations; a named person gives every verdict.
The year lands $1,006,205.59 ahead of the board plan. Hiring landed slower than the plan carried; the working reforecast restarts the ramp in September.
Stands on · Released actuals through July 2026 · FY2026 Budget (Board-approved)
Actuals come off the mirrored ledger, variances wear their sign, and the lines worth a human’s time carry an amber flag. The materiality floor that decides which lines flag is a governed, versioned policy — with a required reason every time it changes.
Revenue +$206,613.14 less cost of revenue +$86,231.21 less operating expense −$373,556.06 = Operating income +$493,937.99
On a flagged line, Sebastian reads the entries, tells timing from performance, and drafts the note — citing the journal entries and documents it rests on. Accept, rewrite, or dismiss: the verdict is recorded, attributed, and remembered next month.
Where this comes from · 3 entries · total $875,351.15 — ties to the statement line.
The forecast grid wears the seam: months released by the close are the ledger’s, every month after is this version’s own. Set a cell by hand and it keeps your name and your reason. Carry it through the year in one keystroke.
Double-click a line and it opens as a tab of the page’s own workbook: counterparties from the AP mirror down the rows, a stated basis for every carried figure, and a roll-up that is a real formula. It stays scratch until you adopt it onto the working forecast.
Hand-set on the plan: the plan carries 68,400.00; this book builds to 65,218.51 — a gap of 3,181.49 (2026-08 to 2026-12).
Forecast versions are append-only, content-hashed, and attributed. A version becomes the budget only when an owner or administrator adopts it with a note; stale lineage blocks the action rather than quietly proceeding.
Board approved the reforecast at the September meeting. The hiring ramp restarts with two backfills; revenue holds the Apex renewal.
Hands and agent go through the same service, the same validation, and the same record — for every act.
same recordEvery figure traces to the ledger through one governed register; deterministic code computes, the model never does the arithmetic.
drill to sourceA what-if recomputes on screen with a banner up. Revert un-happens it. Nothing writes to the plan without a stated confirm.
never an editThe floor that decides what flags is a versioned policy with a required reason on every change.
policy-cited flagsThe agent drafts; a named person accepts, adopts, and publishes. Nothing becomes the plan of record on its own.
explicit decisionWhat the deployment cannot state — a cash outlook missing its calendars, a metric with no measure — says so instead of drawing something.
refusals over guessesReview the current close, evidence, and journal-entry capabilities alongside early-access surfaces.
See the dependency-aware close workspace that precedes governed planning decisions.
Understand how source versions retain provenance and content verification.
AI for accounting and FP&A on the ledger you already run. No migration. No rip and replace.