---
id: object/pageextension/6110
type: object
title: Page extension 6110 "E-Doc. Payment Journal"
summary: Page extension 6110 "E-Doc. Payment Journal" in EDocument (Microsoft.eServices.EDocument.RemittanceAdvice), extends "Payment Journal". Introduced in BC29, still in BC30.
tier: official
language: en
tags:
  - pageextension
  - edocument
versions:
  introduced: "29"
  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: 7b3fedc7e55d94b37b47916b3696fa84aa92b34b7d88a0fc0e72e5c92ff7e3e8
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Apps/W1/EDocument/app/src/RemittanceAdvice/EDocPaymentJournal.PageExt.al
    title: src/Apps/W1/EDocument/app/src/RemittanceAdvice/EDocPaymentJournal.PageExt.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects:
    - object/page/256
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes:
    - change/bcapps/11483
    - change/bcapps/9578
object_type: pageextension
object_id: 6110
name: E-Doc. Payment Journal
namespace: Microsoft.eServices.EDocument.RemittanceAdvice
app: EDocument
extends: Payment Journal
first_version: "29"
last_version: "30"
present_in:
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 5
  events: 0
  subscribers: 0
  controls: 1
  actions: 2
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 0
  implements: 0
---

# Page extension 6110 "E-Doc. Payment Journal"

> Page extension 6110 "E-Doc. Payment Journal" in EDocument (Microsoft.eServices.EDocument.RemittanceAdvice), extends "Payment Journal". Introduced in BC29, still in BC30.

EDocument · Microsoft.eServices.EDocument.RemittanceAdvice · BC29-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Apps/W1/EDocument/app/src/RemittanceAdvice/EDocPaymentJournal.PageExt.al) · facts from BC29

Extends [Payment Journal](../page/256.md).

## 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 |
|---|---|---|---|
| addafter(Exported to Payment File) | Remit. Advice E-Doc. Created | [Remit. Advice E-Doc. Created](../tableextension/6101.md#fields) | Specifies whether a remittance advice electronic document has been created for the payment. |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Remittance Advice E-Document | Open Remittance Advice E-Doc. | Opens the electronic document that was created for this payment. |  |
|  | Void Remittance Advice E-Doc. | Clears the remittance advice e-document flag for the selected payment(s) and cancels the related e-document, allowing it to be recreated. |  |

## Procedures

5 local procedures, no public ones.

## Triggers

OnAfterGetCurrRecord

## Relations

- extends [Page 256 "Payment Journal"](../page/256.md)

## Recent changes

- 2026-09-24 [#11483 [E-Documents Core] - Linkage & Traceability](../../changes/bcapps/11483.md) (main, BC30, feature)
- 2026-08-11 [#9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments)](../../changes/bcapps/9578.md) (main, BC30, feature, added)

## Across versions

- Present in: BC29-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: "pageextension", object_name: "E-Doc. Payment Journal")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.
