With transaction categorization, you can systematically apply metadata to transactions using categorization rules. Rules apply when transactions are created or upon reconciliation and are maintained directly in the web app.

📘

Early Access Feature

This feature is in early access. Any organization can use this feature. If you have questions about its functionality or need support setting up categorization rules, please reach out to [email protected] or your customer success manager.

Use Cases

Metadata fields in Transactions can hold helpful business data for a myriad of use cases:

• Accounting Workflows: streamline data transformation by applying relevant data such as GL account codes to metadata;
• Financial Operations & Controls: classify financial transactions granularly to analyze bank fees, revenue actuals, or interest.
• Payment Operations: apply metadata tags based on bespoke workflows, such as marking a transaction as high value or from an important counterparty.

Metadata fields are included in reports, Push to Warehouse exports, and can be used to filter data in the web application.

Overview

To enrich transactions, users need to perform two steps; listed below:

1. Set up valid metadata keys to be used for categorization. For more information on this step refer to Metadata Allow-List;
2. Create and activate categorization rules. For more information on this step refer to Categorization Rules.

Permissions

Metadata keys, values, and categorization rules are discrete elements within our roles and permissions framework.

Similar to Reconciliation Rules, users in the "Finance Manager" role and "Finance Controls" permission set have access to this feature as a default. For more information on managing access to these resources, refer to our documentation on Roles & Permissions.