Operating design / AI-native finance

Close the books every day. Decide in real time.

September 2026  |  Seed-stage operating model, vendor-agnostic

Every day, a team of AI agents runs the close as a loop. Source activity is captured, coded, supported, reconciled, and either processed by rule or handed to a human for judgment. Then the loop runs again tomorrow. The process is AI-native: the agents do the work, the accounting system holds both the transaction and the evidence behind it, and a person steps in only where judgment is needed.

Runs every dayThe agent team keeps feeds, searches, coding, accruals, reserves, and exception queues current.
Rules firstEstablished vendors and repeatable transactions flow without unnecessary review.
Evidence attachedSupport travels with the record from financial statements to source documentation.
Judgment visibleUnusual changes stop for a documented human decision, then return to the loop.
SOURCES Cash and banking Live bank feeds Credit-card transactions Account transactions Payments and transfers Source data + timestamp Payables AP inbox, repository, and APIs Invoice and payment integrations Contracts and approvals Receipts and service dates Searched every day HR and talent Wage and bonus changes Expected starts and salaries Terminations and benefits Worker status changes People data + effective date Billing Invoices and cash received Aging and disputes CRM and collections status Credits and reserve signals Customer activity + status every source feeds the loop DAILY AGENT LOOP runs every day, then again tomorrow 1Capture and code Run feeds and AP search Match, classify, and reconcile Apply account and vendor rules Attach linked evidence 2Accrue and reserve Accrue known obligations Update payroll and people changes Refresh reserve signals Document assumptions and support 3Review and reconcile Review output from 1 and 2 Run flux and variance analysis Compare to prior month, same day Return unusual findings to 1 and 2 4Report and analyze Summarize the day's work Give a clear flux readout Flag new vendors and anomalies Flag off-trend month-to-date spend unusual findings returned to 1 and 2 Human in the loop In: an item the agents cannot resolve by rule. Each gets an owner, amount, question, due date, and decision. Out: the decision, recorded back in the loop. OUTPUTS DELIVERED what the loop leaves in the accounting system every day Coded transactions Account, vendor, owner, and linked source evidence Accruals and reserves Daily estimates, assumptions, support, and controlled updates Reconciliations and queue Ties, exceptions, decisions, owners, dates, and resolutions Traceable reporting Statements, ledger, transaction, evidence: one unbroken chain

Design standard

The accounting system is the system of record for the transaction and its evidence. A reviewer can move from the financial statements to the ledger, to the transaction, to its support, without Accounting having to find and package it later. Because the books and variance signals are current, leadership can identify what changed and course-correct sooner.