Masters
Master quality is output quality.
014 minSales MastersCustomers, and the ledgers each sale posts to.
024 minPurchase MastersVendors, expense categories and purchase ledgers.
034 minItemsItems, HSN codes, and pushing corrections downstream.
Why this group decides everything downstream
Nothing on these pages is a transaction, and everything on them shapes one. A customer with no GSTIN cannot be a B2B invoice. An item with the wrong HSN files a wrong return. A ledger name that does not match the client's Tally company creates a second ledger on import.
Every master page carries the same three tools, and they are worth knowing once:
- Missing-GSTIN counts
- At the top of the customer and vendor tabs. Not a vanity metric — it is a list of invoices that will be classified wrongly.
- Duplicate finders and merge
- A duplicate splits a client's credit, HSN summary or turnover across two records — the kind of thing that only surfaces at reconciliation.
- Tally Prime format export
- Use this rather than a plain export when the goal is to create masters in Tally. In Tally: Gateway › Alt+O › Import › Masters › Default Template.
Merging is blocked across different GSTINs
Quillix refuses to merge two records carrying different GSTINs, on either side. Different
GSTINs mean two registrations — legally two parties, even under one trading
name. On the purchase side that refusal is protecting the client's ITC: merging
two registrations posts credit against the wrong GSTIN, and it will not match in 2A.
A bulk import never silently overwrites
Before any ledger import commits, Quillix shows the parse split into new
rows and rows that already exist, and asks you to choose:
Merge updates matching rows and adds the rest; Append only adds the new
ones and leaves existing rows untouched. Read the split — choosing the collision policy
yourself is the point.
Last updated