Accounts

• Company (field CPY)

When this field is populated with a company code, the inquiry is filtered in order that only those data concerning the selected company are displayed.

• Site (field FCY)

When this field is populated with a site code, the inquiry is filtered in order that only those data concerning the selected site are displayed.

• Ledger type (field LEDTYP)

The ledgers types available from this field are:

• those having the accounting type 'General' checked,
• filtered on the basis of the entitty chosen in the Company/Site field.

• Selection currency (field CURSEL)

Optional field used as filter for the transaction currency. If the field is blank, all the entries will be displayed in the company currency.

• Ledger currency (field CURLED)

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

• Start date (field DATDEB)

Accounting date range. Ranges are included.

• End date (field DATFIN)

• Accounting balance (field LIBSOL)

Balance of the account in company currency, matching the currency in which the main general ledger is kept, on the inquiry end date.

 For a group of companies having fiscal years with different end and start dates, the accounting balance is not calculated/displayed.

• field DEVISE

Account balance currency. It is always the company currency.

• Chart of accounts (field COA)

This field reminds the chart of accounts linked to the company (or to the group of companies or the group of sites) and to the selected ledger type.

• Account (field COMPTE)

It is used to select the account to be viewed. It must be of normal type. This account belongs to the chart of accounts selected in the current record.

• Control (field COLLEC)

It is used to perform a selection on a specific collective account.

• Control group (field GROUPE)

It is used to perform a selection on a specific collective account group.

• BP (field TIERS)

Field used to select a BP.

• Date (field ACCDAT)

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

• Type (field TYP)

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.

• Document no. (field NUM)

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.

• Debit (field DEBIT)

Amount expressed in the transaction currency.

• Ledger debit (field DEBLED)

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

• Credit (field CREDIT)

Creditor amount expressed in the transaction currency.

• Ledger credit (field CDTLED)

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

• Line description (field DES)

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.

• Due date (field DUDDAT)

Open item payment due date.

If the MAXPD - Maximum period (companies) activity code is activated, a blocking message is displayed if the last due date is greater than the period specified, depending on the case, at the level of the following parameters or of the Contractual period possibly specified at the BP level.

• DMAXPAYP - Maximum period (Public sector) (TC chapter, RSK group) when the BP is a public sector organization.
• DMAXPAY - Maximum period (companies) (TC chapter, RSK group) when the BP is a private sector company.

• Value (field VALDAT)

Value date.

• Co. (field CPY)

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

• Site (field FCYLIN)

Specifies the code of the site concerned by the processing.

• Ctrl. (field SAC)

This field specifies the code of the collective account group if the inquiry concerns a BP.

• Match letter (field MTC)

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.

• Matching date (field MTCDAT)

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

• Maximum date (field MTCDATMAX)

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

• Status (field STA)

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 (field JOU)

Journal code attached to the document.

• Reference (field REF)

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.

• Curr. (field CUR)

Code used to identify the transaction currency of the journal.

• Ledger currency (field DEVLED)

• Offset (field OFFACC)

This field is used to indicate the contra account.
The offset of each entry line is updated upon creation.

• For BP accounts, by the first expense account found,
• for expense or tax accounts, by the first BP found (or other balance sheet account).

If left blank, it will be initialized upon journal posting.

• Partner (field CSLCOD)

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.

• Partner (field CSLBPR)

• Flow (field CSLFLO)

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.

• Distribution (field DSP)

Defined here are the allocation methods for the line amount on the different dimensions of each dimension type.

These methods are defined as follows:

• the entry of an analytical allocation key previously configured,
• in amount: it is then possible to allocate the amount to as many dimensions as required.
• in percentge: a calculation is performed based on the sum of the coefficients used in the allocation.

For instance:
On a basis of 100, a coefficient of 10 will be read as 10%. But, on a basis of 50, a coefficient of 10 will be equivalent to 20%.

For these two later cases, it is possible to pre-initialize the allocation with an already existing key. The final display will be " $ ". 

• field CCE1

• Ledger amount (field AMTLED)

Amount expressed in ledger currency.

• Amount in currency (field AMTCUR)

Amount expressed in the transaction currency.

• Declared tax (field AMTVAT)

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

• Quantity (field QTY)

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

