/
Invoicing Solution Key Features

Invoicing Solution Key Features

Owned by Suprit Bhattacharjee
Last updated: Oct 17, 2022
4 min read

Compute Tax Details

  • Compute Tax Details API provided for calculation of tax details sent in the request payload.

  • Configurations required

    • HSN-Tax rule mapping has to be uploaded on RMS UI, if just hsn will be passed in the request payload and not the tax rules.

 

Store Tax Details and Get Tax Details

  • Tax Details computed in the Compute Tax API call can be stored in RMS, when the request param “store“ is passed as true.

  • These same details can also be fetched using the Get Tax Details API call.

 

Generate Invoice and Get Invoice

  • Generate Invoice API provided for generation of invoices, with the order details sent in the request payload.

  • If tax details already computed with Compute Tax API call, the same details will be printed in the invoice as well.

  • If tax details not computed, then these details would have to be passed in the request payload of the Generate Invoice API call.

  • Configurations

    • Invoice Prefix - The text that will be used as prefix for the generated invoice id

    • Invoice Series - The number from which the invoice id series will begin

    • Invoice Alias - The identifier for the configuration, required when there are multiple invoice configurations

    • E-Invoicing Enabled - Whether E-Invoices have to be generated or not

    • Invoice Template- Which Invoice Template to be used for generating invoices

  • Example -

    • Suppose the invoice prefix is configured as “INCREFF-” and invoice id as 1.

    • Then the first invoice generated would have the invoice id as “INCREFF-1”, the second invoice would have the invoice id as “INCREFF-2” and so on.

 

Invoice Template Customizations

  • Invoice Templates can further be customized as per the client’s requirements:

    • Logo to be displayed on the invoice

    • Signature to be displayed on the invoice

    • Remarks to be displayed on the invoice

    • Cosmetic changes on the invoice

      • Removal of fields

      • Addition of fields that will be fixed across all invoices

    • IRN and QR code can be added to the invoice, if it is an e-invoicing case.

    • Additional invoice metadata can also be added in the invoice. This metadata will be passed in the request payload of the Generate Invoice API call. These are the data passed in the form of Key Value pairs which will be printed on the Invoice also. Example-

      • Suppose the key value pair {“Customer Id“:”1001”} is passed as metadata.

      • Then this data will be printed on the invoice as Customer Id: 1001 in the invoice

 

Multiple Invoice Configurations

  • There can be multiple invoice configurations. Each of them would be identified with the help of invoice aliases that are configured on UI. This invoice alias will be then passed in the request payload of the API call to identify which invoice configuration to be used to generate invoices. 

  • For example,  there are 2 invoice configurations - 

    • 1st configuration - invoice alias: invoice-config-1, invoice prefix: INCREFF-, invoice id: 1

    • 2nd configuration - invoice alias: invoice-config-2, invoice prefix: INCREFF2-, invoice id:1001

    • If invoice alias invoice-config-1 is passed in the request payload, then invoice id would be INCREFF-1

    • If invoice alias invoice-config-2 is passed in the request payload, then the invoice id would be INCREFF2-1001

  • Similarly, different templates can be configured against different invoice configurations

 

Generate Credit Note and Get Credit Note

  • Generate Credit Note API provided for generation of credit notes, with the order details sent in the request payload.

  • If tax details already computed with Compute Tax API call, the same details will be printed in the credit note as well.

  • If tax details not computed, then these details would have to be passed in the request payload of the Generate Credit Note API call.

  • Configurations

    • Credit Note Prefix - The text that will be used as prefix for the generated credit note id

    • Credit Note Series - The number from which the credit note id series will begin

    • Credit Note Alias - The identifier for the configuration, required when there are multiple credit note configurations

    • E-Invoicing Enabled - Whether E-Invoices have to be generated or not

    • Invoice Template- Which Credit Note Template to be used for generating invoices

  • Example -

    • Suppose the credit note prefix is configured as “CRN-” and credit note id as 1.

    • Then the first credit note generated would have the invoice id as “CRN-1”, the second credit note would have the credit noet id as “CRN-2” and so on.

  • Multiple Credit Note Configurations can be there (in a similar manner to multiple invoice configurations) and different credit note templates can be configured against these credit note configurations.

  • Credit Note Templates can be customized as well (just like Invoice templates).

E-Invoicing Solution

  • If E-Invoices have to be generated, RMS has integration with Cleartax for this.

  • Configurations

    • Cleartax auth token

    • Cleartax owner id

    • GSTIN

    • Is Invoice from Cleartax (true/false)

  • To use this, the E-Invoicing enabled has to be set as true for the invoice configuration.

 

E-Waybill Solution

  • For E-waybill generation, RMS has integration with Cleartax.

  • Configurations

    • Cleartax auth token

    • Cleartax owner id

    • GSTIN

  • Generate E-waybill API provided for generation of E-waybill against an IRN (generated during the Generate Invoice API call).

  • Get E-waybill API provided to get the E-waybill details.