Rules in plain English
Rules in plain English
tested on your history
Write a rule in plain English. It is tested on your past invoices before it can touch money.
From English to production
How a rule gets from a sentence
to a posted bill
You type it in English
The system checks the rule is that kind and tells you if not.
It generates the code
And shows you the logic in plain language before you approve.
It compiles in the sandbox
No imports, files, network, clock or randomness, plus a timeout.
It is tested on your history
Coding rules must reproduce examples; match rules are backtested.
You approve, it activates
As a new version, with one-click rollback and an audit row.
Four surfaces
Coding, posting fields, composition, matching
Coding rules set GL, class and department; posting-field, billing and match rules cover the rest.
- Inclusion: every exclusion recorded with the deciding rule and the amount
- Source: bill from the receipt, or from the purchase order
- Placement: items versus expenses, freight and tax classified correctly
“Code Globex lines to 600200 and the site named in the description. If the line mentions security, use 600250 instead.”
The safety story
Nothing governs money until it passes a test
Every rule type must pass its own tests, or activation is refused.
- Order is precedence; drag to reorder
- Shipped rules are ordinary editable rows you can change or delete
- Every change audited with the user who made it
Rules,
answered
Your controller or AP lead — the person who knows the coding logic and would enjoy writing it down. No developer, no release cycle.
It will not activate if the backtest fails. A wrong live rule rolls back in one click, with a full audit trail.
No. The model writes the code once; the approved code runs sandboxed, so the same invoice codes identically every time.
Write your first rule with us
Pick a vendor. Describe how it should be coded. Watch it backtest against that vendor’s last twelve invoices.