A configurable gate that narrows which posted ledger lines may be paired with a bank statement line. Rules run as a cascade in sequence order — the first filters the candidate ledger lines, the next filters that rule's survivors, and so on — so a candidate must satisfy every rule, and a rule that eliminates all remaining candidates fails the statement line outright. Rules scoped to one bank account take precedence over rules left global, and when no active rule applies the engine falls back to a built-in policy that requires amount within 100, date within 5 days, reference overlap and matching direction, with auto-match off.
Fields
| Field | Label | Type | Required | What it does |
|---|
AmountTolerance | Amount Tolerance | Decimal | | Maximum absolute difference between the statement line's signed amount and the ledger line's debit-minus-credit, applied only when the Amount criterion is selected. Zero means an exact match; left empty it falls back to a permissive built-in default of 100, which is rarely what an author intends. |
AutoMatch | Auto Match | Boolean | | When on, this rule confirms the match itself as soon as its survivors have an unambiguous winner — a single survivor, or a top candidate that strictly outscores the runner-up — writing the reconciliation match, flipping the statement line to Matched and short-circuiting the rest of the cascade without asking anyone. Ranking is by date proximity plus a bonus for reference overlap, so an exact tie is left for manual confirmation. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created On | DateAndTime | Yes | |
DateTolerance | Date Tolerance | Number | | Maximum whole days between the statement line's transaction date and the journal's date, applied only when the Date criterion is selected. Left empty it falls back to the built-in default of five days. |
Id | Id | Guid | Yes | |
IsActive | Is Active | Boolean | | |
MatchingCriteria | Matching Criteria | PickList | | A comma-separated subset of Amount, Date, Reference, TransactionType and DocumentNumber. Every selected criterion is a hard gate a candidate ledger line must pass, not a weighting: TransactionType requires the statement line's signed amount and the ledger line's debit-minus-credit to share the same sign, and DocumentNumber compares the statement reference against the journal's voucher name. At least one criterion is mandatory at save time, and a rule that somehow ends up with none is skipped by the engine. Values: Amount, Date, Reference, TransactionType. |
MatchingType | Matching Type | PickList | | It is nonetheless mandatory at save time, and only OneToOne and OneToMany are seeded in the picklist even though the underlying vocabulary also defines ManyToOne and ManyToMany. Values: OneToOne, OneToMany. |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Name | Text | Yes | |
OwnerId | Owner | Lookup → UserAccount | Yes | |
RecordTypeId | Record Type | Guid, hidden | | |
Sequence | Sequence | Number | | Position in the cascade, lowest running first: rule one filters the candidate ledger lines and each later rule filters the previous rule's survivors, so the ordering decides which candidates ever reach the later gates. Rules with no sequence sort last. |
SubscriptionKey | Subscription Key | Guid, hidden | Yes | |
UpdatedDateTime | Updated On | DateAndTime | Yes | |
Actions
| Action | Label | Type | What it does |
|---|
Clone | Clone | ServerAction (Clone) | Create a copy of this record |
Delete | Delete | Delete | Delete |
DeleteEntity | Delete | Delete | DeleteEntity |
DeleteRow | Delete | Delete | DeleteRow |
Edit | Edit | Edit | Edit |
EditEntity | Edit | Edit | EditEntity |
EditInline | Edit | EditInline | Edit |
EditRow | Edit | Edit | Edit |
NewInLine | New | NewInline | NewInLine |
