---
id: object/page/1288
type: object
title: Page 1288 "Payment-to-Entry Match"
summary: Page 1288 "Payment-to-Entry Match" in Base Application (Microsoft.Bank.Reconciliation). Present since at least BC23, still in BC30.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: null
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 105205e89318b8775b2a2eaee23c23f9cf5cf87b7d3f1b299efd6fac7ca63ba6
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Bank/Reconciliation/PaymenttoEntryMatch.Page.al
    title: src/Layers/W1/BaseApp/Bank/Reconciliation/PaymenttoEntryMatch.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 1288
name: Payment-to-Entry Match
namespace: Microsoft.Bank.Reconciliation
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 2
  events: 0
  subscribers: 0
  controls: 7
  actions: 0
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 2
  called_by: 0
  implements: 0
---

# Page 1288 "Payment-to-Entry Match"

> Page 1288 "Payment-to-Entry Match" in Base Application (Microsoft.Bank.Reconciliation). Present since at least BC23, still in BC30.

Base Application · Microsoft.Bank.Reconciliation · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Bank/Reconciliation/PaymenttoEntryMatch.Page.al) · 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"](../table/1294.md)

## 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"](../codeunit/1255.md) (4 calls: `FetchData → MatchSingleLineBankAccountLedgerEntry`, `FetchData → MatchSingleLineCustomer`, `FetchData → MatchSingleLineEmployee`, …)
- [Codeunit 10 "Type Helper"](../codeunit/10.md) (1 call: `FetchData → GetOptionNo`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: none

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## 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.