Recurring Entry Balancing

Use this function to generate entries with a recurring entry adjustment. You must launch this processing after posting the actual invoice.

The recurring entry adjustment can be performed for:

The generated entry completes or decreases the total of recurring amounts based on the amount actually invoiced.

The recurring entry processing is used to balance the recurring entry account in order to determine the cost or the actual revenue.

Example 1:
Let us consider a supplier recurring entry, for an amount of 300 tax excl. over three months.
Actual amount of the invoice: 373.86 tax incl.
The system generates the following entries:

Example 2:
A recurring entry is created for entries in EURO ledger currency. An intermediate invoice is processed in USD transaction currency. The system simultaneously generates:

You can manage as many recurring adjustment entries as there are transaction currencies involved.

The partner and flow initialization rules are the same as those that are followed for the generation of journal entries. The same rules also apply to any controls used on the partner and flow fields.

Read the documentation for Partner initialization and Flow initialization.

Prerequisites

Refer to documentation Implementation

Screen management

The status of entries in the launch screen must be 'Final' when the 'Actual' entry category is selected and when the company:

Entry screen

The selection criteria are used to limit the selection of the recurring entries to be processed. You do not need to enter all the fields.

The system selects by default all the recurring entries and generates an accounting entry for all those whose total amount of generated recurring entries is different from the related invoice.

Field descriptions

Criteria

All companies (field TOUSOC)

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

Specific 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 CPY)

This is the code of the assignment company of the entity.
This optional zone makes it possible to specify entities common to several companies.

Legislation (field LEG)
All sites (field TOUSIT)

If this check box is selected, all the sites of the current company are affected by this process.

If not selected, you can enter a specific site.

Site (field FCY)

Enter the site code.

All users (field TOUUSR)

No help linked to this field.

User (field USER)
Ledger type (field LEDTYP)

Use this field to define the ledger type concerned by the journal balance. In this function, only Manual ledgers can be accessed.

You can read the balance on the selected ledger and balance the account for that ledger type. The propagation then initializes the accounts for the non automatic and non prohibited ledger types. This initialization process is based on the entry type setup and account setup.

The propagated amount is the one calculated on the main general ledger in transaction currency. This amount is then converted into the currency of the propagated ledgers.

When generating the journal balance, the propagation depends on the selected entry type.

The entry type used during the journal generation and the entry type used during the balance generation (actual mode) must be consistent.

If the two entry types are not consistent, the balance process must be launched on each non-propagated manual ledger where the account needs to be balanced.

Examples

Entry type

Authorized ledgers

Legal

Analytical

IAS

Journal generation FRODG

LEG

ANA

IAS

Balance generation FRODG

LEG

ANA

IAS

Selected ledger type = Social, Generation type = Actual

In this case, when generating the balance, the propagation is global.

Entry type

Authorized ledgers

Legal

Analytical

IAS

Journal generation FRODG

LEG

ANA

IAS

Balance generation FRODI

LEG

ANA

Selected ledger type = Legal; Generation type = Actual

Here, the propagation is incomplete. The IAS ledger is not propagated. If you want to balance the account on the IAS ledger, relaunch the balance process for this ledger type using an entry type that only authorizes IAS ledgers.

For an automatic ledger type, the amounts in transaction currency are not calculated from the balance.

They are the same as the currency amounts calculated for the original manual ledger. The ledger amounts for the automatic ledger are calculated by converting its currency amounts according to the journal entry rates.

From recurring entry (field ABTDEB)

The selection criteria of the recurring tasks to be closed must be defined.

To recurring entry (field ABTFIN)
Start date (field DATDEB)

Date from which the records are selected.

End date (field DATFIN)

Date until which the records are selected. This date can only correspond to the end of a period.

Generation

Generation type (field TYPGEN)

This field can be used to specify the generation type:

  • Actual: The actual accounting document is a document that can always be viewed and printed (GL, Balance, etc.).
  • Active or inactive simulation.
    See the documentation on the simulation for further information.

It is possible to generate first the journal entry in simulation mode, then, after verification, to restart the processing in actual mode.
In this case, the simulation journal is automatically cancelled and replaced by the real journal which will take into account the new non-invoiced receipts if they exist.

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:

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)

Each accounting journal entered is linked to a given type. The notion of journal type is used to regroup accounting journals based on their common use principles.

You can specify the entry type, knowing that it will prevail on the default one defined in the GAFTYPACC - Default recurring doc type parameter (CPT chapter, DEF group).

Journal (field JOU)

The journal can be initialized by default according to the journal type that has been chosen.
It corresponds to the accounting journal in which the entry will be recorded.

Entry date (field DATPCE)

This field identifies the due date.

Log file (field TRACE)

Select this check box to generate a log file at the end of the run.

Batch task

This function can be run in batch mode. The standard task ACCGAFBAL is provided for that purpose.

Specific Actions