Applies To: Work 365 (Dynamics 365 / Power Platform)
Audience: Billing Teams, Administrators, Finance Teams
Overview
If certain License Change Logs (LCLs) don’t appear on invoices, the cause is usually skipped historical cycles or orphaned LCLs from deleted/voided invoices. Left unaddressed, these gaps create missed revenue and reconciliation issues.
? See also: Work 365 Support Portal – Troubleshooting Uninvoiced LCLs
Why This Happens
Invoice runs executed before older LCLs were billed
If a billing contract was invoiced while earlier LCLs were still pending/not marked for billing, those LCLs remain unbilled.Invoices deleted or voided
When an invoice that contained an LCL is deleted/voided, the LCL can become eligible again but won’t always be auto-picked up on a new invoice.Inactive or missing billing schedules
LCLs aligned to inactive/misconfigured schedules are skipped in subsequent runs.
? Reference: Work 365 Support Portal – Billing Contracts & Schedules
Quick Diagnosis (Fastest Checks)
Open the LCL → confirm Status/Status Reason = Active (not Archived).
Check Invoice / Invoice Line lookups → must be empty to be billable again.
Ensure Effective Date is on/before the target billing period.
Open the Billing Contract → verify Billing Schedules are Active and correctly dated.
Confirm no older cycles remain unbilled for the contract (Work 365 invoices oldest periods first).
Resolution Steps
Step 1: Identify the affected LCLs
Go to License Change Logs in Dynamics 365 / Power Platform.
Use (or create) a view: “Uninvoiced LCLs (Active)”.
Filter for Effective Date < current billing cycle and Invoice/Invoice Line IS NULL.
Note all impacted records.
Step 2: Generate a full-cycle invoice for the earliest unbilled period
Open the Billing Contract tied to the affected LCLs.
Generate the invoice for the oldest missing cycle (e.g., invoice June before July).
Verify the invoice contains both:
The period’s full-cycle line, and
A separate LCL line for the missed change.
? Reference: Work 365 Support Portal – Generating Invoices Manually
Step 3: Remove a duplicate full-cycle line (only if that period was already billed)
If the newly generated invoice includes a duplicate full-cycle line for a period already billed:
Open the invoice → remove that line or mark it Non-billable.
Go to Billing Schedules and deactivate the duplicate schedule to prevent recurrence.
Step 4: Process remaining periods
Repeat Step 2/3 for each remaining unbilled cycle (e.g., July, August) until all LCLs are invoiced.
Resume normal automated billing after clearing the backlog.
Nice-to-Know Fixes (if lines still don’t appear)
Unit/Price alignment: Ensure Sales Unit, Monthly Unit Selling Price, and Selling Price per Unit are populated and consistent on the Subscription/LCL.
Write-in avoidance: Confirm the Product on the Subscription and a matching Price List Item exist on the Billing Contract’s Price List.
Provisioning state: If LCLs are still Awaiting Provisioning, complete/toggle provisioning (Not Applicable → Awaiting Provisioning) before invoicing.
How to Prevent Future Occurrences
| Preventive Action | Description |
|---|---|
| Monitor “Uninvoiced LCLs” weekly | Keep a dashboard/view and action items promptly. |
| Avoid deleting invoices with LCLs | Deleting can orphan LCLs; prefer Void or reassign as per finance policy. |
| Validate readiness before invoice runs | Ensure all prior LCLs are ready before starting a new cycle. |
| Manage overlapping cycles carefully | If running a future cycle early, confirm older LCLs are fully processed first. |
| Audit billing schedules | Keep schedules active, correctly dated, and aligned to subscriptions. |
| Archive historical LCLs | Once invoiced (or intentionally excluded), set LCLs to Archived to avoid repeats. |
Summary
LCLs usually fail to invoice due to skipped historical cycles, deleted/voided invoices, or inactive schedules.
Fix: Identify the earliest unbilled LCLs → generate invoices in order → remove any duplicate full-cycle lines → resume automation.
Routine monitoring and schedule hygiene prevent gaps and protect revenue.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article