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.

A product tour of InvoiceIQ by Analytos: Accounts Payable and Accounts Receivable on one platform.

From English to production

How a rule gets from a sentence to a posted bill

01

You type it in English

The system checks the rule is that kind and tells you if not.

02

It generates the code

And shows you the logic in plain language before you approve.

03

It compiles in the sandbox

No imports, files, network, clock or randomness, plus a timeout.

04

It is tested on your history

Coding rules must reproduce examples; match rules are backtested.

05

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
New coding rule — Globex ServicesDraft v3

“Code Globex lines to 600200 and the site named in the description. If the line mentions security, use 600250 instead.”

Backtest: 12 of 12 past invoices reproducedActivate

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
Posting Log
GX-88412Posted · VB-4410j.doe
CF-1189Refused · price variance 6.2%j.doe
INV-1001Posted · VB-4411a.rao
NW-5531Waiting · receipt expectedsystem

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.