BitMed Logo
Setup & ManagementOwner

The tax review queue

On this page

When to use this: products with missing or suspect GST/HSN collect here (mostly after imports). Clear it before GST filing month — wrong rates here mean wrong GSTR reports.

Steps

  1. Products → Tax Review. Four filters split the work: Conflicts, Missing, Low-trust and All. Each row shows the product, the tax it currently holds and where that came from — and, on a conflict, the supplier invoice value in red underneath.

    In the picture, 1 is the filter row, 2 searches by product name, 3 is one row — Current: HSN 3004 @ 18% · source: manual against Supplier invoice: HSN 3004 @ 12% — and 4 is the three actions on every row.

  2. Fix each row.

    • Accept supplier takes the rate from the supplier invoice.
    • Edit opens Set tax, where you choose the HSN Code and GST Rate yourself and Save.
    • The third action is Keep current on a conflict, and Mark OK on a row that is only flagged as missing or low-trust — both mean "this is already right, stop flagging it".
    • Several supplier conflicts at once? Accept all supplier values applies them to every row in the current view in one click.

    1 is the active Conflicts filter, 2 is Accept all supplier values, 3 and 4 are the two fields in Set tax, and 5 saves.

    BitMed refuses an illegal rate. Only 0%, 5%, 18% and 40% are valid slabs — 12% and 28% left the structure on 22 September 2025, and medicines under HSN 3003/3004 moved from 12% to 5%. If a supplier invoice quotes an abolished slab, Accept supplier and Accept all supplier values reject it and show an error rather than storing it.

  3. Empty view ≠ empty queue. The screen opens on Conflicts, so "No HSN/GST conflicts to review." only tells you that bucket is clear.

    1 is the filter you are on, 3 is its empty message — and 2 is the point: check Missing, Low-trust and All before you call the job done. Products brought in by the setup wizard are never conflicts, so they land under Low-trust or Missing and are invisible on the opening screen.

  4. Check back once a month, and always right after a bulk import — imports are the most common source of flagged rows.

Good to know

  • GSTR-1/3B (→ RPT-02) are only as correct as these rates.
  • Which bucket a product lands in: a product with an HSN and a non-zero rate that BitMed did not verify files under Low-trust; one with a 0% rate files under Missing; a product whose supplier invoice disagrees with your stored rate files under Conflicts.
  • A product saved from the product form with no confirmed tax shows up here too, not just imported ones (→ PROD-01).
BitMed AI