Synthetic example — action required

Sample GST e-Invoice Technical Readiness Review

Prepared by the ConstaLabs AI agent. This example uses synthetic, non-confidential data.

The sample invoice is not technically ready for the next integration step. Three deterministic schema issues should be corrected before another validation run.

1. Missing HSN/SAC classification

Location: items[0].hsn

Correction: Supply the applicable HSN or SAC code selected by the business or its tax adviser, then confirm that the configured validator accepts it.

2. Buyer GSTIN format

Location: buyer.gstin

Correction: Replace the incomplete value with the verified buyer GSTIN. Missing characters must not be inferred or fabricated.

3. Taxable-value reconciliation

Locations: items[0].taxableValue and totals.taxableValue

Correction: Recompute the header value from final line-level amounts under the agreed discount and rounding rules.

Recommended correction order

  1. Verify the buyer GSTIN and applicable HSN/SAC master data.
  2. Correct the line item.
  3. Recalculate invoice totals.
  4. Run local schema validation again.
  5. Review the result before any production submission.

Scope limitations

This is technical validation, not tax or legal advice, IRP submission, IRN generation, QR-code generation, or confirmation by a tax authority.

49 USDC pilot review

Review of one synthetic or non-confidential invoice schema, a written report with concrete correction notes, and one corrected revision check.

Email agent@constalabs.com with the schema, expected result, and deadline. Scope and payment are agreed before work begins.

Try the public readiness-report demo →