Use this function to run a transfer code, in other words, to close the accounts whose root is contained in the setup of the balance transfer code.
Validating a balance transfer code implies that the launch parameters are consistent between the chart of accounts linked to the balance transfer, the ledger type and the selected company.
It is necessary to define the selection criteria of the accounts to be closed and to specify the characteristics of the generated documents: type, journal, date.

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

Prerequisites

See also Refer to documentation Implementation

Screen management

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

  • either a French legislation company (the FRADGI/TC chapter/CPT group parameter is set to 'Yes' and it cannot be modified),
  • or a non-French company applying the French DGI no. 13L-1-06 compliance rules (the FRADGI/TC chapter/CPT group parameter is set to 'Yes' and it cannot be modified).

Entry screen

Header

Company group (field GRPSOC)

Specify a company or a group of companies in order to limit the running of the balance transfer code to a given company or group of companies.
Using the tabulation, the detail of the company of the group specified in this field is displayed in the Company section.
Ledger type (field LEDTYP)

Select the ledger type that will be impacted by the balance.

Grid Companies

Company (field SOC)

Criteria

Balance transfer (field DUM)

Balance transfer code that will impact the balance.

Site (field SITE)

Enter or select a site to limit the process to that site.
Start date (field STRDAT)

This field identifies the first day of the period involved by the balance.
End date (field ENDDAT)

This field identifies the last day of the period involved by the balance.

Generation

Generation type (field TYPGEN)

The generation can take place in real or simulation mode, which enables the journals to be viewed before the actual generation is carried out.
Entry status (field SIM)

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:

SEEINFO 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
Transaction (field DACDIA)

Select the entry transaction that will be used to generate the entries.
Entry type (field VCRTYP)
Journal (field VCRJOU)

Enter the journal code (1 to 5 alphanumerical characters).
The journal can be initialized by default depending on the journal type that has been chosen. It corresponds to the accounting journal in which the entry will be recorded.
Note The entry of a non authorized journal code at the journal type level is not possible.

Warning Journal codes can apply to a specific company, a specific site, or a specific group. This information is defined when the journal code is created but the selection window for this field (using the selection tool) does not take this into account. These controls are applied when you select or confirm the journal code. You can amend the journal code if an error message warns that it is invalid.
Entry date (field VCRDAT)
Log file (field TRACE)

Batch task

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

Specific Actions

Memo

Click this action to save the current settings to a Memo code to be reused later. The memo is linked to your user profile, not to the function or the screen.

NoteThe STD memo code is associated with the screen and is loaded immediately when you open the function.

For more information on the advanced use of the Memo action, refer to the documentation on the General ergonomics of SAFE X3 software.

Recall

Click this action to enter a Memo code to load the settings associated with the code.

Delete Memo

Click this action to delete a Memo code.

Limitation

The management and generation of accounting documents using the double-entry method is not available for this function because it does not use an automatic journal process. Only functions that use an automatic journal process can use the double-entry method for a company.

Warning The KRU - Russian legislation activity code must be active to use the double-entry method for a company.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

The posted documents will have the 'Final' status for the company

If the processing is launched for a given company and this company has selected Conformity DGI no. 13L-1-06 (i.e. the value of the FRADGI/TC chapter/CPT group parameter is set to 'Yes'), the actual entries generated by the processing will have the 'Final' status.

The posted documents will have the 'Final' status for one or more companies

The processing is launched for all companies or a group of companies, and if at least one of the companies chose Conformity DGI no. 13L-1-06 (i.e. the value of the FRADGI/chapter TC/group CPT parameter is set to 'Yes'), the actual entries generated by the processing will have the 'Final' status.

Tables used

See also Refer to documentation Implementation