Creating Consolidation Journal Files

You use Consolidation journal files to import and export journals in the system. You can create journal files using an ASCII format supporting multibyte character sets (MBCS) or a file encoded with the Unicode format, using Little Endian byte ordering. By default, journal files use the JLF file extension.

A line starting with an exclamation point (!) indicates the beginning of a new section in the journal file, and must be followed by a valid section name (for example, JOURNAL). A line starting with an apostrophe (') is considered a comment line and is ignored by the system.

Journal Version Section

This file section contains the Financial Consolidation and Close version that you used to extract journals. The version number is automatically generated when you extract journals.

Note:

This section is optional.

Example: !Version = 19.05

Journal Group Section

!GROUP=<journal group name>,<journal group description>

For example, this example defines two journal groups:

!GROUP=Allocations,Allocations Journals Group !GROUP=Tax,Tax Journals Group

Dimension Order Section

The Dimension Order lists the order in which the journal entry is defined. A journal file can contain the Dimension Order section once, at the top of the file, or included for each journal separately. You can also include the section at the top of the file and then overwrite it by specifying it for a specific journal in the file.

Example: DIMENSION_ORDER=Entity,Account,Intercompany,Movement,Multi-GAAP,Product

POV Section

!POV=<scenario>,<year>,<period>,<Consolidation dimension member>

<scenario> = any valid scenario in the app

<year> = any valid year in the app

<period> = any valid period in the app

<Consolidation dimension member> = any valid input consolidation dimension member in the app. Currently limited to "FCCS_Entity Input", "FCCS_Translated Currency Input", "FCCS_Parent Input", "FCCS_Contribution Input"

Journal Section

!JOURNAL=<journal name>,<journal group>,<journal status>,<journal type>,<balance type> (if enabled), <Data Source dimension member>,<journal view>

<journal name> = text up to 50 characters

<journal group> = optional text up to 30 characters, must be created in advance if used but can be imported in the same file as the journal that uses it*

<journal status> = W (working), P (posted)

<journal type> = R (regular), A (accrual), L (accrual reversal)

<balance type> = B (balanced), U (unbalanced) - balance type is only applicable if Unbalanced Journals are enabled

<Data Source dimension member> = any valid journal Data Source member in the application (default is "Journal Input")

<journal view> = PER (periodic and the default), YTD (year-to-date), JTD (journal-to-date)

*the following header line(s) can precede the journal headers

!GROUP = <group name>,<group description>

Example

Following is an example of the .jlf file required for two journals to be posted to the "FCCS_Translated Currency Input" Consolidation dimension member and the "DS_Jnl_EUR" Data Source member:

!VERSION=1

!GROUP=YTD Grp,YTD Grp Description

!GROUP=Periodic Grp,Periodic Grp Description

!DIMENSION_ORDER=Entity,Account,Intercompany,Movement,Multi-GAAP,Product

!POV=Actual,FY20,Jan,FCCS_Translated Currency Input

!JOURNAL=TCI Jnl,YTD Grp,W,R,DS_Jnl_EUR,PER

!DESC=Jnl description

LE-0011-EUR,[Cash Overdraft Parent].[Cash],FCCS_No Intercompany,FCCS_Mvmts_Cash,FCCS_Local GAAP,[Product].[No Product],D,100.00,

LE-0011-EUR,[FCCS_Cash And Cash Equivalents].[Bank1],FCCS_No Intercompany,FCCS_Mvmts_Cash,FCCS_Local GAAP,[Product].[No Product],C,100.00

!JOURNAL=another TCI,Periodic Grp,P,A,DS_Jnl_EUR,PER

LE-0011-EUR,[Cash Overdraft Parent].[Cash],FCCS_No Intercompany,FCCS_Mvmts_Cash,FCCS_Local GAAP,[Product].[No Product],D,100.00,

LE-0011-EUR,[FCCS_Cash And Cash Equivalents].[Bank1],FCCS_No Intercompany,FCCS_Mvmts_Cash,FCCS_Local GAAP,[Product].[No Product],C,200.00

History Section

This file section contains the Consolidation journal work flow history. Each journal can have multiple History sections.

!HISTORY=<user>,<action>,<comments>

Note:

This section is optional. If you are exporting journals using Migration, this section is exported if the journal workflow is enabled.