Organic compliance, built in
The certifier asks for evidence. Your ledger already has it.
Mass balance, lot trace-back, supplier certificates and audit reports — computed from the same purchases, inventory movements and sales you already reconcile. No second system, no spreadsheet week.
- Runs on your own hardware
- AI never writes SQL
- Tenant isolation by Postgres RLS
- Every irreversible action audited
- Statements parity-gated hourly
Compliance software usually means re-entering what the ledger already knows. Finanly computes the evidence from the same rows you closed — so the numbers agree with the books by construction.
Mass balance
Inputs in, outputs out, to the kilo.
Pick a period and a product. The engine sums certified inputs from purchase invoices and lots, outputs from sales and fulfillments, and shows the allocation detail behind every line. Yield and variance are computed, not typed.
- Per-lot allocations from inventory movements
- Payout and invoice sources recognized automatically (Shopify, PayPal, Stripe, WooCommerce, Amazon channels)
- Runs are stored; each report run keeps its artifact
Trace back
From a sold lot to the farm gate.
Start from anything a customer received and walk upstream: roast batch, green lots, supplier, certificate, purchase invoice, bank line. Every hop is a real record with a real ID.
- Movements and allocations synced from the ledger
- Supplier certificate validity shown inline
- Export the chain as part of an audit report
Supplier certifications
A registry that warns before it expires.
Register each supplier's standard, certifying body and validity window. Purchases from a supplier with an expiring or missing certificate are visible in the compliance categorization queue before they become a finding.
- Create and update certificates from the UI
- Validity surfaced in trace-back and mass balance
- Categorize purchases by compliance category and scope
The five tools
What is in the sidebar today.
Transaction Categorization
Tag purchases and sales with a compliance category and scope; queue of untagged lines.
Supplier Certifications
Registry of certificates with standard, body and validity; expiries visible.
Trace Back
Upstream chain from any sold lot to inputs, supplier and invoice.
Mass Balance
Inputs vs outputs per period and product with allocation detail.
Audit Reports
Generate a report run and download the artifact for the certifier.
AI narrative
The private model writes the explanatory narrative around numbers the engine already computed. It explains; it never calculates.
Compared
Spreadsheet season vs compliance from the ledger.
Traditional ERP / bookkeeping
- Re-key purchases and sales into a compliance workbook
- Certificates in a shared drive; expiries noticed at audit
- Trace-back reconstructed by hand from emails
- Numbers that drift from the books
- A week lost before every inspection
Finanly
- Same rows you already categorized and reconciled
- Registry with validity, surfaced where purchases happen
- One click from sold lot to supplier certificate
- Mass balance agrees with the ledger by construction
- Report runs stored with their artifacts
Scope, honestly
Built in. Expanding.
The engines are deterministic and shipped. The broader traceability platform they descend from is being adapted in phases; what you see here is what runs today.
FAQ
Straight answers
Which standards does it cover?
The engines are standard-agnostic: they compute mass balance and trace-back from lots, movements and allocations. Certificates are registered with their standard (for example EU Organic or USDA NOP) and body; the audit report presents the evidence a certifier under either scheme asks for.
Where does the inventory data come from?
From the ledger connector's stock movements (ERPNext today) and from fulfillment and landed cost flows: Shopify fulfillments become stock entries, inbound shipments carry lots. Compliance lots, movements, allocations and certifications are synced into the canonical store.
Is the AI involved in the numbers?
No. Mass balance and trace-back are deterministic services in core-api. The private model is called only for the narrative section of an audit report, with the computed figures as input.
Can I download the report?
Yes. Audit Reports creates a report run; when it completes you download the artifact from the same page. Runs and artifacts are kept, so you can show the certifier exactly what you produced and when.
Does this replace a full traceability platform?
Not yet, and we do not claim it does. This is the financial-ledger side of traceability: what was bought, moved, sold and certified. Deeper adaptations of the origin platform's engine are planned as a later phase.
Which companies use it?
It is built for the coffee business in the stack (green lots in, roasted blends out). If your product flow is different, run one mass balance on last quarter before relying on it.
Turn your next inspection into a download.
Private beta. Tell us which certifier you report to.