Table 1252 "Bank Pmt. Appl. Rule"
Base Application · Microsoft.Bank.Reconciliation
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC262 procedures added, 1 events added
- BC272 events added
- BC288 fields changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Bank.Reconciliation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Bank Pmt. Appl. Rule |
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Match Confidence Δ BC28 | Option | Specifies your confidence in the application rule that you defined by the values in the Related Party Matched, Doc. No./Ext. Doc. No. Matched, and Amount Incl. Tolerance Matched fields on the line in the Payment Application Rules window. | OptionCaption: None,Low,Medium,High |
| 2 | Priority Δ BC28 | Integer | Specifies the priority of the application rule in relation to other application rules that are defined as lines in the Payment Application Rules window. 1 represents the highest priority. | |
| 3 | Related Party Matched Δ BC28 | Option | Specifies how much information on the payment reconciliation journal line must match the open entry before the application rule will apply the payment to the open entry. | OptionCaption: Not Considered,Fully,Partially,No |
| 4 | Doc. No./Ext. Doc. No. Matched Δ BC28 | Option | Specifies if text on the payment reconciliation journal line must match with the value in the Document No. field or the External Document No. field on the open entry before the application rule will be used to automatically apply the payment to the open entry. | OptionCaption: Not Considered,Yes,No,Yes - Multiple |
| 5 | Amount Incl. Tolerance Matched Δ BC28 | Option | Specifies how many entries must match the amount including payment tolerance, before the application rule will be used to apply a payment to the open entry. | OptionCaption: Not Considered,One Match,Multiple Matches,No Matches |
| 6 | Direct Debit Collect. Matched Δ BC28 | Option | Specifies if the Transaction ID value on the payment reconciliation journal line must match with the value in the related Transaction ID field in the Direct Debit Collect. Entries window. | OptionCaption: Not Considered,Yes,No |
| 30 | Score | Integer | — | not editable |
| 40 | Review Required Δ BC28 | Boolean | Specifies if bank statement lines matched with this rule will be shown as recommended for review. | |
| 41 | Apply Immediatelly Δ BC28 | Boolean | Specifies whether to search for alternative ledger entries that this line can be applied to. If turned on, the value is applied to the first match and alternative ledger entries are not considered. |
Keys
- Key1: Match Confidence, Priority (clustered)
- Key2: Score
Events published
OnBeforeValidatePriority(var BankPmtApplRule: Record "Bank Pmt. Appl. Rule"; var IsHandled: Boolean)+ BC26 (integration)OnInsertDefaultMatchingRulesBeforeInsertHighConfidenceRules(var BankPmtApplRule: Record "Bank Pmt. Appl. Rule"; var RulePriority: Integer)+ BC27 (integration)OnGetBestMatchScoreOnAfterSetFilters(var BankPmtApplRule: Record "Bank Pmt. Appl. Rule"; ParameterBankPmtApplRule: Record "Bank Pmt. Appl. Rule")+ BC27 (integration)
Procedures
LoadRules(): Loads all payment application rules into the current temporary record. Used for efficient processing of multiple rules during payment matching operations. Must be called on temporary table instances for performance optimization.GetBestMatchScore(ParameterBankPmtApplRule: Record "Bank Pmt. Appl. Rule"): Integer: Determines the best matching score for given payment application criteria. Evaluates all applicable rules based on the provided matching parameters and returns the highest score achievable, enabling optimal rule selection for payment matching.GetReviewRequiredScoreFilter(): TextIsMatchedAutomatically(MatchConfidence: Option; NoOfAppliedEntries: Integer): BooleanGetTextMapperScore(): Integer+ BC26GetMaxTextMapperScore(): Integer+ BC26GetTextMapperScore(SubstringLength: Integer; ExactMatch: Boolean): Integer+ BC26 (internal)GetMatchConfidence(MatchQuality: Integer): IntegerGetLowestScoreInRange(AssignedScore: Integer): IntegerGetHighestScoreInRange(AssignedScore: Integer): IntegerGetHighestPossibleScore(): IntegerInsertDefaultMatchingRules()
Plus 5 local procedures.
Triggers
OnInsert, OnRename
Pages and codeunits on this table
- Page 1252 “Payment Application Rules” (source table)
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 46 “SelectionFilterManagement” (1 call:
GetReviewRequiredScoreFilter → GetSelectionFilter)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Bank Pmt. Appl. Rule"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.