---
id: object/page/62
type: object
title: Page 62 "Applied Vendor Entries"
summary: Page 62 "Applied Vendor Entries" in Base Application (Microsoft.Purchases.Payables). 1 public procedures. 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: 113f215f24b4691ef13ec0ebab353b0054bba28a2acf1fc8e5681c5e73bcc7fd
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Purchases/Payables/AppliedVendorEntries.Page.al
    title: src/Layers/W1/BaseApp/Purchases/Payables/AppliedVendorEntries.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/payables-how-apply-purchase-transactions-manually
    title: Reconcile vendor payment receipts or refunds in the payment journal
    date: null
    commit: null
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/payables-how-apply-purchase-transactions-manually
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/finance/manage-payables
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 62
name: Applied Vendor Entries
namespace: Microsoft.Purchases.Payables
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:
  - docs/learn-smb-docs/business-central/payables-how-apply-purchase-transactions-manually.md
counts:
  fields: 0
  procedures: 3
  events: 0
  subscribers: 0
  controls: 20
  actions: 5
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 1
  implements: 0
---

# Page 62 "Applied Vendor Entries"

> Page 62 "Applied Vendor Entries" in Base Application (Microsoft.Purchases.Payables). 1 public procedures. Present since at least BC23, still in BC30.

Base Application · Microsoft.Purchases.Payables · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Purchases/Payables/AppliedVendorEntries.Page.al) · facts from BC29

## Properties

| Property | Value |
|---|---|
| Caption | Applied Vendor Entries |
| SourceTable | Vendor Ledger Entry |
| PageType | List |

## 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 |
|---|---|---|---|
| Control1 | Posting Date | [Posting Date](../table/25.md#fields) | Specifies the vendor entry's posting date. <small>from the table field</small> |
|  | Document Type | [Document Type](../table/25.md#fields) | Specifies the document type that the vendor entry belongs to. <small>from the table field</small> |
|  | Document No. | [Document No.](../table/25.md#fields) | Specifies the vendor entry's document number. <small>from the table field</small> |
|  | Description | [Description](../table/25.md#fields) | Specifies a description of the vendor entry. <small>from the table field</small> |
|  | External Document No. | [External Document No.](../table/25.md#fields) | Specifies a document number that refers to the customer's or vendor's numbering system. <small>from the table field</small> |
|  | Global Dimension 1 Code | [Global Dimension 1 Code](../table/25.md#fields) | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company's most important activities, are available on all cards, documents, reports, and lists. <small>from the table field</small> |
|  | Global Dimension 2 Code | [Global Dimension 2 Code](../table/25.md#fields) | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company's most important activities, are available on all cards, documents, reports, and lists. <small>from the table field</small> |
|  | Purchaser Code | [Purchaser Code](../table/25.md#fields) | Specifies which purchaser is assigned to the vendor. <small>from the table field</small> |
|  | Currency Code | [Currency Code](../table/25.md#fields) | Specifies the currency code for the amount on the line. <small>from the table field</small> |
|  | Original Amount | [Original Amount](../table/25.md#fields) | Specifies the amount of the original entry. <small>from the table field</small> |
|  | Amount | [Amount](../table/25.md#fields) | Specifies the amount of the entry. <small>from the table field</small> |
|  | Debit Amount | [Debit Amount](../table/25.md#fields) | Specifies the total of the ledger entries that represent debits. <small>from the table field</small> |
|  | Credit Amount | [Credit Amount](../table/25.md#fields) | Specifies the total of the ledger entries that represent credits. <small>from the table field</small> |
|  | Closed by Amount | [Closed by Amount](../table/25.md#fields) | Specifies the amount that the entry was finally applied to (closed) with. <small>from the table field</small> |
|  | Closed by Currency Code | [Closed by Currency Code](../table/25.md#fields) | Specifies the currency code of the entry that was applied to (and closed) this vendor ledger entry. <small>from the table field</small> |
|  | Closed by Currency Amount | [Closed by Currency Amount](../table/25.md#fields) | Specifies the amount that was finally applied to (and closed) this vendor ledger entry. <small>from the table field</small> |
|  | User ID | [User ID](../table/25.md#fields) | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. <small>from the table field</small> |
|  | Source Code | [Source Code](../table/25.md#fields) | Specifies the source code that specifies where the entry was created. <small>from the table field</small> |
|  | Reason Code | [Reason Code](../table/25.md#fields) | Specifies the reason code, a supplementary source code that enables you to trace the entry. <small>from the table field</small> |
|  | Entry No. | [Entry No.](../table/25.md#fields) | Specifies the number of the entry, as assigned from the specified number series when the entry was created. <small>from the table field</small> |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Entry | Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history. |  |
|  | Detailed Ledger Entries | View a summary of the all posted entries and adjustments related to a specific vendor ledger entry. | [Page 574 "Detailed Vendor Ledg. Entries"](../page/574.md) |
| Processing | Find entries... | Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.) |  |
|  | Show Posted Document | Show details for the posted payment, invoice, or credit memo. |  |
|  | Show Document Attachment | View documents or images that are attached to the posted invoice or credit memo. |  |

## Procedures

- `GetCreateVendorLedgerEntry(): Record "Vendor Ledger Entry"`

Plus 2 local procedures.

## Triggers

OnAfterGetCurrRecord, OnInit, OnOpenPage

## Relations

- source table [Table 25 "Vendor Ledger Entry"](../table/25.md)

## Called by

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 1313 "Correct Posted Purch. Invoice"](../codeunit/1313.md) (1 call: `ShowAppliedEntries → (object)`)

## Across versions

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

## Documented on Microsoft Learn

- [Reconcile vendor payment receipts or refunds in the payment journal](https://learn.microsoft.com/dynamics365/business-central/payables-how-apply-purchase-transactions-manually)

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: "Applied Vendor Entries")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.