...
Change
...
log:
...
Date: |
|---|
...
Author: |
|---|
...
Version: |
|---|
...
Changes: |
|---|
...
Completed | Ext. | Int. | Is in Core | Jira Ref. | |
|---|---|---|---|---|---|
|
...
|
...
0.1 |
...
Doc. |
...
created |
...
No |
| x | N/A |
...
N/A |
...
18 |
...
July |
...
2013 |
...
Luca |
...
Casarini |
...
0.2 |
...
Doc. |
...
completed |
...
Yes |
| x | N/A |
...
N/A |
...
22 July 2013 | SD | 1.0 | Checked | Yes | x |
| N/A | N/A |
Overview
Name of report | Monthly Accounting Report |
Schedule | Monthly |
System | Retail/Wholesale; Prepaid/Postpaid |
Customer role | Informed, Responsible |
CDRator Operations role | Informed |
CDRator role | Informed |
Description of the roles:
- Escalate - the recipient escalates to the Informed role if the content of the report becomes a concern.
- Informed - the recipient gathers information by the content of the report. No reaction is expected.
- Responsible - the recipient is expected to read the content of the report (or a part of it) and to take the necessary actions.
| Note |
|---|
CDRator Operations is involved only in case of a Managed Service Agreement with the customer. |
Monthly Accounting Report
This report provides a monthly summary of all debits and credits, grouped according to the GL (General Ledger) code configuration. Of course, it is scheduled every month and considers usage from the previous calendar month.
If the GL code configuration is not complete, the report still returns information about traffic with missing GL codes.
No information is available on GL Group ID, GL Group and GL Code; instead, Description returns the name of the charge items that should be mapped to a GL code along with a message that explains the missing GL configuration:
When the GL configuration is complete, the report can be generated again safely.