Context rules

Use the Rules tab of a context in the Matcher module of Lerian Console to manage its match rules. The rules tell the match engine how to pair transactions across the two sides of the context.

Accessing the Rules tab

In the Matcher sidebar, go to Configure → Contexts.

Click the name of a context to open its page.

Select the Rules tab.

Rules list

The tab lists the match rules in priority order. Rules evaluate from top to bottom, and the first match wins. Each row shows the position number, the strategy badge, and a short summary of the configuration. A row can also show up and down arrows, an edit button, and a delete button. The module sets the priority of a new rule for you. The form has no priority field. To change the order, use the up and down arrows.

Creating a rule

On the Rules tab, click New rule. The New rule sheet opens.

Select a Strategy:

Strategy	Description
Exact	Field-for-field equality
Tolerance	Amount and date within a band
Date lag	Settlement delay window
Fuzzy	Approximate reference similarity

The fields of the strategy appear below it. See Rule types.

Optionally, click Advanced settings to show more fields.

Click Save.

You cannot change the strategy of a rule after you create it. To change it, delete the rule and create it again.

Matcher never confirms a match from a Fuzzy or a Date lag rule automatically. These rules propose matches for review.

Rule types

Exact

Matches transactions when the selected fields are equal. Top-level switches:

Field	Description
Match amount	Compare the amounts
Match currency	Require the same currency
Match date	Compare the dates
Match reference	Compare the references

Advanced settings adds:

Field	Description
Date precision	`DAY` or `TIMESTAMP`
Compare references ignoring case	Ignore letter case when you compare references
Reference must be present	When Match reference is on, refuse a pair if either reference is blank
Sign mode	`same` matches like signs. `opposite` matches a refund against its charge. `ignore` compares magnitudes only
Match base amount	Also match on the base amount, which is the amount converted to the base currency
Match base currency	Also match on the base currency
Allocation (1:N and N:1)	Partial allocation settings. See Allocation settings
Composite key fields	Extra named fields to match on, together with the switches above. Click Add key field to add one

Tolerance

Matches transactions when the amounts and dates are within a band. Top-level fields:

Field	Description
Absolute tolerance	The largest amount difference that still matches. The amount band uses the larger of this value and the percent tolerance
Percent tolerance	A fraction: `0.005` is 0.5%. The amount band uses the larger of this value and the absolute tolerance
Date window (days)	How many days apart the two sides can be dated, from 0 to 3650
Match currency	Require the same currency

Both tolerances start at 0. A value of 0 is valid.

Advanced settings adds:

Field	Description
Rounding mode	How amounts round before Matcher compares them: `HALF_UP`, `BANKERS`, `FLOOR`, `CEIL`, or `TRUNCATE`
Rounding scale	Decimal places for rounding, from 0 to 10
Percentage base	The amount that the percent tolerance applies to: `MAX`, `MIN`, `AVERAGE`, `LEFT`, or `RIGHT`
Match reference	Compare the references
Compare references ignoring case	Ignore letter case when you compare references
Reference must be present	When Match reference is on, refuse a pair if either reference is blank
Sign mode	`same`, `opposite`, or `ignore`, as for Exact
Match base amount	Apply the amount band to the base amounts, which are the amounts converted to the base currency
Match base currency	Also require the same base currency
FX variance band	Extra cross-currency tolerance as a fraction: `0.0025` is 25 basis points. A difference inside it still matches and opens an FX rate variance exception
Lockbox deduction band	How much a payment set can short-pay an invoice set in N:M matching, as a fraction of the invoice face: `0.05` is 5%. The shortfall stays open
Business days and timezone	The Holiday calendar and the Timezone for date comparison. The timezone starts at UTC
Allocation (1:N and N:1)	Partial allocation settings. See Allocation settings
Composite key fields	Extra named fields to match on, as for Exact

Date lag

Matches transactions that occur within a set number of days of each other. Top-level fields:

