Skip to content
Quillix docs
Home Support Open app → (opens in a new tab)

GST Filing Import

Where Sidebar GST Filing Import

For clients whose books you do not keep. They send a register or a portal export; Quillix reads it, classifies every invoice, validates the GSTINs and reconciles it — so you can file from it directly.

Where this lives
This screen belongs to GST Filing only clients, whose sidebar is flat rather than grouped — so the path is Sidebar › GST Filing Import with no middle step. It is auditor-level only: the client's own admins never see it. Bookkeeping + GST clients use Bulk Import instead.
SCREENSHOT · the section assignment view showing each sheet mapped to B2B, B2CL, B2CS, notes, exports and HSN, with the column mapping editor open

Quillix works out what kind of workbook it is and parses each GSTR-1 section out of it — B2B, B2CL, B2CS, credit and debit notes, exports and HSN.

  1. Download the template first if the client has nothing in a usable shape.
  2. Choose File and upload the workbook.
  3. Check the detected fields and the section it assigned each sheet to.
  4. Open the column mapping editor to correct anything it placed wrongly.
Note
Quillix remembers the layout of a client's workbook, so a client whose file always has the same awkward shape is mapped correctly on every upload after the first.

Errors block the commit; format-only issues do not. The difference is whether the figure would be wrong or merely written oddly.

  1. Work through the Errors group first — these must be resolved.
  2. Review anything marked Flagged, where the value parsed but looks doubtful.
  3. Format-only items are noted for information and do not stop you.
Note
A party name written differently on the invoice and on the portal is not an error — Quillix normalises away things like M/S, Pvt and Ltd, so only a genuinely different party is raised.

Compares what the workbook contains against what it should contain, and reports the differences before anything is committed.

  1. Review the totals and the differences reported per section.
  2. Check the GSTINs found — an invalid one will not classify correctly as B2B.
  3. Once you are satisfied, click Approve & Commit.
Why state codes, not text
Place of Supply is compared as a state code. The same state can arrive as 33, Tamil Nadu or 33-Tamil Nadu — comparing those as strings would flip every intra-state sale to IGST.
  1. Read the duplicate warning if one appears before you commit.
  2. Decide whether the file genuinely overlaps a previous import, or whether the client has reused an invoice number.
Worth reading rather than clicking past
A reused invoice number is a real problem in the client's own numbering, not just an import nuisance — and this warning may be the only place it ever surfaces.

An optional check that calls the GST registry for each unique customer GSTIN in the file — live registration status, legal and trade name, and registration type.

  1. Choose to verify customers from the review stage.
  2. Quillix tells you how many unique GSTINs it will check before it starts, and asks you to confirm.
  3. Anything cancelled, not found, or with a name that does not match is flagged on the invoices below.
This one costs money
GSTINs Quillix has checked before are free, but each new one uses an API credit — which is why it is opt-in and asks first rather than running on every import.
  1. Open the saved mappings manager to see what has been remembered for this client.
  2. Remove a mapping if a client changes their file format and the old layout is now wrong.
First thing to check
If an upload suddenly maps columns to the wrong sections, a stale learned layout is the most likely cause.

Last updated