---
id: object/page/2000001-be
type: object
title: Page 2000001 "EB Payment Journal" (BE)
summary: Page 2000001 "EB Payment Journal" (BE) in the BE country layer (Microsoft.Bank.Payment). 1 public procedures, 2 events. Introduced in BC28, still in BC30.
tier: official
language: en
tags:
  - page
  - be layer
versions:
  introduced: "28"
  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: a60fff159755fbed0c21ebf79873198e93ca97f94e727739ac409575c3de63c4
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/BE/BaseApp/Local/BankMgt/Payment/EBPaymentJournal.Page.al
    title: src/Layers/BE/BaseApp/Local/BankMgt/Payment/EBPaymentJournal.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations:
    - localization/be
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 2000001
name: EB Payment Journal
caption: EB Payment Journals
namespace: Microsoft.Bank.Payment
app: Base Application
extends: null
first_version: "28"
last_version: "30"
present_in:
  - "28"
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
country: BE
counts:
  fields: 0
  procedures: 8
  events: 2
  subscribers: 0
  controls: 44
  actions: 6
relations:
  out: 0
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
---

# Page 2000001 "EB Payment Journal" (BE)

> Page 2000001 "EB Payment Journal" (BE) in the BE country layer (Microsoft.Bank.Payment). 1 public procedures, 2 events. Introduced in BC28, still in BC30.

BE country layer · Microsoft.Bank.Payment · captioned "EB Payment Journals" · BC28-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/BE/BaseApp/Local/BankMgt/Payment/EBPaymentJournal.Page.al) · facts from BC29

An object of the [BE localization](../../localizations/be.md), not part of W1.

## Properties

| Property | Value |
|---|---|
| Caption | EB Payment Journals |
| SourceTable | Payment Journal Line |
| PageType | Worksheet |
| UsageCategory | Tasks |
| ApplicationArea | Basic, Suite |

