Clearing the review queue

What the review queue is

Every document you forward or upload gets read by Verinode's extraction pipeline: it identifies the document type, pulls out the numbers and dates, and tries to work out which vendor, carrier, TPA, client, or internal section the document belongs to. Most of the time that guess is confident enough that the document files itself and shows up in the Vault with no action from you.

Sometimes it isn't confident enough. A statement with no clear vendor name on it, an email with an ambiguous subject, a scanned form Verinode can partially but not fully read: these land in the review queue instead of filing automatically. The review queue is where that backlog collects and where you clear it, one document at a time or in a batch.

Verinode never files a document on a guess it isn't confident in. Reviewing here is what turns "Verinode's best guess" into a confirmed record.

Where to find it

Open Vault from the sidebar, under the My Data section, at iq.verinode.ai/data. (The old /documents link redirects here.) When documents are waiting, the Vault nav item and the My Data section header carry a number badge, a live count of everything waiting on you across the review queue and the failed-uploads bin combined.

The review queue itself lives at /data/review. You can also land there straight from the upload tray: click a completed upload that needed review, or a failed one (failed uploads route to their own Failed bin, a separate list from this one).

The page header reads:

Documents Verinode couldn't classify with full confidence. Confirm the best guess in one tap, edit the entity, or discard.

with a Back to Vault link underneath it.

What each row shows

Every pending item is a row in the list. Top to bottom, a row shows:

• Label: the document's subject line if it has one, otherwise a humanized version of its document type (for example "Invoice" instead of a raw type token).
• Meta line: the document type, then the intent Verinode read from it (if any), then a confidence percentage, then how long ago it arrived (just now, "12m ago," "3h ago," "2d ago," and so on).
• Suggested entity: if Verinode has a guess, you'll see "Suggested: [Name] (Type)", for example "Suggested: Acme Restoration Supply (Vendor)." If it has no guess at all, the row instead reads "No suggestion. Pick an entity manually."
• A Review button on the right, which opens the detail modal for that one document.

Above the list, a summary line tells you how many documents are waiting in total ("3 documents waiting"), and, when only some of them have a suggestion, how many do ("· 2 have a suggestion").

The two batch actions

Next to the summary line sit two buttons that act on the whole queue at once, so a bulk import doesn't force you into dozens of individual taps.

• Discard all: asks you to confirm ("Discard every pending review item? This cannot be undone.") and then drops every pending item in the queue. There is no undo.
• Confirm all suggestions: accepts Verinode's best guess for every item that has one. Items with no suggestion (the ones reading "Pick an entity manually") are skipped, since there's nothing for Verinode to confirm on your behalf. This button is disabled outright when nothing in the queue has a suggestion to confirm.

After a batch action runs, a result line appears below the buttons summarizing what happened, for example "4 confirmed · 1 need manual entity pick" or "6 discarded." If a batch run hits its per-click cap before it finishes the whole queue, the result line adds "more remain, run again," and you simply click Confirm all suggestions again to work through the rest. If a batch action fails outright, the error appears in the same spot instead.

Reviewing one document

Clicking Review on any row opens the review modal. What it shows, top to bottom:

Document. The subject or document type, the document type again, the intent, the confidence percentage.

What Verinode read. A plain-language summary of the document's contents, when Verinode has one to show.

Extracted. The key fields Verinode pulled out, whichever apply: Vendor, Total (formatted as currency), Date, Period (a date range), Lines (line item count). Only the fields that actually have a value show up here.

Where does this belong? A dropdown listing every section the document could file under: the counterparty sections (a vendor, a carrier, a TPA, a client) and the internal sections (Team, Training & CE, Certifications, Compliance, Safety, Financials, Equipment, Fleet, Facilities, Processes, Recruiting, Reputation, and a General / Other catch-all for anything that doesn't fit elsewhere). It defaults to whatever Verinode judged most likely, with a one-line hint underneath explaining what belongs in that section. If nothing fits, General / Other always works: the document is filed and kept even with no structured data attached, as long as you add a note.

Which vendor / carrier / TPA / client? Shown only when you've chosen a counterparty section. A search-and-create picker: search your existing records, or type a new name and Verinode creates that record the moment you confirm. If Verinode already had a guess and it matches the counterparty type you picked, that guess is pre-filled; the modal also tells you what Verinode's best guess was, so you can either re-pick it or choose something different.

What kind of document? Shown only when the section you picked covers more than one document type (Team, for instance, covers roster, payroll, and performance-review documents). Choose the one that matches.

The completion form. Whatever structured fields that document type calls for (dates, amounts, named rows), pre-filled with what Verinode already extracted. Fill in anything left blank. A section with a single document type and no counterparty to pick just tells you: "Confirm to file this under [Section]. Nothing else to add."

Bulk books. Occasionally a single upload is really a whole book of records at once (a job export, a client list, a vendor list) rather than one document about one counterparty. When that's what Verinode detects, the modal replaces the counterparty picker with a summary: how many rows, and (for a job export) how many distinct carriers or TPAs those rows touch. Confirming here files every row in the book at once, each one keeping its own vendor, carrier, or TPA assignment; there's nothing else to pick.

At the bottom, three buttons: Cancel (closes without acting), Discard, and Confirm. Discard on a bulk book warns you first, naming the row count, since it throws away every row in that import, not saved anywhere else. Confirm is disabled until you've made every choice the form actually requires (a category, a valid counterparty name, any required completion fields); it will not let you file an incomplete record.

Confirming or discarding a single document closes it out of the queue and refreshes the list. There's no separate save step: the Confirm button is the save.

The empty state

When there's nothing waiting, the page shows a single line and nothing else:

No documents waiting for review.

That's the state you're working toward. An empty review queue means every document Verinode has read recently was confident enough to file on its own, or you've already cleared what wasn't.

How to work the queue

1. 1Open Vault from the sidebar and check the badge. A number there means something is waiting; click through to /data/review.
2. 2Scan the summary line for how many documents have a suggestion. If most do, start with Confirm all suggestions to clear the easy majority in one click.
3. 3Check the result line. If it says documents remain, click Confirm all suggestions again.
4. 4Work through what's left one row at a time with Review: pick the right section, confirm or correct the entity, fill in anything the completion form is still missing, then Confirm.
5. 5If a document genuinely isn't worth keeping (a duplicate, spam, something misforwarded), Discard it from inside the modal rather than leaving it to age in the queue.
6. 6Only reach for Discard all when you're certain the entire queue is disposable: it is not selective and it does not undo.

Related reading

• Forwarding documents: how documents get into Verinode in the first place, and what happens to the ones that file automatically.
• Connecting your data: the broader picture of every way data flows into Verinode.
• Understanding your margin: what the confirmed numbers behind a document eventually feed into.
• Clients and carriers: where a confirmed carrier or client document ends up living.