Valid conditions for Reconciliation Rules

You can add a variety of conditions with different fields, operators, and values when creating Reconciliation Rules. The flexibility enables you to reconcile a variety of real-world behaviors accurately and automatically.

The table below lists the valid operators and values for each field type.

Transactions fields

FieldOperator(s)Value(s)
currencyequalsValid ISO 4217 Currency Code,expected_payment.currency
directionequals“credit”, “debit”, expected_payment.direction
internal_account_idequalsValid Internal Account UUID, expecteed_payment.internal_account_id
as_of_dateless_than_or_equalsexpected_payment.date_upper_bound
as_of_dategreater_than_or_equalsexpected_payment.date_lower_bound
typeequalsach, wire, check, rtp, book, sen, other
expected_payment.type
vendor_descriptionequals, containsConstant String (e.g. “hello”), Expected Payment custom identifiers (e.g. expected_payment.custom_identifiers.key)
details.path_to.key (alphanumeric characters or underscores)equalsConstant String (e.g. “hello”), custom identifiers (e.g. expected_payment.custom_identifiers.[key])

Incoming Payment Details fields

Incoming Payment Details fields can also be used in place of transaction fields. This reconciles the Expected Payment to the same transaction that is linked to the Incoming Payment Detail.

FieldOperator(s)Value(s)
typeequalsach, book, check, eft, interac, rtp , sepa, signet, wire, expected_payment.type
virtual_account.counterparty_idequalsValid Counterparty UUID, expected_payment.counterparty_id
data.lockbox_numberequalsConstant String (e.g. “hello”), custom identifiers (e.g. expected_payment.custom_identifiers.[key])
data.check_numberequalsConstant String (e.g. “hello”), custom identifiers (e.g. expected_payment.custom_identifiers.[key])
details.path_to.key (alphanumeric characters or underscores)equalsConstant String (e.g. “hello”), custom identifiers (e.g. expected_payment.custom_identifiers.[key])

Expected Payment fields

FieldOperator(s)Value(s)
currencyequalsValid ISO 4217 Currency Code, transaction.currency
directionequals"credit", "debit", transaction.direction
internal_account_idequalsValid Internal Account UUID, transaction.internal_account_id
date_upper_boundgreater_than_or_equaltransaction.as_of_date
date_lower_boundless_than_or_equaltransaction.as_of_date
typeequalsAny valid Payment Order type,
transaction.type
counterparty_idequalsValid Counterparty UUID, transaction.incoming_payment_detail.virtual_account.counterparty_id
custom_identifiers.keyequals
contains
Constant String (e.g. hello), transaction.vendor_description, transaction.details.path_to.key, transaction.incoming_payment_detail.data.path_to.key,
transaction.paper_item.lockbox_number, transaction.paper_item.check_numb

Note: paths can only contain alphanumeric characters and underscores