Unclassified 0
The two columns a human recognises are the original subject and the original filename. The stored name throws both away.
Suspected duplicates 0
Capture matched each of these to an earlier document on Content Key — the original filename and the byte count. That is not a hash. They are out of the worklist, not out of the register: check one before voiding it, and clear
Duplicate Of if the match is wrong.The document
📄
Choose a document from the list.
Classify
The folder comes from this, read from the vocabulary.
The number on the document — certificate, invoice, BOL.
Inactive counterparties are listed — a historical document still came from one.
Add a counterparty. This adds it to
tbl_Counterparties and then selects it above —
the document is filed against a counterparty that already exists, never one
invented on the way past. Permit, legal name and aliases are curated
later; three fields is the whole of it.
As you would say it. Matching ignores case, spaces, apostrophes and
punctuation, so heavens cellars already finds
Heaven's Cellars — you will be told rather than
given a duplicate.
What the vendor's own emails — and you — actually call them, when that
differs from the name on the invoice. Several are fine; separate them with
; — and the file token is derived from the FIRST one,
because the short name is the one that reads well in a filename.
⚠ This goes in the filename of every document this
counterparty ever sends. It is derived from the name — shorten it now
if you want it shorter, because changing it later means renaming files.
What they are to us. Tick every one that applies — Aridus is a
grower and a crush facility and a bulk seller.
Voiding moves the file. It goes to
Source Documents/Voided/ and the row is marked
Void. It cannot be undone by classifying it again —
a later attempt is refused and nothing happens. The document type, the classified-by
and the classified-date are kept as the record of what was believed.
build 2026-09-30d — errors scroll into view