Built for books an auditor will read.

FynOS holds a company's orders, payouts, stock, bills and journals, so it is built the way a finance system should be: each company kept apart, every action checked against the person's role, payments and proposed changes held for approval, and a record of who did what.

Each company kept apart, every action checked against a role, and a record of who did what.

Access and approvals

Roles that match the job
From owner and approver to viewer and warehouse.
Permissions per module
Each action a separate permission, set per module.
Maker and checker
Whoever submits a bill cannot approve it.
A role per company
A different role in each company of a group.
Payments approved first
No bank file before the batch is approved.
Proposals wait for a person
Changes Alfred or an agent proposes wait for confirmation.

Roles that match the job
Owner, admin, finance manager, payables, receivables, approver, viewer and warehouse.
Permissions per module
Create, read, update, delete, approve, export and configure are separate permissions, set module by module.
Maker and checker
Whoever submits a bill cannot approve it. Payment batches and Alfred's proposals wait for a person.
A role per company
A person can hold a different role in each company of a group, and an outside accountant gets only the access you grant.
Payments approved first
A payment batch must be approved before its bank file can be exported, and each line is then marked paid or returned.
Proposals wait for a person
Changes Alfred or an agent proposes, such as a journal or a new vendor, run only after a person confirms them. Routine entries from orders, payouts and stock post automatically, and the audit trail records them.

Data

A schema per company
Each customer's data lives in its own database schema.
Append-only settlements
Payout records are added to, never overwritten.
Audit trail
Who changed what, and when.
Report lines traceable
Report lines open to the records behind them.
Encrypted bank details
Vendor bank accounts are encrypted at rest.
Encrypted in transit
TLS on every connection.
Hosted on AWS
Run on Amazon Web Services infrastructure.
Your data stays yours
Export tables and reports to CSV at any time.

A schema per company
Each customer's data lives in its own database schema.
Append-only settlements
Payout records in the settlement ledger are added to, never overwritten.
Audit trail
Who changed what, and when.
Report lines traceable
Report lines open to the journal lines and records behind them.
Encrypted bank details
Vendor bank accounts are encrypted at rest.
Encrypted in transit
TLS on every connection.
Hosted on AWS
Run on Amazon Web Services infrastructure.
Your data stays yours
Export tables and reports to CSV at any time.

Assurance

Controls designed to the Trust Services Criteria used for SOC 2 reports. No SOC 2 report has been issued yet.

Claude.

The AI connection is read-only and approved one company at a time.

Sign in with FynOS
OAuth, using your own FynOS login.
Read-only
It can look, never change, create or delete.
Consent per company
One company per approval, up to 30 days.

Sign in with FynOS
OAuth, using your own FynOS login.
Read-only
The AI app can look, but it can never change, create or delete anything.
Consent per company
Each approval covers one company and lasts up to 30 days. Individual pay records are never shared.

How the connection works →

Security questions: support@fynos.ai