Skip to content

Error Code Reference

Applies to: All subscriptions

Purpose

Let anyone look up an error and know, in seconds, who can fix it. That single classification is the most valuable thing on the page, because it decides whether the reader acts or raises a ticket — and getting it wrong costs either a wasted ticket or a document that never becomes compliant.

Audience

Support teams, administrators, integration developers, end users. This section must be usable cold, at 2am, by someone who has read nothing else.

Prerequisites

None. That is deliberate.

Reference

The classification

Every error is marked with who can resolve it:

Marker Meaning What the reader should do
you The user or the customer's own team can fix it Fix the data or the document and retry
admin A Complifly administrator or the customer's IT team Escalate internally, not to Complifly
statute Fixed by law. No software can change it Understand the constraint and take the lawful alternative
support Requires Complifly support Raise a ticket, with the request identifier

The statute category is the one worth internalising. Roughly a third of the errors a customer meets are legal constraints, not product defects. A missed reporting window, a cancelled counterparty registration, a consumed document number: no configuration change, escalation or support ticket alters any of them. Treating a statutory constraint as a product problem produces a ticket nobody can close.

The families

Family Origin Page
Platform Complifly itself — authentication, authorisation, state Platform Error Codes
Validation Complifly's own checks, before any government call Validation Error Codes
NIC The government, on a generation or amendment attempt NIC Error Codes
Integration ERP write-back delivery Integration Error Codes

Which family am I looking at?

The error Family
A number such as 2150 or 4010 NIC
A field name such as BillTo_Pos or Item_HsnCd Validation
An uppercase code such as TOKEN_EXPIRED or GSTIN_NOT_PERMITTED Platform
An approval refusal such as ROLE_MISMATCH or SELF_APPROVAL Platform — see Approval workflow
A message about your ERP endpoint Integration

Two structural facts worth knowing

Validation runs before the government call. A validation error costs nothing and names a field. A NIC error costs a billed call and returns a number. If you are seeing NIC errors for something validation could have caught, that is worth raising — the point of validating first is to make it rare.

Errors are also keyed in the product's own help. Each code resolves to an explanation inside the application, on the screen where it appears. This portal is the reference; the in-product help is the answer at the moment of failure. They are keyed on the same identifiers, so they cannot drift apart.

Validation

You are using this section correctly if, for any error, you can state within a minute:

Question Where the answer is
Which family is it? The table above
Who can fix it? The fixedBy marker on the entry
Is it statutory? Marked explicitly, with the provision cited
What is the next action? The entry's resolution steps
Should I escalate? Only if marked support, or if the resolution steps do not apply

Troubleshooting

Symptom Cause Action
An error code is not listed here New, or specific to your provider Capture the code, the request identifier and the document, then escalate
The listed resolution does not work The situation differs from the common case Escalate with what you have already tried
A statutory error is escalated repeatedly The statute classification is not being read No ticket can resolve it. Route these to the tax lead, not to support
The same error recurs at volume A systemic cause — mapping, master data, or an ERP configuration Fix the cause. Handling instances one at a time will not keep up
Support asks for information you do not have The request identifier was not captured Capture it on every failure. See API Conventions