## 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 |
|---|---|---|---|
| General | Batch Name | `CurrentJnlBatchName` | Specifies the batch name of the payment journal. |
|  | Bank Account | `BankAccountCodeFilter` | Specifies the bank account from which the payment is made. |
|  | Export Protocol | `ExportProtocolCode` | Specifies the payment journal line export protocol code, which controls what payment file will be generated in the payment journal. |
| Control1 | Export Protocol Code | `Rec."Export Protocol Code"` | Specifies the code that identifies the protocol to use for exporting the payment history. |
|  | Separate Line | `Rec."Separate Line"` | Specifies if the payment message is formatted using separate lines. |
|  | ISO Currency Code | `Rec."ISO Currency Code"` | Specifies the ISO code that defines the currency associated with the payment journal entry. |
|  | Standard Format Message | `Rec."Standard Format Message"` | Specifies whether the message in the Payment Message field is a standard format message or not. |
|  | Posting Date | `Rec."Posting Date"` | Specifies the date on which you want the payment to be posted. |
|  | Account Type | `Rec."Account Type"` | Specifies the type of account that the entry on the journal line will be posted to. |
|  | Account No. | `Rec."Account No."` | Specifies the customer or vendor number that the entry on the journal line will be posted to. |
|  | Description | `Rec.Description` | Specifies a description of the entry. |
|  | Applies-to Doc. Type | `Rec."Applies-to Doc. Type"` | Specifies the type of the posted document that this document or journal line will be applied to when you post, for example to register payment. |
|  | Applies-to Doc. No. | `Rec."Applies-to Doc. No."` | Specifies the number of the posted document that this document or journal line will be applied to when you post, for example to register payment. |
|  | Payment Message | `Rec."Payment Message"` | Specifies the payment message that is to be included in this payment. |
|  | Amount | `Rec.Amount` | Specifies the outstanding amount. |
|  | Pmt. Disc. Possible | `Rec."Pmt. Disc. Possible"` | Specifies the payment discount that is subtracted from the remaining amount of the outstanding entry. |
|  | Currency Code | `Rec."Currency Code"` | Specifies the currency code of the payment. |
|  | Currency Factor | `Rec."Currency Factor"` | Specifies the currency exchange factor that is based on the date of the payment. |
|  | Bank Account | `Rec."Bank Account"` | Specifies the bank account that the payment will be posted to. |
|  | Beneficiary Bank Account | `Rec."Beneficiary Bank Account"` | Specifies the beneficiary bank account. |
|  | Beneficiary Bank Account No. | `Rec."Beneficiary Bank Account No."` | Specifies the number of the account that the payment will be posted to. |
|  | Beneficiary IBAN | `Rec."Beneficiary IBAN"` | Specifies the International Bank Account Number (IBAN) for the recipient of the payment. |
|  | SWIFT Code | `Rec."SWIFT Code"` | Specifies the SWIFT code for the bank account that the payment is made from. |
|  | Bank Country/Region Code | `Rec."Bank Country/Region Code"` | Specifies the country/region code of the bank account. |
|  | Instruction Priority | `Rec."Instruction Priority"` | Specifies the order of importance for processing the payment. |
|  | Shortcut Dimension 2 Code | `Rec."Shortcut Dimension 2 Code"` | Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. |
|  | Shortcut Dimension 1 Code | `Rec."Shortcut Dimension 1 Code"` | Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. |
|  | ShortcutDimCode[3] | `ShortcutDimCode[3]` | — |
|  | ShortcutDimCode[4] | `ShortcutDimCode[4]` | — |
|  | ShortcutDimCode[5] | `ShortcutDimCode[5]` | — |
|  | ShortcutDimCode[6] | `ShortcutDimCode[6]` | — |
|  | ShortcutDimCode[7] | `ShortcutDimCode[7]` | — |
|  | ShortcutDimCode[8] | `ShortcutDimCode[8]` | — |
|  | IBLC/BLWI Code | `Rec."IBLC/BLWI Code"` | Specifies the IBLC/BLWI code, regarding the kind of payment. |
|  | IBLC/BLWI Justification | `Rec."IBLC/BLWI Justification"` | Specifies the IBLC/BLWI justification, describing the kind of payment. |
|  | Code Payment Method | `Rec."Code Payment Method"` | Specifies a code to identify the payment method. |
|  | Code Expenses | `Rec."Code Expenses"` | Specifies the code expense that was defined in the export protocol. |
|  | Status | `Rec.Status` | Specifies the status of the export protocol that is associated with the payment journal. |
| Bank Account Name | BankAccName | `BankAccName` | — |
| Remittee Name | Remittee Name | `AccName` | Specifies the name of the customer or vendor who has been entered on the payment journal. |
| Total Remittee (LCY) | Total Remittee (LCY) | `(Balance + Rec."Amount (LCY)" - xRec."Amount (LCY)")` | Specifies the amount of the payments of the customer or vendor that has been entered on the payment journal line. |
| Total Balance (LCY) | Total Balance (LCY) | `(TotalBalance + Rec."Amount (LCY)" - xRec."Amount (LCY)")` | Specifies the total balance in the payment journal. |
| FactBoxes | Payment File Errors | part [Page 1228 "Payment Journal Errors Part"](../page/1228.md) | — |
|  | Control1900919607 | part [Page 699 "Dimension Set Entries FactBox"](../page/699.md) | — |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Line | 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. |  |
| Account | Card | View or change detailed information about the record on the document or journal line. |  |
|  | Ledger Entries | View the history of transactions that have been posted for the selected record. |  |
| Payment | Suggest Vendor Payments... | Create payment suggestions as lines in the payment journal. |  |
|  | Check Payment Lines | Test the payment journal lines to validate the payment journal lines. The validation that is performed on the journal lines depends on the type of check that is specified in the Export Protocols window. |  |
|  | Export Payment Lines | Export the payments to a file. An export protocol defines the payment file format that you want to use for the electronic banking payments. Each journal line contains all the information needed for payment of an outstanding entry. |  |

## Events published

- `OnOpenPageOnBeforeTemplateSelection(var PaymentJournalLine: Record "Payment Journal Line"; var PmtJrnlMgt: Codeunit PmtJrnlManagement; var CurrentJnlBatchName: Code[10]; var IsHandled: Boolean)` (integration)
- `OnBeforeClearVariables(var PaymentJournalLine: Record "Payment Journal Line"; var BankAccountCodeFilter: Code[1024]; var ExportProtocolCode: Code[20]; var IsHandled: Boolean)` (integration)

## Procedures

- `GetExportProtocol()`

Plus 5 local procedures.

## Triggers

OnAfterGetCurrRecord, OnAfterGetRecord, OnDeleteRecord, OnInit, OnNewRecord, OnOpenPage

## Across versions

- Present in: BC28-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). 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: "EB Payment Journal")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.

A BE country object, not part of W1: the default corpus does not have it; `bcatlas_list_countries` shows which countries the atlas has.