Check GST refund allocations in Codex
Install the free Fast GST Refund plugin, check a receipt shared by two invoices, and use the result to review your working.
Use the free Fast GST Refund plugin to check invoice-to-receipt allocations in Codex and retrieve preparation guidance for Statement 3 and Annexure B. Start with the fictional example below, then use the same steps with anonymous rows from your working file.
Guidance and record checks need no account. To receive a generated JSON file in Codex, connect a Fast GST Refund account that already has access to the claim. You need a Codex client that supports local plugin marketplaces; OpenAI documents this flow for Codex in the ChatGPT desktop app.
Install the plugin
- Download Fast GST Refund for Codex, version 1.3.4.
- Extract the ZIP into a new project folder. Keep
.agentsandplugins/fast-gst-refundtogether inside it. On macOS, press Command–Shift–. in Finder to show hidden folders. - Open the extracted folder as a trusted project in Codex and restart the desktop app.
- Open the Plugins directory, select the local marketplace fast-gst-refund-local, and install or enable Fast GST Refund. Review the connection to
https://fastgstrefund.com/mcpif prompted. - Start a new chat in that project.
The package includes the marketplace file used by OpenAI’s local installation instructions.
Check your first receipt allocation
Ask Codex:
Use Fast GST Refund to check these anonymous allocations. Invoice row 1 is ₹5,000, invoice row 2 is ₹8,000, and receipt row 1 is ₹10,000. I allocated ₹5,000 from that receipt to each invoice. Show the remaining balances in rupees.
Expand the tool activity and look for check_receipt_allocation. With these fictional amounts, the expected result is:
| Record | Amount remaining |
|---|---|
| Invoice row 1 | ₹0 outstanding |
| Invoice row 2 | ₹3,000 outstanding |
| Receipt row 1 | ₹0 available to allocate |
The receipt is fully allocated. Invoice 2 has ₹3,000 outstanding, so that is the record to follow up.
To see an error result, ask:
Check a separate example: invoice row 1 is ₹5,000, receipt row 1 is ₹4,000, and I allocated ₹5,000 from that receipt to the invoice.
The checker should flag the receipt as overallocated by ₹1,000.
Get preparation guidance
For the records needed before filling Statement 3, ask:
I export software services under LUT and am preparing Statement 3. Use Fast GST Refund to get a checklist of records and checks.
For a purchase-statement issue, ask:
Use Fast GST Refund to explain what to check when Annexure B reports a duplicate document.
These requests retrieve a prepared checklist or troubleshooting steps with guide links. Use the Statement 3 example, Annexure B example and upload-error guide to review the source explanation.
Use your own figures
Give the allocation checker row numbers and amounts. Keep the mapping to invoice numbers and bank references in your local working file, and keep taxpayer identifiers and document contents out of that tool’s inputs. Credentials never belong in any tool’s inputs.
Ask Codex to show the returned balances beside your row labels. Review the corresponding records and resolve differences before using the working for a claim. The free preparation pack includes blank templates, an offline allocation checker and a review checklist.
Check Statement 3 and Annexure B records
To see which fields a statement needs and where each one comes from, ask:
Use get_annexure_b_requirements. Explain the information needed and its source, including eligibility and reversals. Do not collect anything yet.
get_statement3_requirements returns the same for export documents and BRC/FIRC rows.
To check records, try this fictional Statement 3 data, which contains one mistake:
Use validate_statement3 on this fictional data: GSTIN 29ABCDE1234F1ZW, period April to June 2026, invoice EXP-001 dated 31-04-2026 for ₹1,00,000, FIRC FIRC0012345 dated 20-05-2026 for ₹1,00,000. Both are services.
The check should report that the invoice date is not a calendar date, because April has 30 days. Checking needs no account. The tool applies the offline utility’s own checks and returns every problem at once.
Save the upload files in Codex
Connect your Fast GST Refund account using Codex’s connection settings. Sign in on the Fast GST Refund page and approve the connection. Enter the sign-in code on that page, never in the conversation. Your account must already have access to the GSTIN and refund period you are preparing.
After correcting the records, ask:
Validate both corrected statements. If there are no errors, generate the Statement 3 and Annexure B JSON files for my connected account. Save each returned file unchanged and confirm its filename and SHA-256.
Codex should call the two validation tools before the generation tools. Each successful generation returns the file content, a download URL and a SHA-256 checksum. Review the saved files before uploading them to the GST portal.
If generation reports that sign-in is required, reconnect Fast GST Refund in your client’s connection settings, then retry the same request. In Codex CLI, leave the conversation, run codex mcp login fast-gst-refund, complete the browser sign-in and resume the conversation. If it reports that your account lacks access to the claim, it has not created a file. The plugin shows no price and starts no purchase.
The tools do not fetch GST returns, accounting records or email attachments, and they do not submit a refund application.
If the plugin does not appear
Confirm that .agents/plugins/marketplace.json and plugins/fast-gst-refund/plugin.json are inside the project folder you opened. Restart the app after extracting or updating the package.
To enable the plugin explicitly for a trusted project, add this entry to .codex/config.toml. Create the file if needed and preserve existing settings:
[plugins."fast-gst-refund@fast-gst-refund-local"]
enabled = true
Restart the app, then start a new chat. See OpenAI’s project plugin configuration.
For help, send support your Codex version, tool name and error message. To connect another assistant, use the MCP setup guide. The privacy notice explains request handling and the analytics opt-out.