• Mark (field CHK)

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.

• Statistic 1 (field STT1)

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

• Tax (field TAX)

When the account on the line is subject to tax, the tax field is accessible for entry. It is initialized with the tax code associated with the account. According to 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, the rules, and the terms for the deduction applicable to the operation.

If the Control type field is set to Inactive for the Account, you can enter any value on the line.

If the Control type field is set to Authorization for the Account, you can only enter a code listed in the Tax control grid on the Management tab in the Account. Otherwise, you receive a blocking message.

If the Control type field is set to Restrictionfor the Account, you can only enter a code that is not listed in Tax control grid. Otherwise, you receive a blocking message.

• Unit (field UOM)

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.

• Entry date (field ENTDAT)

• Module (field ORIMOD)

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.

• Source (field ORIGIN)

• Source transaction (field ORICOD)

• Source document (field BPRVCR)

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.

• Document date (field BPRDATVCR)

• Transaction (field DACDIA)

Code of the entry transaction used for the posting.

• Multiplying rate (field RATMLT)

• Dividing rate (field RATDIV)

• Reminder (field FLGFUP)

• Pay approval (field FLGPAZ)

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...).

• Created (field CREDAT)

• Creation author (field CREUSR)

• Change date (field UPDDAT)

• Change author (field UPDUSR)

• Reconciliation date (field CHKDAT)

• Journal site (field FCY)

The site code for the operation is initialized with the site associated with the user code. It can be modified on the condition that it is chosen in the list of authorized sites.
The site must be a financial one.
It can be modified on the line and the record of the journal will generate line postings (on the accounts defined in the chart of accounts).

• Category (field CAT)

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.

• Header description (field DESVCR)

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

• Interbank code (field BANCIB)

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.

• Marking (field MRK)

No help linked to this field.

• Chronological number (field CHRNUM)

• Free reference (field FREREF)

• Final number (field FNLPSTNUMW)

• Final date (field FNLPSTDAT)

• Project (field PJTLIN)

• Cost type (field PCCCOD)

• Date (field DAT)

Period end date.

• Debit balance (field SOLDEB)

This field specifies, if the selection currency having been entered, the debit balance of the period in the selection currency.

• Credit balance (field SOLCRE)

This field displays the credit balance of the period in the selection currency.

• Debit transactions (field TOTDEB)

This field specifies, in the event of the selection currency having been entered, the total of the debtor movements over the period in the selection currency.

• Credit transactions (field TOTCRE)

This field specifies, in the event of the selection currency having been entered, the total of the creditor movements over the period in the selection currency.

• Ledger debit balance (field CTVSOLDEB)

This field specifies the account debtor balance, on the period date end, in the ledger keeping currency.

• Ledger credit balance (field CTVSOLCRE)

This field specifies the account creditor balance, on the period date end, in the ledger keeping currency.

• Ledger debit movements (field CTVTOTDEB)

This field specifies the sum of the debtor movements over the period in the ledger keeping currency.

• Ledger credit movements (field CTVTOTCRE)

This field specifies the sum of the creditor movements over the period in the ledger keeping currency.

• Debit in ledger currency (field DEBLOC)

Total of the debtor movements in the ledger keeping currency for all periods inquired.

• field DEVLOC

Currency in which the debit total is expressed in ledger keeping currency.

• Credit in ledger currency (field CRELOC)

Total of the creditor movements in the ledger keeping currency for all periods inquired.

• field DEVLOC2

Currency in which the credit total is expressed in ledger keeping currency.

• Balance in ledger currency (field SOLLOC)

Balance of the movements, in ledger keeping currency, for all the selected periods.

• field SNSSOL

Sense of the balance.

• Debit in selection currency (field DEBCUR)

If the selection currency has been entered, this field displays the total of the debtor movements in the selected currency for all periods viewed.

• field DEVCUR

Selected currency.

• Credit in selection currency (field CRECUR)

If the selection currency has been entered, this field displays the total of the creditor movements in the selected currency for all periods viewed.

• field DEVCUR2

• Balance in selection currency (field SOLCUR)

Balance, expressed in the selection currency, calculated on those movements whose currency is identical to the selection currency.

• field SNSSOL2

Code of the selected currency.