Routing conditions

Admin+

Conditions decide which processed documents a routing rule applies to. Each rule evaluates its conditions against a document the moment processing finishes, and sends the email only when the conditions match.

Match all vs match any

Each rule groups its conditions into two sets:

• Match all. Every condition in this set must be true. This is a logical AND.
• Match any. At least one condition in this set must be true. This is a logical OR.

If you leave one set empty, it does not block the match. An empty match-all set counts as satisfied, and an empty match-any set counts as satisfied. A rule with no conditions at all matches every document, so add at least one condition to keep a rule targeted.

The eight condition fields

You can build conditions on these document fields:

• vendor.name: the vendor or supplier name.
• invoice.total: the document total amount.
• invoice.currency: the currency code, such as USD or EUR.
• invoice.status: the document status, such as open or paid.
• invoice.document_kind: the document type, such as invoice or receipt.
• tags: the tags applied to the document.
• email.from: the sender address of the email that carried the document.
• email.subject: the subject line of that email.

Operators

The operator you pick depends on the field:

• equals: the field matches the value exactly. Available on every field except tags.
• contains: the field includes the value as a substring. Useful for vendor.name, email.from, email.subject, and tags.
• greater than and less than: compare numbers. Use these on invoice.total to route by amount, for example everything above 500.

The rule builder shows more operators depending on the field type, such as "not equals", "starts with", "ends with", and "is empty".

Related

Ready to try this?

Inbox Ledger turns your inbox into clean accounting data. The free tier includes 10 credits, refilled every 30 days.

Start free