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

Field	Operator(s)	Value(s)
currency	equals	Valid ISO 4217 Currency Code,`expected_payment.currency`
direction	equals	“credit”, “debit”, `expected_payment.direction`
internal_account_id	equals	Valid Internal Account UUID, `expected_payment.internal_account_id`
as_of_date	less_than_or_equals	`expected_payment.date_upper_bound`
as_of_date	greater_than_or_equals	`expected_payment.date_lower_bound`
type	equals	ach, wire, check, rtp, book, other `expected_payment.type`
vendor_description	equals, contains	Constant String (e.g. “hello”), Expected Payment custom identifiers (e.g. expected_payment.custom_identifiers.key)
details.path_to.key (alphanumeric characters or underscores)	equals	Constant 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.

Field	Operator(s)	Value(s)
type	equals	ach, book, check, eft, interac, rtp , sepa, wire, `expected_payment.type`
virtual_account.counterparty_id	equals	Valid Counterparty UUID, `expected_payment.counterparty_id`
data.lockbox_number	equals	Constant String (e.g. “hello”), custom identifiers (e.g. `expected_payment.custom_identifiers.[key]`)
data.check_number	equals	Constant String (e.g. “hello”), custom identifiers (e.g. `expected_payment.custom_identifiers.[key]`)
data.role	equals	Always "receiving"
data.payment_type	equals	Mirrors the Incoming Payment Detail type (e.g. ach, wire, rtp, stablecoin)
data.payment_subtype	equals	For ACH, this is the SEC code (e.g. CCD, PPD). For Stablecoins, this is either ethereum, solana or base
data.receiving_party_name	equals	The name of the party receiving the payment
data.statement_descriptor	equals	A free-form statement descriptor set by the originating bank or sender
data.message	equals	A message composed from the ACH addenda and description field (for ACH), or, a message composed from the originator-to-beneficiary information lines (for Stablecoin, Wire), or, a message composed from the remittance data and purpose fields (for RTP)
data.originating_party_name	equals	The name of the party that originated the payment. Only for ACH, Wire, RTP
data.originating_party_vendor_identifier	equals	A vendor-assigned identifier for the originating party. Only for ACH, Wire, RTP
data.originating_party_bank_name	equals	The name of the originating party's financial institution. Only for ACH, Wire, RTP
data.originating_routing_number	equals	The routing number of the originating party's bank. Only for ACH, Wire, RTP
data.originating_account_number	equals	The account number of the originating party. Only for ACH, Wire, RTP, Stablecoin
data.originating_account_number_type	equals	The type of the originating account number (e.g. iban, clabe, wallet_address). Only for ACH, Wire, RTP, Stablecoin
data.originating_routing_number_type	equals	The type of the originating routing number (e.g. aba, swift). Only for ACH, Wire, RTP
data.originating_party_address	equals	The address of the originating party. Only for ACH, Wire, RTP
data.crypto_tx_hash	equals	The on-chain transaction hash. Only for Stablecoin
data.path_to.key (alphanumeric characters or underscores)	equals	Constant String (e.g. “hello”), custom identifiers (e.g. `expected_payment.custom_identifiers.[key]`)

Expected Payment fields

Field	Operator(s)	Value(s)
currency	equals	Valid ISO 4217 Currency Code, `transaction.currency`
direction	equals	"credit", "debit", `transaction.direction`
internal_account_id	equals	Valid Internal Account UUID, `transaction.internal_account_id`
date_upper_bound	greater_than_or_equal	`transaction.as_of_date`
date_lower_bound	less_than_or_equal	`transaction.as_of_date`
type	equals	Any valid Payment Order type, `transaction.type`
counterparty_id	equals	Valid Counterparty UUID, `transaction.incoming_payment_detail.virtual_account.counterparty_id`
custom_identifiers.key	equals 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