Financials >  Closing processes >  Fiscal year end  

Display all Hide all

This function is used to close a fiscal year for a company and to generate in general accounting the corresponding carry-forward entries.

SEEINFO The analytical carry-forwards are managed, but no entry is carried out.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

The fiscal year end process is carried out on a single screen in which the following must be specified:

  • the company for which the fiscal year is closed,
  • the entry type and the journal on which the carry-forward entries must be generated.

The start date for the new fiscal year is automatically displayed. Once this information is entered and the process is launched, a log file is used to follow the operation that is carried out.

Process automation

The controls carried out when closing the last period of the fiscal year have checked the following elements, among others:

  • settling of the balance,
  • balance/General ledger equality,
  • settling of open items,
  • settling of uppercase matching,
  • existence of at least one matched entry on an account set up as "matchable",
  • existence of the allocated accounts and dimensions,
  • entered accounts and dimensions (on those dimension types for which allocation is mandatory),
  • depreciation expenses process already launched.

Two steps are involved in the process:

  • first, the balance sheet accounts are closed in a pending account (ANOUVO parameter value).
    An entry is generated by currency, or by site/currency together (according to the generation type selected in the "Ledger" function),
  • second, the pending account is closed in the results account (defined at the level of the accounting code linked to the company or site).

The analytical carry-forwards depend on the values of the associated parameters. The amounts are carried forward to the same dimensions (if the dimension has been set up with the "RAN" option).
These carry-forwards are only updated on the different dimension types set up with retained carry-forward entries.

The "Year end simulation" utility is used to simulate the results of this processing.


SEEREFERTTOSee the documentation on the Year End Simulation for further information.

Parallel processing

Monthly periodic processing - Stock

For this processing to be possible, no stock-related entry must occur on the concerned period. To do so, the period must be blocked through the stock status (balance adjustment or forbidden).
This processing is used for:

  • the creation of a history cumulated by month that will be used when launching the statistical reordering (exc. MRP) to recalculate the reordering thresholds, the maximum and security stocks and finally the economic lots,
  • the update of the last monthly process date. Depending on the parameter value, the processing is denied if there are pending transactions.
Annual periodic processing - Stock

For this process to be possible, the same conditions must be met as previously mentioned ( stock status).
This processing is used for:

  • the update of the last annual process date in the product-site,
  • the return to zero of the total annual receipts and issues. Depending on the parameter value, the processing is denied if there are pending transactions,
  • the return to zero of the stock counts running for stock parameters.
Depreciation expenses

It is necessary to generate the depreciation expenses independently of the year-end process because it does not generate them automatically, it does not check whether they exist or not, and it does not turn the closing process into a blocking process.
In case of disposal of fixed assets, the application automatically generates a DAP entry.
If a fixed assets acquisition is carried out on a closed period, the calculation start date is necessarily included in an open period.

SEEINFO If the depreciation expenses are launched in real mode during the fiscal year, the application generates depreciation expense entries along with book vs. tax depreciation entries. 

Close

 

Fields

The following fields are present on this tab :

Grid Selection

this is the code of the Company on which the processing of FY end entry generation will be launched.
The processing can be launched on several Companies in parallel , and for a given ledger type. If the FY end entry generation concerns several ledgers, the function must be relaunched.

  • All ledgers (field TOUREF)

The fiscal year-end processing can be launched for all ledgers associated with the account core model of the current company. In this case, there are several types of journals:
  • Ledger (field LEDTYP)

This function is used to close a fiscal year for a company and to generate in general accounting the corresponding carry forward postings.

It is necessary to specify the entry and journal type for which the entries must be generated.
  • New fiscal year (field DATFIYNEW)

Indicate the start date for the following fiscal year.

The type (or types) of journals used must be single-ledger.

Specify the journal concerned by the carry-forward entry generation.

 

 

Block number 2

  • Detailed log file (field TRACE)

The flag Detailed log makes it possible, if checked, to obtain a summary of all the generated journals at the end of processing.
  • Simulation (field SIMUL)

Select the Simulation check box to run a test of the journal entry and associated carry-forwards without creating a permanent journal entry.

You can run a simulation multiple times to verify results. When you are satisfied with the results of the simulation, be sure to clear the Simulation check box to run the Fiscal Year End process and create the actual journal entry and associated carry-forwards.

Close

 

Batch tasks

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

Specific Buttons

The following fields are included on the window opened through this button :

  • Memo code (field CODE)

You use a memo code to save the criteria applied to an entry screen. Use this field to find out if a memo code has already been saved for the current screen values.

Use the following buttons to manage memos:

Recall: Recall a previously defined and saved memo.

Memo: Save the current values of the screen in a memo file with a code to be specified.

Del. Memo: Delete a previously saved memo.

If a memo named STD (standard) is associated with the screen, it is loaded when opening the function.

Close

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

If a memo code entitled STD is associated with the screen, it is loaded immediately on entering the corresponding function.

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

Click this action to enter a Memo code previously saved and change the setup.

Click this action to delete a Memo code.

Error messages

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

All the periods are not closed

It is necessary to close the open periods in the fiscal year to be closed.

Fiscal year XXX not open

The carry-forward entries will be generated in the first period of the fiscal year to be closed + 1. The fiscal year in which the entries have been generated is closed.

Period XXX not open

The carry-forward entries will be generated in the first period of the fiscal year to be closed + 1. The period is not opened.

No site attached to company XXX

The option for generating an entry by company is kept. The site specified in the header of the carry-forward entries corresponds to the company's main site. And yet, the company does not have a main site.

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 parameter FRADGI/chapter TC/group CPT is 'yes'), the documents generated by the processing have the status 'Final'.

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 parameter FRADGI/chapter TC/group CPT is 'yes'), the documents generated by the processing have the status 'Final'. 

Impossible to place an exclusive lock on the company

It is not possible to lock a company if it is subject to updates in another function.

Tables used

SEEREFERTTO Refer to documentation Implementation