Page 1288 "Payment-to-Entry Match"

Base Application · Microsoft.Bank.Reconciliation · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Payment-to-Entry Match
SourceTable	Applied Payment Entry
PageType	CardPart

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Control6	Match Confidence	`BankPmtApplRule."Match Confidence"`	Specifies the quality of the match between the payment and the open entry for payment purposes.
	Related Party Matched	`BankPmtApplRule."Related Party Matched"`	Specifies how much information on the payment reconciliation journal line must match with the open entry before a payment is automatically applied.
	Document No./Ext. Document No. Matched	`BankPmtApplRule."Doc. No./Ext. Doc. No. Matched"`	Specifies if text must match with the field on the open entry before the application rule will be used to automatically apply the payment.
	Amount Incl. Tolerance Matched:	`AmountMatchText`	Specifies how many entries must match the amount, including payment tolerance, before a payment is automatically applied to the open entry.
	No. of Open Entries for	`BankAccReconciliationLine.GetAppliedEntryAccountName(Rec."Applies-to Entry No.")`	Specifies the number of open entries for the customer or vendor.
	Within Amount Tolerance	`NoOfLedgerEntriesWithinAmountTolerance`	Specifies the number of open entries where the payment amount is within the payment tolerance of the amount.
	Outside Amount Tolerance	`NoOfLedgerEntriesOutsideAmountTolerance`	Specifies the number of open entries where the payment amount is outside of the payment tolerance amount.

Procedures

2 local procedures, no public ones.

Triggers

OnAfterGetCurrRecord

Relations

source table Table 1294 “Applied Payment Entry”

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 1255 “Match Bank Payments” (4 calls: FetchData → MatchSingleLineBankAccountLedgerEntry, FetchData → MatchSingleLineCustomer, FetchData → MatchSingleLineEmployee, …)
Codeunit 10 “Type Helper” (1 call: FetchData → GetOptionNo)

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: "page", object_name: "Payment-to-Entry Match"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.