Message the work in. Review the books out.

01

Intake from the channel you already use.

A document or question can arrive by email, Slack, SMS-style text, photo upload, voice note, or the web app. The product foundation already treats these as channel-neutral agent runs, rather than separate workflows.

• Email and web are the first practical surfaces.
• Slack, SMS-style text, and voice are planned channel surfaces.
• Each channel gets an appropriate plain-text fallback for approvals.

02

Documents are captured, de-duplicated, and attached.

Source documents, bank statements, invoices, bills, credit notes, payment processor records, PEPPOL messages, payroll journals, and POS feeds are routed into the accounting workflow with source references preserved.

03

The agent drafts the accounting treatment.

The agent uses the company context, the source document, the ledger framework, and the accounting knowledge base to propose the treatment. LLM calls happen outside database transactions; posted accounting data is protected by application and database guards.

04

You review the items that need judgment.

The Review Queue shows the amount, counterparty, plain-English account treatment, risk flags, reasoning, source attachments, and proposed action. Low-confidence, duplicate, locked-period, cross-currency, and missing-source cases are surfaced before posting.

05

Approval posts the books and preserves the trail.

When a proposal is approved, the posted record, reasoning log, and audit event are correlated. Posted journal entries are immutable; later corrections happen through reversal or adjustment, not silent edits.