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

Bulk Import

Where Sidebar › Sales › Bulk Import

Brings a client's sales register in from a spreadsheet, resolving every customer and every item against the masters you already have. The point is to import a year of sales without quietly filling the masters with duplicates. Auditors and associates only.

First
Nothing touches the books until the final step. Upload, mapping and review are all staged — Cancel & Re-upload starts again cleanly at any point before you approve.
SCREENSHOT · the review stage with the green auto-resolved summary collapsed, yellow flags, and a red decisions-required group blocking the commit

Import a sales register

  1. Download the template if the client has not sent a file yet, so the columns arrive in a shape Quillix already understands.
  2. Choose File and upload the client's workbook.
  3. Check the columns Quillix detected and map anything it could not place.
  4. Work through the review panels — this is the real work.
  5. Click Approve & Commit. The count on the button is how many invoices will be created.

Review what Quillix resolved

Every customer and item the file mentions is matched against the masters and sorted into three groups by how confident the match is.

Auto-resolved — green
Matched with high confidence, collapsed to a summary. Expand it if you want to check, but you do not have to.
Yellow flags
Matched at lower confidence. Pre-filled with Quillix's best guess and fully overridable.
Decisions required — red
Genuinely ambiguous. These block the commit until you resolve them.
Note
Nothing is guessed silently at low confidence, and nothing obvious is put in front of you. If the commit button is blocked, look for the red group.

Leave a bad row out

  1. Choose Skip this row on the offending row.
  2. Where a file has many bad rows, skip all the errored ones in one go.
  3. Skipped rows are simply not imported; everything else commits normally.
Write down what you skipped
A skipped row is a sale that is not in the books. It will surface later as a gap in the register rather than as an error, which is a much harder thing to notice.

Why the second import is easier

Quillix remembers the resolutions you make. A name like ABC Traders that you point at a master record once is resolved automatically next time.

  1. Resolve the ambiguous names carefully on the first import for a client — that is the run that pays for itself later.
  2. On later imports of the same client's file, expect most names to land in the green group by themselves.
Note
It also remembers tolerant column matching, so a client whose spreadsheet always uses their own odd header names stops being a problem after the first run.

Check what landed

  1. Read the completion summary, then spot-check a few invoices in Sales History.
  2. Import another file if the client sent the year in parts.
Numbering
The invoice counter is advanced past whatever numbers were imported, so the next invoice raised in Quillix will not collide with anything in the file. Check the numbering in Settings if the client's register used an unusual format.

Last updated