xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Reconciliation Matching Rule — entity reference
REFERENCE · Last reviewed

Reconciliation Matching Rule — entity reference

One test in the cascade the Bank Reconciliation workspace runs when an unmatched bank statement line is opened. Rules run in Sequence order and each one keeps only the candidate ledger lines that pass it, so a suggestion must pass every rule; a rule that leaves no candidate means the line gets no suggestions. A rule with Auto Match on confirms a clear winner as soon as it has run and stops the cascade. Rules are created from the workspace's Matching rules tab and belong to the bank account selected there. An account's own rules replace rules that belong to no account. With no applicable rule, the built-in policy applies: amount within 100, date within five days, overlapping reference and the same direction, with no auto-match. Rules are read only when a line is opened, so changes never affect matches already confirmed.

Fields

FieldLabelTypeRequiredWhat it does
AmountToleranceAmount ToleranceDecimalThe largest difference allowed between the statement amount and the ledger amount. It is used only when the criterion is Amount. Zero means an exact match, and left empty it means 100, so enter a value on every Amount rule.
AutoMatchAuto MatchBooleanWhen on, the rule confirms a match by itself after it has run, if its survivors have a clear winner: a single candidate, or a top score strictly higher than the second. The match is recorded as automatic, the statement line becomes Matched and later rules do not run. Ties are never confirmed. Off by default and not on the New form; tick it on the rule's record page, normally only on the last rule of the cascade.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated OnDateAndTimeYes
DateToleranceDate ToleranceNumberThe largest gap, in whole days, allowed between the statement line's transaction date and the journal date. It is used only when the criterion is Date. Left empty, it means five days.
IdIdGuidYes
IsActiveIs ActiveBooleanWhether the rule runs. Switching it off pauses the rule without deleting it; the Matching rules tab shows it as Inactive. On by default.
MatchingCriteriaMatching CriteriaPickListThe test this rule applies. Amount compares the statement amount (deposit minus withdrawal) with the ledger amount (debit minus credit) within Amount Tolerance. Date compares the statement transaction date with the journal date within Date Tolerance. Reference requires the statement reference and the journal line narration to overlap, one containing the other, ignoring case. TransactionType requires the money to move the same way on both sides. The forms take one value per rule, so build combined tests from several rules. It defaults to Reference and is required. A document number test exists in the product but is switched off in the list of values. Values: Amount, Date, Reference, TransactionType.
MatchingTypeMatching TypePickListThe intended cardinality of a match, OneToOne or OneToMany. It is required and defaults to OneToOne, but matching does not read it: every confirmed match pairs one statement line with one ledger line. Values: OneToOne, OneToMany.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesThe rule's name, shown in the Matching rules tab of the Bank Reconciliation workspace.
OwnerIdOwnerLookup → UserAccountYesThe user who owns the rule record. It does not affect matching.
RecordTypeIdRecord TypeGuid, hidden
SequenceSequenceNumberPosition in the cascade: the lowest runs first, and each later rule only sees the candidates the earlier rules let through. Rules with no sequence run after every numbered rule.
SubscriptionKeySubscription KeyGuid, hiddenYes
UpdatedDateTimeUpdated OnDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteEntityDeleteDeleteDeleteEntity
DeleteRowDeleteDeleteDeleteRow
EditEditEditEdit
EditEntityEditEditEditEntity
EditInlineEditEditInlineEdit
EditRowEditEditEdit
NewInLineNewNewInlineNewInLine