Page extension 4023 "SendVendLedgerEntryRemitAdvice"
UKSendRemittanceAdvice · Microsoft.Purchases.Vendor.RemittanceAdvice
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
UKSendRemittanceAdvice · Microsoft.Purchases.Vendor.RemittanceAdvice · BC29-30 · source at ea08af5e · facts from BC29
Extends Vendor Ledger Entries.
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| addlast(Functions) | Send Remittance Advice obsolete Pending 29.0; #if not CLEAN29 | 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. |
Procedures
1 local procedures, no public ones.
Relations
- extends Page 29 “Vendor Ledger Entries”
Recent changes
- 2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature)
Deprecations
- procedure SendVendorRecords: guarded (#if not CLEAN29)
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: "SendVendLedgerEntryRemitAdvice"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.