Tasks to be completed when documenting an operation (from creation to publication)

 1. Enter the Title of the operation / page

2. Add the following Labels : 

    • Scope of applicability: ww, country_accounting 

    • Country or group of countries (if applicable): belux, china, france, italy, lam, nam, uk_ie, bulgaria, dach, netherlands, iberia, poland, latvia, australia, india, japan, south_korea, thailand, singapore, new_zealand, emea_transversal, apac_transversal

    • Unit and Domain according to the List of labels to be used in the Finance Service Line space

      • E.g. 1: WW Operation in Financial Accounting under domain "Central Finance Processes & Compliance":
        • Labels to be used: ww, financial_accounting, central_fin_proc_compliance

      • E.g. 2: France Operation in Financial Accounting:
        • Labels to be used: country_accounting, france, financial_accounting
          (for country operations, the Domain is always country_accounting)


3. Fill in all fields as described above

4. Name the title of each section using OPD methodology naming convention - Infinitive verb without the “to”, mainly action verb...something) - " I do something..."

5. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow 


Domain: 1. Enter the Domain identified in OPD matrix (for Country specific operations, Domain = Country Accounting)

Responsibility area: 2. Enter the responsibility area described in OPD matrix ("N/A" for Country Accounting Operations)

Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)


Scope

3. Remove the icon when not applicable


ERP

4. Remove the icon(s) when not applicable


Frequency

5. Remove the icon(s) when not applicable

 

References

6. Add the link to SAP transaction(s) (when it exists)



Forms

7. Insert the links accordingly and change the link text with the Form name



Attachments

8. Add the link to attachments or external links




Previous operation << >> Next operation



example

1. Objective and Scope

1.1. Objective of this Operation

This procedure are realized to online register of accounting dice of company 5726

His objective are prevention and guarantee of the information with the Mexican GOV, for that XLM files by transactions became available in an eventual request of GOV


1.2. Scope

Detail the scope (legal entities, etc.)

The XML files of transactions accounting performed by electronic way, should be send monthly to Mexican Government. They consists by:

  • Accounting Balance
  • Chart of Account

Occasionally may be required the Journal and Auxiliary Acounting.

The companies that have obligation of sends are Solvay Flour and Solvey Mexiacana 5726, the Cytec 7723 there’s no obligation to send, but the activities should be realized, because, if the obligation use start to demands, the Government can request the retroactive files.

2. Definitions

Definitions should be added in the Finance Glossary - Add definition and link it to respective Letter in Finance Glossary 

See Finance Glossary:


3. Tasks description

WHAT and HOW - Main content of the operation

The content should be mainly organized in 2 levels of Headings to ensure a proper link with the Table of Contents.

Select the level of heading in the "Paragraph" option.

3.1.1 ABSTRACT

CHART OF ACCOUNTS

FIGLMX_EACCT


5720 SFM0009134CA202202CT

7723 CME931021US3202202CT

5726 SME000303KAA202202CT


ACCOUNT BALANCE

 FIGLMX_EACCT


5720 SFM0009134CA202202BN

7723 CME931021US3202202BN

5726 SME000303KAA202202BN


AUXILIARY ACCOUNTING

 FIGLMX_EACCT


5720 SFM0009134CA202202XC

7723 CME931021US3202202XC

5726 SME000303KAA202202XC


JOURNAL ENTRIES

FIGLMX_EACCT

S_ALR_87012401


5720 SFM0009134CA202202PL

7723 CME931021US3202202PL

5726 SME000303KAA202202PL

3.1. I generate XML files...

In transaction FIGLMX_EACCT

Use the Variants :

5720 CHART OF ACCOUNTS

5726 CHART OF ACCOUNTS


Reporting Year: Confirm the corresponding year

Reporting Month: Confirm the corresponding month

Click to Run  

3.2. Step 1 of Task 1 (Ensure the accounts...)


Ensure that there is not any account without classification, if that was, it would be with group 2.

In this case, are correct.

Click to back.

3.3. Step 2 of Task 1 (I save the files...)

Select the local that you wish save the XML file in the field Selection Of Path and File.

The file should be saved with the name: RFC+Year+Month+CT

Examples:

5720 SFM0009134CA202202CT

5726 SME000303KAA202202CT

7723 CME931021US3202202CT

Check the option “No Character Set Conversion”


Click in

If there is any account with the same examples, it should be confirmed  with the CAM, what is the grouper code by account  of SAT, corresponding to account to include in the balance.


To select and copy the dice, check the option:

Print preview of View



Go to the item 3.2 to view how to insert a new account in balance sheet structure.


3.4. I do login on PF1...

3.4.1. Step 1 of Task 2 (I use the Mandante 020...)

Input the new account on balance structure
Connect in SAP, putting ES in the Language of Logon, as below:


3.4.2. Step 2 of Task 2 (I open the resumen...)

Go to transaction OB58

Click in position

"Fin.Stmt Vers." ZMEX for WP1

"Fin.Stmt Vers." ZMX3 for PF1

Select the line and click in Positions bal./PyG


Support File on link: https://www.gob.mx/cms/uploads/attachment/file/151586/codigo_agrupador.pdf

Click in the group below that you wish insert the account, before click in “assigner cuentar”


Fill in the account and flag both fields


After entering the data, click in:

