Transfer pricing in SAP: the data a controlled transaction requires

A data problem before it is a problem of price

The law deals with income tax. The calculation of these taxes is on the page for IRPJ and CSLL calculation, and the declaration of the transactions continues in the ECF.

The rules and the manual that decide what the system must keep

Each rule defines one piece of what the company must show: the rule, the proof and the declaration.

The general map of income tax rules that touch SAP is on the legislation page.

Eight kinds of link and the data each one needs

The system only knows that a transaction is controlled if the partner record says what the link is.

Paragraph 1 applies without prejudice to other cases: the underlying test is influence that leads to conditions different from market ones. The IN extends control to transactions with entities covered by arts. 24 and 24-A of Law 9.430/1996. The link changes over time, so the master record needs validity dates.

Thirteen transaction codes and where each one comes from in the system

The law defines a controlled transaction as any commercial or financial relationship between related parties, direct or indirect, including contracts and arrangements (art. 3).

The ECF separates 13 transaction codes, grouped above. The origin shown is typical, and each environment has its own design: the inventory of controlled transactions shows where each type starts and who answers for it.

Nine data items the documentation asks for and the source of each

The IN requires the Local File to carry these items, and the ERP covers only part of them.

Six lines come from SAP, two depend on client analysis outside the ERP and one mixes the two sources. Treating the groups separately avoids asking the system for what it does not have and forgetting what it has.

Six points the law requires you to look at before any comparison

The law's first step is to describe the transaction as it actually happens, and the ERP is a source for that description.

When the characteristics in the contracts and documents differ from those that result from the facts and the parties' actual conduct, the transaction is delineated by the conduct (art. 7, paragraph 2). For the system, orders, shipments, invoices and payments are evidence of conduct. A contract that says one thing and a document flow that shows another is the difference the law tells you to resolve by the facts.

What SAP's help describes for selling and billing inside the group

The price of a transaction between group companies starts in documents with different origins and roles.

1. 01

   Customer order

   The end customer orders from the selling company.

2. 02

   Intercompany order and delivery

   The delivering company receives the intercompany order and makes the delivery and goods issue.

3. 03

   Two invoices

   The customer invoice (type F2) and the intercompany invoice (type IV2) are created with reference to the delivery, after the goods issue.

4. 04

   Entry at the selling company

   The selling company posts the intercompany invoice as a purchase, because it buys the goods to resell them.

The document types named are those of the standard Customizing delivered with client 000, and each environment may use others. The help describes the flow between companies in the same system. With a counterparty abroad outside it, the data may come in another way, such as export billing, accounts payable or a manual posting.

SAP's transfer price and the law's transfer price are not the same thing

The ERP uses the phrase for inventory and result valuation. The law uses it for the tax base.

The help records that the system can keep up to three valuation approaches in parallel, in a currency and valuation profile, and that activities are not valued by these prices at that point. For services between group companies, the help does not describe this valuation.

Source: SAP help, S/4HANA, version 2025 FPS02, in Multiple Valuation Approaches and Transfer Prices: Transfer Pricing Concepts.

Services, royalties, interest and allocations: the data the posting must carry

Most of what the law calls a controlled transaction does not go through goods billing.

These operations may be accounting postings, with no source invoice. The risk is not having a key that finds them later. The common key with the partner master data and the ECF transaction code solve that search.

Six methods and the data each one requires from the system

The law lists the accepted methods. For the ERP, each one is a list of fields with the same operation key.

Six blocks of the comparability analysis and what stays inside and outside SAP

The IN lists seven typical steps, with no linear order (art. 21). Six blocks, and some of them use data from the system.

1. 01

   Period and internal comparables

   Define the period of the analysis and check whether the company itself has the same transactions with unrelated parties (IN, art. 21, I and II).

2. 02

   Sources of external comparables

   Identify the available sources and the reliability of each. This step is outside the ERP.

3. 03

   Method, indicator and tested party

   Select the method, the profitability indicator and the tested party, with documented reasoning (Law, art. 15).

4. 04

   Comparables and comparability adjustments

   Identify the potentially comparable transactions and make reasonably accurate adjustments.

5. 05

   Range and conclusion

   When the method gives a range of observations, the appropriate range decides whether the terms respect arm's length (Law, art. 16).

