FAQ: PIS/COFINS for Resale

Purchases

Applies to:
SAP ERP (All releases)

Summary
Several distinguished scenarios are possible regarding calculation and posting of PIS and COFINS taxes on
resale purchases. Each scenario depends both on the nature of the operation and the nature of the involved
companies, from a fiscal perspective. To cover all possible approaches, SAP notes 947218, 1063650 and
1088901 have been delivered. However, their correct usage is sometimes dubious. Taking that into account,
this paper seeks to provide an overview on the solutions and help you understand the involved concepts,
plus choosing the right customizing.
Author: Eduardo Rubia
Company: SAP Brasil
Created on: 12 January 2009

Author Bio

26 years, SAP Support consultant, part of the RCA Team. Expertise area: XX-CSC-BR*.
Broader area: Logistics. Currently located in So Paulo, Brazil.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 1
 FAQ: PIS/COFINS for Resale Purchases

Table of Contents
Introduction .........................................................................................................................................................3
Scope..................................................................................................................................................................3
Pre-requisites......................................................................................................................................................3
Solution ...............................................................................................................................................................4
1 Which are the resale scenarios currently covered by the system? .........................................................4
1.1 Scenario I: Normal resale .................................................................................................................................4
1.2 Scenario II: Industry resale ...............................................................................................................................4
2 Which SAP notes should be used for each resale scenario?..................................................................4
2.1 Scenario I: Normal resale .................................................................................................................................4
2.2 Scenario II: Industry resale ...............................................................................................................................4
3 How should the tax code look like for each scenario?.............................................................................4
3.1 Scenario I: Normal resale .................................................................................................................................5
3.2 Scenario II: Industry resale ...............................................................................................................................5
4 When should the 'IPI Contributor' flag be turned on in the Branch/Filial? ...............................................6
5 Whats the function of ICOR / PCRE condition types?............................................................................6
6 How does including PIS/COFINS in the net price influence the tax? ......................................................6
7 Why for Scenario I the Accounting document postings for PIS/COFINS dont match the PIS/COFINS
values in the Nota Fiscal tax item detail?........................................................................................................6
7.1 Background:......................................................................................................................................................7
8 My companys scenario is not covered by the available solutions or my company is not satisfied with
the system logic. How to proceed? .................................................................................................................7
Copyright.............................................................................................................................................................8

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 2
 FAQ: PIS/COFINS for Resale Purchases

Introduction
This paper seeks to provide an overview on the purchases for resale solution involving PIS and COFINS in
Brazil. Also, through answers to FAQs, we hope to help you understand the involved concepts, plus
choosing the right customizing to fit your actual scenario

Scope
Important: this SAP paper aims to help customers and consultants understand the scope of the solution. It
does not intend to provide reference for legal interpretation. Any disagreements must be punctually
discussed with the involved companies legal division and if needed, also ASUG. See question 8.

Pre-requisites
SAP note 947218 must be applied.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 3
 FAQ: PIS/COFINS for Resale Purchases

Solution
Below follows a set of Frequently Asked Questions and their corresponding answers

1 Which are the resale scenarios currently covered by the system?

1.1 Scenario I: Normal resale

In this scenario, the following aspects characterize the process:
The buying Branch is not an IPI Contributor and the material usage is resale.
The goods are bought to be later resold. The IPI is not credited and PIS/COFINS credit values have
to be adjusted into the accounting posting.

1.2 Scenario II: Industry resale

In this scenario, the following aspects characterize the process:
The buying Branch is an IPI Contributor and the material usage is resale.
Although the usage is resale, the goods are used for industrialization. In this case, the whole process
goes on as a normal industrialization purchase.

2 Which SAP notes should be used for each resale scenario?

2.1 Scenario I: Normal resale

