Change Log:

• September 29th 2021- IMPORTANT: SUNAT Changed the definition of 2 concepts (LegaMonetaryTotal at header level, and AllowanceTotalAmount), it will impact validations. This wiki is in  update process:

• LMTLEAMTV1 - before: eDc Hd Ttl Amt noDisc noTax,     now: eDc Hd Ttl Amt +Disc noTax=> discounts and global surcharges must be added
• LMTATAMTV1 - before: all surcharges and discounts,       now: only those not affecting the taxable amount

Introduction

Tax office requested that all the monetary information MUST BE PRESENT in the comercial and accounting systems, and not just in the XML presented, so this wiki provides sample pricing elements to help customers generate invoices compliant with the regulations.

Consider reading the blog https://blogs.sap.com/2020/06/19/invoicing-in-peru-via-sap-sales-distribution-pricing-details-required-from-sunat/ where the semantic meaning of each element are explained before proceeding to the configuration.

Note sometimes the IGV is referenced as “VAT” as it is a similar tax in English

Understanding taxes reporting

As explained in the Blog, tax information and the corresponding business reason must be reported. This is driven by configurable catalog 7 (issued and updated from SUNAT side on regular basis). Also, the entries from catalog 7 must be aggregated using catalog 5 at header level.

Notice the access sequence to report the taxes must contemplate the Order Reason.

Also, since this is not required in accounting, all these conditions are statistical. What is important to consider is that whenever a condition value must be transferred to SAP Document Compliance, it must be marked as printable (A,B,C,a,b,c) to keep consistency with the rest of the SAP ERP functionality.

Subtotals are not sufficient as SUNAT reporting requirements include taxable amounts and other elements that are supported with conditions.

Sample statistical conditions and subtotals used in this document (sorted in feasible order)

Notice, if you are already generating invoices in a Peruvian company code, all this information should have been already considered as part of your pricing schema (not necessarily statistical!), so only minor adjustments to pricing should be required for transparent reporting purposes. Namely, as such, most of these entries and rules must be already in your current pricing procedure, it is not necessary to create or modify them.

Sample pricing adjustments for Peruvian Companies

Assuming standard SAP pricing is used as basis, some extra elements might need to be added in order to generate all legally required reporting values:

* 100 = gross / 811: sample surcharge e.g. Freight / 809-810: sample discounts

Monetary Information to be contained in billing documents

This is the list of UBL 2.1 constructs requested from SUNAT and the corresponding definition

Summarization Rules

In order to prevent warnings in CDRs (official approval from SUNAT or designee OSE), it is required to perform all corresponding summarization for the legal monetary totals section, see this example:

Relevant Pricing Components

Notice: specific VOFM transaction routines are not provided, customers are required to perform specific calculations:

Requirements

Some subtotal or tax exclusions might be required to eliminate items not required

Formula Condition Values

To produce the required information, e.g. the detraction rules in particular, requires specific calculations.

Formula base values

When the unit price is required, the quantity for the condition must be set to the unit.

Printing Indicators

As explained above, all new printing indicators must be used (cannot be combined with old as that is not supported from SD side). It is important to configure this pricing indicator in such a way that it keeps records of empty or zero value tags when requested by SUNAT.

Relevant Catalog Tables - Sample Data

Tax Offices provides catalogs to map the XML semantic information. The information is highly dynamic, SAP does not deliver the content, it must be completed and maintenained from the SUNAT validation spreadsheets (Validations) updated normally on monthly basis.

The first column of each catalog table is a FREE key, you can define any value (Catalog Item Code - this is ment to be mnemotechnical)

Sample rows for catalogs 5 and 7:

Catalog 5 - Tax Types, etc.. summarized at header level

Catalog 7 - Types of Tax Impact detailed at line item level

Catalogs 09, 10, 16, 51, 53 and 54 have to be filled up in a samilar fashion from SUNAT latest validation spreadheet. Remember the first column (Catalog item code) is free and should be used to generate mnemotechnical codes.

Catalogs Metadata

Catalog Metadata explains SUNAT the reference information used for semantic, this information is not changing frequently

Amounts Mapping (view EDOPEMAPAMOUNTV)

Amount mapping transfer the pricing information to the XML constructs.

Press F1 in the XML Node ID column to read the SUNAT definition for the element.

Sample data for Invoice (copy to credit note, debit note, boleta, etc...):

Sample Pricing  Coding snippets for particular element (VOFM transaction)

This is a list of sample pricing requirements and value calculation useful to produce SUNAT required values.

DISCLAIMER: Notice these snippets are highly dependent on the existing pricing configuration and can be used only as reference if needed and adjusted accordingly. SAP has neither responsibility nor support for any of the snippets.

Pricing Requirements:

950 - How to turn on and off header level elements (not required, but useful for business user)

  *********************************************************************
