Skip to content

What Complifly Does

Applies to: All subscriptions

Purpose

Draw the boundary precisely: what Complifly takes responsibility for, what your ERP retains, and what GST law leaves with you as the taxpayer regardless of what any software does. This boundary decides project scope, staffing and, when something goes wrong, who fixes it.

Audience

Project sponsors, solution architects, implementation consultants and the customer's tax or finance lead. Read before scoping.

Prerequisites

Steps

1. Understand the position in the landscape

   +------------+      +----------------------+      +--------------+     +---------+
   |  Your ERP  |      |      Complifly       |      |   Licensed   |     |  NIC /  |
   |            |      |                      |      |     GSP      |     |  GSTN   |
   | SAP, D365, |=====>| Ingest -> Validate ->|=====>|              |====>|         |
   | Tally,     |      | Correct -> Promote ->|      | Webtel /     |     |         |
   | Oracle,    |<=====| Generate -> Print -> |<=====| Masters India|<====|         |
   | custom     |      | Track                |      |              |     +---------+
   +------------+      +----------------------+      +--------------+
    system of           compliance workspace          licensed            government
    record              and evidence store            transport           systems

Three facts follow from this picture and drive most design decisions later:

  • The ERP stays the system of record. Complifly holds compliance state — IRN, signed QR, e-Way Bill, status — not your books.
  • Complifly never talks to NIC directly. All government traffic goes through a licensed GSP. Which GSP is a per-tenant configuration, and it can change over a tenant's life. See GSP Abstraction.
  • The GSP is on the critical path only where it must be. Reads are answered from Complifly's own store wherever it already holds the answer. This is deliberate: GSP reads are billed per call, put a third party on the latency path of your screens, and consume the rate-limit headroom that IRN generation genuinely needs.

2. Know the two ways a document enters

Path Who uses it How it works Where documented
API ingest Production ERP integrations The ERP posts its own native payload; a mapping template translates it to the NIC envelope Ingest API
File upload Onboarding, exception handling, ERPs without an integration budget A spreadsheet or CSV is uploaded, mapped and validated as a batch job Knowledge Base

Both converge on the same validation, routing, duplicate check and storage. The choice is an integration decision, not a compliance one — a document is treated identically once it is inside.

A third path exists where the Invoice Generation Module is licensed: the invoice is created inside Complifly rather than received from anywhere. See Invoice Generation Module.

3. Know what the platform routes automatically

Complifly decides whether a document needs an IRN, an e-Way Bill, or both, from the document type after mapping:

Document type Meaning Route IRN issued
INV Tax Invoice IRN Yes
CRN Credit Note IRN Yes
DBN Debit Note IRN Yes
CHL Delivery Challan e-Way Bill only No
BIL Bill of Supply e-Way Bill only No
BOE Bill of Entry e-Way Bill only No

Routing is configurable per company where the default does not match the business — for example, an organisation that wants a delivery challan to also raise an IRN for internal control. See Document Type Routing.

4. Accept the responsibility split

This is the table to agree with the customer's tax lead in writing, at kickoff.

Responsibility Owner Notes
Invoice content, pricing, quantities Customer (ERP) Complifly transmits; it does not compute your commercial terms
Place of Supply, supply type, reverse charge flag Customer Carried through unchanged. Complifly validates internal consistency only
HSN and SAC classification Customer Format is validated; correctness of the classification is a tax position
Tax rate selection Customer, with optional assistance The rate master can supply a default; the determination remains the taxpayer's
Document numbering uniqueness Customer (ERP) NIC permanently consumes a number per supplier, type and year. A restarted ERP series causes duplicate-IRN rejections
NIC schema conformance Complifly Validated locally before any government call
GSP transport, retry, provenance Complifly Including routing follow-on actions back to the GSP that issued the document
Evidence retention (IRN, signed QR, payload) Complifly See Housekeeping
GST return filing Customer On the government portal. Complifly is not a filing utility
e-Way Bill validity monitoring Shared Complifly alerts on approaching expiry; extending it is a user action inside the statutory window

5. Understand what the platform guarantees, and what it cannot

It guarantees that a document reaching the government has passed schema and rule validation, that the outcome is stored with its evidence, that follow-on actions are routed to the provider that issued the original document, and that a tenant sees only its own data.

It cannot override a government rejection, reopen a statutory window that has closed, release a document number NIC has consumed, or make a cancelled counterparty GSTIN valid. Complifly's job in those cases is to tell you which kind of failure you have and who can act — which is why every error in this portal is classified by who fixes it. See Error Code Reference.

Validation

Confirm your understanding is correct and shared:

Check How to verify
The responsibility table is agreed The customer's tax lead has signed the table in step 4, not merely seen it
The entry path is decided Each ERP in scope is assigned to API ingest or file upload, with an owner and a date
Routing matches the business Every document type the customer issues appears in the step 3 table with the correct route, or has a configured override
Numbering is understood The customer can state how their ERP guarantees document-number uniqueness per financial year, per GSTIN
Nobody expects return filing Confirmed explicitly in the kickoff minutes

Troubleshooting

Symptom Cause Action
Documents rejected as duplicates soon after go-live ERP numbering restarted, or the same document sent from two systems NIC consumes a number permanently. Fix the ERP series before sending more. See NIC Error Codes
Delivery challans are not producing an IRN Expected behaviour — CHL routes to e-Way Bill only If an IRN is genuinely wanted, configure an override in Document Type Routing
Tax amounts differ from the ERP Complifly transmits what it receives; a mapping rule may be transforming a value Inspect the mapped payload. See Ingest Failures
Customer asks Complifly to correct a Place of Supply Misread responsibility boundary The correction belongs in the ERP; re-issue after correcting there
A screen is slow and the GSP is blamed Most reads are served locally, so a slow screen is usually not the GSP Check Performance Issues before escalating to the provider