Sample Categorization Rules

This feature can support custom rules based on your use case. To help illustrate functionality, below are sample rules.

Rules shown here are for illustrative purposes only and your actual implementation may vary.

General Ledger Account Tagging

This sample rule tags general ledger codes on transactions as they are reconciled to streamline month-end book closes.

If the following conditions are met:

• Transaction Internal Account is Customer Revenue (*2450); AND
• Transaction direction is Credit

Apply metadata:

Treasury Codes

In this example, we apply metadata to a transaction with a specific description field. Treasury codes are often used to support downstream reporting.

If the following conditions are met:

• Transaction direction is Credit.

AND

• Transaction vendor_description contains "CREDIT_POS"

Apply metadata:

High-value payments

This sample rule flags transactions that require further work by a payment operations team, in this case, a high-priority counterparty.

If the following conditions are met:

• Reconciled Payment Order Counterparty is ACME Co; AND
• Transaction Amount is greater than $500.00; AND

Apply metadata: