Deterministic coding

Decide the accounting the same way every time

GL account, class and department are decided by your rules, the same way every time.

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

3+

segments resolved independently on every line

0

model calls at posting time

1

method recorded per resolved segment

3

recurrences before a fix is offered as policy

How a line is coded

Several decisions, not one

Segment by segment

GL, class and department each have their own logic: fixed value, lookup, project map or keyword match.

Signals, wherever they are printed

Vendors print the cost centre in different places. Signal lookups read it wherever that vendor puts it.

A watchlist, not a guess

Uncategorised products are flagged, not silently miscoded. PO invoices take GL, class and department from the PO.

Lookup tables

Your lookups, imported from what you already have

Excel or CSV import. A person confirms the mapping; values are checked against the chart of accounts.

  • Client-maintained — no developer in the loop
  • Validated against the live chart of accounts
  • Header and posting-field rules: memo, department, dates, custom posting fields, with per-vendor exceptions
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

Correction learning

Your corrections compound

A clerk’s repeated fix — three times by default — is suggested to an approver as a new rule.

  • Approver in control of what becomes policy
  • Every promotion versioned with rollback
  • Coding diagnostics compare against the bill as it actually posted and name the cause of any difference
Posting Log
GX-88412Posted · VB-4410j.doe
CF-1189Refused · price variance 6.2%j.doe
INV-1001Posted · VB-4411a.rao
NW-5531Waiting · receipt expectedsystem

Coding, answered

  • The model writes the rule once and you approve it. Posting runs it sandboxed: same input, same output.

  • Extra segments resolve the same way; custom posting fields get a default plus per-vendor exceptions.

  • Upload the bill as it was posted. Coding diagnostics compare line by line and name the cause of each difference.

Stop re-deciding the same coding

Bring one vendor whose invoices are hard to code. We will write the rule with you and backtest it against their history.