Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{noprint}{float:right|width=300px|background=lightgrey|border=solid blue 2px|margin=10px|padding=8px}
*Contents*
{toc:all=true|depth=4|excerpt=true|indent=14px}
{float}{noprint}
*Change log:*
|| *Date:* || *Author:* || *Version:* || *Changes:* || Completed || *Ext.* || *Int.* || *Is in Core* || Jira Ref. ||
| {page-info:created-date|dateFormat=dd MMMM yyyy} | {page-info:created-user} | 0.1 | Doc. created | Yes/No | | x | N/A | N/A |
| 18 July 2013 | Luca Casarini | 0.2 | Doc. completed | Yes | | x | N/A\\ | N/A\\ |




h1. Monthly Accounting Report

This report provides a monthly summary of all debits and credits, grouped according to the GL (General Ledger) code configuration. It is of course scheduled every month and considers usage from the previous calendar month.

!rpt10.png|border=1!

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:

!rpt11.png|border=1!


When the GL configuration is complete, the report can be safely be generated again.