#10064 Add support for “External Document No.” in Subscription Contracts Fixes #8818
Subscription Contracts now support an External Document No. field that is automatically transferred to generated sales documents and posted invoices, improving support for EAN invoicing scenarios.
- 4files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-09-22 by dksander (community contribution) · 4 files (+39 -0), 3 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Added External Document No. field to Subscription Contracts
- Field value is automatically propagated to sales invoices during billing document creation
- Propagation continues through to posted sales invoices
- New test validates the end-to-end transfer of the field value
- Low-risk change that only extends functionality when the field is populated
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 8060 “Create Billing Documents”, Subscription Billing: modified
- Page 8052 “Customer Contract”, Subscription Billing: modified
- Table 8052 “Customer Subscription Contract”, Subscription Billing: modified
Context
- Fixes: #8818 [BC Idea]: Add support for “External Document No.” in Subscription Contracts (required for EAN invoicing) (closed)
- Work items: AB#648226
- Labels: ADO: Sync, AL: Apps (W1), From Fork, Team: Finance
- Systems: development
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).