Page 29 "Vendor Ledger Entries"

Base Application · Microsoft.Purchases.Payables · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Vendor Ledger Entries
SourceTable	Vendor Ledger Entry
PageType	List
UsageCategory	History
ApplicationArea	Basic, Suite
Permissions	TableData “Vendor Ledger Entry” = m

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	Specifies the vendor entry’s posting date. from the table field
	Document Date	Document Date	Specifies the vendor entry’s document date. from the table field
	Invoice Received Date	Invoice Received Date	Specifies the date when the vendor’s invoice was received. from the table field
	Document Type	Document Type	Specifies the document type that the vendor entry belongs to. from the table field
	Document No.	Document No.	Specifies the vendor entry’s document number. from the table field
	External Document No.	External Document No.	Specifies a document number that refers to the customer’s or vendor’s numbering system. from the table field
	Vendor No.	Vendor No.	Specifies the number of the vendor account that the entry is linked to. from the table field
	Vendor Name	Vendor Name	Specifies the name of the vendor account that the entry is linked to. from the table field
	Message to Recipient	Message to Recipient	Specifies the message exported to the payment file when you use the Export Payments to File function in the Payment Journal window. from the table field
	Description	Description	Specifies a description of the vendor entry. from the table field
	Global Dimension 1 Code	Global Dimension 1 Code	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. from the table field
	Global Dimension 2 Code	Global Dimension 2 Code	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. from the table field
	Vendor Posting Group	Vendor Posting Group	Specifies the vendor’s market type to link business transactions made for the vendor with the appropriate account in the general ledger.
	IC Partner Code	IC Partner Code	Specifies the code of the intercompany partner that the transaction is related to if the entry was created from an intercompany transaction. from the table field
	Purchaser Code	Purchaser Code	Specifies which purchaser is assigned to the vendor. from the table field
	Currency Code	Currency Code	Specifies the currency code for the amount on the line. from the table field
	Payment Method Code	Payment Method Code	Specifies how to make payment, such as with bank transfer, cash, or check. from the table field
	Payment Reference	Payment Reference	Specifies the payment of the purchase invoice. from the table field
	Creditor No.	Creditor No.	Specifies the vendor who sent the purchase invoice. from the table field
	Original Amount	Original Amount	Specifies the amount of the original entry. from the table field
	Original Amt. (LCY)	Original Amt. (LCY)	Specifies the amount that the entry originally consisted of, in LCY.
	Amount	Amount	Specifies the amount of the entry. from the table field
	Amount (LCY)	Amount (LCY)	Specifies the amount of the entry in LCY.
	Debit Amount	Debit Amount	Specifies the total of the ledger entries that represent debits. from the table field
	Debit Amount (LCY)	Debit Amount (LCY)	Specifies the total of the ledger entries that represent debits, expressed in LCY.
	Credit Amount	Credit Amount	Specifies the total of the ledger entries that represent credits. from the table field
	Credit Amount (LCY)	Credit Amount (LCY)	Specifies the total of the ledger entries that represent credits, expressed in LCY.
	Running Balance (LCY)	`CalcRunningVendBalance.GetVendorBalanceLCY(Rec)`	Specifies the running balance in LCY.
	Remaining Amount	Remaining Amount	Specifies the amount that remains to be applied to before the entry is totally applied to. from the table field
	Remaining Amt. (LCY)	Remaining Amt. (LCY)	Specifies the amount that remains to be applied to before the entry is totally applied to.
	Bal. Account Type	Bal. Account Type	Specifies the type of account that a balancing entry is posted to, such as BANK for a cash account. from the table field
	Bal. Account No.	Bal. Account No.	Specifies the number of the general ledger, customer, vendor, or bank account that the balancing entry is posted to, such as a cash account for cash purchases. from the table field
	Due Date	Due Date	Specifies the due date on the entry. from the table field
	Pmt. Discount Date	Pmt. Discount Date	Specifies the date on which the amount in the entry must be paid for a payment discount to be granted. from the table field
	Pmt. Disc. Tolerance Date	Pmt. Disc. Tolerance Date	Specifies the latest date the amount in the entry must be paid in order for payment discount tolerance to be granted. from the table field
	Original Pmt. Disc. Possible	Original Pmt. Disc. Possible	Specifies the discount that you can obtain if the entry is applied to before the payment discount date. from the table field
	Remaining Pmt. Disc. Possible	Remaining Pmt. Disc. Possible	Specifies the remaining payment discount which can be received if the payment is made before the payment discount date. from the table field
	Max. Payment Tolerance	Max. Payment Tolerance	Specifies the maximum tolerated amount the entry can differ from the amount on the invoice or credit memo. from the table field
	Open	Open	Specifies whether the amount on the entry has been fully paid or there is still a remaining amount that must be applied to. from the table field
	Dispute Status	Dispute Status	Specifies if there is an ongoing dispute for this document. from the table field
	On Hold	On Hold	Specifies that the related entry represents an unpaid invoice for which either a payment suggestion, a reminder, or a finance charge memo exists. from the table field
	User ID	User ID	Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field
	Source Code	Source Code	Specifies the source code that specifies where the entry was created. from the table field
	Reason Code	Reason Code	Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field
	Reversed	Reversed	Specifies if the entry has been part of a reverse transaction. from the table field
	Reversed by Entry No.	Reversed by Entry No.	Specifies the number of the correcting entry that replaced the original entry in the reverse transaction. from the table field
	Reversed Entry No.	Reversed Entry No.	Specifies the number of the original entry that was undone by the reverse transaction. from the table field
	Entry No.	Entry No.	Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field
	G/L Register No.	G/L Register No.	Specifies the G/L register number that groups related G/L entries from the same posting. from the table field
	Transaction No.	Transaction No.	Specifies the transaction number that groups related G/L entries from the same posting. from the table field
	Exported to Payment File	Exported to Payment File	Specifies that the entry was created as a result of exporting a payment journal line. from the table field
	Dimension Set ID	Dimension Set ID	Specifies a reference to a combination of dimension values. The actual values are stored in the Dimension Set Entry table. from the table field
	RecipientBankAcc	Recipient Bank Account	Specifies the bank account to transfer the amount to. from the table field
	Shortcut Dimension 3 Code	Shortcut Dimension 3 Code	Specifies the code for Shortcut Dimension 3, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 4 Code	Shortcut Dimension 4 Code	Specifies the code for Shortcut Dimension 4, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 5 Code	Shortcut Dimension 5 Code	Specifies the code for Shortcut Dimension 5, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 6 Code	Shortcut Dimension 6 Code	Specifies the code for Shortcut Dimension 6, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 7 Code	Shortcut Dimension 7 Code	Specifies the code for Shortcut Dimension 7, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 8 Code	Shortcut Dimension 8 Code	Specifies the code for Shortcut Dimension 8, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Closed at Date	Closed at Date	Specifies the date at which the vendor ledger entry was closed. from the table field
	Remit-to Code	Remit-to Code	Specifies the address for the remit-to code. from the table field
