70.2 CSV Mapping and Lookup Tables
70.2.1 Concept ¶
A lookup table translates an invoice value into a target value - e.g.:
| Supplier (match column) |
Vendor number (result column) |
| Sample Office Supplies Ltd |
70001 |
| Baker IT Services LLC |
70002 |
The corresponding placeholder (inserted via Insert placeholder ▼ → Lookup tables) returns at runtime the result value of the row whose match column fits the invoice value. This enables, among others:
- Target folder per supplier: directory
C:\Invoices\<mapping> - each invoice ends up in its supplier's folder
- DATEV account mapping: the personal account of the DATEV task from seller → vendor number (see chapter 14.3)
- Clerk routing: email sending with a recipient per supplier (alternatively: the CSV recipient list of the send task, see chapter 17.3)
70.2.2 Matching and options ¶
Configurable per lookup table (management: see chapter 40.12):
- Matched via: which invoice/file value serves as the key (selected via the placeholder menu, e.g. "Invoice issuer: Company" or "Customer number") and against which column it is compared - as exact match, "contains", or regular expression; multiple conditions (AND-combined) are possible as well
- Result column: which column provides the target value
- Advanced: ignore case, "Replace result with", allow empty results, and the processing status on a missing match (No match or Error)
You maintain the entries directly in the editor or import them from a CSV file - hence the name CSV mapping.
70.2.3 Global placeholders ¶
For fixed name-value pairs without table logic, there are additionally the global placeholders (see chapter 40.13) - e.g. a central filing path referenced in many profiles and changed in one place when needed.
70.2.4 Behavior on a missing match ¶
If the mapping finds no match, the replacement value comes first: if "Replace result with" is set under Advanced, it is used and the task runs normally. Without a replacement value, the table option Processing status when no match is found decides: the task is not executed and receives the status Error (default - the invoice appears in the Errors tab, the following tasks are skipped) or No match (the following tasks continue). The log message names the table and the matching values, for example "Lookup table "Cost centers": no match for = "Example Ltd"". Processing thus stays controllable even for unknown suppliers.