search

API - Only by CT Inhouse SAP ECC/HANA

API - Only by CT Inhouse SAP ECC/HANA

Scope of Services for E-invoicing Integration-ASP API-

a)Feature List of Cleartax E-Invoicing Software is as below

Module
Feature
Description

Data Import

  • Excel Ingestion option (Custom Mapper, govt. template, CT template).

  • Excel / JSON output (In govt. template); for non-integrated clients.

Data Validation

  • Validation check (for e-Invoice Schema, ANX-1, EWB Part A) on the invoice content.

  • Sends invoice to Invoice Registration portal (IRP) for e-Invoice (Invoice Reference Number/QR code) generation.

  • Collects the generated e-Invoice and QR code from IRP.

Custom invoice printing from IRP-signed JSON (incl. Digitally signed QR, co. logo, etc.)

Business Intelligence Reporting

Reports

Basic MIS of historical e-invoicing activity on Cleartax

Data Archive

Archiving and retrieval of e-invoices.

b. Scope of Services for EINV and EWB API integration (SAP ECC/S4 HANA)

The deliverables shall encompass designing and development of the following components.

1.Design and develop a dashboard in ERP (hereinafter referred to as ClearTax Compliance Cockpit)

2. The selection screen shall have options to filter documents based on Company code/Plant code, Document number range/series, Document date range, Document type, Document status, Any other relevant attribute.

3. The report to extract and list outward documents from the source ERP shall cover the following ClearTax document types relevant for E-Invoicing - Invoice, Credit Note and Debit Note for the transaction types B2B, SEZ, Exports and Deemed Exports.

4.The report shall display the status of E-Invoice action at document level. Based on the activity, the status of the documents may change with the success message and metadata (IRN, IRS, QR Code, etc) or error message for the use of end users.

5. The report shall have UI elements to select one or more documents and action buttons to trigger the following actions either for a single document or for bulls documents (multi select):

  • Generate IRN

  • Cancel IRN

  • Get E-Invoice by IRN

  • Get E-Invoice PDF (Print)

6. The actions can be triggered as per customer’s requirement either -

  • On a real-time basis when an invoice is generated or approved and / or

  • On a scheduled basis and / or

  • On click of UI elements in the ClearTax Compliance Cockpit.

7. For each action specified above,

  1. Transform the source data/documents into the format acceptable by Cleartax APIs and/or in consonance with what is prescribed/acceptable by the Government.

  2. Perform field level validation and business validation checks as per Cleartax and Government API schema.

  3. Load the transformed data/documents using RESTful APIs to the Cleartax application.

  4. Receive the response based on user action lil‹e generated IRN (Invoice Reference Number), signed e-Invoice, signed QR Code (Quick Response code), IRN, Cancelled date, etc from Cleartax APts along with additional information, errors and other metadata.

  5. Update the generated IRN, signed e-Invoice, signed QR Code, Cancelled date, etc and other metadata back‹ in the ERP.

  6. Customise invoice printing to include the IRN and QR code within ERP - up to 3 custom invoices; Disable printing of invoices where IRN and /or E way Bill is applicable but not generated.

  7. Handle errors and exceptions for (i) Cleartax validations (ii) Internet downtime (iii) Cleartax API downtime (iv) Invalid response from Cleartax application.

c. Scope Limitations and Customer Dependencies

  1. The scope of integration is limited to application development. Any network, firewall, OS, Basis level configurations will need to be done by the customer's IT team.

  2. Infra: Cleartax and its system integrator will commence the project once infra is set up by the customer’s infra team and the customer provides necessary access to Cleartax and its system integrator . This activity should be done by the Customer within 5 working days from project kick-off date

  3. Network: Cleartax does not provide end to end service on network set up.

  4. Basis: Cleartax does not provide any support related to Basis.

  5. Maintaining master and transaction data: Cleartax will not create or maintain the master and transaction data.

  6. A remote connection / VPN / iVPN connectivity would be required at the delivery center of ClearTax /its system integrator. Alternatively the customer may provide a laptop incase VPN access cannot be provided. If the Customer chooses to provide a laptop then it shall be provided within 7 working days of the execution of this Engagement Letter. Skype or any other mode of remote access shall not be acceptable unless the Customer agrees to additionally pay for such remote access.

  7. Customer shall share appropriate Business requirement/functional documentation about the system configuration with the consulting team for study and understanding.

  8. Appropriate and timely system access to the consulting team shall be provided at periodic intervals or based on the milestones.

  9. ClearTax/SI shall submit the system to the customer team for Approval/User AcceptanceTesting (UAT). In the interest of timely completion of the project, all the test cases as per the functionalities agreed in Scope of Work in this LOE are to be tested and UAT sign-off to be provided by the customer within 14 days of moving the project to UAT.

  10. Once the UAT sign-off is provided by the customer need to give necessary clearance to move the code to production within 7 days.

  11. In case the UAT sign off is not provided within 14 days as per point (ix) above, the project will be deemed to have successfully gone live and ClearTax shall be entitled to raise invoices for the amounts payable by the Customer.

d. Integration Post Go-Live Support – Cleartax will provide one-month post go live support to the customer from the go-live date of integration. Such support includes fixing any breakages in functionality only with respect to the original scope of work for integration. It excludes

  1. additional features or enhancements which are not contained in the original scope of work for integration.

  2. breakages in functionality arising out of any subsequent changes (including but not limited to changes in APIs / schema fields) stipulated by the government/GSTN/NIC after the initially agreed scope of work.

e. Annual Maintenance (AMC) for Integration - Customer may avail annual maintenance services for integration for the Period of Engagement by paying appropriate AMC fee. The AMC support will include fixing any breakages in functionality only with respect to the original scope of work for integration. It excludes

  1. additional features or enhancements which are not contained in the original scope of work for integration.

  2. breakages in functionality arising out of any subsequent changes (including but not limited to changes in APIs / schema fields) stipulated by the government/GSTN/NIC after the initially agreed scope of work.