Table 271 "Bank Account Ledger Entry"

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

Learn documents this table through its pages: Page 165 “Bank Acc. Ledg. Entr. Preview” (1 Learn page), Page 372 “Bank Account Ledger Entries” (1).

Properties

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.

Keys

• Key1: Entry No. (clustered)
• Key2: Bank Account No., Posting Date
• Key3: Bank Account No., Open, Posting Date, Statement No., Statement Status, Statement Line No.
• Key4: Document Type, Bank Account No., Posting Date
• Key5: Document No., Posting Date
• Key6: Transaction No.
• Key7: Bank Account No., Global Dimension 1 Code, Global Dimension 2 Code, Posting Date
• key8: Statement No., Statement Line No.
• Key13: Bank Account No., Posting Date, Statement No., Closed at Date, Statement Status, Reversed, Open

Events published

• OnAfterCopyFromGenJnlLine(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry"; GenJournalLine: Record "Gen. Journal Line") (integration): Integration event raised after copying field values from a general journal line. Allows subscribers to customize or extend the field transfer process.
• OnAfterUpdateDebitCredit(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry"; Correction: Boolean) (integration): Integration event raised after updating debit and credit amount fields. Allows subscribers to customize debit/credit calculation logic or add additional processing.
• OnAfterSetBankReconciliationCandidatesFilter(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry") (integration): Integration event raised after setting filters for bank reconciliation candidates. Allows subscribers to modify or extend the filtering criteria for reconciliation matching.

Trigger event subscribers

• OnAfterInsertEvent: Codeunit 20 “Posting Preview Event Handler” OnInsertBankAccountLedgerEntry
• OnAfterModifyEvent: Codeunit 20 “Posting Preview Event Handler” OnModifyBankAccountLedgerEntry

Procedures

• ShowDimensions(): Opens the dimension management page to display dimensions associated with this entry.
• CopyFromGenJnlLine(GenJnlLine: Record "Gen. Journal Line"): Copies field values from a general journal line to populate this bank account ledger entry. Transfers standard fields and dimensions, then raises integration event for customization.
• UpdateDebitCredit(Correction: Boolean): Updates the debit and credit amount fields based on the transaction amount and correction flag. Positive amounts become debits, negative amounts become credits, with correction logic applied.
• GetAppliedStatementNo(): Code[20]: Retrieves the statement number associated with this entry if it has been applied to a bank statement. Checks for applied check entries or direct bank account entry application status.
• IsApplied(): Boolean: Determines whether this bank account ledger entry has been applied to a bank statement.
• SetStyle(): Text: Determines the visual style to apply to this entry in list displays. Applied entries receive favorable styling to indicate their reconciled status.
• SetFilterBankAccNoOpen(BankAccNo: Code[20]): Applies filters to show only open entries for a specific bank account. Resets all existing filters and sets up optimized key and filtering for open entry retrieval.
• CopyFromBankAccLedgerEntry(BankAccountLedgerEntry: Record "Bank Account Ledger Entry"; StatementNo: Code[20]): Creates a new bank account ledger entry by copying key fields from an existing entry. Used for creating related entries with specific statement association during reconciliation processes.
• SetBankReconciliationCandidatesFilter(BankAccReconciliation: Record "Bank Acc. Reconciliation"): Sets filters on the record to find potential candidates for bank reconciliation matching. Filters for open, non-reversed entries with remaining amounts within the reconciliation date range.

Plus 2 local procedures.

Triggers

OnInsert

Relations

• drill-down page Page 372 “Bank Account Ledger Entries”
• lookup page Page 372 “Bank Account Ledger Entries”
• Our Contact Code: TableRelation Table 13 “Salesperson/Purchaser”
• Bal. Account No.: TableRelation Table 15 “G/L Account” (conditional)
• Bal. Account No.: TableRelation Table 18 “Customer” (conditional)
• Bal. Account No.: TableRelation Table 23 “Vendor” (conditional)
• Source Code: TableRelation Table 230 “Source Code”
• Reason Code: TableRelation Table 231 “Reason Code”
• Bal. Account No.: TableRelation Table 270 “Bank Account” (conditional)
• Bank Account No.: TableRelation Table 270 “Bank Account”
• Closed by Entry No.: TableRelation Table 271 “Bank Account Ledger Entry”
• Reversed by Entry No.: TableRelation Table 271 “Bank Account Ledger Entry”
• Reversed Entry No.: TableRelation Table 271 “Bank Account Ledger Entry”
• Check Ledger Entries: CalcFormula Table 272 “Check Ledger Entry”
• Statement Date: CalcFormula Table 273 “Bank Acc. Reconciliation”
• Statement Line No.: TableRelation Table 274 “Bank Acc. Reconciliation Line”
• Statement No.: TableRelation Table 274 “Bank Acc. Reconciliation Line”
• Bank Acc. Posting Group: TableRelation Table 277 “Bank Account Posting Group”
• Global Dimension 1 Code: TableRelation Table 349 “Dimension Value”
• Global Dimension 2 Code: TableRelation Table 349 “Dimension Value”
• Currency Code: TableRelation Table 4 “Currency”
• Shortcut Dimension 3 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 4 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 5 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 6 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 7 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 8 Code: CalcFormula Table 480 “Dimension Set Entry”
• Dimension Set ID: TableRelation Table 480 “Dimension Set Entry”

Referenced by

22 fields in 7 objects relate to this table (TableRelation or CalcFormula).

• Table 270 “Bank Account”: Balance, Balance (LCY), Balance at Date, Balance at Date (LCY), Credit Amount, Credit Amount (LCY), Debit Amount, Debit Amount (LCY), Net Change, Net Change (LCY)
• Table 273 “Bank Acc. Reconciliation”: Bank Account Balance (LCY), Total Balance on Bank Account, Total Outstd Bank Transactions, Total Outstd Payments
• Table 271 “Bank Account Ledger Entry”: Closed by Entry No., Reversed by Entry No., Reversed Entry No.
• Table 1692 “Posted Bank Deposit Line”: Bank Account Ledger Entry No., Entry No.
• Table 179 “Reversal Entry”: Entry No.
• Table 272 “Check Ledger Entry”: Bank Account Ledger Entry No.
• Table 7250 “Bank Acc. Rec. AI Proposal”: Bank Account Ledger Entry No.

Pages and codeunits on this table

• Page 165 “Bank Acc. Ledg. Entr. Preview” (source table)
• Page 372 “Bank Account Ledger Entries” (source table)
• Page 381 “Apply Bank Acc. Ledger Entries” (source table)
• Page 413 “Applied Bank Acc. Ledger Entry” (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 408 “DimensionManagement” (1 call: ShowDimensions → ShowDimensionSet)

Countries that replace it

AU, CA, ES, FR, MX, NZ, RU, US

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: "table", object_name: "Bank Account Ledger Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.