Skip to content

Prerequisites

Applies to: All subscriptions

Purpose

Move the discovery of blockers from day three of an implementation to day zero. Every item here has stopped a real project somewhere; each is cheap to establish in advance and expensive to discover late.

Audience

Implementation consultants and the customer's project manager. Section leads use the individual pages.

Prerequisites

Steps

Work the three checklists in parallel, not in sequence — the commercial and statutory items usually have the longest lead times, and they are the ones that stop a go-live.

Checklist Covers Typical lead time
Technical Prerequisites Infrastructure, platform, network, ERP readiness 2 to 4 weeks
Commercial and Statutory Prerequisites Licences, GSP credentials, registrations, statutory obligations 4 to 8 weeks — start first
Information Checklist The data and decisions Complifly needs from the customer 1 to 2 weeks

The five that stop projects

If you read nothing else on this page, establish these five before committing to a go-live date.

# Prerequisite Why it stops a project Owner
1 GSP credentials issued and tested Without them nothing reaches the government. Issuance involves a third party and is not under your control Customer, with Complifly
2 The e-invoicing obligation is confirmed Whether the customer must e-invoice at all, and from when, depends on their aggregate annual turnover. Getting this wrong changes the scope and the deadline Customer's tax lead
3 Every GSTIN in scope is listed and active Documents are scoped per GSTIN. A missing or inactive registration surfaces as unexplained rejections at the worst moment Customer
4 The ERP can emit and consume Complifly cannot integrate with a system that has no outbound path and no owner to build one. This is frequently discovered late Customer's ERP team
5 Document numbering is unique per GSTIN per year NIC permanently consumes a number per supplier, type and year. An ERP that restarts a series will collide, and there is no remedy Customer's ERP team

Sequencing

  Week 0        Week 2        Week 4        Week 6        Week 8
    |             |             |             |             |
    +-- commercial and statutory ------------------+
    |   (GSP credentials, licences, obligation)    |
    |                                              |
    +-- information gathering --+                  |
    |   (GSTINs, masters, users) |                 |
    |                            |                 |
              +-- technical preparation -----------+
              |   (infrastructure, network, ERP)   |
                                                   |
                                                   +--> installation begins

Technical preparation can start late and still finish on time. Commercial and statutory preparation cannot — it depends on third parties whose timelines you do not control. Start it in week zero, on the day the project is confirmed.

Validation

The project is ready to schedule an installation when all of the following are true. A single unresolved row is a reason to move the date, not to start anyway.

Check Evidence required
Technical checklist complete Every row marked done, with a named owner
Commercial checklist complete Licences and credentials in hand, not promised
Information checklist complete Data supplied in the requested format and reviewed for quality
The five blockers cleared Each has a named owner who confirms it in writing
Environments agreed Development, test and production defined, with separate provider credentials
Go-live date is derived, not assumed The date comes from the longest lead time on the checklists, not from a business preference

Troubleshooting

Symptom Cause Action
GSP credentials still not issued in week 6 Started too late; issuance depends on a third party Escalate commercially. No technical work can substitute for this
The customer is unsure whether e-invoicing applies to them Turnover threshold and applicability date not confirmed by the tax lead Get it in writing. Do not proceed on an assumption about a statutory obligation
The ERP team has no allocated effort Complifly was scoped as though it integrates with no ERP-side work Re-scope. Every integration path needs ERP work; see Integration Guides
Master data arrives incomplete or malformed Format not agreed before extraction Supply the template before the extract, not after. See Information Checklist
Infrastructure has been ordered against the wrong specification Sizing agreed before volumes were known Re-check against Sizing and Capacity; these figures are estimates and should be sanity-checked against your own volumes
The go-live date was fixed before this section was worked Date driven by a business event rather than by lead times Present the sequencing diagram above with real dates. Moving a date is cheaper than a failed go-live