Purpose

The purpose of this page is to clarify the customizing and usage of Export Confirmation. In below example Export Confirmation is shown as an isolated process (without linking to incoming invoices and VAT separation). Process of VAT separation was described in SAP WIKI: Separate VAT

The old version of SAP WIKI: Export Confirmation and Separate VAT Accounting

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Overview

For charging 0% VAT export should be confirmed within 180 days. This means that all required by law documents were completed. If export was not confirmed in this timeframe than VAT with standard VAT rate will be posted. If export was confirmed late then standard VAT posted earlier for non-confirmed export can be reimbursed.

Below there is a scheme of export confirmation process without linking to incoming VAT invoices.

In this process below transactions or Fiori tiles specific for Russian localization will be used:

Fiori tile Manage EAEU Import Notifications creates document which confirms export to the country from EAEU
Transaction J3RSCD01 (report J_3RS_CCD) / Fiori app “Manage Export Customs Declaration” creates an export Customs Declaration for far abroad country
Transaction J3RSCONFIRMEXPORT (report J_3RS_EXPORT_CONF) / Fiori app “Export Confirmation (Russia)” confirms export by creating secondary events for export confirmed on time (secondary event “”) and export confirmed late (secondary event 08)
Transaction J3RSCONFIRMEXPORT (report J_3RS_EXPORT_CONF_ERR) / Fiori app “Export Confirmation Error Processing” creates secondary event for not confirmed export (secondary event 03)
Transaction J3RFUM26 (report J_3RFUM26) / Fiori app “Secondary Events” – makes VAT transfer documents for secondary events

How to check that the last version of Export confirmation is being used

Transaction J3RSCONFIRMEXPORT (reports J_3RS_EXPORT_CONF and J_3RS_EXPORT_CONF_ERR) replaces transaction J3RSEXPORT (report J_3RSINVOICE). For more details refer to SAP Note: 2847009-New Export Confirmation Report.

Minimal requirement for Transaction J3RSCONFIRMEXPORT:

SAP ERP 6.0 Release 617 and higher
SAP S/4HANA all versions

To be sure that the last version of Export confirmation solution is being used please implement all Notes relevant for your system’s Support Package using search term J3RSCONFIRMEXPORT OR J_3RS_EXPORT_CONF_ERR OR J_3RS_EXPORT_CONF and recommendations from the KBA: 2383765 - "SAP RU-FI, UA-FI, KZ-FI: How to find full list of Notes with restriction by SP on ONE Support Launchpad"

Customizing of Export tax codes

In transaction OBCG (the view V_T007K) for Grouping Version EXPT VAT Codes should be customized:

In transactions OBCG and OBCH (the views V_T007K and V_007L) for Grouping Version SHP VAT codes should be customized:

In transaction FTXP export VAT codes should have chain of three codes. In the current example:

L0 → L1 → L2:

In the view (transaction SM30) J_3RTSE_CODE alternative tax codes for secondary events should be customized:

Creation Export invoice

First create a sales order, then post an outbound delivery and a create billing document. The billing document should be released to FI with tax code assigned to Grouping Version EXPT.

Document flow for the current example:

Standard Order 56032 (transaction VA01)
Outbound Delivery 80059722 (transaction VL01N)
Billing Document 90034439 (transaction VF01)
FI Invoice 100021651

FI Invoice 100021651 has two revenue lines:

Document for Export Confirmation

For export to far abroad countries, create Customs Declaration using transaction J3RSCD01 / Fiori app “Manage Export Customs Declaration”.

For export to EAEU, create an Import Notification using the “Manage EAEU Import Notifications” Fiori app.

Countries included into EAEU should be maintained in the table FIRUD_EACU_CNTRY:

In the current example, customer is in Kazakhstan thus “Manage EAEU Import Notifications” Fiori app will be used.

Import Notification TEST_FOR_WIKI (Internal Number 0000000288) has been created for all items from Billing Document 90034439.

