Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Rules based engine

The rule-based engine maps the invoice line to purchase order lines using fields such as unit price, delivered unit price, exact description, exact amount and amount round off.

The digitized invoice in accepted state moves to suspected duplicate state where the AP specialist verifies if the invoice is duplicate or not. When the invoice is confirmed to be not duplicate, the state of the invoice changes to received. The rules-based engine maps the fields in invoice such as unit price, derived unit price, exact description, exact amount and amount round off with the purchase order lines. If the invoice fields doesn't match with any of the fields in the purchase order lines, then the invoice state changes to matching error.

Image omitted: rules-based-engine.png
Rules based engine

Parent Topic:Using Accounts Payable Invoice Processing

Related topics

Invoice ingestion using the AP Invoice API

Invoice processing overview

Invoice processing cases

Invoice exceptions

Tolerance Rules and Variances for invoices

Invoice approvals

View invoice documents in the Source-to-Pay Workspace