Auditable Code

Finance software you can audit.

Open-source tools and field notes for finance teams who build their own systems — where every number ties back to its source, and no script moves money on its own.

See the tools Browse the toolbox

The rules

Every tool here follows the same seven rules. They come from audit practice, not from software fashion.

Engineering rules
Money is DecimalFloating point drifts by fractions of a cent. Ledgers do not.✓
Raw data is read-onlyExports from the ERP stay untouched. Work happens on copies.✓
Every number is traceableSource, formula, intermediate steps, result — in that order.✓
Tests before trustCore logic ships with automated tests and a self-check you can run.✓
A person approves moneyAutomation drafts payments and postings. A person releases them.✓
Secrets stay out of codeKeys and passwords live in local config that never reaches a repository.✓
AI drafts, people auditAI writes fast. Every change is reviewed the way an auditor reviews a schedule.✓

Tools

Small, focused and free. Each one solves a problem finance teams hit every month.

Open-source tools and their status
ToolWhat it doesStatus
finance-claude-starterRules, folder layout and prompts that let a finance team use AI coding tools without breaking controls.In progress
money-float-linterFinds floating-point arithmetic on money in Python code before it reaches a report.Planned
bank-reconcileMatches a bank statement to the ledger with date and amount tolerance, and writes the working paper with formulas.Planned

Code will be published at github.com/cuixiuxiong-arch as each tool is ready.

Toolbox

Open-source software tested in a real finance and IT setting — what each tool does, what it was used for, and whether it earned a place.

Open the toolbox

Who is behind this

Auditable Code is run by Edgar Cui, a finance manager with seven years across manufacturing and retail who builds reporting pipelines, ERP integrations and dashboards.

Contact

Questions, ideas for a tool, or a finance process that needs fixing.

[email protected]