Symptom
- After selecting Save to GSTN in the statutory reporting flow, the submission does not occur.
- The document status does not change after submission.
- No error logs are displayed during or after the submission flow.
- Executing: Run Statutory Report > Prepare and save > Save to GSTR1 > New Run > open period file > Save to GSTN results in no submission and unchanged status.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Click Run Statutory Report.
- Navigate to Prepare and save.
- Click Save to GSTR1.
- Click New Run.
- Open the file generated for the target period.
- Click Save to GSTN.
- Observe that the reports are not submitted, the document status does not change, and no logs appear.
Cause
A supplier invoice number contains spaces and/or special characters that do not comply with the allowed validation pattern required by the tax authority, which prevents successful processing and status update.
Resolution
- Identify the supplier invoices included in the affected run where the Supplier Invoice Number contains spaces or unsupported special characters.
- Cancel the documents that were created with an invalid supplier invoice number format.
- Recreate the documents using a valid Supplier Invoice Number that complies with the application’s supported format. The invoice number should contain only permitted alphanumeric characters and supported separators, with no spaces or unsupported special characters.
- Rerun the applicable process and verify that the documents are processed successfully and the expected status and logs are generated.
See Also
Keywords
gstn submission, gstr1, document and reporting compliance, drc, india gst, save to gstn, save to gstr1, status not updating, no logs, supplier invoice number format, validation pattern, special characters, spaces in invoice number, statutory report submission, submission failure , KBA , FI-LOC-FI-IN-GST , Goods and Services Tax , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public