Skip to content

Module Map

Applies to: All subscriptions

Purpose

Show what each module is on its own, what every module needs from the platform underneath, and where modules genuinely depend on one another — so that a reader of any page in this portal can tell whether it applies to their subscription.

Audience

Anyone scoping a subscription, and every reader deciding which sections to read.

Prerequisites

Reference

How to read the portal by subscription

Every page carries an Applies to line directly under its title, naming the modules it is about:

Line reads Meaning
All subscriptions Platform-level. Applies whatever you have licensed
A module name Only relevant if you have that module
Several module names Relevant if you have any of them

Front matter carries the same information as a modules: list, so pages can be filtered or built into a subscription-specific export later.

The platform underneath

Some things are not a module and are never optional:

Platform capability Why it is not optional
Organisation, GSTIN and address registry Every document is scoped to a registration
Users, roles and access control Somebody has to sign in
Tenant isolation Enforced in the database, for everyone
Reference data — state codes, supply types, HSN and SAC lists, unit codes Shipped with the platform; you do not load it
Installation, configuration, monitoring, backup, upgrade The system has to run

This is why most of Sections 02 to 08 and 13 to 17 read All subscriptions.

The modules

Module What it does standing alone Needs from the platform Default
e-Invoice Registers invoices, credit and debit notes with the government; stores the reference number, signed QR and evidence; prints compliant documents Registrations, users, a GSP connection On
e-Way Bill Authorises movement of goods; Part-B, validity, extension, cancellation, consolidated bills, multi-vehicle Registrations, users, a GSP connection On
Invoice Generation Creates invoices inside Complifly — customer and item masters, numbering, approvals, receivables and a general ledger Registrations, users Off
TDS Withholding tax — deductions, challans, returns, certificates, notices Registrations, users, TAN Licensed separately
Data Privacy Consent notices and versions, capture and withdrawal, grievances, evidence packs Users Licensed separately
ERP Write-back Sends compliance outcomes back to the originating ERP An ERP integration, and at least one of e-Invoice or e-Way Bill Off

Which modules are genuinely standalone

Module Can run alone? Notes
e-Invoice Yes Documents arrive from your ERP or by upload
e-Way Bill Yes The standalone pipeline raises a bill from a challan or bill of supply, with no invoice registration involved
Invoice Generation Yes, but rarely useful alone It produces invoices; without e-Invoice they are never registered with the government
TDS Yes A separate tax regime; shares only the platform
Data Privacy Yes Shares only the platform
ERP Write-back No It reports outcomes, so it needs a module producing them

How they interact

        Your ERP ------------+                 +---- Invoice Generation
                             |                 |     (creates documents
                             v                 v      inside Complifly)
                       +---------------------------+
                       |   Validation and routing  |   platform
                       +---------------------------+
                             |                 |
                   INV/CRN/DBN             CHL/BIL/BOE
                             v                 v
                       +-----------+     +-----------+
                       | e-Invoice |---->| e-Way Bill|  a bill can be raised
                       +-----------+     +-----------+  FROM a registered invoice
                             |                 |
                             +--------+--------+
                                      v
                             +----------------+
                             | ERP Write-back |  outcomes returned to the ERP
                             +----------------+

        TDS  ---- independent ----  Data Privacy     share only the platform

The interactions that matter in practice:

Interaction Detail
Invoice Generation feeds e-Invoice A document raised in Complifly follows exactly the same path as one received from an ERP — validation, routing, registration. It bypasses nothing
e-Invoice feeds e-Way Bill A bill can be raised from a registered invoice. That path needs e-Invoice; the standalone pipeline does not
Both feed Write-back Write-back reports what e-Invoice and e-Way Bill did. With neither, it has nothing to report
Document routing spans both Which document types produce a registration versus a bill is one setting covering e-Invoice and e-Way Bill together
The GSP connection serves both One provider assignment covers e-Invoice and e-Way Bill; it is not per module
TDS and Data Privacy touch neither They share users, registrations and infrastructure, and nothing else

What this means for master data

The most common licensing misunderstanding, and worth stating plainly:

If you have You load
e-Invoice and/or e-Way Bill Organisation, GSTINs and addresses only. Party and item details arrive inside each document from the ERP
Invoice Generation The above, plus customer, item, rate and numbering masters — because you are now creating documents rather than receiving them

See Information Checklist.

Validation

Check Pass condition
You know your modules Confirmed against the contract, not assumed from what appears on screen
Each is enabled per registration Checked for every GSTIN, not just one
Interactions understood You know why enabling Invoice Generation alone registers nothing
Reading path chosen You know which sections apply and which to skip
Write-back has a producer If licensed, at least one of e-Invoice or e-Way Bill is enabled

Troubleshooting

Symptom Cause Action
A page describes something you do not have It belongs to a module outside your subscription Check its Applies to line
Invoice Generation produces documents that never reach the government e-Invoice not licensed or not enabled Invoice Generation creates; e-Invoice registers
Write-back produces no events No module is producing outcomes, or write-back is off Check both
A module is licensed but invisible Not enabled for that registration See Modules and Licensing
You loaded customer and item masters and nothing uses them Those masters belong to Invoice Generation Harmless, but unnecessary without it