Dimensions

This field is used to specify the code for a company, group of companies or group of sites.
This optional code is used to define entities common to several companies or sites.
 If the inquiry is launched for a group, the companies (or sites) must have the same currency for the selected ledger type.

Specify the analytical postings to be viewed, by entering:

• the dimension type and the dimension,
• the company/the site (the site is optional),
• the date range.

The ledger types (manual or automatic) available from this field are filtered depending on the entity chosen in the Company/Site field and they have an analytical accounting type.

This field is used to filter the journals by transaction currency.

The specified ledger currency depends on the type of ledger selected.

These two fields are used to define the date ranges.
These ranges are used to filter the lines whose date is included within this time interval.

 For a group of companies with FYs with different start and end dates, the account bal sht amount is not calculated/displayed.

Code of the impacted dimension type, chosen from the dimension types set up for the selected ledger.

Specify the analytical postings to be viewed, by entering:

• the dimension type and the dimension,
• the company/the site (the site is optional),
• the date range.

Date on which the transaction is posted. The fiscal year and the accounting period are determined starting from this date.

Each accounting journal entered is linked to a given type. The journal type corresponds to the nature of the entered posting: customer invoice, miscellaneous operations, cash receipt, etc.

This information comes with management rules relating to VAT, reminders, etc. It is one of the key elements of the journal entry.

The setup of the selected journal type determines if you can open or close the propagation to the manual ledgers.

The journal type prevails and interrupts the propagation to the other ledgers of the company of the entry site.

This field represents the unique identifier of a journal in a journal type.
The journal number is generated automatically via a counter linked to the journal type. This number can also be entered manually, if such an option has been defined when creating each journal type.
If the entry of the journal number is authorized and this number is blank, the journal number is generated according to the setup of the sequence number counter associated with this type of journal.

Amount expressed in the transaction currency.

Debtor amount expressed in the currency in which the ledger is kept.

Amount of the operation in transaction currency.

Creditor amount expressed in the currency in which the ledger is kept.

This is a free field, designed to explain the posting of this entry
The default value of this field is the Description field entered in the journal header.

By using " / ", the account title is displayed by default ; and with "=", the previous line description is copied.

It is the accounting code of the selected entry line.

Code identifying the BP that can have various roles based on the context:

• Customer,
• Supplier,
• Carrier,
• Sales rep,
• Miscellaneous BP,
• Prospect,
• Service provider

It is the due date of the journal which the entry line come from.
 This date must not be confused with the due date of the open item (a BP line can point to several open items with different due dates from each other, and from the due date of the journal).

Value date.

Enter the company code or use the Look up tool to search for and select the code.

Specifies the code of the site concerned by the processing.

It is the collective account code of the entry line.

This field stores the match letter that characterizes the matching group.
The letter can be:

• Uppercase letter: matching is total,
• Lowercase letter: matching is then only partial.

This field stores the date of the day on which the journal line was matched.

This field stores the maximum accounting date of the journals in the matching group.

Use this field to select the journal status: Temporary or Final.

When set to Final,  the only modifications you can make on a journal are for informational purposes only or if they concern the analytical postings. The date, amounts, accounts, VAT code, and other purely accounting information can no longer be modified.

Journal code attached to the document.

This field contains the journal reference.
Entry of this field is free and not controlled, but it can be useful when looking for a journal whose number is unknown, or to match accounts.

Code used to identify the transaction currency of the journal.

This field is used to specify the contra account.
 The counterpart of each entry line is updated upon creation. If left blank, it will be initialized upon journal posting.

This field is available depending on the inquiry screen setup selected in the Inquiry screens function GESGTC.

This field is only available if the CSL - Consolidation activity code is active at the folder level.

This is a display-only field that is populated according to the following:

The value can default from the setup of the corresponding Journal entry transaction (GESGDE).

There is no default value for this field when a journal entry is created from an automatic journal entry or manually. However, you can define a default value for this field when you create an automatic journal entry using the Automatic journal variables function (GESGVG).

For example, on a sales invoice, to create a default value for the partner field on duty free and VAT lines, use the syntax [ F: SIH ] BPR. The automatic journal field is then populated with the partner code charged on TTC line of the sales invoice.

The field can also default to the partner for the Extraction for Consolidation (BALCONSO) if the option Free criteria is selected.

You can only enter a Business partner that has one the following characteristics: Customer, Supplier, or Miscellaneous BP for this field.

Partner initialization: The initialization rule only applies to accounts with Optional or Mandatory Partner management selected and only for the first ledger defined in the journal entry transaction with consolidation management selected.

For control accounts
The Business Partner defined at the journal entry line level setup is the default partner.

If no Business Partner is defined at the journal entry line level setup, the partner defaults to the CSLBPRDEF – Default partner (CPT chapter, CSL group) parameter value. If this parameter is defined, there is no default partner value.

For General accounts
If the Entry partner check box is selected for the general account defined at the journal entry line level setup, the partner for this general account line defaults to the partner defined in the first control line.

