Integrating E-invoicing System for SAP ECC/S4 HANA system

A complete solution for all your eInvoice Integration

Overview :

  1. Client is running SAP S4HANA or SAP ECC
  2. Client want to Automate the process of eInvoice Generation & eway bill process through SAP Integration
  3. The integration shall be done with SAP PI/PO or SAP CPI as a Middleware.
  4. Client has chosen ASP and integration shall be with done with ASP API.
  5. Time line for the project shall be about 6-8 weeks for eInvoice integration

e-Invoice (generation) Integration Process Flow


e-Invoice scenario

  1. Generating the IRN # for the invoice
  2. Cancellation of the INR # for cancelled invoice
  3. Generating the IRN # for Debit Note / Credit Note
  4. Updating the status of IRN # to SAP Custom table
  5. Creation of the T-Code for the Viewing the status of the Invoice and IRN # and related details
  6. Creation of the custom table to maintain the Inv # , IRN # and related details
  7. Update of the 2 invoice form to print the IRN # ( this shall only be the entry of one field at any suitable location in invoice form and shall be printed on the location that form design shall not change, if design is changed same shall be treated as change request.


Solution Highlights

  1. Use standard/Custom SAP ABAP object for data extraction prescribed by SAP Such as BAPI, PROXY, ALE IDOCS, ALV reporting etc. (Such object are commonly used by all SAP customers for reporting and analysis purpose)
  2. ABAP Objects are Deployed in Customer environment and retrofitted to customer configuration.
  3. These object are scheduled to extract and push data outside SAP as per the schedule(Customizable) defined.
  4. Object are also enhanced for capturing any additional mandatory data required by ASP system which may not be available in the SAP currently.
  5. Extract file from the SAP system is picked by ASP API’s and this process is automated as part of scheduling engine available as part of ASP integration layer
  6. Entire process is automated with out any manual intervention



  1. Basis work for the SAP is out of scope.
  2. Remote Access to SAP landscape is mandatory
  3. Knowledge Transfer on Invoice Program and any customization if any
  4. Knowledge transfer on the tables where all mandatory data of the invoicing is maintained shall be given to team
  5. Secure internet access for Integration layer to communicate with ASP API’s
  6. The configuration in SAP is available as per the business logic
  7. Any Master data maintenance is part of customer responsibility.


List of Deliverable

  1. Business Requirement Document
  2. Integration Architecture
  3. API’s for the SAP and any API integration
  4. ABAP Object in SAP for data picking and update
  5. System handover for UAT
  6. User Guide
  7. GO Live and System handover
  8. 4 weeks post go live hand holding support from offshore



  1. SAP PO / PI is up and running
  2. There is maximum of 5 invoice type and one company code to integrate
  3. If there is more invoice and company code then same shall be additional scope
  4. Basis resource is available with the customer
  5. Invoice Smart form and STO smart form update is already done by the client and not required as part of the project ( only 5 form update with eInvoice # shall be made)
  6. All e-Invoice related data is available in SAP if not then this need to be taken care by Customer team.
  7. All master data update is customer responsibility
  8. ABAP work elating to Picking up data from SAP system in scope
  9. Invoice form update to reflect the e-Invoice number is out of scope of this proposal and need to be taken care by the client SAP team
  10. All other scenario of e-Invoice are out of scope


Customer responsibility

  1. Provide the remote access to the SAP System
  2. For connectivity if any upgrade of the SAP patch / note application as required
  3. Open the defined port and network setting to Enable communication with the ASP server
  4. Provide the KT on the customization on the invoice program if any
  5. Provide KT on the company eWay bill and IRN # generation process
  6. Provide timely signoff on deliverable in 48 hrs
  7. Keep all the test scenario and test data in Dev/QA server
  8. Perform the testing in 72 hours and cover all scenario
  9. All the issues to be reported in 1stRound of the testing cycle
  10. Multiple testing cycle shall delay the project hence only 2 testing cycle is kept in scope
  11. Provide Basis resource for movement of TR quickly to the test system from the dev system


Why Choose Us

Client Satisfaction

Our Clients Are Our First Responsibility

Good Review

Our Client Believe Us.We Provide All Digtal and Tech Solution For Your Business.

Leave a Reply

Your email address will not be published. Required fields are marked *