synthetic cfo generates SAP and Oracle ledgers from accounting rules, with fraud planted, every planted record written down at the moment it is planted, and innocent look-alikes beside nearly every scheme, so fraud detection can be trained and measured without a single real record.
For teams that build, buy or audit fraud detection and audit analytics on SAP and Oracle.
Describe the financial environment you need, then refine it in conversation. Built from accounting rules, never from real data.
Set every parameter explicitly.
Live analytics computed straight from your generated databases.
Think of it as marking an exam. We plant fraud in known places and write the answer key down as we plant it, so unlike real data, where nobody knows the true answer, we can grade any fraud-detection tool on exactly what it caught, what it missed, and where it raised a false alarm.
No tool of your own? Watch a fraud detector get graded on this dataset, in one click. Each is a different quality of detector, so you can see the whole range:
Run your tool (a script, an AI model, audit software) against this dataset, then bring back the record IDs it flagged, and we find them in whatever it exported.
Your identity, plan and preferences in one place.
Authorization: Bearer scfo_..., or install the Python client (the pip command on the evaluate page) and pass it to the client (also served as a single file, no dependencies). Quickstart on the evaluate page.From first sentence to scored model in four steps.
Migration pair: migration pair for a bank builds SAP ECC and S/4HANA from one seed: the operational subledgers are identical row for row in the two legs, and the record-to-report journal layer is generated separately for each, with its own chart, trial balance and labels (Team plan and above).
Multi-year fraud arc: retail company over 3 years, heavy fraud builds consecutive years where the schemes escalate, plus a consolidated database (Team plan and above).
Clean baseline: completely clean pharma data, no fraud produces a pristine zero-fraud control environment.
Reproducibility: every job records a seed; the same seed and configuration regenerate a byte-identical dataset on the same engine version, and a newer engine builds a different one (Reproduce says which before you press it). Set a fixed seed under Advanced.
A synthetic company's ERP, posting documents in real time. Purchase orders, invoices, payments and journals stream past as the year advances - and some are fraud, hidden in the flow like they would be in a real system. The answer key stays sealed until each scheme's reveal point, so a detector is scored on catching it live, never on peeking. Freeze the world into a downloadable audit package anytime; it matches exactly what you watched.
Every dataset ships as a four-layer package
Computed live from your generated database
Running now and recently finished. Stays here after a refresh.
Your saved conversations
What happened while you were away