Journals
Journal structure¶
Both entity journals and consolidation journals are logically composed of two parts:
- a header, i.e. the container of the journal’s general attributes (code, description, etc.). This part defines how the journal must be managed, whether it must be carried forward, the consolidation scenarios on which it must be processed, etc..
- rows, i.e. the records of the saved entries for that journal.
When entries are inserted, CCH Tagetik checks whether the journal satisfies the double entry logic, i.e. whether it is balanced. The double entry logic requires every operation to be recorded twice, on two accounts, simultaneously and with opposite signs. To do this, CCH Tagetik adds together all the amounts entered on the various accounts with “Balance Sheet” nature and “Normal” type used in the journal, and reports the total amount in the “Balancing” field present under the table of rows.
Note: when saving each row edit, all the calculated base type accounts which belong to the process and have one of the accounts edited in the journal as their input are run.
Journal management¶
Journals can be managed in different ways depending on the project type and the client’s requirements.
| Management type | Description |
|---|---|
| Sentence case | Journals are managed by individual period and the data entered are cumulative. This is the complete method and recommended for statutory consolidations. |
| Periodic | The journals are managed from the requested period until the end of the process. Recommended for consolidation in the management setting. Note: on single submission processes, you can manage rows in periodic mode for periodic journals. |
Periodic management for single submission processes¶
If the process on which you are working is a single submission process, periodic management can be performed in two different ways:
- directly from the management of a journal’s rows. In this case, in the save step, it is saved not only on the period in question but also on all subsequent periods that belong to the same process.
- using the Periodic management function (Periodic Management page). In this case, the user can enter the journal data for all periods until the end of the process.
If the process on which you are working is a submission by scenario/period process, its valuation tells the carry forward data processing to copy the data from the previous period. In more detail, during this data processing the amounts of the journal of a period are made cumulative by automatically copying the periodic data from previous periods of the same journal.
Journals numbering¶
CCH Tagetik allows you to choose the Journals numbering method (see Default Settings window).
By default, the Journals numbering method is manual; therefore, when creating a new journal, the user specifies a prefix and suffix which are concatenated to generate the journal number.
If the journal numbering method is automatic, however, the user does not have to specify a prefix and suffix, as the journals are generated with an automatically assigned journal number:
- EJ_
_ , for Entity journals_ - CJ_
_ for consolidation journals_ ,
In order to avoid any anomalies in the journal numbering, the original scenario recoding utility will not allow a scenario for which journals have already been generated with automatic numbering to be chosen as the source or target scenario.
Moreover, the journal recoding utility will not allow journals prefixed with EJ_ or CJ_ to be recoded, nor will it allow an identifier beginning with EJ_ or CJ_ to be chosen as the new journal number.
Despite these precautions, it will still be possible to encounter gaps in the journal numbering. For example, if some journals are deleted, or if categories, entities, currencies are deleted, or the data table cleaning utility is used. The copy utilities may also discard some journals, but in this case it will also be noted that the scenario/period contained in the journal number does not correspond to the scenario/period to which the journal was copied.