Intercompany journal creation
Use this function to generate journals in each company used in he Intercompany journal entry. You can automatically generate one or several journal transactions according to the selection criteria.
In this function, you should:
- Run the generation in provisional mode so as to identify the intercompany journals that can be generated.
- Generate a log file indicating the intercompany journals that were created and the intercompany journal recording used.
- Create or recall a memo.
- Check if the accounting period date is open for the source company and all target companies.
This function is available only if the INTCO - Intercompany transactions activity code is active.
Although the Partner and Flow fields are not part of the Intercompany journal entry function (GESGIC), the partner and flow are initialized when posting to the Intercompany journal.
French electronic signatures for sales invoices and journal entries
In compliance with French and Portuguese antifraud legal requirements and to ensure data security, electronic signatures are automatically generated when a customer invoice or journal entry is posted or set to Final, respectively. After the electronic signature is generated, further modifications to any of the fields identified below can be easily detected.
You can use the Electronic signature control function (FRADSICTL) to review the current electronic signature and highlight any inconsistencies.
See the “French electronic signature how to guide” or the "SVAT certification for Portuguese legislation guide" on the tab for details on implementing this feature. This document is intended for administrators and consultants who maintain and update Sage X3.
Exceptions
Data from invoices or journal entries posted before activating the electronic signature feature is not added to the DKSDATAFRA table and therefore no electronic signature is created.
Legislations other than French or Portuguese do not need to generate electronic signatures.
The electronic signature is a record in the Electronic signatures table (DKSDATAFRA) that includes data from the following fields in the Sales invoice (SINVOICE) and Account entries (GACCENTRY) tables:
|
Field code
|
Description
|
Data source: SINVOICE
|
Data source: GACCENTRY
|
|
ORIDOC
|
Origin of the document
|
1
|
2
|
|
DOCTYP
|
Journal
|
SINVOICE.SIVTYP
|
GACCENTRY.TYP
|
|
DOCNUM
|
Journal description
|
SINVOICE.NUM
|
GACCENTRY.NUM
|
|
TOTTAX(9)
|
Total by tax rate
|
SIH.AMTTAX(i) + SIH.BASTAX(i)
|
|
|
AMTATI
|
Invoice amount with VAT
|
SIH.AMTATI
|
|
|
DATTIM
|
Date and time of the signature
|
Datetime$
|
|
|
INVSNS
|
Document type
|
Evaluate SIH.SNS
|
|
|
CPYNAM
|
Company name
|
CPY.CPYNAM
|
|
|
POSCOD
|
Company postal code
|
BPA.POSCOD
|
|
|
CPYEECNUM
|
Company VAT number
|
CPY.EECNUM
|
|
|
BPRNAM
|
Customer name
|
SIH.BPRNAM(0)
|
BPARTNER.BPRNAM
|
|
BPREECNUM
|
Customer postal code
|
SIH.POSCOD
|
|
|
JOU
|
Journal code
|
|
GACCENTRY.JOU
|
|
DESTRA
|
Journal description
|
|
GACCENTRY.DESTRA
|
|
FNLPSTNUM
|
Final number
|
|
GACCENTRY.FNLPSTNUM
|
|
ACCDAT
|
accounting date
|
SINVOICE.ACCDAT
|
GACCENTRY.ACCDAT
|
|
ACC
|
Account code
|
|
GACCENTRYD.ACC
|
|
BPR
|
BP
|
SINVOICE.BPR
|
GACCENTRYD.BPR
|
|
LIN
|
Journal entry line
|
|
GACCENTRYD.LIN
|
|
LINDES
|
Line description
|
|
string$([F:DAE]DES<>"",
[F:DAE]DES)+string$([F:DAE]DES="","NA")
|
Prerequisites
Refer to documentation Implementation
Screen management
Entry screen
Field descriptions
Criteria
| All companies (field ALLCPY)
|
|
|
Select this checkbox to include all companies. To run this process for a single company, do not select this checkbox.
| Company (field CPY)
|
|
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)
|
|
This field specifies on which legislation the process is carried out. It can only be accessed if the box "All companies" is selected.
Note: If the company code is entered (All companies unselected), the Legislation field can not be accessed and displays the legislation parameters for the selected company.
|
| All sites (field ALLFCY)
|
|
Select this check box to include all sites. To run this process for a single site, leave clear.
|
| Site (field FCY)
|
|
Enter the site code.
The site must be a financial site. This determines the site and the company for the entry posting.
|
| All users (field ALLUSR)
|
|
Select this check box to include all users. To run this process for a single user group, leave clear.
The current user will be used if the user/group code is blank.
|
| User (field USR)
|
|
Enter the user responsible for the creation of journal entries.
|
| From entry (field STRVCR)
|
|
Enter the starting and ending intercompany entries to further define the selection. These entries will be taken into account when generating the journals.
|
| To entry (field ENDVCR)
|
|
| Start date (field STRDAT)
|
|
These two fields are used to define the date ranges. These ranges are used to filter the intercompany entries with a date included within this time interval.
|
| End date (field ENDDAT)
|
|
Generation
| Generation type (field TYP)
|
|
These options indicate the category of the documents to generate. The generated journals can be real or simulated.
- If Actual is selected, the actual accounting document can always be viewed and printed (for example, General Ledger, Balance, and so forth).
- If Active simulation is selected, the simulation document is also integrated with the inquiry screens and the printed documents. It can then be converted into an actual journal.
- If Inactive simulation is selected, the simulation document is deactivated in order to become an inactive simulation where no inquiries and reports are available.
The journal entry can be generated in simulation mode and after the verification to restart the processing in real mode. The simulation journal entry is automatically cancelled and replaced by the real journal entry which will take into account the new operations if they exist.
|
| Entry status (field STA)
|
|
Select the journal status.
- Selecting Temporary allows you to run the journal generation and modify the journals.
- Selecting Final allows you to run the journal generation and create the journal entries.
- If the company has FRADGI set to Yes, all the journal entries must be posted with a Final status.
- If the parameter FRADGIMSG is set to Yes, a warning message appears to indicate that the journal entries must be posted with a Final status.
|
| Log file (field TRACE)
|
|
Select this check box to view a log file of all intercompany journal entries based on the selection made in the Entry status section.
|
Specific Buttons
|
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.
The 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.
|
Error messages
The only error messages are the generic ones.
Tables used
Refer to documentation Implementation