Recurring Entry Generation

• All companies (field TOUSOC)

Select this check box to run the process for all companies. Otherwise, you need to select a company.

Special case

In a multi-legislation environment, this check box is not available. The process can only be run one company at a time because the document type and journal for the posting are likely for a single legislation.

• Company (field SOCIETE)

Enter the company code for which the processing has been started.

 The company code:

• must necessarily refer to a legal entity,
• must necessarily be entered if the box "All companies" is not checked.

• Legislation (field LEG)

• All sites (field TOUSIT)

Select this check box to run the process for all sites. Otherwise select a site.

• Site (field SITE)

Enter the site code for which the processing has been started.

 It is mandatory to enter this field if the box "All sites" is not checked.

• All users (field TOUUSR)

When this box is checked, the data associated with all the users are involved by the process (if it is not checked, only the user whose code is given is involved (if no code given, the current user).

• User (field USER)

If a user code is entered in this field, the process only includes accounting documents entered by the user. If left blank, only accounting documents for the current user are included.

• From recurring entry (field ABTDEB)

The accounting document type used on actual generation of the recurring entry is defined at recurring task setup level.
It is possible at processing level to choose the document generation type

• Actual: The actual accounting document is a document that can always be viewed and printed (GL, Balance, etc.).
• 'Active simulation' or 'Inactive simulation'.
   Please refer to the documentation on the simulation for further details.

It is possible first to generate the document in simulation mode, then, after checking, to restart the processing in actual mode.
In that case, the simulation document is automatically deleted and replaced by the actual document.

• To recurring journal (field ABTFIN)

• Until (field DATFIN)

Date up to which the recurring task journals are generated (only if this date is comprised between the validity start and end ranges of the recurring task).

• Generation type (field TYPGEN)

The accounting document type used on actual generation of the recurring entry is defined at recurring task setup level.
It is possible at processing level to choose the document generation type

• Actual: The actual accounting document is a document that can always be viewed and printed (GL, Balance, etc.).
• 'Active simulation' or 'Inactive simulation'.
   Please refer to the documentation on the simulation for further details.

It is possible first to generate the document in simulation mode, then, after checking, to restart the processing in actual mode.
In that case, the simulation document is automatically deleted and replaced by the actual document.

• Entry status (field ECTSTA)

In the event of an actual generation, the status of the journal can be:

• Temporary
• Final

The entry status for entries must be Final when the requested generation type is Actual and the company meets one of the following criteria:

• French legislation company with the FRADGI - French fiscal regulation parameter (TC chapter, CPT group) set to Yes and not editable;
• Foreign company applying the French 'DGI no. 13L-1-06' compliance rules with the FRADGI - French fiscal regulation parameter (TC chapter, CPT group) set to Yes and editable.

The status defines your ability to modify the document. Once final, the modifications of the journal are only for information purposes or concern the analytical postings. The date, amounts, accounts, VAT code, and other purely accounting information can no longer be modified.

In temporary mode, most of the information displayed on the journal can be modified. The modification options can vary based on:

• The nature and the origin of the accounting document:
  • Temporary payment document: bank line that cannot be deleted
  • Purchase invoice document: BP line that cannot be deleted, purchase account and VAT that cannot be modified

• The management events that have an impact on the account document are:
  • Charge account with a declared VAT amount
  • Matched VAT account or not

• Entry type (field TYPPCE)

When a journal type is entered, the processing is only started for the journals for which this type has been used.
Only the journal types for which the simulation category has been checked are submittted here.

This field can be access only in simulation mode: when generating in real mode, the type of journal used is that defined in the recurring task setup.

• Journal (field JOU)

This field is used to select the simulated generation journal.

• Log file (field TRACE)

If this box is checked, a summary is provided of all the generated documents at the end of the processing.