SAP ACR (Advanced Compliance Reporting): what it produces, what it does not, and how to prove the SPED file it creates

ACR delivers the report. The data, the decision and the proof remain with you

ACR, Statutory Reporting and DRC Brazil: what each SAP text says

Seven SAP sources, with reading date. What SAP does not say comes right below.

The same work appears under different names depending on the source and the date. The table shows what each SAP text says, with no interpretation. When you talk with your team, use the name from your release's documentation, not from the latest page: that way nobody looks in the wrong help for a feature the version does not have.

For the contrast between TDF, ACR and DRC on the SAP Help side, see the page on SAP TDF, and for electronic document delivery, migration from GRC NF-e to DRC. The blog article on what DRC and ACR deliver in tax compliance gives the risk reading.

Does ACR fit my obligation?

Seven answers and the guidance comes out in three groups: where ACR helps, where it needs add-ons, and where the path is different.

In which situations ACR helps, and in which it is worth waiting

Four signs to use it and five to think twice, all taken from what the documentation shows.

Where ACR ends and DRC begins

Six points of comparison, all based on SAP's text. On mobile, each row becomes a card.

From setting up the entity to the delivered file, in eight steps

The flow that SAP's help describes for generating a SPED file through ACR.

1. 01

   Create the reporting entity

   It is the legal entity required to deliver, with one or more organizational units and a lead one. The assignment depends on time (Customizing in Document and Reporting Compliance).

2. 02

   Assign category and periodicity

   The category groups the report versions. The periodicity defines start, offset in days and a warning before the due date. SAP's example uses a 10-day offset and a warning 7 days before.

3. 03

   Find the task and filter by status

   In Run Statutory Reports, the report name and the status (completed, due soon, overdue) lead to the task. The statuses come from SAP itself: Completed, Due Later, Due Soon, Overdue and Submission Completed.

4. 04

   Open a new run

   Enter the report parameters. In EFD ICMS IPI, leaving the Record field empty generates the full file. The run can be immediate, scheduled or in the background.

5. 05

   Check the generated file

   The run appears in the Generated section. The link in the Document name column opens the TXT in the statutory report tab, and the file can be downloaded.

6. 06

   Submit outside SAP and record the status

   For the first four obligations in the table of Brazilian obligations, the help says to submit the file to the authority and update the run status to Accepted or Rejected.

7. 07

   Rectify with a new phase

   To adjust master data of an already completed SPED file, SAP opens the rectification phase, with the activity Process SPED master data, and says to run again with the same data.

8. 08

   Keep the evidence

   Parameters, file, receipt and status stay as proof of delivery. The generic help mentions an audit trail; for Brazil, this is not confirmed in the pages read.

The five SPED files SAP documents in ACR, and what each one needs to run

What SAP's help lists for each report, side by side, with the page that covers the obligation itself.

What SAP must have ready before the first file

Six groups of prerequisites, with what SAP's help says about each. Without these items ready, the first file comes out incomplete, or does not come out at all.

What ACR does, by topic, and where SAP documents it

Twenty-six features, each with the source and the reading date. Filter by topic, edition or by what Brazil confirms.

Eight points where the SPED file comes out wrong even with ACR working

Report design, version, reprocessing and evidence. For each one, what SAP states and what is judgment.

Six proofs for the ACR file before delivery

To prove is to run, compare and keep. What the help describes does not replace what your SAP does.

1. 01

   Full file versus partial file

   Generate EFD ICMS IPI with the Record field empty and compare the totals with the tax assessment. Evidence: file, parameters and reconciliation with E110 and E210.

2. 02

   Same company in three cuts

   Run by company, by state registration and by central EFD, when your case has all three. Evidence: totals that match across the cuts or an explained difference.

3. 03

   ECD and ECF in the period layout

   Confirm the reference chart of accounts, J210 and the layout version for each period. Evidence: file against the Receita manual for the period.

4. 04

   Rectification in a new phase

   Run the rectification phase with the same parameters and compare the new file with the original. Evidence: difference only in the changed data.

5. 05

   Validation in the PVA

   Import the file into the official validator of the obligation. Evidence: validator report with no pending error, kept with the run.

6. 06

   Closed period against delivered

   Run a period already delivered again, after each Note or release, and compare with the file from that time. Evidence: zero difference or a justified one.

At the end of each scenario, what closes the delivery is the evidence: parameters used, generated file, receipt, status and the person responsible for the check. The general roadmap of scenarios, criteria and evidence is in tax testing in SAP. The regression tester that SAP describes exists in the documentation, but for Brazil, confirm with SAP; use a script or your own comparison.

ACR readiness checklist ACR

Twenty items in five groups. Select what you already meet and see the gaps, with guidance for each one.

Six ACR decisions and who answers for each one

Who decides, who designs and proves, and what evidence remains.

TDF, older release, custom program and GUEPARDO: what the SAP sources support and what remains open

Three common situations and what the sources read allow us to state about each.

ACR builds the report from the tax data already in SAP. Where the tax calculation comes from is another question. GUEPARDO Tax belongs to NTT DATA. DFSpro, Authorized Channel, also implements the product and handles the GUEPARDO governance. The useful question is which data feeds each report, not which product replaces which.

Configure, prove and keep the evidence stored

Five deliveries in SAP around ACR, with the page that goes deeper into each one.

We act as specialists in tax on SAP and GUEPARDO Tax, and we also implement SAP, migrate and run rollouts. Within ACR, our part is to design, configure and prove. Day-to-day operation stays with your team, or with the support of AMS Fiscal.

Three roles, three responsibilities

To prove is to demonstrate the behavior of the system. Accepting the result is up to the company.

Want to see what the routine looks like next to your team? Read how we work with your team.

Source of each piece of information and the date it was read

Sources from SAP, the SAP community and official bodies, with the reading date of each. KBA previews are public; the full content requires login.

Pages that go deeper into what ACR leaves to other topics

Six readings that complete this one, each with its own scope.

Tell us how SPED comes out today from your SAP

Tell us the release, the obligations and the current path. We start from your answers, with no price or deadline set in advance.

To go deeper first: ancillary obligations and SPED in SAP and SAP TDF.