For CFOs

Which AI agents can act on systems of record
without you signing the check.

If you are the person who signs the audit opinion, you are also the person who owns the question: when an AI agent writes into our general ledger, our subledger, our vendor master, or our payroll — what stops it from writing whatever it wants?

Syntheka is built for that question. This page is the evaluation checklist we use with finance leadership. Honest on what we do, what we don't do, and where we are not yet ready for your environment.

Why this matters to finance

The question is not "can it act" but "can it act under the controls you sign for".

A CFO who evaluates AI agent platforms is not asking about model size or prompt quality. The question is segregation of duties, audit trail integrity, and the specific control objectives you already attest to (SOX 404 for public; the equivalent for private; statutory audits for regulated industries).

What Syntheka actually does

The capability list, scoped honestly.

Syntheka is an ontology-driven action platform. Agents propose typed actions on typed objects (vendor, contract, certificate, payment, settlement, refund, chargeback, etc.). Every action enters the approval DAG. Every approval is recorded. Every execution is reconciled.

Approval

Approval DAG

The initiator cannot self-approve — enforced server-side, in code.

Multi-node approval with segregation of duties, configurable per workflow. The same engine that gates a payment run can gate an outbound email blast.

Audit

Bi-temporal audit log

Append-only and hash-chained — retroactive edits are flagged, not silently absorbed.

Both transaction time and valid time are recorded. Replayable for the retention period.

SAP · ERP

Three-way reconciliation

A write is not done until the external system confirms the round-trip.

SAP, NetSuite, QuickBooks, vendor portals — platform intent ↔ system of record state ↔ field evidence.

Multi-entity

Multi-entity / multi-ledger

Cross-entity writes require explicit operator override; the default is refuse.

Entity, company, and ledger are first-class fields on every action — an action against Entity A cannot accidentally write to Entity B's books.

Reversal

Reversible actions

Reversal is a compensating entry, not a deletion.

Every reversal itself enters the approval DAG and carries its own hash chain.

Deployment

Self-hosted / private cloud

Your data and your keys stay in your perimeter.

Docker Compose, single-command full-stack bootstrap. Air-gapped capable.

What Syntheka does NOT do

Honest boundaries.

If any of these are required for your evaluation, Syntheka is not the right vendor today. We will tell you, and refer you elsewhere if we can.

The CFO evaluation checklist

Twelve questions to ask of any AI agent vendor.

Use these against any vendor, including us. If a vendor cannot answer them clearly, treat that as the answer.

  1. Is segregation of duties enforced in code, or is it a recommendation in documentation?
  2. Can the initiator of an action also approve it through any sequence of role changes?
  3. Is the audit trail append-only and hash-chained? Can you prove it has not been edited retroactively?
  4. Do you record bi-temporal timestamps (transaction time + valid time)? Or only one of them?
  5. How do you reconcile platform intent against system-of-record state after the write?
  6. Can a single human operator trigger an action that touches two entities or ledgers without an override?
  7. Where do credentials live? Can the vendor access our systems of record with their own credentials?
  8. What happens if the platform goes down mid-action — does the system of record state remain consistent?
  9. What is the reversal path for every action? Is reversal a deletion or a compensating entry?
  10. Can you demonstrate a single concrete action end-to-end, on a real system of record, in under 60 minutes?
  11. What is your upgrade and patch cadence, and what is the customer-facing change log?
  12. If we decide to leave, what is the exit path — data portability, audit trail export, credential revocation?
Pricing for finance

Three numbers that matter.

Syntheka's pricing is published, not quoted. There are no per-action variable surprises because there are no per-action variables in the price.

TierPriceFits
Starter$500 / monthOne team, one workflow, one site
Professional$2,000 / monthMulti-workflow, multi-site, multi-approver
EnterpriseQuote (custom)Self-hosted, air-gapped, regulated environment

A fixed-fee pilot is $1,500 for one site, 60 days, up to two workflows. The pilot pricing is honored for the first three customers.

For the e-commerce marketplace recovery template, outcome-aligned pricing (verified recovery per claim) is available as an option. We do not bill on assumed resolution; every claim is customer-verified before the invoice.

How to start

The CFO path through the pilot.

Most CFOs we work with run a 60-day pilot in parallel with their existing process — not a replacement. The pilot ends with a measurable comparison, not a swap.

  1. Week 1: Define the action in scope (a payment run, a vendor master change, a refund queue). Identify the existing process owner.
  2. Weeks 2-3: Syntheka composes the agent from the industry template plus your artifacts. No data leaves your environment.
  3. Weeks 4-6: Run the pilot in shadow mode — every Syntheka-proposed action is compared against the existing process, side by side.
  4. Weeks 7-8: Report. The decision to adopt, extend, or end is yours, with the comparison data.