6. 06

   Reproducing the search

   If the tax authority asks, the taxpayer reproduces the searches of the databases used to select the comparables (IN, art. 63).

Internal comparables are the prices the company itself charges unrelated parties. They are in SAP, and extracting them with the same criteria as the controlled transaction is data work. External ones come from third-party databases.

Three types of adjustment and the trail the compensating one requires

The compensating adjustment changes the value of the transaction on both sides. The system must record the change in a way the audit can rebuild.

How the compensating adjustment must appear

When the adjustment increases the tax base or reduces the loss, items III and IV of art. 50 do not apply (paragraph 3). The ECF asks for the value of the adjustment in the transaction and the accounts used in record X371.

Four checks between the transaction, the adjustment and the ledger

The declaration of controlled transactions only holds up if the values match the accounting.

1. 01

   Value before adjustments

   The ECF asks for the value of the transaction before the transfer pricing adjustments. The report starts from the ledger and the result accounts of each transaction.

2. 02

   Adjustments in their own account

   Voluntary and compensating adjustments sit in separate accounts, so the original value and the adjustment can be read without ambiguity.

3. 03

   Compensating adjustment accounts

   Record X371 uses the account code of the taxpayer's chart of accounts (J050) and, where there is one, the cost center (J100), with the balance used and the debit or credit indicator.

4. 04

   Totals by type

   The total of each ECF transaction code must close with the sum of the transactions of that type in the ledger.

The difference report follows the method of the page on tax and accounting reconciliation, with one more key: the entity code, set by the company itself in the ECF.

Source: SAP help, S/4HANA, version 2025 FPS02: SAP Intercompany Reconciliation.

The central piece: a list with key, original value and adjustment

DFSpro designs this report together with the company's areas. Without it, the Local File and the ECF may depend on spreadsheets rebuilt every year.

Run every year with the same criteria, the report builds a comparable historical series. Three design choices define its quality: the key between transaction and contract, the level of totals and who may change a line already delivered.

Three value bands and three documents

The size of the obligation depends on the total value of controlled transactions of the previous year.

The Local File lists the largest transactions of goods and of services that add up to 80% of the total of each type. Commodities, rights, restructurings, cost sharing, financial operations and intangibles enter in full (art. 57, paragraph 2). The limit applies to the list, and the transfer pricing rule applies to all transactions.

Six records of block X where the transaction becomes a declaration

The ECF receives the transactions in its own records, and each one has a data source in the environment.

The records must be filled in by everyone who has controlled transactions, even those exempt from the Local File. They appear when block 0 shows operations abroad and with a related person. The ECF itself, with e-Lalur and mapping, is on the page for ECD and ECF.

The TDF creates the ECF report, and what remains is to check the scope

The report exists. The question is which block X records it delivers in your environment.

Checking whether records X360 to X375 are in the scope of the environment is a record-by-record check. What is left out comes in through an extension or a tool of its own, designed so the file keeps coming out of the same flow. The TDF page describes the product.

Source: SAP help, Tax Declaration Framework for Brazil, version 1.0 SP20: SPED reports and Tax Obligation Monitor.

Contract registration in e-CAC by the tenth day of the following month

Commodities have their own obligation, built around the contract and not the invoice.

Renegotiating or extending the contract requires a new registration, with the number of the original registration (art. 64, paragraph 3). The registration is required even if the PIC method ends up not being used (art. 38, paragraph 1, I). The page on foreign trade covers the import and export flow.

A simplified rule that still asks for a cost base and allocation

The simplified approach replaces the comparison with a fixed profit rate, but the proof of cost is still needed.

To use the rule, the system must show the cost base of the service and the allocation criterion between group members, proportional to each one's benefits (art. 53, paragraph 3). The same data serves cost sharing. The decision to opt for the approach is the company's.

Five dates and one permanent rule of the transfer pricing cycle

Each date depends on a data item the system must have ready before it.

1. 01

   Day 10 of the month after the contract

   Registration of the commodity contract in e-CAC (IN, art. 64).

2. 02

   End of the calendar year

   Deadline for the compensating adjustment under the rule's definition (IN, art. 48, II). Art. 50, paragraph 2, allows it up to the delivery of the ECF, with permanent record in the year of the transaction.

3. 03

   Last business day of July

   Submission of the ECF for the previous calendar year (IN RFB 2.004/2021, art. 3).

