Currently it is not possible to perform usage-based cut-off-date billing using the Subscription billing module.

When usage data has been imported e. g. for January and February, but the vendor subscription invoice is created for January only, SB still assigns all open usage data (including February) to the January invoice.

Furthermore, the quantity displayed in the vendor invoice reflects the February usage data which should not be included in the January invoice.

Version: 26.0.30643.33009

Potential root causes:

1) We believe that CU #8060 is responsible. It appears that no proper restriction is applied based on the invoice period.

Path: SubscriptionBilling/Source/Subscription Billing/Billing/Codeunits/CreateBillingDocuments

2) During the usage data import, the quantity of the subscription is calculated chronologically based on the latest usage data end date (CU #8026). This results in only the cumulative quantity from February remaining in the subscription – which is then incorrectly carried into the purchase invoice, even though the invoice period does not match

Path: SubscriptionBilling/Source/Subscription Billing/Usage Based Billing/Codeunits/ProcessUsageDataBilling

3) SB would probably need to recalculate the quantity based on the invoice period during invoice creation?