Field	Description
Min days	The smallest day lag that matches, from 0 to 3650. It starts at `0`
Max days	The largest day lag that matches, from 0 to 3650. It starts at `0`
Expected order	Which side you expect to have the earlier date: `ABS` (either side), `LEFT_BEFORE_RIGHT`, or `RIGHT_BEFORE_LEFT`
Include the min and max days	Include the boundary days in the lag window

Max days must be equal to or greater than Min days. If you turn off Include the min and max days, Min days must be more than 0.

Advanced settings adds:

Field	Description
Fee tolerance	The largest amount difference that still matches. It starts at `0`
Match currency	Require the same currency
Match reference	Off by default. Turn it on to require equal references
Compare references ignoring case	Ignore letter case when you compare references
Reference must be present	When Match reference is on, refuse a pair if either reference is blank
Business days and timezone	The Holiday calendar, the Timezone, and Count business days only. Count business days only measures the lag in business days and needs a calendar
Allocation (1:N and N:1)	Partial allocation settings. See Allocation settings

Fuzzy

Matches transactions by approximate reference similarity, with optional checks on amount, currency, and date. Top-level fields:

Field	Description
Minimum similarity	A ratio from 0 to 1: `0.80` is 80% similar. References below it never match. At or above it, Matcher grades the pair into a confidence score. See Confidence scoring. It starts at `0.80`
Match amount	Compare the amounts
Match currency	Require the same currency
Match date	Compare the dates

Advanced settings adds:

Field	Description
Date precision	`DAY` or `TIMESTAMP`
Reference must be present	On by default. Refuse a pair if either reference is blank
Sign mode	`same`, `opposite`, or `ignore`
Allocation (1:N and N:1)	Partial allocation settings. See Allocation settings

Allocation settings

Each strategy has an Allocation (1:N and N:1) block in Advanced settings:

Field	Description
Allow partial allocation	Split one amount across several counterparts. A remainder stays open as an open item
Fee-aware split	Allocate the gross share of each leg (net plus fee) instead of its net amount
Allocation direction	`LEFT_TO_RIGHT` or `RIGHT_TO_LEFT`
Allocation tolerance mode	`ABS` or `PERCENT`
Allocation tolerance	The remainder that a split can leave: an amount in `ABS` mode, or a fraction in `PERCENT` mode (`0.01` is 1%)
Allocate on the base amount	Turn it on to allocate on the base amount, which is the amount converted to the base currency. On Exact and Tolerance rules, Matcher then also matches on the base amount and the base currency

Previewing a rule

On an Active context, the rule sheet also shows a Preview matches panel. Use it to test the rule before you save it.

Fill in the rule fields.

In Preview matches, click Run preview.

The panel shows how many pairs Would match, the Unmatched left and Unmatched right counts, and up to 25 would-match pairs. The preview forms 1:1 pairs only. It does not apply fee normalization, FX variance bands, or allocation, so a live run can match more. The preview saves nothing. When you change a field, run the preview again.

Editing a rule

Click the edit button on a rule. The Edit rule sheet opens. The Strategy field stays locked. Change the other fields and click Save.

Reordering rules

Use the up and down arrows on a row to move the rule. Rules evaluate from top to bottom, and the first match wins.

Deleting a rule

Click the delete button on a rule. A dialog names the rule type and its priority and asks you to confirm. Click Confirm. The other rules keep their order.

Overview

Guides

Console

MCP Server

Operations

Accessing the Rules tab

Rules list

Creating a rule

Rule types

Exact

Tolerance

Date lag

Fuzzy

Allocation settings

Previewing a rule

Editing a rule

Reordering rules

Deleting a rule

​Accessing the Rules tab

​Rules list

​Creating a rule

​Rule types

​Exact

​Tolerance

​Date lag

​Fuzzy

​Allocation settings

​Previewing a rule

​Editing a rule

​Reordering rules

​Deleting a rule

Accessing the Rules tab

Rules list

Creating a rule

Rule types

Exact

Tolerance

Date lag

Fuzzy

Allocation settings

Previewing a rule

Editing a rule

Reordering rules

Deleting a rule