Help Center

A Google account and a configured workbook containing SETTINGS, CLIENTS, INVOICE_GEN, INVOICE_LOG, GSTR1_EXPORT, and TEMPLATE_INVOICE. Confirm the workbook is configured by the seller before entering data.

Reload the spreadsheet. The menu is added by the Apps Script onOpen trigger. If it remains missing, confirm the script is attached to the spreadsheet and contact the maintainer. Do not run code from an untrusted copy.

The script checks the active Google account email against an active entry in a LICENSES tab with a valid-until date. Confirm you are using the provisioned account and contact support. Do not send your Google password.

The code reads My_Name, My_GSTIN, My_Address, My_State_Code, Invoice_Prefix, Next_Invoice_Num, Bank_Name, Bank_Account, Bank_IFSC, and UPI_ID from key/value rows in SETTINGS. Some outputs may be blank if optional details are missing.

The current code compares My_State_Code with the client's State_Code: equal codes result in CGST/SGST; different codes result in IGST. This is a basic automation rule, not a complete place-of-supply determination. Confirm the correct treatment for your transaction with current rules and a qualified adviser.

The script reads Invoice_Prefix and Next_Invoice_Num from SETTINGS, then updates the next number after writing the invoice. Check the key spelling, numeric value, and log row. Avoid simultaneous invoice creation and reconcile the log.

Keep an audit copy before making changes. The exporter skips rows whose status is exactly "Cancelled", but the code does not provide a complete credit-note or correction workflow. Follow your accounting process and ask a qualified professional how to correct a finalized invoice; do not simply erase records you may need to retain.

After creation, the script clears B3:B7 and leaves B2 (client ID) in place.

The script creates or reuses a Drive folder named IndieOS_Invoices and a subfolder named for the invoice year-month. The generated filename includes the invoice number and a sanitized client name.

Confirm the invoice exists, TEMPLATE_INVOICE exists, Drive authorization was granted, and the Apps Script has the required access. The PDF template uses fixed cell addresses; moving those cells may break population.

The script emails the generated PDF attachment to the address in the client's Email field using Gmail authorization. Test only with a controlled inbox before using real client addresses.

No. It creates a JSON draft in GSTR1_EXPORT. You must review, validate, and file through the applicable official process.

It selects non-cancelled, unreported invoices by invoice date and expects client GSTINs and HSN/SAC values. The current source constructs a B2B-style structure; do not assume it handles every transaction type, return table, amendment, credit note, or tax scenario.

Check the YYYY-MM period, invoice dates, status, and reported flag. The source changes the reported flag for included invoices when it prepares an export. Keep a backup and inspect the output before rerunning.

No. Schema requirements can change and validation has not been represented as guaranteed. Test the exact generated file with the current GST Offline Tool and resolve its errors before use. Never treat preparation as filing.

It reads spreadsheet records, uses Drive to create/store PDFs, uses Gmail to send them when requested, and checks the active Google account email for licensing. Google's account, authorization, and service terms apply. Review the deployed script and privacy policy before use.

No. It is not tax, legal, or accounting advice and should not replace professional review.