How validation protects your invoices
Validation is the layer that decides whether an invoice is safe to move forward. It catches duplicates, mismatches, and other issues before an invoice reaches approval, so you do not pay something that looks wrong.
Two systems, one outcome
Validation is the combination of:
- System rules. A small set of platform-defined checks (duplicate detection, three-way match) that apply to every entity.
- Integration hooks. Custom checks specific to certain ERP integrations.
Both run on every invoice. The output of either is a notice on the invoice.
When validation runs
Validation kicks in automatically as part of the invoice lifecycle:
- The invoice arrives (email forwarding or upload).
- The agent extracts the data.
- Validation rules and integration hooks run.
- Any blocking issues surface as notices and the invoice waits for human review.
- Once notices are resolved, the invoice continues into approval routing.
You also trigger validation manually with the Validate action when you have fixed an issue and want to re-check.
What gets checked
The platform includes three system rules out of the box:
- Duplicate Invoice detection.
- Duplicate Credit Memo detection.
- Line-item three-way match (verifies invoice, PO, and receipt agree).
Integration-specific tenant validation adds extra checks for certain ERPs (SAP, NetSuite, and others) where the integration knows about details only that ERP cares about.
See How validation works for the technical detail and Validation Rules for the rule-by-rule reference.
What you see
Validation results show up in two places on an invoice:
- The Validation Failed panel on the invoice detail page surfaces blocking errors with severity, the affected field, and the recommended action.
- Notices appear in the right panel when a check failed in a way that should alert the reviewer (duplicates, processing errors, price-change detections, and the validation-failure roll-up).
When validation has blocking errors, the invoice status moves to Pending Validation and waits until a person resolves the errors. See Soft Revalidation for how to re-run validation after fixing the errors.
Configuring validation
You cannot author new system rules. Severity overrides on existing rules (turning a blocking error into a warning, or disabling it entirely) are not yet self-serve in the in-app Settings nav — they're requested through your Mod AI implementation manager. See Configuring rule severity.