4. 04

   Three months after the ECF deadline

   Global File and Local File, through e-CAC (IN, art. 56).

5. 05

   Thirty days from the Notice of Findings

   Deadline to amend the ECF and the DCTF, only for the transfer pricing adjustments (IN, art. 67).

6. 06

   Throughout the year

   Supporting documents are organized contemporaneously with the transactions and kept available to the tax authority (IN, art. 62).

The ECF deadline and the amendment follow the page for ECD and ECF.

What the law sets for information that is late, incorrect or missing

System data reaches the tax authority through declaration and documentation. When they fail, the rule provides a penalty for each situation.

Each penalty has a minimum of BRL 20,000.00 and a maximum of BRL 5,000,000.00 (art. 35, paragraph 1). The penalty for inaccurate information does not apply to proven formal errors or to immaterial information, under the conditions the tax authority regulates. Applying it to a specific case is for the client and the client's accountant.

Thirty days, per transaction, and the trail that supports the amendment

An amendment only works if the company can reprocess a whole transaction in a few days.

1. 01

   Notice of Findings

   When the authority disagrees with the tax base, it notifies the taxpayer by Notice of Findings, before the assessment (IN, art. 67).

2. 02

   Thirty days to amend

   The taxpayer may amend the ECF and the DCTF, only for the transfer pricing adjustments.

3. 03

   Amendment per transaction

   Each controlled transaction is a matter of its own, and a partial amendment of it is not accepted (art. 67, paragraph 3).

4. 04

   Effect on the penalty

   If there is a tax credit, the ex officio penalty does not apply when it is paid in full with late-payment charges by the deadline (paragraph 5).

The rule makes the benefit depend on four requirements of the taxpayer: not acting against a binding normative act, being cooperative, making reasonable efforts and adopting coherent and justifiable criteria (paragraph 1). The system helps by showing the trail: who prepared each data item, when and with what criteria.

Three instruments of the law and the history that supports them

The law provides instruments to give predictability to those with controlled transactions.

These are paths of decision between the client and the tax authority. The system does not choose any of them, but the quality of the history decides whether the company can use any one without rebuilding the data.

What changed in 2023 and 2024 and what that requires of the master data

Whoever has operated for years with related parties carries contracts from the earlier regime.

For the system, the practical effect is the historical series: contracts signed before 2024 may have effects afterwards, and the contract start and review data must be in the master record.

Eight mistakes that make data reach the documentation wrong

The origin may be in a process or in master data, and not only in the calculation.

The mistake may be in the handover between areas. Tax defines the rule, controllership posts the value and IT maintains the master data. The reconciliation links the three ends.

Six questions to measure the readiness of the data

An answer of "I don't know" points to where next year's documentation will fail.

From the inventory of transactions to proof in a closed period

Six system deliveries, in order. The controlled transactions report is the center.

1. 01

   Inventory of transactions

   A survey of the environment's controlled transactions, by ECF type, with the source of the data and the person responsible.

2. 02

   Partner and contract master data

   Design of the fields for link, validity, signing date and renegotiation.

3. 03

   Controlled transactions report

   A report by operation key, with original value, adjustment and account, reconciled with the ledger.

4. 04

   Adjustment trail

   Record of the document, account and date of the voluntary and compensating adjustment.

5. 05

   ECF check

   Comparison of the generated X360 to X375 records with the report, and extension of what is left out.

6. 06

   Proof in a closed period

   Reproduction of a year already declared, to show that the report reaches the same value.

It can start with a SAP Tax Diagnostic or at the end of a migration to S/4HANA.

If the configuration needs code, the tax ABAP developmentcomes in, and the behavior is proved with the tax testing.

Who proves and who decides

The system shows what happened. What the company does with it is the decision of whoever answers for it.

DFSpro does not issue opinions, does not choose a method and does not set a target price. The position, the classification and the result of a controlled transaction belong to the client and the client's advisers.

Rules and manuals of reference

Law, normative instruction, ECF manual and SAP help.

Common questions about transfer pricing in SAP

Bring the list of transactions with related parties and the documentation from last year

Describe the transaction types and how the data is gathered today. The reply starts from your environment, the ECF records and who decides each point, with no price and no commitment on deadline.

To go further first: ECD and ECF in SAP and IRPJ and CSLL calculation.