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 it is actually a rule of that kind and tells you if it is not.
It generates the code
And shows you the logic back in plain language before you approve anything.
It compiles in the sandbox
No imports, no file or network access, no clock, no randomness, a timeout.
It is tested on your history
Coding rules must reproduce your example invoices; match rules are backtested on bills you already posted.
You approve, it activates
As a new version, with one-click rollback and an audit row naming who changed it.
Four surfaces
Coding, posting fields, composition, matching
Coding rules decide GL, class and department. Posting-field rules set memo, department, dates and custom fields. Billing rules decide which lines are billed, from which document, and on which sublist. Match rules add your own conditions to the nine checks.
- 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
Placement rules are exercised against every charge shape the composer can produce. Match rules are backtested against your own already-posted bills. Coding rules must reproduce their stored example invoices. Activation is refused otherwise.
- 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. If a live rule turns out wrong, roll back to the previous version in one click; the audit trail shows who changed what and when.
No. The model writes the code at authoring time. At posting time the approved code runs in a restricted sandbox, which is why 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.