Skip to content

Product Overview

Applies to: All subscriptions

Purpose

Establish a shared and accurate mental model of Complifly before anyone installs, configures or integrates it. Most implementation problems that surface late are traceable to a misunderstanding formed on day one — usually one of two: that Complifly replaces the ERP, or that it decides tax positions on the customer's behalf. It does neither.

Audience

Everyone. This is the only section a non-technical project sponsor is expected to read in full, and the first section every technical reader should read.

Prerequisites

None. This is the entry point to the portal.

Steps

Read these pages in order:

  1. What Complifly Does — the position in the landscape, the document lifecycle, and the explicit list of what remains the customer's responsibility.
  2. Modules and Licensing — the five modules, what each covers, and how a module is switched on for a given GSTIN.
  3. Glossary — the statutory and product vocabulary used throughout this portal. Worth ten minutes even for readers who know GST well, because several terms have a Complifly-specific meaning.

The one-paragraph version

Complifly is a compliance workspace that sits between your ERP and the Indian government tax systems. Your ERP remains the system of record for invoicing. Complifly receives documents from it, validates them against the National Informatics Centre (NIC) schema and against GST rules, obtains an Invoice Reference Number (IRN) and e-Way Bill from the government through a licensed GST Suvidha Provider (GSP), returns the results to the ERP, and retains the signed evidence.

The document lifecycle

Every document follows the same seven-stage path, whether it arrives by file upload or by API:

Ingest → Validate → Correct → Promote → Generate → Print → Track
Stage What happens Where a document can stop
Ingest The document enters from an ERP API call or an uploaded file Rejected at the door for authentication, scope or duplicate
Validate Checked against required fields, formats and GST rules — before any government call Quarantined into the Correction Cockpit
Correct A user fixes what validation found Stays until fixed or deleted
Promote The corrected document is moved into the live pipeline Fails re-validation and returns to correction
Generate The IRN, and optionally the e-Way Bill, is obtained from the government via the GSP Rejected by NIC with a numbered error
Print A compliant document is rendered with the signed QR code —
Track Status, expiry and outcomes are monitored, and results are sent back to the ERP Write-back can fail and retry independently

Validation happens before the government call, deliberately. A rejection from NIC costs a billed API call, consumes rate-limit headroom, and arrives as a numbered code that a user must interpret. A local validation failure costs nothing and names the field.

What Complifly is not

It is not Because
An accounting system It does not maintain your books. The Invoice Generation Module can raise invoices and post a subsidiary ledger, but it does not replace your ERP's general ledger of record
A tax advisor Place of Supply, supply type and reverse charge are your determinations. Complifly carries them through unchanged and validates their internal consistency — it does not decide them
A GSP Complifly connects to the government through a licensed GSP. It is a consumer of that licence, not the holder
A replacement for the GST portal Return filing, ledger balances and notices remain on the government portal

This distinction matters commercially as well as technically: a customer who believes Complifly determines their tax positions will not staff the review that GST law expects of them.

Validation

You have understood this section correctly if you can answer all five of these without looking:

Question Correct answer
Where does Complifly sit? Between the ERP and the government systems (NIC and GSTN), reached through a licensed GSP
Who decides Place of Supply? The customer, in their ERP. Complifly validates consistency; it does not determine the position
What are the seven lifecycle stages? Ingest, Validate, Correct, Promote, Generate, Print, Track
Why does validation run before the government call? To avoid billed, rate-limited calls that would fail anyway, and to name the failing field rather than return a numbered rejection
What replaces the ERP? Nothing. The ERP remains the system of record

Troubleshooting

Symptom Cause Action
Stakeholders expect Complifly to file GST returns The distinction between compliance evidence and return filing was not made early Re-read What Complifly is not. Filing stays on the government portal
Business team asks Complifly to "fix" a Place of Supply Belief that the platform determines tax positions The correction belongs in the ERP. Complifly will carry through whatever the ERP sends
Project plan has no ERP-side work Assumption that Complifly integrates without ERP changes The ERP must emit documents and consume outcomes. See Integration Guides
A module the customer expected is absent from the UI Module not licensed or not enabled for that GSTIN See Modules and Licensing