Page extension 6110 "E-Doc. Payment Journal"
EDocument · Microsoft.eServices.EDocument.RemittanceAdvice
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument.RemittanceAdvice · BC29-30 · source at ea08af5e · facts from BC29
Extends Payment Journal.
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 | 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”
Recent changes
- 2026-09-24 #11483 [E-Documents Core] - Linkage & Traceability (main, BC30, feature)
- 2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature, added)
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.