Document Types

• Entry type (field TYP)

Enter the accounting entry types to be included in the group. Entry types in the group must have the same legislation, tax code, tax management and tax allocation.

• Legislation (field LEG)

Optional field containing the legislation code (Miscellaneous table 909).
This value is checked during folder creation and validation and when adding data to copy a legislation.

• Description (field DESTRA)

Common title of the current record.

• Short description (field SHOTRA)

The short description replaces the standard description when display or print constraints require it.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Group (field GFY)

A journal type can be used on a company or a dedicated group. Enter the code of the group or the company to limit the use of the journal type.

• Default journal (field DEFJOU)

The default journal is optional. If entered, it will be submitted on journal entry.

• Manual sequence no. (field MANNUM)

It is possible to choose to manually or automatically number the journals using a numbering sequence identified by a counter.
Both systems can coexist but one of them must be chosen.
The counter will come into force on journal entry.

 The counter is only attached to the main general ledger.

• Sequence number (field COU)

• EU tax sequence no. (field COUVATCEE)

• Active (field ENAFLG)

Flag used to activate the document type.

• Access code (field ACS)

This access code makes it possible to prohibit access to the current record for some users.

If the field is populated, only users that have this access code with read access rights (and write access rights respectively) can view (or with write access rights, modify) the record.

Read-only access also controls inquiries for entries in this journal type and, in execution mode, enables entries to be posted for this journal type.

• Validity start date (field VLYSTR)

Used to define a validity start date for the record: before this date, the record cannot be used.

• Validity end date (field VLYEND)

Used to define a validity end date for the record : after this date, the record cannot be used.

• Actual (field VCRREA)

Specifies if actual journals can be created with this type. Otherwise, it is only possible to enter simulation entries.
Actual journals are final or temporary. No distinction is specified in the balance.

• Simulation (field VCRSIM)

Specifies if simulation journals can belong to this type.
A simulation journal can be:

• Active - updates the balance
• Inactive - amounts are withdrawn from the balance

• Off-balance-sheet entries (field VCROUTBSE)

If the journal is classified as being off-balance-sheet, all the accounts used for this journal are associated with an off-balance-sheet category.

• Template (field VCRMOD)

Specifies if "journal templates" can be created with this type. The journal templates are documents that do not create any movements in accounting but that can be used for copies, recurring tasks, calculated MOs, etc.

• Period (field PER)

Defines the period type on which entries of this type can be posted.

• Standard: A maximum of 28 periods can be created.
• Carry-forward entries: Based on the last day of the fiscal year, automatically submits on the first day of the next fiscal year.
• Closing: The last day of the first month of the non-closed fiscal year that is found by default.
  

• Reminders (field FUP)

Specifies if this document type must be taken into account for reminders. The documents of type 'customer invoices', 'customer credit memos', 'doubtful receipts' are generally checked.

• Expense creation (field FLGEXPCRE)

This check box is subject to activity code FAS.
It is used to indicate if the entry of a journal associated with this journal type must lead to the automatic creation of an expense in the Fixed assets module.
This mechanism works only if the following setup is implemented:

• Account setup:
  - The Fixed asset tracking must be activated in order to authorize the use of the account for the assets and expenses managed in the Fixed assets module.
  - The Expense creation, from the validation of a journal allocated to the account, must be authorized.
  - The Accounting nature must be specified.
• Journal entry:
  - Its Category must be: Actual.
  - Its Status must be: Final.

• Fee declaration (field DAS2)

This field specifies if this journal type must be taken into account for the declaration of fees (1099 file). Usually, the Supplier invoiceand Supplier credit memo must be taken into account.

• Rate type (field TYPRAT)

Specify the exchange rate type that must be used to convert the amounts in currencies. When the program searches for the exchange rate, it will be based on the exchange rate of the day (accounting date) or of the original document (original date).

• Rate date (field RATDAT)

Select the date to determine a default exchange rate when the journal is expressed in multiple currencies.

Document date: the accounting date

Original date: date the document was created

• Open item type (field DUDTYP)

This local menu is only considered for the import of entries or the entry of journals. It is only used if the HDU activity code is activated.
It enables the history of the events to be viewed on an invoice: the invoice on its creation date, its balance to be settled on a reference date if there are several payments, etc. This history is built in the ATB Point in time.
 The posting of journals coming from other modules (for instance, the posting of BP invoices) does not take this setup into account.

• Open item management (field DUDDATFLG)

This field specifies if it must be possible to view the open items posted for this document type from the open item management function.
 Open items are generated only for the main general ledger.

• VAT on debit (field VAT)

Specifies if this document type must be taken into account for the VAT declarations on debits. The customer and supplier invoices, as well as the MOs, are the main types of documents impacted by this flag.

• VAT on payment (field VATPAI)

Specifies if this document type must be taken into account for the VAT declarations on collections. This box must be checked for all types of documents settling an invoice. Cash collections or disbursements are the main types of documents concerned by this flag.

• Temporary fiscal year (field PREACC)

• Service provisions (field ESDTRK)

Select this check box to identify journal types to search when running the European Services Declaration.
When creating a journal type, this option is checked by default when the Reminder check box is selected.

• Treasury open items (field DUDCASFLG)

Check this box in order to find the entry type in the cash schedule.

• Payment method (field PAM)

Enter a default payment mode (see Miscellaneous table no. 3).

In journal entry or import, the payment mode of a BP open item is initialized as follows:

• If Open item management is selected and a payment mode is attached to it, the open item is always generated with this payment mode, regardless of the BP payment terms.
• If Open item management is selected and no payment mode is attached to it, the open item is generated with the first payment mode in the BP payment terms.

The payment terms can be Pay-by-BP/Paid BP or the Bill-to-BP/Billing BP, according to the payment condition initialization setting. See documentation for the PAYTERMVAL - Init payment conditions parameter value.

• No. (field NUMLIG)

It is the line number.

• Journal type (field TYPJOU)

This grid is used to specify if this type of document can be used for all types of journals (Sales, Purchase, Cash management, MOs 1 to 3, Carry-forward, ana MOs 1 to 3).

• Authorization (field AUZJOU)

The field specifies for each journal if this type of document can be entered on the corresponding journal type. Some fields are automatically entered based on the category.

• Ledger (field LEDTYP)

The Ledger block submits the list of manual ledgers for the propagation according to the LEDTYPAUT - Automatic ledger type (TC chapter, MIS group) parameter settings.
This list cannot be modified.

 You must have at least one Authorized or Mandatory ledger type.

• Authorization (field AUZLED)

Select one of the following values:

• None: No propagation is carried out to the various ledgers, regardless of the account setup.
• Authorized: Propagation is authorized if the account setup enables it.
• Mandatory: Propagation is carried out automatically, if the account setup enables it.