The Queue Package API now validates calculations before generating a package. If errors or open queries are present and the “Allow Efiling with errors or open queries” setting is disabled, the API returns a clear error message and prevents package generation.
A new parameter “ignoreAttachmentErrors” added to the Queue Package API payload to handle the validations related to the files attached via this API.
When this parameter is present with a value Yes in the payload, the API ignores the validation errors associated to the files attached, and generates the package, although ignores the errors, these are reported as part of Get E-FIling Status API response.
When it is absent or present with a value No, the API validates the attachments and stops the generation of the package in the case of errors.
Each package queued via the Queue Package API will now have a unique Submission ID. Previous submission packages will continue to be replaced when a new package is queued for the same calculation.
A calculation cannot have more than one return in Queued state at any given point in time, the new package queued replaces the existing one. As each package will have its unique submission ID, all other E-Filing APIs which work on the given submission ID will show a meaningful error if the submission ID for the old package was supplied as it would have been replaced or not valid anymore.
The Queue Package API and Get E-Filing Form Codes List APIs now also work on calculations that are opened in the UI.
The “Submission ID” column is now available in the Queued, History, and Failed tabs in the EFM application. Users can manually add this column to the grid, and their view preferences persist.
A new column “Test Submission?” has been added to the Queued, History, and Failed tabs in EFM application. Users can manually add this column to the grid, and their view preferences persist. It shows NA for the records where not applicable or information not available.
Users are now prompted to explicitly confirm the submission type (Live or Test) before filing a return. A validation message ensures that the selection is made before proceeding which reduces risk of accidental live submissions.
The PDF in the Review zip will have submission ID printed in the footer along with the IR Mark.
The iXBRL in the Review and Submission zip files will have submission ID printed on them.
The PDF in the Review zip is now generated with the default print style respecting the formatting, notes and queries configuration as defined in the print style.