Trust

Every number has a source. Every change has a history.

Finance needs more than a plausible answer. Sebastian keeps posted, estimated and forecast amounts apart, works under policies you write, leaves approvals with people, and treats your data as yours. Here is how.

Talk to us How we handle data

An empty meeting room with a long table and tall windows

Kinds of truth

Five kinds of number, never silently mixed.

A forecast can move on new evidence before accounting posts an entry. That is the point. But a projection must never read as a posted actual, and a proposal must never quietly become an approved one.

Posted

In the general ledger. Authoritative. Comes only from the ERP.

Estimate

Incurred but not yet posted, calculated from evidence such as usage or a signed contract.

Forecast

Expected for the rest of the period, from the working outlook or an approved version.

Approved

A budget or forecast version a named person approved. Changes only with a new approval.

Draft

A scenario or proposed accounting treatment. Never applied until someone approves it.

Explainable

Any material figure opens to its evidence

P / 1

Result, drivers, records

A financial line opens into the drivers that moved it, and each driver into the contracts, positions, invoices or usage records behind it.

P / 2

Calculation and accounting status

The formula, the inputs, and whether the amount is posted, estimated or forecast. Reproducible from the input and model versions at the time.

P / 3

Work and decisions

The review, approval or decision attached to the figure, with who did it, when, and what they saw.

Policies

Sebastian works under rules you write

Match tolerance, approval authority, posting authority, write-off ceilings. Each one has a name, a number, and a plain description of when it applies. Sebastian cites the policy on every piece of work it does.

Settings · Policy

Sebastian follows these rules when it works

+ New

Accounts payable

AP Policy 1Match toleranceHow far a bill may differ from its purchase order and still tie out.

AP Policy 3Approval authorityWhich bills need a human approver, how many, and who may not be one.

AP Policy 6Unusual amountsWhen a bill is large enough against a vendor's usual to need a second look.

Journal entries

Journal Policy 1Posting authorityThe person who prepared an entry cannot post it.

Reconciliation

Reconciliation Policy 5Write-offsWhat each role may write off, and where the rest goes.

Your data

Processed under contract. Never used to train shared models.

Ownership: Your financial records, and the outlooks, scenarios and workpapers Sebastian produces for you, are yours. We process them only to provide the service, under our terms and data processing agreement.
Model training: We do not use customer data to train, fine-tune or develop any model shared across customers, ours or a third party’s. Model providers we use are contractually prohibited from training on your data.
Security measures: Encryption in transit and at rest, single sign-on and role-based access, least-privilege access for our staff, logging and monitoring, and regular review of our suppliers. Security questionnaires and reports are available on request.
Retention and export: You can export your data in a machine-readable format at any time and for 30 days after termination. We then delete it from active systems, and from backups within 90 days. Posted entries remain in your ERP.
Residency and transfers: Data is hosted in the United States. Transfers from the EEA, UK and Switzerland rely on Standard Contractual Clauses and the UK Addendum. Details are in the Privacy Policy.