Service Provider-Agnostic Solution for Electronic Invoicing in Turkey

[former_member810647]

Introduction

To date, the eInvoicing solution for Turkey supported only one particular service provider. With this change, it is now possible to integrate with any service provider in Turkey to submit electronic invoices. To integrate with another service provider, it is necessary for the provider to first create a service based on the API definition which has been published on SAP API Business Hub. This API will then be consumed by SAP for eInvoicing. The below eInvoices are supported for this solution.

1. Basic eInvoices


2. Commercial eInvoices


3. Consumer eInvoices


4. Export Registration eInvoices


5. Incoming Basic eInvoices


6. Incoming Commercial eInvoices

Additionally, the following log files have been made available for improved response tracking, which you can access by choosing Goto ->  History in the eDocument Cockpit:

• Response file from a service provider upon successful submission of documents. The file type is RESP_SENT.


• Response file from a service provider upon successful cancellation of consumer invoices. The file type is RESP_CANC.

Customizing

To enable the service provider agnostic solution, you need to configure the below value mappings for the AIF namespace /EDOTR

1. SERVICE_PROVIDER
   

   In this value mapping, you have to indicate your service provider by entering the corresponding eDocument class. Configure the value mapping as follows:

   
   
   
   
   
   • 
     
     
     
     • eDocument Class Name: If your service provider is Foriba, enter CL_EDOC_TR_SP_FIT. If you use any other service provider, enter CL_EDOC_TR_SP_GEN, this will enable the service provider agnostic solution.
     
     
     • Internal Value: SRVCE_PROV.
     
     
     
     
   
   
   
   


2. SERV_PROV_PARAMS

In this value mapping, you set the parameters that depend on service providers. The below two parameters are supported as of now:

1. 
   
   
   
   1. 
      
      
      
      1. INV_DOCTYP - This parameter is used to configure the document type for outgoing eInvoice XMLs as supported by your service provider. The available document types are 'ENVELOPE' or 'INVOICE'.
      
      
      2. PACK_SIZE - This parameter is used to control how many incoming documents can be fetched in a single request. This can vary across service providers.
      
      
      
      
   
   
   
   

You need to configure the value mapping as follows:

• 
  
  
  
  • 
    
    
    
    • Service Provider-Dependent Parameter: Choose a parameter from the input help. The available parameters include:
      
      
      
      • INV_DOCTYP (Document Type in Outgoing Invoice XML File)
      
      
      • PACK_SIZE (Size of Incoming Message Package)
      
      
      
      
    
    
    • Parameter Value: Enter the parameter value.
    
    
    
    
  
  
  
  

Please note that this value mapping needs to be configured after discussing it with your service provider, and it is only required if you are using the provider-agnostic solution.

 

Integration Flows

The below two new integration flows have been introduced in the package SAP Document and Reporting Compliance: Electronic Invoices and Delivery Notes for Turkey which need to be configured and deployed.

1. Turkey Invoice via Any Service Provider


2. Turkey eArsiv via Any Service Provider

Steps to configure and deploy the integration flows are mentioned in the integration guides attached to the package. Please note that Turkey Invoice via Any Service Provider needs to be configured and deployed even if you are only using the eArsiv solution. These integration flows are available in the latest version of the package.

 

Additional Information

If you are using SAP S/4HANA Cloud, then the solution is already available for use with the 2208 release.

If you are an OP customer, please implement the SAP Notes below to receive the solution.

• 3125170 - eDocument Turkey - eInvoice - Service Provider-Agnostic Solution: Pre-Requisite Objects


• 3219903 - eDocument Turkey - Service Provider-Agnostic Solution for eInvoice: Proxy objects


• 3134407 - eDocument Turkey - eInvoice: Service Provider-Agnostic Solution (Basic Solution)


• 3129528 - eDocument Turkey - eInvoice: Service Provider-Agnostic Solution (Full Solution)


• 3249682 - eDocument Turkey - eInvoice - Service Provider-Agnostic Solution: AIF Customizing (SAP ERP)


• 3249773 - eDocument Turkey - eInvoice - Service Provider-Agnostic Solution: AIF Customizing (SAP S/4HANA)

If you are a service provider looking to support eInvoicing solution, then you can visit the API package SAP Document and Reporting Compliance: Electronic Documents for Turkey. The API definition for eInvoicing can be found under the API Integration with E-Invoicing Service Providers. The detailed documentation to the API definition can be found in the documents section of the API package.

To know more about Turkey solution, you can read the solution overview blog.

 

Please feel free to leave your questions/feedback below.

To stay updated, I encourage you to follow Document and Reporting Compliance. You can read the other blogs available, and ask your questions here.