Chained Automation (i.e. Assigned Vendor + Chart of Accounts)
Mapping rules are evaluated top-to-bottom and left-to-right, enabling chained logic. Here, an incoming invoice matching the Vendor Display Name "Microsoft" and its Bill-To Address is first resolved to LinkedIn as the assigned vendor - which then triggers a subsequent rule to automatically assign the Services GL account.
.png)
Custom Formula
When a direct field assignment isn't sufficient, mapping values support a {{ }} template syntax. This allows you to read from any accessible field on the invoice, apply transformations, and write the result to your target field - covering calculations, string manipulation, date logic, and more. The full list of accessible fields and available functions is discoverable directly in the input.
Type
#inside a template expression to see all accessible fields.Type
/to see all available functions.
Remove “#” From Invoice Number Extraction
Suppose your vendor sends bills with a “#” prefix to the Invoice Number. This prefix can be removed from the extraction under the Invoice Number tab by entering the following formula.
.png)
Train Invoice Date to the Statement Date
Some vendors calculate due dates from a fixed monthly statement date rather than the invoice date. This mapping shifts the invoice date to the 28th of its month, ensuring due date calculations downstream are based on the correct reference date rather than the raw invoice date.
.png)