E-Invoice and E-Way Bill API Changes for Ship-to GSTIN and E-Way Bill Closure

Update at a glance

GSTN announced API changes involving mandatory Ship-to GSTIN capture and voluntary e-way bill closure. ERP users and API integrators should validate field mapping, error handling, user permissions and test cases before relying on the changed workflow in production.

Key points to review

Review ERP/API field mapping and validation. Test B2B, bill-to/ship-to and dispatch scenarios. Retain API response and user-action logs for audit trail.

Who should review this

Business owners, finance teams, compliance personnel and advisers whose facts or regulated activity fall within the official update.

Practical response

Verify the operative source, assess applicability, document the decision, assign an owner and retain evidence of any process or filing change.

Key points

• Review ERP/API field mapping and validation.
• Test B2B, bill-to/ship-to and dispatch scenarios.
• Retain API response and user-action logs for audit trail.

Why it matters

• The update may affect process, documentation, system configuration, filing or governance decisions.
• The full official source must be checked for applicability, effective date, conditions and later amendments.

Practical next steps

1. Open and archive the official source linked above.
2. Identify affected entities, transactions, periods, systems and responsible owners.
3. Prepare a short applicability and change-impact note.
4. Update the compliance calendar, SOP, system or document checklist only after professional review.
5. Record the reviewed date and monitor for superseding updates.

Official source: Read the complete source (2026-06-17).