Accounting period control
Use this parameter to ensure consistency between financial data records and fixed assets data records during a fiscal year/period breakdown.
When set to Yes for a company, the following controls are enforced:
In Financials
You cannot close a period under these conditions:
- If it is the current period of a depreciation context.
- If this period is an open period of the depreciation context and the posting for this period is Actual.
- If this period is not closed in Fixed assets.
Any modifications to the fiscal year or period breakdown related to a ledger type will desynchronize the depreciation contexts for the company using this ledger.
If at least one context of the company is desynchronized, you can no longer perform single or mass processes like revaluation, depreciation, method change, closing, etc., in Fixed assets for this company. Because closing in Fixed assets is prohibited, you also cannot close in Financials.
You can view the desynchronization status of a context in the Status of contexts function and click the looking glass icon on a line. This opens the Detailed status screen to see why the context is desynchronized in the Calculation section. The Type of modification field displays CNX, which indicates that a context has been modified. The Modified parameter field value is DESYNC. In addition, when you access the Fixed assets function (GESFAS), you receive a notification if a depreciation context is desynchronized.
To resolve this problem, you must run a Context synchronization process.
In Fixed assets
You can only create a context if the following conditions are met:
- The fiscal year/period division has been created in accounting management (automatic division upon company creation).
- At least one fiscal year and one period are open in accounting management. The current accounting period in Fixed assets is also open.
- At least one additional fiscal year (open or not) is defined after the first fiscal year opened in accounting. This is needed so that the next fiscal year at the level of the Fixed assets can be created.
Note: The "next" periods in Fixed assets do not need to be open in Financials. - The context breakdown is automatically performed as follows:
- The first fiscal year opened is the current fiscal year for the context.
- The first period opened is the current period.
You cannot directly modify the fiscal year/period breakdown.
After you extend a period in Financials, run the Contexts synchronization process to extend the period in Fixed assets.
You cannot shorten a period.
After you shorten a fiscal year in Financials, run the Contexts synchronization process to shorten the fiscal year in Fixed assets.
You can only open a period if it is open in Financials.
You can only change the posting type of a period from Simulation to Actual when the period is open in Financials.
If at least one context of the company is desynchronized, you can no longer perform single or mass processes like revaluation, depreciation, method change, closing, etc., in Fixed assets for this company. In addition, when you access the Fixed assets function (GESFAS), you receive a notification if a depreciation context is desynchronized.
You can only close a fiscal year or period if the following conditions are met:
- The next period (next current period) is open in Financials, even if you are closing a fiscal year.
- The context must be synchronized with Financials.
When the context posting type is Simulation, you can close the period in Fixed assets even if it is closed in Financials. When generating entries in Actual mode, accounting entries related to the closed period are generated for the first period open in Financials. In this case, in Automatic journals, the First date check box must be selected.
Level of localization/Global variable
This parameter is defined at the level Company. It belongs to Chapter AAS (Fixed assets) and the Group CPT (Accounting Rule), The following parameters are also associated with this chapter and group :
No global variable is associated with it.
Linked parameters
The following parameters are linked to the parameter ACCPERCTL :
Common Data
FRADGI (defined at level Company) : French fiscal regulation
Functions concerned
The following functions are associated with this parameter :
Fixed assets > Processes > Depreciations > Depreciation calcs
Fixed assets > Processes > Depreciations > Period and FY closing
Fixed assets > Processes > Utilities > Context synchronization
Fixed assets > Processes > Depreciations > Provisional flows generation
Fixed assets > Processes > Depreciations > Impairment
Fixed assets > Processes > Movements > Asset disposal
Fixed assets > Processes > Movements > Depreciation method change
Fixed assets > Processes > Depreciations > Revaluation
Fixed assets > Processes > Movements > Mass asset split
Fixed assets > Processes > Movements > Accounting allocation change
Fixed assets > Processes > Movements > Analytical/geographic transfer
Fixed assets > Processes > VAT adjustment > Assets
Fixed assets > Processes > VAT adjustment > Global
Setup > Fixed assets > Depreciation contexts
Fixed assets > Fixed assets > Assets
Common data > General accounting tables > Fiscal years
Common data > General accounting tables > Periods
Fixed assets > Fixed assets > Production plan
Fixed assets > Processes > VAT adjustment > Expenses
Fixed assets > Processes > Status of contexts
Fixed assets > Processes > Account. interface > Generation of accounting entries
Comments
The default values and modification terms for this parameter value rely on the FRADGI - French fiscal regulation parameter value and on the company legislation.
At the folder level: The default value is No.
At the FRA legislation level: The default value is Yes.
At the company level:
- If the company submits to French legislation: The default value is Yes and cannot be modified if the FRADGI parameter is set to Yes.
- The default value is No and can be modified if the FRADGI parameter is set to No.
If the company does not submit to French legislation, the default value for this parameter is No, but it can still be modified.
If you change the parameter value from No to , then for each managed context, you need to link all plans to the same ledger.