## (BRA) Understanding Electronic Tax Reporting for Brazil

This chapter provides overviews of:

- Electronic tax reporting

- Custom programming

- Electronic tax reporting process

### Electronic Tax Reporting

You might be required to report taxes electronically according to the requirements of Ato COTEPE 70 of 2006, or Ato COTEPE 11 of 2007. Companies subject to the reporting requirement must report via magnetic media all of their business transactions that occurred over a period of time. The government defines the period of time (reporting date range), the required information, and magnetic media layout.

This table describes the data that companies must report:

Type of Data | Description
General ledger | Debit and credits, and accounts with a balance other than zero (0) are reported in the accounting files.
Accounts payable and accounts receivable | Transactions between the company and the customers and suppliers are reported in the customer and supplier files. All transactions, such as purchases and sales, that occurred within a period are considered without regard to status.
Fixed assets | The company's fixed assets, including retired assets, are reported in the fixed assets file.
Inventory | The stock entries, such as those for sales, purchases, inventory movement, and manufacturing, and the balance for each item, are reported in the inventory files. This information is grouped by fiscal company.
Manufacturing | The part list is reported in the manufacturing files.
Fiscal books | The information contained in the fiscal documents (notas fiscais) is reported in the fiscal documents files. Documents issued by the company and those issued by the company's suppliers are reported separately. The files are generated and grouped by the fiscal company.
General information | General information such as data about suppliers and customers, data about individual and legal entities, account master information, business units, and items are included in the electronic files.

### Custom Programming

Not all data required by the government resides in the tables provided by JD Edwards EnterpriseOne. JD Edwards EnterpriseOne provides programming to generate the registers for these blocks:

- 0, A, B, C, E, H, I, and Z for Ato COTEPE 70 of 2006.

  Additionally, the system generates records for block 9 when you complete the join block process.

- 0, C, D, E, H, 1, and 9 for Ato COTEPE 11 of 2007.

When you use the JD Edwards EnterpriseOne software to generate the registers for these blocks, the system creates all of the registers for the block, but populates only those registers for which data resides in JD Edwards EnterpriseOne tables.

You must create custom programs to process data that does not reside in the JD Edwards EnterpriseOne tables and write that data to these tables:

- Electronic Reporting – Process Header (F76B05210) and Electronic Reporting Processing Details (F76B05211) for tax reporting according to Ato COTEPE 70 of 2006.

  After you write data to the F76B0530 and F76B0531 tables, you can run the Electronic Reporting Join Blocks Process program (R76B0640) to populate the Text Processor Header table (F007101) and Text Process Detail Table (F007111) and generate the flat files that you submit to the government. These flat files will include the data from the JD Edwards EnterpriseOne tables as well as the data that you process from other sources.

- Ato Cotepe Process (F76B0740) and Electronic Reporting Processing Details (F76B0511) tables for Ato COTEPE 11 of 2007.

Your custom programming should include data for:

- The registers in that are not populated by JD Edwards EnterpriseOne programming.

- Blocks for which you must report data and that JD Edwards EnterpriseOne programming does not generate.

- JD Edwards EnterpriseOne tables that you have modified.

For Ato COTEPE 11 of 2007, you must include your custom programs when you set up sequencing in the Ato Cotepe Block Setup program (P76B0730).

### Electronic Tax Reporting Process

The electronic tax reporting process consists of generating data for reporting and then sending that data to the government.

The data that you generate includes:

- Blocks

  Blocks include groupings of registers with similar information. For example, block H includes information about inventory.

- Registers

  Registers include records, which are detailed information for each register. JD Edwards EnterpriseOne programming creates all of the registers for the blocks that it generates, but populates the detailed information only for the data that resides in JD Edwards EnterpriseOne tables.

  For example, registers for block H include the inventory total amount (register H005), inventory quantities of each item (register H010), the parts lists for manufactured items (register H030), and so on.

- Records

  Records are the details of the information for the register.

  For example, records for the part list for manufactured items (register H030) include information about quantity and unit of measure for the part that was saved to the Bill of Materials Master table (F3002).

Important! You must set up a single entry job queue to ensure the correct execution sequence of batch applications. If the job queue allows more than one entry, two processes could be executed at the same time, which could cause transactions integrity issues.

Ato COTEPE 70 of 2006

You use the Elec Rpt Extractor Process program (P76B0510), to create the blocks, the registers for the blocks, and populate the records for the registers for which data resides in JD Edwards EnterpriseOne tables.

After you generate the data, you can review it, and then run a process to join the data in the registers and generate a flat file that you submit to the government.

To use the tax reporting process provided by JD Edwards EnterpriseOne:

1. Set up the system for tax processing.

   See (BRA) Setting Up Your System for Electronic Tax Reporting.

2. Use the extractor process to generate the blocks and registers supported by JD Edwards EnterpriseOne programming JD Edwards EnterpriseOne tables.

   See Extracting Data for Tax Reporting.

3. Review data generated by JD Edwards EnterpriseOne programming.

   See Reviewing Records Generated by the Extraction Process.

4. Run your custom programming to populate blocks and registers for which data do not reside in JD Edwards EnterpriseOne tables.

5. Run the Electronic Reporting Join Blocks Process program (R76B0640) to generate block 9 and populate the Text Processor Header table (F007101) and Text Process Detail Table (F007111) and generate the flat files.

   See Joining Data into Flat Files.

Ato COTEPE 11 of 2007

You use the Ato Cotepe 11 Administ Process program (P76B0740) to generate the blocks, the registers for the blocks, and to populate the records for the registers for which data resides in the J.D. Edwards OneWorld or JD Edwards EnterpriseOne tables. If you set up the Ato Cotepe Block Setup program (P76B0730) with custom programs, the system also generates block, registers, and records for which you run your custom programs.

After you generate the data, you can review the text file and copy the text files to media that you submit to the government.

To use the tax reporting process provided by Oracle:

1. Set up the system for tax processing.

   See (BRA) Setting Up Your System for Electronic Tax Reporting.

2. Set up blocks and specify the sequencing for the programs to run.

   See Specifying Blocks, Versions, and Sequencing.

3. Generate the blocks, registers, and records; and populate the text files.

   See Extracting Data for Tax Reporting.

4. Review the data generated.

   See Reviewing Records Generated by the Extraction Process.

5. Copy the text files to media to submit for tax reporting.

   See Working with the Text File Processor.