Skip to main content
How it works

How your close runs itself

Connect your sources, get close tasks shaped from your data, confirm the plan — then the close fires on schedule while you work exceptions. Approved SQL does the bulk; the LLM drafts it and handles genuinely ambiguous cases.

One flagship workflow · packaged close

Your close on autopilot

Fifteen minutes to first connection. A week to first close. Then the close shapes itself from your data, runs itself on schedule, and leaves you the exceptions — with evidence for everything.

  1. 1

    Connect your sources

    ERP, bank feeds, Drive and OneDrive. The moment a source connects, we explore it — column profiles pulled live, no sample uploads. The lake starts filling on day one.

    Native depth · 200+ via Apideck
  2. 2

    Get your close shaped

    Suggest close tasks: bank recs per account, AP/AR, inventory, COGS, statements, flux — scoped from your actual data, dependencies auto-wired. Not a template; your close.

    Tasks shaped from your data
  3. 3

    Review and confirm

    A pre-checked proposal with per-task scope you can edit and regenerate with plain-English notes. Your confirm is the sign-off — nothing runs before it, and the draft is the audit record.

    1 human sign-off
  4. 4

    The close runs itself

    Scheduled runs fire in dependency order. Simple tasks replay canonical clones, judgment work goes to agent flows — only genuinely complex work gets a generated pipeline. Cost follows complexity.

    Scheduled · gated · ordered
  5. 5

    Work exceptions, then certify

    Morning view: what completed, what waits, what needs you. Adjusting JEs move draft → approve → post → revert. Certify with the evidence attached — every number traces to its run.

    Exceptions only

Run bundle · October close

Execution trace
All tasks complete
48
tasks run
1,189
rows matched
6
reviewed
$0.01
tolerance

Pipeline trace

Dependency order · 09:00–09:14 UTC

Verified
IN
Input
complete
SQL
Parse
complete
REV
Match
6 items
OUT
Post
complete
run_sql · match_batch_04 · 412 rows09:04
review_gate · approved · controller09:10
post · NetSuite · read-back verified09:14

Auto-match trend

Illustrative monthly rate

99.6%
97.4%
Jun
98.1%
Jul
98.8%
Aug
99.2%
Sep
99.6%
Oct
Every value traces to a lake version, run bundle, and sign-off.

Interface illustration — sample run figures. Inputs, queries, review decisions, and write-back confirmations stay attached.

See the published benchmark

Workflows

Built-in Accounting Workflows

Bank Reconciliation

Match bank transactions against GL entries with multi-strategy matching. Flag discrepancies for human review.

Month-End Close

Sequential close workflow combining reconciliation, classification, and validation with checkpoints.

Invoice Processing

Take AP invoices from raw PDF or email through PO matching, GL coding, and posting.

Revenue & Accruals

Classify transactions by delivery status and create recognition or deferral journal entries.

Payroll Reconciliation

Three-way matching across the payroll register, bank debits, and GL postings.

Financial Reporting

Generate Excel reporting packs with Balance Sheet, P&L, Cash Flow, and Notes.

Cash Application

Match incoming payments to open invoices and clear suspense automatically.

Collections

Prioritize the AR queue and automate dunning by risk score.

Vendor Management

Keep vendor data clean and consistent across the AP pipeline.

Procurement

Automate purchase-order and approval workflows before invoices arrive.

Deterministic by default. AI only where it earns its keep.

Most AI accounting tools run every transaction through a language model, which makes results non-repeatable and hard to defend to an auditor. We do the opposite: a DuckDB SQL engine processes the bulk of the work — matching, classification, validation — the same way on every replay. The LLM drafts that SQL for your review and handles genuinely ambiguous cases the rules can't resolve.

1. SQL runs the bulk

run_sql runs matching, classification, and validation on DuckDB. An approved query replays deterministically; a schema change or new period forces a re-review.

2. LLM handles the edge cases

Only transactions the rules can’t confidently resolve are escalated to an LLM call — narrow, targeted, and logged like everything else.

3. Every step is logged

Every SQL query, every LLM call, and every human approval or override is written to the audit trail — exportable for external review.

What Sets Us Apart

Reviewed SQL Execution

Your logic runs as SQL, reviewed by you, then replayed deterministically on DuckDB. The LLM drafts the SQL and handles cases the rules can’t resolve.

Visual Pipeline Builder

Compose workflows from a registry of 120+ atomic tools across matching, extraction, GL classification, consolidation, fixed assets, and more — drag-and-drop, with human review gates and conditional branches, no code.

US Accounting Standards

Financial statements formatted to US accounting presentation standards. Classification rules applied automatically, with your team reviewing before anything posts.

Full Chain-of-Custody Audit Trail

Every SQL query, every LLM call, and every human approval is logged and exportable — not just a summary, the actual decision trail.

Ready to automate your finance ops?

See the workflows in action — then join early access for onboarding as we expand.

See the workflows
How It Works | FinAdvantage