If the Entry partner check box is not selected for the general account defined at the journal entry line level setup, the partner defaults to the CSLBPRDEF – Default partner parameter value. If this parameter is not defined, there is no default partner value.

If no control account line has been found, the partner defaults to the CSLBPRDEF – Default partner parameter value. If this parameter is not defined, there is no default partner value.

Limit: If the journal entry is posted with several control account lines, the partner defaults from the first control account line. The partner is the same for all the general account lines where the Entry partner check box is selected.

Note: When the journal entry transaction has several ledgers with consolidation management, the partner initialized on the first ledger is propagated to the other consolidated ledgers. If for any reason no partner can been initialized on the first ledger but is mandatory on another ledger, a blocking message appears notifying you that partner management is mandatory.

Flow code coming from the account if the flow code management has been chosen for the account.

Flow initialization: The initialization rule only applies to accounts with Optional or Mandatory flow management selected and only for the first ledger defined in the journal entry transaction whose consolidation management is selected.

When creating or posting a journal entry, the journal entry line flow code defaults as follows:

If a flow code is parameterized on the journal, it defaults to that value.

If there is no flow code on the journal, the flow code defaults to the value defined on the account.

The flow depends of the direction on the journal entry line.

If the direction is Credit, the flow defaults to Flow if Credit. 

If the direction is Debit, the flow defaults to Flow if debit.

If the amount is 0 for both debit and credit, the flow defaults to Flow if debit

If there is no flow code on the account, the flow code defaults to the flow defined in the CSLFLODEF - Default flow parameter.

If this parameter is not defined, there is no default flow code value.

Note: When the journal entry transaction has several ledgers with consolidation management selected, the flow initialized on the first ledger is propagated to the other consolidated ledgers. If for any reason no flow has been initialized on the first ledger but is mandatory on another ledger, you receive a blocking error message that flow management is mandatory for the current account.

Amount expressed in the transaction currency.

Amount expressed in ledger currency.

Declared amount (basis or amount depending on the account type) in the tax declaration

On analytical inquiry, the quantity of non-financial units is displayed.

This field is used to perform the reconciliation of the banking operations that are actually listed on the hardcopy bank statement.
Any character string with a maximum of five characters is authorized for the reconciliation. This string must contain lowercase letters and/or numbers. Upper case letters are reserved for the reconciliation from imported bank statements.

These fields store the three possible statistical families of the accounting journal.

When the account on the line is liable for tax, the tax field is accessible for entry. It is initialized with the tax code associated with the account. Based on the context, it is necessary to verify that this tax code corresponds to the tax actually applicable, or it should be modified. The tax code defines the rate, rules and terms for the deduction applicable to the operation.

On analytical inquiry, this field determines the non-financial unit linked to the displayed account.
The non-financial unit is determined when setting up an account associated with a given value.
This unit is called upon entry.

It identifies the source module of the accounting journal.
The source document, its date and the module are automatically entered whenever the journal scomes from a different module.

 A journal coming from a module other than the accounting cannot be deleted.

The 'source document' and 'document date' fields respectiveley correspond to the reference (journal number) and date of the BP journal.
For example:
for the supplier, it is the number and date of the supplier invoice.

Code of the entry transaction used for the posting.

This field is only accessible upon creating or duplicating a journal. It is initialized according to the NIVBONPAYE parameter data.
Upon recording the journal, the open item is created and the value entered here calls the payment approval of the open item (pending, conflict, payment approval...).

This field displays the creation (entry) date of the object.

This field displays the user who created (entered) the record.

This field displays the date of the last modification entered for the object.

This field displays the user that made the last modification on the recording.

The site code for the operation is initialized with the site associated with the user code. It can be modified provided it is chosen from the list of authorized sites.
The site must be a financial site.
It can be modified on the line and the saving of the journal will generate reciprocal account entries.

The category is set up in the journal type.
The accounting journal category can take one of five values:

Actual:
The actual journal can also be viewed and printed (GL, Balance, etc.). The document is integrated into the balance when said document is saved.

Active simulation/inactive simulation:
Once activated, the simulation journal is also integrated to the inquiries and print-outs. It can be converted into an actual journal or de-activated in order to become an inactive simulation journal (i.e. it is not visible in inquiries and prints: for instance, the stock count postings).
 A period of a ledger type cannot be closed until the simulation postings have been either converted to actual postings or cancelled. The change of status of the simulation journals is made using the processes in the accounting functionality.

Off balance sheet:
The off balance-sheet journal can only be posted to off balance-sheet category accounts (via the account classification). It is generally used to track financial commitments.

Template:
The journal template can be used as the basis for the generation processings of actual or simulation entries (e.g. generation of recurring entries). It is not integrated to the GL accounting.

Entering a value to enable the header description for the journal postings.

The interbank code is used by all the banks to specify the bank transaction type on the lines of the bank statements that are sent to their customers.
It is used to facilitate (sort, selection) and control the bank reconciliation between the postings in a bank account with the lines in the bank statements.
This field is initialized in the journals generated for the entered payment lines with an appropriate payment attribute.