* Monetary Totals configuration
* Header level subtotal
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM KOBED_950.
* Turn off header level sub total for items
  if KOMP-KPOSN = '000000'.
    sy-subrc = 0.
  else.
    sy-subrc = 4.
  endif.
ENDFORM.


FORM KOBEV_950.
  sy-subrc = 0.
ENDFORM. 

951 - How to turn on and off item level elements (not required, but useful for business user)

  *********************************************************************
* Monetary Totals configuration
* Item level subtotal
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM KOBED_951.
* Turn on item level sub total for items
  if KOMP-KPOSN = '000000'.
    sy-subrc = 4.
  else.
    sy-subrc = 0.
  endif.
ENDFORM.


FORM KOBEV_951.
  sy-subrc = 0.
ENDFORM. 

952 - How to exclude repeating VAT conditions at item level (can be also achieved using conditions groups if preferred)

*********************************************************************
* 
* Tax exclusion at item level
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM KOBED_952.

FIELD-SYMBOLS: <xkomv> type komv_index,
                 <komv>  type komv.


data w_remove like sy-subrc VALUE 0.   " 999 --> remove, 0 ---> stay


* Check if VAT condition is already set
loop at XKOMV ASSIGNING <xkomv>
where KPOSN    = KOMP-KPOSN.

if <XKOMV>-KSCHL = 'EDCC'
or <XKOMV>-KSCHL = 'EDCE'
or <XKOMV>-KSCHL = 'EDCB'
or <XKOMV>-KSCHL = 'EDCD'
or <XKOMV>-KSCHL = 'EDCA'.
           w_remove = 999.
exit.
endif.
endloop.

if w_remove = 999.
  sy-subrc = 4.
endif.

ENDFORM.


FORM KOBEV_952.

ENDFORM.

953- How to exclude repeating VAT conditions at header level 

*********************************************************************
* VAT exclusion at header level
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM KOBED_953.

FIELD-SYMBOLS: <xkomv> type komv_index,
                 <komv>  type komv.
data w_remove like sy-subrc VALUE 0.   " 999 --> remove, 0 ---> stay

* Check if VAT condition is already set
loop at XKOMV ASSIGNING <xkomv>
where KPOSN    = KOMP-KPOSN.

if <XKOMV>-KSCHL = 'EDCI'
or <XKOMV>-KSCHL = 'EDCJ'
or <XKOMV>-KSCHL = 'EDCK'.
           w_remove = 999.
exit.
endif.
endloop.

if w_remove = 999.
  sy-subrc = 4.
endif.


ENDFORM.


FORM KOBEV_953.

ENDFORM.

954- How to Turn On and Off Free of charge conditions

***********************************************************************
* This item determines the free of charge based on the total amount
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM KOBED_954.
  sy-subrc = 4.
if KOMP-KPOSN ne 0 and KOMP-NETWR eq 0.
    sy-subrc = 0.
endif.
ENDFORM.


FORM KOBEV_954.
  sy-subrc = 0.
ENDFORM.

Condition Value:

980- List Price

*********************************************************************
* List Prices - calculate list price
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM FRM_KONDI_WERT_980.

FIELD-SYMBOLS <xkomv> type komv_index.


*search for basic price

loop at XKOMV assigning <XKOMV>
where KSCHL = 'PR00'.
    xkwert = <XKOMV>-kbetr.
endloop.

ENDFORM.

981- Net Unit Price

*********************************************************************
* Net Unit Price - calculate final unit price
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM FRM_KONDI_WERT_981.

FIELD-SYMBOLS <xkomv> type komv_index.

loop at XKOMV ASSIGNING <xkomv> where stunr = xkomv-stunB. "← adjust as appropriate
 xkwert = <xkomv>-KBETR.
 exit.
endloop.

ENDFORM.

982- Detraction statement, maximum percentage selection

*********************************************************************

* Peruvian Detraction - calculate statement amount
* This requirement is ment to be used in SAP Document Compliance
* for subtotal activations (XML elements construction)
*

FORM FRM_KONDI_WERT_982.

  FIELD-SYMBOLS <tkomv> type komv.

  data lv_max_kbetr like komv-kbetr.

*search for the maximum detraction (percentage)

  loop at TKOMV assigning <TKOMV>
    where KSCHL = 'J1PD'.
     if lv_max_kbetr < <Tkomv>-kbetr.
        lv_max_kbetr = <Tkomv>-kbetr.
    endif.
  endloop.

*Apply to condition total

   xkomv-kbetr = LV_MAX_KBETR.
   xkwert = xkomv-kbetr * xkomv-KAWRT / 100000.

ENDFORM.

Helper validation spreadsheet

Since monetary values calculation is pretty complex, this sample spreasheet can be used to verify calculations. Notice that depending on your use case, the spreadsheet might need to be adjusted.