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

Sales Masters

Where Sidebar › Masters › Sales Masters

The reference data the sales side resolves against — who the client sells to, and which Tally ledger each sale posts to.

Two fields decide the return
Registration type decides B2B versus B2C versus export treatment. Place of supply decides IGST versus CGST plus SGST. Get either wrong and every invoice to that customer is misclassified — and the return is where you will notice.
SCREENSHOT · the Customers tab with the With GSTIN / Missing GSTIN counts above the party list

Add and maintain customers

  1. Add a customer directly, or import a list from Excel — headings are matched tolerantly and existing customers are detected rather than duplicated.
  2. Watch the With GSTIN and Missing GSTIN counts at the top of the tab.
  3. Fill in the missing GSTINs. That count is the single most useful data-quality signal on the page.
What a missing GSTIN actually costs
A customer without one cannot be invoiced as B2B and can never be matched in their 2A. The count is not a vanity metric; it is a list of invoices that will be classified wrongly.

Set the registration type

Declares what kind of party this is — Regular, Unregistered, Consumer, Composition, Export, SEZ Unit, SEZ Developer or Deemed Export. It is required.

  1. Choose the registration type on the customer record.
  2. A GSTIN becomes mandatory for Regular and Composition parties — Quillix will not save those without one.
  3. For an Export customer, set the buyer's country. Everyone else defaults to India.

Contact details and place of supply

  1. A customer carries phone, pincode, address, country and — importantly — place of supply.
  2. Set place of supply on customers whose delivery state differs from their billing state.
The return reads place of supply, not the address
A customer billed in one state and supplied in another gets this wrong if you leave it blank. It is what decides IGST versus CGST plus SGST, so it is not optional detail.

Find and fix bad data

  1. Run the duplicate finder to catch the same customer entered twice under slightly different names.
  2. Run the GSTIN check to find invalid numbers. It can apply fixes in bulk rather than just listing problems.
  3. Open the merge tool — it suggests likely duplicates by GSTIN or similar name. Choose which record to keep and confirm. Undo is available in the same session.
Merging does not rewrite history
Invoices already issued keep the GSTIN they were filed with — only the party label moves. Nothing you have already reported to the department is rewritten.

Map sales to Tally ledgers

Each sales ledger holds the HSN or SAC code and the GST rate that sales posted to it default to, alongside the Tally name.

  1. Open the Sales Ledgers tab and review the mapping. Use the bulk import strip to download a pre-filled template, fill it in, and upload it.
  2. Set the GST rate on the ledger so sales at that rate map to the right ledger automatically — this is what makes the Tally export split CGST/SGST and IGST onto the correct ledgers without mapping each invoice.
  3. Add the HSN or SAC code where the ledger is specific to one kind of supply.

Two repair tools worth running

Auto-Generate Missing
Creates a ledger mapping for every item without one, working the right ledger out from the item's GST rate and whether the buyer is registered. Run it after adding items in bulk — an item with no mapping has nowhere to post in the Tally export.
Fix SAC Mappings
Items with a SAC code are services and should post to a service ledger. This finds ones mapped to a goods ledger and corrects them. Worth running after any bulk import — a service posted to a goods ledger lands in the wrong place in both Tally and the HSN summary.
The Service ledgers tab
It only appears for clients that deal in services. If you expect it and it is not there, check the client's Settings — Quillix shows it based on what the client deals in.

Last updated