30.5 Text Criteria

30.5.1 Overview

Text criteria compare text properties of the invoice (supplier, file name, routing ID, ...) with a value. The comparison is case-insensitive.

30.5.2 Operators

Operator Matches if ...
contains / does not contain the value does (not) occur in the property text
is equal to / does not equal the property text does (not) exactly equal the value
starts with / does not start with the property text does (not) start with the value
ends with / does not end with the property text does (not) end with the value

30.5.3 Value placeholders

Special placeholders are available in the value of a text criterion (insertable via Insert placeholder... in the criterion dialog):

Placeholder Meaning
<AND> Combines several partial values within ONE criterion: all parts must match. Example: Sample<AND>Ltd
<OR> It is sufficient if one of the partial values matches. Example: Sample<OR>Baker
<AND> with <OR> The value is split at <AND> first, then each part at <OR>. Example: Invoice<AND>2025<OR>2026 = contains "Invoice" and also "2025" or "2026"
<BeginOfRegex>...<EndOfRegex> The enclosed part is evaluated as a regular expression. Example: <BeginOfRegex>INV-\d{4}<EndOfRegex>
<NumberRange{from,to}> Matches if a number from the range occurs in the property text. Example: <NumberRange{1000,1999}>
<EntryFromList{ListName}> Matches if an entry of the given filter list matches (see chapter 30.10)

The placeholders can be combined with plain text and with each other, e.g. INV-<NumberRange{2026000,2026999}> or <EntryFromList{Suppliers}><AND>Ltd. The German forms <UND>/<ODER> are accepted as well.

Both separators in the same value: If <AND> and <OR> occur in the same value, the program splits at <AND> first and then checks each part on its own. <OR> therefore only applies within an AND part: Invoice<AND>2025<OR>2026 means "Invoice" and also "2025" or "2026" - not "Invoice and 2025" or "2026". The criterion dialog shows this reading below the value:

Note: The value combines <AND> and <OR>. The program splits at <AND> first and reads the value as: "Invoice" and ("2025" or "2026"). "Split…" creates rows with exactly this reading.

If a criterion contains both separators for the first time - that is, it did not before you edited it -, the dialog asks when applying; with Do not ask again, this question is no longer asked in future (to switch it back on: chapter 40.17.3). For a different reading, distribute the alternatives across several criterion rows that you connect with OR.

Tip: A criterion with <AND>/<OR> connections can be split into separate criterion rows via Split... (see chapter 8.10.2) - clearer as soon as more than two partial values come together. For a value with both separators, from version 2.3.0 on one row is created per <AND> part; the rows are connected with AND, and the <OR> alternatives stay in their row: Invoice<AND>2025<OR>2026 becomes the rows "Invoice" and "20252026". The program reads the rows exactly like the original value.

30.5.4 Note on the routing ID

The routing ID property corresponds to the invoice's buyer reference (BT-10) - on B2B invoices this often carries a general reference instead of a routing ID.