Export confirmed on time

If export confirmation documents have been received within 180 days from Goods Issue Date (Table LIKP Field WADAT_IST (Actual GI Date)), then export can be confirmed on time.

Mandatory document is Customs Declaration (for export to far abroad country) or Import Notification (for export to EAEU country).

In the current example document that confirms export is Import Notification TEST_FOR_WIKI (Internal Number 0000000288). For this document transaction J3RSCONFIRMEXPORT (or Fiori app “Export Confirmation (Russia)”) should be executed.

Select line (it has status “Not processed”) and press “Create Secondary Event” button. Secondary event will be created (status will be changed to “Secondary Events Created”):

As result table J_3RTSE will be updated:

When Secondary event has been created, VAT Base of export invoice can be transferred by transaction J3RFUM26 (program J_3RFUM26) / Fiori app “Secondary Events”:

As result VAT Base will be transferred to the tax code L2:

Also, table J_3RTSE will be updated with numbers of tax transfer documents:

Table J_3RTSE_REVERS will be updated:

After transfer VAT Base transaction J3RSCONFIRMEXPORT / Fiori app “Export Confirmation (Russia)” will show “green” status for event type “Export Confirmed”:

As result the amount of confirmed export will be shown in VAT Return sections 4 and 9 and in Export Confirmation Registers XML for List of Import Notification will be created:

For creation List of Import Notification for Kazakhstan in transaction BP Tax Number should be filled for Category KZ3 (3204944 - DRC Russia VAT Reporting: Business Partner for Kazakhstan in List of Import Notifications):

And relevant Operation Code should be customized in the view FIRUD_VATOPCODE:

View cluster FIRUVC_VATSUBS:

Export not confirmed

If export confirmation documents have not been received within 180 days from Goods Issue Date (Table LIKP Field WADAT_IST (Actual GI Date)), then VAT should be posted.

New document chain for this example:

First create a Technical Entry for Unconfirmed Export. It can be created from Fiori app “Export Confirmation” / transaction J3RSCONFIRMEXPORT or directly from Fiori app “Export Confirmation Error Processing” / report J_3RS_EXPORT_CONF_ERR.

When a Technical Entry for Unconfirmed Export is being created then in Fiori app “Export Confirmation” / transaction J3RSCONFIRMEXPORT secondary event “Export Not Confirmed” (Secondary event 03) can be created:

Table J_3RTSE will be updated, in the field Import Notification Internal Number (IMPORT_NOTIFICATION) number of Technical Entry will be saved:

When secondary event is created, then VAT can be posted using transaction J3RFUM26 (program J_3RFUM26 or Fiori app “Secondary Events), target VAT code will be taken from the table J_3RTSE_CODE:

Table J_3RTSE will be updated:

Table J_3RTSE_REVERS will be updated:

After posting VAT transfer documents transaction J3RSCONFIRMEXPORT (or Fiori app “Export Confirmation (Russia)”) will show “green” status for event type “Export Not Confirmed”:

As result the amount of unconfirmed export will be shown in VAT Return sections 6 and 9:

Export confirmed late

If export confirmation documents have been received after 180 days from Goods Issue Date (Table LIKP Field WADAT_IST (Actual GI Date)), then standard VAT posted earlier for non-confirmed export can be reimbursed.

First of all, Export Customs Declaration or Import Notification should be registered, then in in Fiori app “Export Confirmation” / transaction J3RSCONFIRMEXPORT secondary events for Export Confirmed Late should be created (Secondary event 08):

Table J_3RTSE will be updated:

Then transaction J3RFUM26 (program J_3RFUM26) / Fiori app “Secondary Events" can be executed, for each revenue item in export invoice two tax transfer documents will be created:

The table J_3RTSE will be updated:

The table J_3RTSE_REVERS will be updated:

As result the amounts will be shown in VAT Return sections 5 and 9 and in Export Confirmation Registers XML for List of Import Notification will be created.

Page tree