How we work
The onboarding journey
Seven phases, one consultant. For each: what you do, what we do, and what you have at the end of it.
| Phase | You do | Complifly does | You have at the end |
|---|---|---|---|
| 1. Kick-off | Name an administrator, an ERP owner and a signatory. | Sets up your company and its registrations. | A company set up and named owners on both sides. |
| 2. Set-up | Provide users and, if you use one, your GSP details. | Configures users, access and numbering; works down the shared checklist. | A checklist showing what is done and what is left. |
| 3. Integration | Your ERP team provides a sample export and does the ERP-side work. | Maps your ERP fields and tests with sample documents. | A working feed from your ERP, tested on samples. |
| 4. Dry run | Run real invoices through and fix what is found. | Reviews validation results with you and explains each one. | Real documents that have passed validation. |
| 5. Readiness review | Join the review and raise anything missing. | Walks the checklist with you and names any blocker and its fix. | An agreed view of what, if anything, blocks go-live. |
| 6. Go-live | Sign off. | A second person at Complifly approves; the decision and its basis are recorded. | A recorded go-live decision and date. |
| 7. Close support | Process live documents; tell us what you notice. | Stays close for the period agreed in your proposal. | A smooth hand-over into normal operation. |
What we need from you to start
- An administrator, an ERP owner and a signatory, by name.
- Your PAN and the GSTINs in scope.
- A sample export from your ERP.
- GSP details, if you already use a GSP.
- The people who will use Complifly, and what each of them does.
- Time from your ERP team: how much depends on your ERP, and we tell you in the proposal.
Your ERP shapes this
Some ERPs connect through our mapping and a supported integration path. Others connect through our REST API and need development on the ERP side. We say which applies to you before you commit.