FactBoxes	IncomingDocAttachFactBox	part Page 193 “Incoming Doc. Attach. FactBox”	—
	Related G/L Entries	part Page 19 “G/L Entries Part”	—

Actions

Group	Action	ToolTip	Runs
Entry	Applied Entries	View the ledger entries that have been applied to this record.	Page 62 “Applied Vendor Entries”
	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.
	Set Dimension Filter	Limit the entries according to the dimension filters that you specify. NOTE: If you use a high number of dimension combinations, this function may not work and can result in a message that the SQL server only supports a maximum of 2100 parameters.
	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”
Functions	Apply Entries	Select one or more ledger entries that you want to apply this record to so that the related posted documents are closed as paid or refunded.
	Unapply Entries	Unselect one or more ledger entries that you want to unapply this record.
	Reverse Transaction	Reverse an erroneous vendor ledger entry.
	Send Remittance Advice	Send the remittance advice before posting a payment journal or after posting a payment. The advice contains vendor invoice numbers, which helps vendors to perform reconciliations.
Incoming Document	View Incoming Document	View any incoming document records and file attachments that exist for the entry or document.
	Select Incoming Document	Select an incoming document record and file attachment that you want to link to the entry or document.
	Create Incoming Document from File	Create an incoming document record by selecting a file to attach, and then link the incoming document record to the entry or document.
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 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.
	Create Payment	Create a payment journal based on the selected invoices.
	Show Change History	View the history of changes for this entry.

Procedures

5 local procedures, no public ones.

Triggers

OnAfterGetCurrRecord, OnAfterGetRecord, OnInit, OnModifyRecord, OnOpenPage

Relations

source table Table 25 “Vendor Ledger Entry”

Pages and codeunits on this table

Table 25 “Vendor Ledger Entry” (drill-down page)
Table 25 “Vendor Ledger Entry” (lookup page)

Extended by

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 113 “Vend. Entry-Edit” (1 call: OnModifyRecord → (object))
Codeunit 408 “DimensionManagement” (1 call: SetDimVisibility → UseShortcutDims)

Called by

Codeunit 4010 “CalculateAmounts” (2 calls: DrillDownNumOfPurchInvoicesDueThisWeek → (object), DrillDownNumOfPurchInvoicesOverDue → (object))
Codeunit 1311 “Activities Mgt.” (1 call: DrillDownOverduePurchaseInvoiceAmount → (object))
Codeunit 1390 “Document Notifications” (1 call: ShowVendorLedgerEntry → (object))
Codeunit 14 “Gen. Jnl.-Show Entries” (1 call: OnRun → (object))
Codeunit 237 “G/L Reg.-Vend.Ledger” (1 call: OnRun → (object))
Codeunit 764 “Aged Acc. Payable” (1 call: DrillDownVendLedgEntries → (object))
Table 1692 “Posted Bank Deposit Line” (1 call: ShowAccountLedgerEntries → (object))
Table 274 “Bank Acc. Reconciliation Line” (1 call: DrillDownOnNoOfLedgerEntriesBasedOnAmount → (object))

Recent changes

2026-08-16 #9067 Production Definition Wizard - Implementation (main, BC30, feature)
2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature)

Countries that replace it

AU, NZ, RU

Documented on Microsoft Learn

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