Sebastian
Request access
Platform · Close evidence

Preserve month-end close evidence with verifiable integrity.

Sebastian stores verifiable accounting evidence as versioned source snapshots with their query parameters, control totals, row counts, and a canonical content hash. This month-end close evidence can cite a precise source version, and the server can detect whether stored content later changes.

Request accessSee the close workspace →
Source snapshot

Close documentation software should preserve the data and its recipe.

A close source snapshot records the query parameters used to produce it together with its rows, control totals, and row count. The source is versioned instead of being replaced by the next refresh.

  • Query parameters keep the scope of the extract explicit
  • Row count and control totals give reviewers concrete completeness checks
  • Version history preserves the source a prior decision relied on
sebastian · evidence / source snapshotIllustrative 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.
Content verification

Hash the canonical content, then verify it on the server.

Sebastian canonicalizes the stored content and records a SHA-256 digest. Verification recomputes the digest server-side, so later mutation can be detected rather than trusted away.

  • Canonical serialization makes the verification input deterministic
  • SHA-256 records a compact fingerprint of the stored snapshot
  • Server-side re-verification reports whether the saved content still matches
sebastian · evidence / verificationIllustrative 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 provenance

Keep the accounting audit trail separate from reviewer judgment.

The source snapshot preserves what was read. The task workbook preserves analysis and review work. Activity records preserve human inputs and decisions. Keeping those layers distinct makes the provenance easier to inspect.

  • Source snapshot: data, parameters, totals, rows, and content hash
  • Review workbook: analysis tied to the close task
  • Activity history: reviewer inputs, decisions, comments, and resolution steps
sebastian · close / evidence historyIllustrative 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.
Evidence model

Specific records instead of an “audit-ready” promise.

Immutable versions

A new source version is appended so prior close work can continue to cite the exact snapshot it used.

versioned
Query provenance

Parameters record the scope used to generate the source rather than preserving only an unexplained table.

scope retained
Control totals

Named totals and row counts can travel with the source for reviewer completeness checks.

checkable
Content digest

A canonical SHA-256 digest fingerprints the stored source content.

SHA-256
Server verification

The server recomputes the digest to determine whether the saved content still matches its fingerprint.

re-verifiable
No assurance shortcut

These controls support evidence integrity; they are not presented as a certification or an auditor endorsement.

evidence, not a badge
Go deeper

See the work up close.

Month-end close

See how evidence versions, review workbooks, tasks, and decisions fit into one close workspace.

Explore

Journal entry automation

Follow an approval-gated agent draft into the persisted journal review lifecycle.

Explore

SHA-256 evidence protocol

Work through what a content digest proves—and what it cannot establish about accounting 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…