Enrichment, Validation, and Matching

After extraction, every invoice is enriched against your business rules, validated for completeness and accuracy, and matched to the right purchase orders, suppliers, and organizations.

Request a Demo

Rules You Configure, Not Code

Every invoice passes through your enrichment and validation pipeline after data extraction. Define the logic once, and it runs automatically on every invoice that meets the conditions.

Organization Matching

Match invoices to the correct entity in your organization structure. Standard field matching, purchase order lookup, or defaulting rules when no match is found.

Supplier Matching

Identify and link vendors from your supplier master data. Match by supplier number, name, VAT ID, or derive the supplier from a linked purchase order.

Field Enrichment

Populate invoice fields using expressions, lookup tables, or database queries. Works at both header and line-item level to fill in what the extraction did not cover.

Invoice and PO Matching

Nuntiq uses a combination of rule-based logic and AI-assisted pre-matching to link invoices to the right purchase orders. The system considers line descriptions, amounts, vendor context, and PO references to suggest the best match.

After matching, PO references are normalized and cleaned automatically. Ambiguities are flagged for review rather than silently resolved, so your team stays in control of the final decision.

AI-assisted PO pre-matching based on line details and amounts
Automatic PO reference normalization and cleanup
Organization and supplier derived from matched POs
Ambiguities flagged for review, not silently resolved

Duplicate detection across invoice number, supplier, date, and amount
Mandatory field checks before invoices proceed
Expression-based validation for custom business logic
Line-level validation for per-item checks
Severity levels (error, warning, info) for each validation issue

Validation

Every invoice passes through your validation rules after enrichment. Duplicate detection catches invoices that have already been processed. Mandatory field checks ensure nothing is missing. Expression-based rules enforce custom logic like "total must equal sum of line amounts".

Issues are flagged with severity levels: errors block the invoice from proceeding, warnings surface for review but do not block, and informational notes give context to the reviewer.

Processing Rule Sets

Enrichment and validation rules are organized into rule sets, which are assigned to processing teams. Different teams can run different logic for different types of invoices within the same account. Rules execute in a defined sequence, each with an activation expression that controls when it applies.