"Keep the physical bill or you'll lose the claim" is one of the most durable bits of Indian tax folklore, and it's mostly wrong. Both GST and income-tax law contemplate records kept in electronic form — a scanned or soft-copy invoice stored in Google Drive is, in principle, a perfectly acceptable record. But "in principle" is doing some work in that sentence, because there are conditions people skip right past: what the document has to be, how long you have to keep it, and what "kept properly" means if an officer ever asks to see it.
Here's the honest version. As always with tax specifics, treat this as the map, not the territory — confirm the details for your situation with a CA, because some of this turns on rules and sector practices that move.
The medium isn't the issue — the document is
Start with the thing people get backwards. Whether a record is paper or digital is largely not the question. The question is whether it's the right record in the first place.
For input tax credit, the document that matters is a valid tax invoice — the one carrying both parties' GSTIN, the invoice number and date, and the tax broken out by rate. A soft copy of a valid tax invoice supports your claim. A crisp, well-organised photo of a payment receipt or a UPI confirmation that was never a tax invoice supports nothing — not because it's digital, but because it was never the right document, paper or pixels. (This is the receipt-versus-tax-invoice distinction that quietly costs people credit.)
So the first rule of storing GST receipts in Drive isn't about Drive at all: make sure what you're storing is the tax invoice, not just proof that money moved.
How long you actually have to keep it
This is the part that makes the storage decision consequential. Under GST, the retention period is long: the law requires you to keep your accounts and records until 72 months — six years — from the due date of the annual return for that financial year (the annual return itself is generally due the 31 December following the year). Income-tax record-keeping rules run on their own multi-year clock as well. And if any assessment, appeal, or proceeding is open, you keep the records until that's done, even if it runs past the six years.
Sit with what that means for where you store things. A receipt from this year may need to be producible in 2032. That is a long time to trust a filing cabinet, a phone that gets replaced, or — and this is the quiet risk — an expense app that may not exist in six years, or that holds your records on its servers under a subscription you've since cancelled. A six-year obligation is a strong argument for keeping the archive somewhere you control, which is the whole case for your own Google Drive over a vendor's database.
"Electronic records" done properly
The GST rules do explicitly allow records to be maintained electronically — but they pair that permission with expectations: records kept digitally should be properly backed up, and you must be able to produce them on demand in a usable form (the rules also speak to authentication, which is worth checking with your CA for your filing setup). Translated out of statute-speak, that's three practical requirements:
- Legible. A scan that's too dark to read is not a usable record. Thermal receipts fade — photograph them early, while the ink is still there.
- Backed up and retrievable. Don't rely on a single device. Cloud storage you control (Drive) satisfies this far better than a folder on one laptop.
- Producible on demand. You should be able to pull a specific invoice quickly if asked — which means it has to be organised, not dumped in one heap.
Google Drive handles the storage-and-backup side of this well. What it doesn't do on its own is the organised-and-producible side at scale, or the reconciliation the next section covers.
What "holds up" looks like at assessment
If the goal is records that survive scrutiny, storage is necessary but not sufficient. You also want:
- The full tax invoice, captured at source — not a payment screenshot standing in for it.
- An organised archive so you can produce a specific invoice on demand rather than scrolling through a year of files. (A sensible folder structure and naming convention is its own short guide.)
- Reconciliation against GSTR-2B, because a stored invoice and a claimable one aren't the same thing — your purchase records need to tie to what's actually reflected for you. (That reconciliation is where getting the data into Tally cleanly earns its keep.)
Drive gives you the legible, backed-up images. The structure and the reconciliation are the parts you still have to add.
The practical setup
Put together, the setup that satisfies the law and your own sanity is: capture the tax invoice at the moment you get it, store the legible image in your own Google Drive where it'll survive the full six-year window, keep it organised so any one invoice is retrievable on demand, and reconcile it against your GST data rather than assuming a stored bill equals a claimed credit. That's exactly the workflow Starlog is built around — the invoice image lives in your Drive as the durable record, while the structured data and categorisation sit on top so the same archive feeds your GST working and your Tally entries. The storage is the easy part; doing it so it holds up is the point.