Sebastian
Request access
Product · Journal entries

Balanced journal drafts, prepared by Sebastian and reviewed by finance.

For controllers evaluating AI journal entry automation, Sebastian uses an explicit approval interrupt before its journal tool creates a balanced draft. Automated journal entries are persisted with their entry lines and may include a reasoning trace before they enter pending review. The agent does not post them directly.

Request accessSee the month-end close workflow →
Prepare

Start with the period context, then build the double entry.

The agent can read period-level journal totals before it proposes an entry. Its request includes the memo, entry date, debit and credit lines, and may include a reasoning trace for a balanced draft.

  • Period-level journal totals give the agent bounded accounting context
  • Line items carry accounts, descriptions, debits, and credits
  • Unbalanced entries are rejected by validation instead of entering review
sebastian · journal / prepared draftIllustrative 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
Approve the tool call

The write boundary is visible before the record exists.

Journal creation is designated as an interruptible write. Sebastian pauses with the proposed tool input, and execution resumes only after the approval decision. Approval creates a draft—not a posted entry.

  • The proposed write can be inspected before execution
  • Conversation state persists across the approval pause
  • The created entry receives agent authorship and a pending-review status
sebastian · agent / approval interruptIllustrative 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.
Review

Human, agent, and imported entries use one journal entry workflow.

The persisted journal records source type, review state, balanced lines, and an optional reasoning trace. A reviewer can post or reject the entry from the journal workflow, leaving the preparation and decision stages distinct.

  • Human, agent, and external-source authorship are represented explicitly
  • Entry lines and any provided reasoning trace remain available during review
  • Post and reject actions update the persisted review lifecycle
sebastian · journal / 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
Control boundary

What Sebastian does—and what it does not claim.

Balanced by schema

Double-entry validation prevents a draft with unequal debit and credit totals from being created.

validated
Approval interrupt

The agent execution pauses before the designated journal-creation write tool runs, creating an explicit accounting AI approval checkpoint.

inspect first
Pending review

The agent tool creates a reviewable draft. It does not directly post the journal entry.

no direct post
Optional reasoning retained

When provided, the accounting rationale remains part of the entry so a reviewer sees more than the final lines.

review context
Persisted lifecycle

Draft, review, post, and reject states live in the journal service rather than only in the interface.

durable state
No blanket SoD claim

Sebastian does not present server-enforced separation of duties as shipped until authenticated actor enforcement is complete.

precise controls
Go deeper

See the work up close.

Month-end close

Place journal preparation inside a dependency-aware close with owners and review workbooks.

Explore

Close evidence

See how source snapshots retain provenance, control totals, and content verification.

Explore

Journal approval control matrix

Test initiation, source completeness, independent review, posting, and reversal controls.

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…