30.11 Validation Criteria
30.11.1 Overview ¶
The Validation group provides two criteria that let a profile react to the result of the formal check (see chapter 50.5). This way, invalid invoices can be separated from valid ones - for example, routed to a clarification folder or reported separately - without changing the rest of the processing.
| Criterion |
Operators |
Value |
| Validation result |
is, is not |
Selection: Not checked, Valid, Valid with warnings, Invalid, Schema error |
| Finding (rule or text) |
Text operators such as contains, starts with, etc. (see chapter 30.5) |
Rule identifier (e.g. BR-DE-15) or part of the finding text |
30.11.2 Validation result ¶
The criterion compares the invoice's stored result with the selected value. Entries without a result - for example when validation is switched off - count as Not checked.
Examples:
Validation result is Invalid
Validation result is not Valid
The second line also matches "Valid with warnings", "Schema error", and "Not checked". If a profile should handle only faulty invoices, use two OR-linked rows with is Invalid and is Schema error.
30.11.3 Finding (rule or text) ¶
The criterion searches all stored findings of the invoice - per finding the rule, the technical identifier, and the text. It matches if the selected text operator applies to at least one finding.
Examples:
Finding contains BR-DE-15
Finding contains Buyer reference
With the rule identifier you react specifically to a particular violation - BR-DE-15, for example, stands for a missing routing ID (buyer reference) in an XRechnung. Invoices without findings have an empty finding text; a criterion with does not contain matches them.
30.11.4 Typical use ¶
A profile "Invoices with errors" with the criterion Validation result is Invalid moves the file to a clarification folder and sends the validation report to purchasing. It is placed before the regular profile and stops processing (option "Do not apply further profiles after this profile", see chapter 8.6). The regular profile then processes only valid invoices.
The program-wide email notification for invalid invoices does not require a filter criterion (see chapter 40.6.6).