Code + customizing from SAP note 947218, plus subsequent coding corrections to this SAP note
(can be found in http://service.sap.com/notes)

2.2 Scenario II: Industry resale

Code + customizing from SAP notes 947218, 1063650, 1088901, plus subsequent coding
corrections to these SAP notes (can be found in http://service.sap.com/notes)

3 How should the tax code look like for each scenario?
To obtain the tax postings in the Nota Fiscal and Accounting Document according to each of the scenarios,
specific sets of configuration must be made.
Basically, the whole control is made through the tax code condition types.
To activate them, there are two ways, depending on your system release:
Up to 4.6C: transaction FTXP or the following IMG path:

4.70 and up: table/view J_1BTAXCODEV or transaction J1BTAX

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 4
 FAQ: PIS/COFINS for Resale Purchases

The relevant condition types that need to be activated for each resale scenario are described below
(according to the used Tax Calculation Procedure):

3.1 Scenario I: Normal resale

Tax Calculation Procedure
TAXBRA TAXBRJ
ICM1 ICM1
IPI2 IPI2
Active Condition Types

IPIS IPSV
IPSV IPSS
IPSS IPSU
IPSU IPSA
IPSA ICOV
ICOF ICOS
ICOV ICOU
ICOS ICOA
ICOU PCRE
ICOA
ICOR
Important: Additional conditions may be turned on/off according to the business scenario (e.g. Substituio
Tributria, Withholding Taxes, etc...)

3.2 Scenario II: Industry resale

Tax Calculation Procedure
TAXBRA TAXBRJ
Active Condition Types

ICM1 Important: This scenario

IPI1 is not supported for
TAXBRJ, although you
IPSF can at your own risk
IPSG adapt the solution from
IPSH SAP Notes 1063650 +
1088901
ICSF
ICOG
ICOH
Important: Additional conditions may be turned on/off according to the business scenario (e.g. Substituio
Tributria, Withholding Taxes, etc...)

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 5
 FAQ: PIS/COFINS for Resale Purchases

4 When should the 'IPI Contributor' flag be turned on in the Branch/Filial?

This flag should only be set for Scenario II: Industry Resale.
To activate it, navigate to the following IMG path:

Inside the branch details, youll find the flag:

5 Whats the function of ICOR / PCRE condition types?

The purpose of these condition types is offsetting the material cost for Scenario I: Normal Resale.
ICOR is used in TAXBRA
PCRE is used in TAXBRJ
For more details about offsetting of PIS and COFINS, see Question 7.

6 How does including PIS/COFINS in the net price influence the tax?
As of the implementation of SAP note 747607, where the solution for MP-135/LC-116 requirements 1 was
delivered, it became possible to define certain taxes as included or not in the purchasing/sales net price. This
is done by customizing entries in table/view J_1BKON1V.
Specifically for PIS and COFINS, the system will handle the formulas for each case automatically,
independently of setting these taxes as included or not in the net price.
Important: To ensure consistency while calculating taxes, however, the user must inform the right net price
in order to achieve the expected values both in the Nota Fiscal and in the Accounting document.
Hint: The right net price is obtained subtracting all taxes not included in the net price from the Total Nota
Fiscal value.

7 Why for Scenario I the Accounting document postings for PIS/COFINS dont match the
PIS/COFINS values in the Nota Fiscal tax item detail?
Because the vendor calculates taxes based on his selling operation, in which IPI has to be paid to the
government. On the buyers side (SAP system), though, IPI is not credited so it must be considered to
recompose the PIS/COFINS base.
Thus, in the Accounting document, the PIS/COFINS value is calculated over a base with IPI, whereas the
physical document (represented in MIRO) has PIS/COFINS calculated over a base without IPI.

1
For more details on this solution, check SAP Note 852302

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 6
 FAQ: PIS/COFINS for Resale Purchases

7.1 Background:
Particularly for Scenario I, there is a difference tax treatment between selling and buying a product. When it
comes to PIS/COFINS, and IPI is involved, what will determine the PIS/COFINS base is the goods usage.
On one side of the process chain, from the seller perspective (vendor), as the IPI is due to be paid, given that
a transformation process occurred, then it cannot be considered a part of the cost and so it is not part of
"Valor dos Produtos". With this, IPI is really not included in PIS/COFINS base for the sale.
On the other side of the process chain, the buyers perspective is different. In case of resale usage for a non-
IPI Contributor, IPI cannot be credited, as long as the purchased goods will not be industrialized, but resold.
Due to that, in the inbound step of the process, the IPI is considered to be a "cost", and costs are part of the
"Valor dos Produtos ". Being that so, IPI must be part of PIS/COFINS base too.
To recompose the PIS and COFINS base in the Accounting document, the system uses condition type ICOR
(TAXBRA) or PCRE (TAXBRJ). These conditions will calculate the difference between the PIS + COFINS
from the physical Nota Fiscal (without IPI) and the PIS + COFINS actually due (with IPI). Such difference will
increase the material cost, which was (correctly) under valuated during GR (due to the pricing condition
NAVS in the PO).

8 My companys scenario is not covered by the available solutions or my company is not satisfied
with the system logic. How to proceed?
As already outlined in the Scope section of this paper, we dont intend to provide reference for legal
interpretation. Instead, our objective is to put relevant information together and allow an easier understanding
of the available solutions for resale purchases in Brazilian Localization involving PIS and COFINS.
So, either in case the business scenario is more complex than the available solutions, or your companys
legal interpretation of the legislation differs from the solution logic delivered by SAP, please get in touch with
any users community of your preference (e.g. ASUG) or your local SAP Representative, so that relevant
points be raised for discussion, evaluated and eventually embedded into the system.
Also consider making formal consultations with Receita Federal do Brasil before enforcing changes into the
system.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 7
 FAQ: PIS/COFINS for Resale Purchases

Copyright
2008 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,
zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All
other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors
or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2008 SAP AG 8