Sebastian
Request access
Product · Accounting

Sebastian AI accounting with a visible human review boundary.

Sebastian combines dependency-aware close management, persistent review workbooks, verifiable source snapshots, and approval-gated journal drafting. AP and reconciliation experiences are available as clearly labeled design-partner re-enactments while their backend implementation gates remain open.

Request accessSee what it unlocks for planning →
sebastian · journal / illustrative pending reviewIllustrative re-enactment · demo data
Illustrative balanced journal draft
JE-DEMO-001 · example dataSebastian
Preparing example…
AccountDebitCredit
6000 · Example expense100.00
2100 · Example accrual100.00
Balanced100.00100.00
Illustrative optional reasoning trace
  1. 1Read persisted period-level journal totals
  2. 2Mapped the proposed debit and credit lines
  3. 3Validated that total debits equal total credits
Accounts payable · early access

Sebastian accounts payable early access: evaluate the decision workflow.

For teams evaluating Sebastian's accounts payable direction, the current product demonstrates controller decisions for bounded AP exception families. It does not present general ingestion, matching, approval routing, payment rails, or ERP write-back as shipped capabilities.

  • Persist controller direction and decision history for supported prototype exceptions
  • One predefined resolution can produce an idempotent accrual entry
  • Use the re-enactment to evaluate product direction, not as customer-performance proof
  • Implementation gates are documented before general accounts payable automation claims publish
sebastian · ap / bill INV-8841Illustrative re-enactment · demo data
Prototype AP exception seeded scenario · example data
Prototype decision trace
Exception
Context
Direction
Follow-through
  • A supported prototype exception family is identified in the seeded scenario.
  • Illustrative context is assembled for a controller to evaluate.
  • MAAwaiting direction
  • ↳Supported prototype resolution creates idempotent accrual follow-through.
Design-partner prototype · not general accounts payable automation
Reconciliations · product direction

A concrete model for match review and exceptions.

The account reconciliations interface is a product re-enactment backed by deterministic demo data, not a claim of live bank or ERP connectivity. It demonstrates the intended match, exception, and evidence-review experience while the persistent reconciliation service and connector inputs are built.

  • Inspect proposed matches and exception context at line level in the re-enactment
  • Evaluate the intended human review path for unmatched items
  • No live-feed, nightly automation, or match-accuracy claim is implied
sebastian · reconciliations / operating accountIllustrative re-enactment · demo data
Reconciliation interaction prototype demo data · no live feed
illustrative states
Illustrative source A
  • Example source row Aexample
  • Example source row Bexample
  • Example source row Cexample
  • Example source row Dexample
Illustrative source B
  • Illustrative candidate Aexample
  • Illustrative candidate Bexample
  • Illustrative candidate Cexample
  • Illustrative candidate Dexample
Illustrative unmatched item · example
Example review state only; no automated-match result or explanation quality is implied.
Review
Close management

One persisted workspace for the close.

Tasks, owners, reviewers, dependencies, comments, files, workbooks, and activity live in one close model. Blocking relationships derive from the task graph, and human completion remains explicit.

  • Dependency-aware tasks show which upstream work is blocking a downstream review
  • Owners, approvers, files, comments, and activity stay attached to the task
  • The current product does not claim to enforce an accounting-period lock
sebastian · close / june 2026Illustrative re-enactment · demo data
Illustrative close workspaceexample states · not customer results
  • Review an upstream close blocker
    Close task graph · Dependency state recorded
    Illustrating…
  • Verify a source snapshot
    Evidence integrity · Content digest checked
    Illustrating…
  • Prepare a balanced journal draft
    Journal workflow · Pending human review
    Illustrating…
  • Approve journal creation
    Human decision · Waiting on your call
    Needs your call
Journal entries

Agent-prepared or entered by finance. One journal lifecycle.

The agent journal tool pauses for approval, validates double-entry balance, and creates a pending-review draft that may include a reasoning trace. Human, agent, and imported entries share the persisted journal workflow.

  • Agent creation is an interruptible write, inspectable before execution
  • Balanced lines, memo, date, author type, and any reasoning trace persist with the entry
  • The agent tool creates a draft and does not post the entry directly
sebastian · journal / JE-2026-0115Illustrative re-enactment · demo data
Illustrative balanced journal draft
JE-DEMO-001 · example dataSebastian
Preparing example…
AccountDebitCredit
6000 · Example expense100.00
2100 · Example accrual100.00
Balanced100.00100.00
Illustrative optional reasoning trace
  1. 1Read persisted period-level journal totals
  2. 2Mapped the proposed debit and credit lines
  3. 3Validated that total debits equal total credits
Evidence

Source snapshots keep their provenance.

Close evidence can be stored as an immutable version with the query parameters, rows, row count, control totals, and canonical content hash needed to identify and re-verify the source used in review.

  • Versioned snapshots preserve the source a prior review relied on
  • SHA-256 content verification detects later change to stored snapshot data
  • Review workbooks and human decision activity remain distinct from source evidence
sebastian · close / evidence · 2110Illustrative re-enactment · demo data
Example close task illustrative files
illustrating…
  • csvexample-source.csvIllustrative task file · 24 KB
  • xlsxreview-workbook.xlsxIllustrative workbook · 38 KB
  • jsoncontrol-totals.jsonIllustrative snapshot · 4 KB
  • pdfreview-note.pdfIllustrative decision · 12 KB
Example files shown. Source snapshots and task attachments persist as separate records.
The full surface

Everything else the accounting close leans on.

Dependency-aware close

Task relationships produce concrete blockers while ownership and review state remain attached to the work.

task graph
Persistent review workbook

Analysis, reviewer decisions, human inputs, comments, and resolution activity remain tied to the task.

review history
Verifiable snapshots

Query scope, control totals, row counts, rows, and a canonical content hash travel with a source version.

SHA-256
Approval-gated agent draft

The agent journal write pauses for approval and creates a balanced entry in pending review.

no direct post
Durable agent state

Agent execution persists across requests and designated tool approvals instead of living only in one browser session.

resumable
Claims with boundaries

AP automation, generalized reconciliations, NetSuite mirroring, ERP write-back, period lock, and enforced SoD remain explicit gates.

no hidden roadmap
Go deeper

See the work up close.

Month-end close

Inspect the implemented task, dependency, review, activity, and evidence workflow.

Explore

Journal entry automation

Follow an approval-gated balanced draft into pending human review.

Explore

Close automation checklist

Classify scope, dependencies, authority, exceptions, and retained evidence.

Explore

Finance AI scorecard

Score a vendor on provenance, authority, exceptions, security, and evidence.

Explore

Keep your ERP. Close and plan in one pane.

AI for accounting and FP&A on the ledger you already run. No migration. No rip and replace.

Request accessSign in
Agents at work · Matching an invoice to its PO line…