Scenario
The user needs to prepare a JSON file for completed invoice transactions to comply with e-invoicing requirements.
Action
The user selects the transaction type as “Invoice,” provides the folder path and file name, and chooses the transaction numbers by date or series. The system generates the JSON and prompts the user to open the file.
Outcome
A valid JSON file is generated for uploading to the e-invoice portal.
Scenario
The user must upload the JSON file to the government’s e-invoice portal for IRN generation.
Action
The user logs in to the GST e-invoice portal using credentials and OTP, navigates to the bulk upload section, uploads the JSON file, and downloads the IRN Excel report.
Outcome
The uploaded invoices receive IRNs, and the acknowledgment data is available in Excel format.
Scenario
The user needs to bring IRN and acknowledgment details from the portal back into ICSoft for recordkeeping.
Action
The user sets field mappings using “Import From Excel for Masters,” uploads the IRN Excel file, and confirms the import.
Outcome
The system stores the IRN and acknowledgment details against the respective invoices.
Scenario
The user wants to verify the updated invoice details after IRN generation.
Action
The user opens the Tax Invoice screen in ICSoft and reviews the invoice acknowledgment number, IRN, vehicle number, and QR code.
Outcome
The invoice reflects the correct IRN and acknowledgment details, ensuring compliance.
Scenario
The user must cancel an e-invoice if errors or changes are identified after IRN generation.
Action
The user filters the transactions by location, date, type, and number. The cancelled invoice is updated, and the system asks for confirmation.
Outcome
The transaction is marked as cancelled, and the records remain consistent and compliant.