[BC Idea]: Automated Billing and Error Logging for Subscription Contracts [SubscriptionBilling] #4443
Description
BC Idea Link
https://experience.dynamics.com/ideas/idea/?ideaid=8f870bca-4f74-f011-95f2-7c1e52cbaa29
Description
Automated Billing Lines and Documents
The goal is to automate parts of the subscription contract billing process for efficiency.
Contract Categories
- Invoices can be created automatically
- Same invoice is posted every month.
- Automation creates and post the invoice.
- Invoices cannot be created automatically
- Manual adjustments required.
- Automation creates a Billing Proposal only.
- Vendor contract invoicing
- Will not be automated.
Automation Workflow
- User defines a billing template for the first category.
- Contracts filtered by type.
- Invoices/credit memos posted on the 25th for the following month.
- Posting & Document Date = 1st of next month.
- Billing template can be automated via Job Queue → creates Billing Proposal and Documents.
- For large volumes of contracts:
- Invoices can be generated daily.
- Today formula is used for automation which applies current date when running in Job Queue.
- Posting handled via Batch Post Sales Invoices in Job Queue.
Additional Features
- Invoices created by automation include an identifier (for filtering).
- Access is restricted via User Setup field to prevent accidental changes.
- Permissions for automated templates:
| Action | With Access | Without Access |
|---|---|---|
| See all templates | Yes | Yes |
| Edit/delete automated templates | Yes | - |
| Edit/delete non-automated templates | Yes | Yes |
| Automate a template | Yes | - |
| Select automated template | Yes | Yes |
| Select non-automated template | Yes | Yes |
| Create proposals/documents (auto & non-auto) | Yes | Yes |
| Delete billing lines/documents (auto & non-auto) | Yes | Yes |
| Post documents (auto & non-auto) | Yes | Yes |
| Clear all documents | Yes | - |
| Clear complete proposal | Yes | - |
- Users can always view all templates, even without automation rights.
Error Logging
Every error during automation must be logged to inform users and prevent incorrect invoices.
- Document-level safety: if one line causes an error, the entire document is discarded (avoiding partial/incorrect postings).
- The automation must be robust, efficient, and resilient:
- It should not stop unexpectedly.
- It should not break processes.
- It should run within reasonable timeframes.
I will provide the implementation for this BC Idea
- I will provide the implementation for this BC Idea
Internal work item: AB#605914