Product Information
Magnetic Media Compliance Reports: The 1005 and 1006 Report Formats
¿Quiere leer este post en español?
This is the first post of a series about the report formats that you receive by default when you install magnetic media compliance reports for Colombia in ACR. The objective of this series is to give you more details about these report formats so that you become able to make the configurations to run them correctly in your system.
To start with the report-formats series, let’s go through the basics you need to know about the 1005 and 1006 report formats.
It’s important that you keep in mind that the 1005 and 1006 report formats are complementary for VAT reporting. That is, sales VAT taxes are reported in the 1006 report format, but VAT taxes of returned sales are reported in the 1005 report format.
The same applies to purchase VAT taxes, which are reported in the 1005 report format, but VAT taxes of returned purchases are reported in the 1006 report format.
This relationship of the 1005 and 1006 report formats for VAT reporting implies that the configuration of these two report formats must be the same. All VAT tax codes used by the company must be entered in the configuration of the report formats. You find the detailed configuration steps below.
Consumption taxes are only reported in the 1006 report format. Generated and returned amounts on sales are reported in the ICON field. So, to identify tax codes related to consumption taxes, you need to classify them as ICON. You also find more details about this in the section about configuration settings in this post.
The 1005 Report Format
What is the 1005 report format?
You use the 1005 report format to report deductible VAT (value-added tax) values of purchases from third parties, and generated VAT values of sales from third parties that were canceled, terminated, or returned. All these values correspond to the prior year.
Find below the information reported in the seventh version of the XML file that you inform to DIAN (Dirección de Impuestos y Aduanas Nacionales) when you run the 1005 report format in the Run Compliance Reports app:
|
ATTRIBUTE |
TITLE |
TYPE |
LENGTH |
CRITERIA |
|
tdoc |
Document type |
int |
2 |
According to what is specified in the DIAN resolution. This data must be always reported. |
|
nid |
Identification number |
string |
20 |
Fill this data without hyphens, periods, commas or blank spaces. This data must be always reported. |
|
dv |
Verification digit |
int |
1 |
For the 31-document type (NIT). Report this data if you have this information. |
|
apl1 |
First surname of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
apl2 |
Second surname of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
nom1 |
First name of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
nom2 |
Other names of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
raz |
Social reason |
string |
450 |
This data is mandatory for legal persons. |
|
vimp |
Deductible tax |
double |
20 |
This data must be a positive and whole number. Do not include periods or commas. This data must be always reported. |
|
ivade |
VAT returns on canceled, terminated or completed sales |
double |
20 |
This data must be a positive and whole number. Do not include periods or commas. This data must be always reported. |
You can find more information about the technical details of the report formats in the DIAN portal: https://www.dian.gov.co/.
How to configure the 1005 report format
Before running the 1005 report format, you need to configure data sources for the extraction. To do so, all you have to do is to specify all the VAT identification codes and the key account codes in the Maintain VAT Codes customizing activity.
To access this customizing activity, go to SAP Customizing Implementation Guide > Financial Accounting > General Ledger Accounting > Periodic Processing > Report > Statutory Reporting: Colombia > Magnetic Media (DIAN) > Configure Data Sources for Report Formats > Maintain VAT Codes.
In the Maintain VAT Codes customizing activity, you find the following view:
In this view, you specify all the VAT identification codes that are relevant for the 1005 report format – which are the VAT identification codes for input taxes (purchase) and for output taxes so that you’re able to see amounts coming from sales returns.
You also inform:
- Procedure
- VAT Tax Code
- Account Key
- Validity period
You don’t need to fill the Amount Classification column, since values are automatically classified according to their tax type (input values go to the VIMP table, whereas output values go to the IVADE table).
Ready! After setting this configuration, the solution automatically extracts and organizes relevant data in the output XML file when you run the 1005 report format.
See below the steps to run the 1005 report format:
Advanced Compliance Reporting (ACR) – Run Compliance Reports app
Execution example: 1005 report format
Execution example: 1005 report format
Execution example: 1005 report format
Execution example: 1005 report format
Execution example: Analytics in 1005 report format
Execution example: Output XML file of 1005 report format
The 1006 Report Format
What is the 1006 report format?
You use the 1006 report format to report the following values:
- Generated VAT taxes on sales
- Consumption taxes on sales
- VAT returns on canceled, terminated or returned purchases
Find below the information reported in the seventh version of the XML file that you inform to DIAN when you run the 1006 report format in the Run Compliance Reports app:
|
ATTRIBUTE |
TITLE |
TYPE |
LENGTH |
CRITERIA |
|
tdoc |
Document type |
int |
2 |
According to what is specified in the DIAN resolution. This data must be always reported. |
|
nid |
Identification number |
string |
20 |
Fill this data without hyphens, periods, commas or blank spaces. This data must be always reported. |
|
dv |
Verification digit |
int |
1 |
For the 31-document type (NIT). Report this data if you have this information. |
|
apl1 |
First surname of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
apl2 |
Second surname of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
nom1 |
First name of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
nom2 |
Other names of who is reporting |
string |
60 |
This data is mandatory for natural persons. |
|
raz |
Social reason |
string |
450 |
This data is mandatory for legal persons. |
|
imp |
Generated tax |
double |
20 |
This data must be a positive and whole number. Do not include periods or commas. This data must be always reported. |
|
iva |
VAT returns on canceled, terminated or completed sales |
double |
20 |
This data must be a positive and whole number. Do not include periods or commas. This data must be always reported. |
|
icon |
Consumption tax |
double |
20 |
This data must be a positive and whole number. Do not include periods or commas. This data must be always reported. |
You can find more information about the technical details of the report formats in the DIAN portal: https://www.dian.gov.co/.
How to configure the 1006 report format
You also need to configure data sources for extraction in the 1006 report format. To do so, you have to enter VAT codes in the Maintain VAT Codes customizing activity too.
The path to access this customizing activity is the same as in the 1005 report format (see the images above). Go to SAP Customizing Implementation Guide > Financial Accounting > General Ledger Accounting > Periodic Processing > Report > Statutory Reporting: Colombia > Magnetic Media (DIAN) > Configure Data Sources for Report Formats > Maintain VAT Codes.
In this view, you specify all the VAT identification codes that are relevant for the 1006 report format – which are the VAT identification codes for output taxes (sales) and for input taxes so that you’re able to see amounts coming from purchase returns.
At this time, after entering the VAT codes, you also have to specify if they are values of consumption tax in the Amount Classification column.
Values that are classified as consumption tax in the Amount Classification column go to the ICON table. Other values are automatically classified according to their tax type (input values go to the IVA table, whereas output values go to the IMP table).
The 1006 report format configuration is done! Now the solution automatically extracts and organizes relevant data in the output XML file when you run this report format.
See below the steps to run the 1006 report format:
Advanced Compliance Reporting (ACR) – Run Compliance Reports app
Execution example: 1006 report format
Execution example: 1006 report format
Execution example: 1006 report format
Execution example: 1006 report format
Execution example: Analytics in 1006 report format
Execution example: Output XML file of 1006 report format
We hope this post is useful for you.
You find all the documentation for magentic media compliance reports for Colombia in the SAP Help Portal, under help.sap.com/viewer/s4h_op_colombia.
If you have doubts about Magnetic Media in Colombia, you can also refer to SAP FAQ Note for Magnetic Media.
Are you missing any information about the magnetic media compliance reports? Let us know in the comments. Your doubt can be the subject of our next post.
And don’t forget to follow the Advanced Compliance Reporting tag to stay tuned on news about Magnetic Media in ACR for Colombia.
See you next time and stay compliant ?,
Rosana
#ACR #SAPGoGlobal #SAPLocalization
If you enjoyed this post, you may be also interested in this one: Reporte de Medios Magnéticos: Lo que usted socio tiene que saber
This post was translated from English into Spanish using the SAP Translation Portal. Check it out!
Hi there Rosana,
thanks for sharing these report overviews. Just wondering if the design studio report that show the contents of the file are delivered by standard SAP or you need to design your own reports per format?
Kind regards,
Hans.
Hi Hans,
The analytical views that show the contents of the file and the XML file mapping are delivered by SAP but you can add or change depending on your contract if the CDS View has a specific Annotation @MetadataExtension set as true.
Still, there are limited annotations that you can use in that case.
Thank you for your question.
Kind Regards,
Matheus Bica
Hi Rosana,
Thank you very much for the detailed explanation. This is very helpful. I started doing the config for Report Format 1005. However I am stuck at a place what Tax Number Type to be assigned to the Tax Categories CO1 to CO5. Also I am trying to Map Tax Number Type to DIAN Identification Document but only values I see in the drop down for Tax Number Types are for Argentina, not the ones applicable for Columbia. Is there any SAP Note where I can find what values are to be configured for Columbia?
Best Regards
Madhu Vutukuri
Hi Rosana,
Sorry for reposting again. I did not find any solution. the tdoc tag is coming empty for me.
Thank you very much for the detailed explanation. This is very helpful. I started doing the config for Report Format 1005. However I am stuck at a place what Tax Number Type to be assigned to the Tax Categories CO1 to CO5. Also I am trying to Map Tax Number Type to DIAN Identification Document but only values I see in the drop down for Tax Number Types are for Argentina, not the ones applicable for Columbia. Is there any SAP Note where I can find what values are to be configured for Columbia?
Hi Madhu,
For the Tax Number Categories you can refer to the SAP KBA 3100751. As mentioned in there, you receive by default the CO1 (Colombia: NIT Number) mapping and it is visible to you already when you set the tax number category in the BP. But, you can also refer to the SAP Note 2684302 for the others (CO2 to C05).
Regarding the map of the Tax Number Types to DIAN Identification Document, it is done via the maintenance views V_1ATODC (Definition of Tax Number Types) and FICODIANV_DOCTYP (Map Tax Number Type to DIAN Identification Documents). The first one (V_1ATODC) is used to maintain the tax number types by its key and description. The second one (FICODIANV_DOCTYP) is used to configure the mapping by associating the tax number type key to an identification document. All DIAN identification documents are already mapped to the correct document number internally in the table, so you do not have worry about that.
I hope it helps! In case you have more questions, please just ask them here.
Thanks for your question.
Kind regards,
Romeu Klering
Hi Romeu,
Thank You very much for the quick response. I was able to review the table V_1ATODC. But then entries in it all belong to Argentina. My question is what are the relevant entries for Columbia. Based on the DIAN requirement, the below is required to show in tdoc.
My question is what values should I maintain in V_1ATODC so that I can then map them in FICODIANV_DOCTYP in DIAN TDoc field so that it shows up in TDoc xml tag. Right now I entered the below values in V_TFKTAXNUMTYPE. Then I mapped 00 to 31 TDoc in FICODIANV_DOCTYP. Still the xml tag is coming as blank in TDoc field for the Vendor that has Tax Code in CO1.
CO1 Colombia: NIT Number BUPA_TAX_NUMBER_CHECK 00
Am I missing something?
Thanks in Advance.
Best Regards
Madhu Vutukuri
Hi Madhu,
I am sorry I did not understood your question at first.
When you define a tax number type in the maintenance view V_1ATODC, the key has no pre-defined values (even though we usually use C1, C2, ...). What is important, is the mapping of this tax number type key in the view FICODIANV_DOCTYP where you will associate it to the DIAN identification document. The numbers displayed in the "tdoc" attribute is already configured in the value ranges of the domain FICODIAN_DOC_TYPE.
Also, the tax number type key must be maintained in the business partner, in the "Customer/Supplier: Tax Data" tab, in the "Tax number type" (STCDT) field.
The customizing done in the views V_TFKTAXNUMTYPE/V_TFKTAXNUMTYPEC are not related to the views mentioned above, and you seem to have maintained it correctly.
I hope I could answer your question now. If I did not, please open a case for the component FI-LOC-FI-CO-ACR so we can better assist you.
Kind regards,
Romeu Klering
Hello Romeu,
You are spot on. It makes sense to maintain the user defined values in V_1ATODC. I followed the below documentation and also came to the conclusion that I need to maintain the Tax Number Type in BP Customer/Supplier: Tax Data. But I do not see any such field in my BP Master Data. I do not know how to bring it. The below link also says that I need to maintain the value CO1-CO (Depending upon the Tax Category applicable to Vendor/Customer) in XREF1 of the Expense Line. I do not know the significance but I did maintain using FB02.
Now my only issue is how to bring the Ta Number Type (STCDT) field to BP.
Master Data for Magnetic Media | SAP Help Portal
Appreciate your help.
Thanks and Regards
Madhu Vutukuri
Hi Madhu,
I am glad you made it. Regarding the XREF1, it is a feature supported by us for Colombia to attend some specific scenarios. You can refer to our FAQ SAP Note (2717885) for more information.
About the STCDT field enablement, our team does not cover that part as we consider a requirement that the field will be already enabled. We suggest that you reach your FI specialist to check the configurations. If you do not have one you can also open a case asking for help, I believe that the team from FS-BP or CA-BP can assist you on this matter.
Kind regards,
Romeu