You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Best Practices for designing Transaction Matching Match Types and its components

edited Sep 5, 2025 4:07PM in Account Reconciliation 1 comment

Summary:

Best Practices for designing Transaction Matching Match Types and its components as to prevent reaching or exceeding governor limits

Increase ARCS Governor Limits

Content (please ensure you mask any confidential information):

Hello, we are facing redesigning our current TM configuration in the past 2 years or longer due to a governor limit of 500 matching rules per match process.

Due to the complexity of one particular French client in the insurance business, we have many business flows, filters and attributes.

For this client, we currently have 2 match types, one for clearing accounts with a data source of GL and the other for bank statements with 2 data sources GL and Bank Statements. Each data source has many filters and attributes. Each of these match types has one match process referring to these data sources. Each of these match processes also has many matching rules referring to these filters and their attributes used in conditions. However, due to the governor limit of 500 per match process, we are facing having to split our clearing account match type by filters into

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!