Save after all changes are made.

4. I go to Accounting balance...

4.1. Step 1 of Task 1 

Go to Transaction:     FIGLMX_EACCT

Use the Variants  :

5720 ACCOUNT BALANCE

5726 ACCOUNT BALANCE


Reporting Year: Confirm the corresponding year

Reporting Month: Confirm the corresponding month

Run:

4.2 Step 2 of Task 1 

...

Confirm that there is no account without assigned in the folder named 2, if there is return to point 1


Click back


Select the location you want to save the XML file in the Selection of Path and File field

The file should be saved as the name RFC+Year+Month+BN

Examples:

5720 SFM0009134CA202202BN

5726 SME000303KAA202202BN

7723 CME931021US3202202BN

Check the option "No Character Set Conversion"

Click run:  

5. I go to Auxiliary accounting...

5.1 Step 1 of Task 2 

Go to Transaction:    FIGLMX_EACCT

Variants :

5720 AUXILIARY ACCOUNTING

5726 AUXILIARY ACCOUNTING

Reporting Year: Confirm the corresponding year

Reporting Month: Confirm the corresponding month

Click Run:


Click back


Select the location you want to save the XML file in the Selection of Path and File field

The file should be saved as the name RFC+Year+Month+BN

Examples:

5720 SFM0009134CA202202XC

5726 SME000303KAA202202XC

7723 CME931021US3202202XC

Check the option “No Character Set Conversion”


Click in


6. I do the Journal entries...

6.1 Step 1 of Task 1

Do the check of point 5 before realize this task!

Transaction:   FIGLMX_EACCT

Variants :

5720 JOURNAL ENTRIES

5726 JOURNAL ENTRIES

Reporting Year: Confirm the corresponding year

Posting date: Insert from 1st to last of the corresponding month

Copy the Xml File Path 

Click Run

6.2 Step 2 of Task 1

After running the report go to the transaction S_ALR_87012401

Paste the copied path from the previous transaction into the Source File field

Select the location you want to save the XML file in the Selection of Path and File field

The file should be saved as the name RFC+Year+Month+PL

Examples:

5720 SFM0009134CA202202PL

5726 SME000303KAA202202PL

7723 CME931021US3202202PL

Check the option “No Character Set Conversion”

Click Run

...


7. I check the do UUID (Folio Fiscal)...

7.1 Step 1 of Task 2

In Mexico all invoices that are issued in Mexico must contain the UUID (Folio fiscal), = Folio Fiscal is a tool with which you can know the validity of an electronic invoice to know if it is recognized by the SAT, if folio is incorrectly registered with SAP it will report error when sending the Journal entries file on the farm validator's website.

Check if all NF’s received in the Cockpit then with the UUID field filled in

Go to the transaction /cockpit/1

Include the Company Code and mark the options highlighted below

Click in the option below:

In posting date include the 1st until the last day of the month being analyzed and click save , than click in run

Make sure that all UUID so filled in the Field Folios Fiscal MX

If you have an invoice that has been issued in Mexico and does not have the Folio filled in, a request must be sent to the AP to include.

NOTE: To include/correct the folio for the purposes of electronic accounting it is only necessary to edit the FI document, and include the information in the text field indicated below:

Ex document 5100000022:

Click 2x on the vendor line:

Click Extras -> Texts

Fill in the Folio in the CFDI field: Unique Identifier


7.2 Step 2 of Task 2 (I prepare all the doccuments to post...)

Include in Shared Drive before placing the procedure in Confluence 

File support for the necessary fixes in the link

8. I validate the XLM documents

8.1 Step 1 of Task 1 

Go to the site

Fill all the information necessary.

Must validate until it contains error '123'


This is the Process number identified in the transaction in SAP, if the SAT requests any specific process to change this field in the transaction, but for validation purposes is correct:

Check the error below


Go to the cockpit transaction and select the company and period being validated as well as in point 5

Copy the UUID codes that are accusing error and make a filter in the cockpit in the field Folios Fiscal MX



Copy the FI document number and ask the AP team to correct the Folios in SAP

8. Save on Drive and share as e-mail.


Save all xml documents in the link bellow:

https://drive.google.com/drive/u/0/folders/1dbpqvWLvT4j99LPFJgssxfKW-KeBRrQr



After that, send an e-mail to Samuel Parra e Ivan Gonzales to inform that the archives are now available on Google Drive. 

To: 

Samuel Parra <samuel.parra@solvay.com>,

Ivan Gonzalez <ivan.gonzalez@solvay.com>

Copie to: 

Jose Armas <jose.armas@solvay.com>,

Adagilson Melo <adagilson.melo@solvay.com>,

Roberta Mansani <roberta.mansani@solvay.com>,

Patrik Silva <patrik.silva@solvay.com>,

Pablo Delapena <pablo.delapena@solvay.com>,

Rafaela Toniol-EXTERNAL <rafaela.toniol-external@solvay.com>,

Eduarda Pretto <eduarda.pretto@solvay.com>;  <sabrina.berton@solvay.com>


Example:

Hola Samuel y Ivan,


Los archivos de la contabilidad electrónica para la empresa 5726 y 5720 están validados, 

Incluye los archivos en Shared Drive


Podría dar el seguimiento y enviar los archivos al gobierno por favor ?

End of document.