The Review Queue: Confirming Uncertain Documents

What the Review Queue is

Every document you send into Verinode, an emailed invoice, a forwarded scorecard, a photo from a job site, a bulk export, gets read automatically and filed against the right vendor, carrier, TPA, client, or job. Most of the time that happens quietly and the document simply appears where it belongs.

Sometimes it cannot. The extraction might be confident about the numbers but unsure which vendor sent the invoice. It might recognize the document type but have no strong match for the counterparty. Rather than guess and file a document under the wrong name, Verinode holds it back and puts it in the Review Queue: a short list of documents waiting on a human decision. Nothing in the queue has been lost or discarded, it is simply paused one step short of being saved.

You have three ways to clear an item: confirm Verinode's best guess in one tap, open it and correct or complete the details yourself, or discard it if it should not be filed at all. As an independent data trust, Verinode never files something under your name without your say-so when its own confidence runs low, that is the entire point of this queue.

Where to find it

Open Vault from the sidebar, under My Data (/data). The Review Queue is a sub-page of Vault at /data/review. From the Review Queue page, a Back to Vault link returns you to the main Vault view.

You do not have to go looking for it, though. The ingestion status icon (the small tray in the sidebar, or in the top bar on a phone) tracks every document you send in. Once a document finishes processing, if it needs a decision from you, its row in that tray carries a small Review tag. Clicking that row takes you straight to /data/review.

The queue list

The page heading reads:

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

Below that, a status line counts what is waiting, for example "3 documents waiting" (singular "1 document waiting" when there is exactly one). If only some of the items have a suggested match, the line adds a second clause, for example "5 documents waiting · 3 have a suggestion", so you can tell at a glance how much of the queue can be cleared in one click versus how much needs a manual pick.

Each row in the list shows:

• The document's label, the email subject line if there was one, otherwise the document type (for example "Invoice" or "Job Export").
• A meta line underneath: the document type, the intent Verinode read from it if any (for example "Payment"), the confidence percentage if Verinode logged one (rounded to the nearest whole number, for example "72% confidence"), and how long ago it arrived ("just now", "14m ago", "6h ago", or "2d ago").
• Either a suggestion or a prompt. If Verinode found a likely match, the row reads "Suggested: [Name] (Vendor)" (or Carrier, TPA, Client, Equipment, matching whatever it thinks the document belongs to). If it found nothing to suggest, the row reads "No suggestion. Pick an entity manually."
• A Review button that opens the document's full detail in a modal, described below.

Confirm all suggestions

The Confirm all suggestions button accepts Verinode's best guess for every item that has one, in a single click, so a batch of imported documents does not force you to tap through each one by hand. It is disabled when nothing in the queue has a suggestion to confirm.

It works through the queue in the order documents arrived (oldest first), confirming up to 25 at a time. If an item's suggestion was only a name with no existing record behind it, Verinode creates that record as part of confirming, exactly as it would if you created it manually from the Review modal.

When it finishes, a result line appears summarizing what happened, for example:

4 confirmed · 1 need manual entity pick · more remain, run again

Each part only shows up when it applies:

• "N confirmed", how many were accepted and filed.
• "N need manual entity pick", items with no suggestion to confirm; these stay in the queue for you to open individually.
• "N failed", items that hit an error while filing; these also stay in the queue.
• "more remain, run again", appears when the queue had more waiting items than the batch could process in one pass. Click Confirm all suggestions again to work through the rest.

If nothing had a suggestion to confirm, the line simply reads "Nothing to confirm."

Discard all

The Discard all button clears every pending item in the queue at once, whether or not it has a suggestion. Because this cannot be undone, clicking it opens a confirmation prompt first:

Discard every pending review item? This cannot be undone.

Confirming reads "N discarded." once it finishes.

Reviewing one document

Clicking Review on any row opens the same modal used everywhere Verinode asks you to resolve an uncertain document. It walks through what Verinode read and lets you correct it before anything is saved.

1. 1Document. The top of the modal repeats the subject or document type, along with the document type, intent, and confidence percentage, so you have the same context you saw in the list row.
2. 2What Verinode read. A plain-language summary of what the extraction found, when Verinode captured one.
3. 3Extracted. A short table of the concrete values Verinode pulled out: Vendor name, Total (formatted as currency), Date, Period (a date range, when the document covers one), and Lines (the number of line items). Only the fields Verinode actually found appear here.
4. 4Where does this belong? A dropdown of every section on the platform the document could be filed under, Team, Training & CE, Certifications, Compliance, Safety, Financials, Equipment, Fleet, Facilities, Processes, Recruiting, Reputation, a vendor, a carrier, a TPA, or General / Other as a catch-all. It defaults to whichever section Verinode guessed, but you can change it if that guess was wrong. Each choice shows a one-line hint describing what belongs there.
5. 5Pick the party (when it's a vendor, carrier, or TPA document). A search field lets you find the existing record or type a new name. If you type a name that does not match anything on file, the modal tells you: "New [vendor/carrier/TPA] "[Name]" will be created when you confirm." If Verinode had a guess and you have not overridden it, the modal reminds you what that guess was, so you can re-pick it in one click if you agree.
6. 6Fill in what's missing (for org sections with a form). If the section you chose has structured fields, for example a certification's holder and expiry, or a safety incident's details, they appear here pre-filled with anything the extraction already read. Required fields are marked, and Confirm stays disabled until they are filled in. Sections with no form (or the General / Other catch-all) instead show a plain note: "Confirm to file this under [Section]. Nothing else to add."

At the bottom, three actions:

• Cancel closes the modal without changing anything, the document stays in the queue.
• Discard removes the document from the queue permanently. If the document is a whole bulk import (a job export, client list, or vendor list, see below), discarding it warns you first with the row count you would be skipping, because nothing in that batch has been saved yet.
• Confirm is disabled until you have picked a section (and, for a counterparty document, a party) or filled in anything required. Confirming files the document for good.

When the document is a whole import, not one document

Some uploads are not a single invoice or certificate but a batch: a job export, a client list, or a vendor list. For those, the modal skips the party picker and instead shows what is in the import, for example:

40 jobs across 6 carriers

with a note that confirming files every row in the batch, and each row keeps its own carrier, TPA, or vendor rather than being pinned to one party.

Empty states

If nothing is waiting, the page shows only:

No documents waiting for review.

This is the normal, healthy state, not an error. Most documents clear the extraction bar and get filed automatically without ever reaching this queue.

Best-practice example

Say you forward a week's worth of vendor invoices to your ingestion inbox. Most file themselves under the right vendor automatically. Three land in the Review Queue: two because Verinode found a strong vendor match but the confidence on the total amount was borderline, and one from a new supplier you have never billed before.

Open /data/review. The status line reads "3 documents waiting · 2 have a suggestion." Click Confirm all suggestions, it accepts the two with a match and files them. The result line reads "2 confirmed · 1 need manual entity pick." Click Review on the last one, type the new supplier's name into the party picker, see the "New vendor... will be created when you confirm" note, and click Confirm. The queue is now empty, and all three invoices are filed, two automatically confirmed, one hand-corrected with a new vendor record created along the way.

Related articles

• Forwarding Documents
• Connecting Your Data
• Understanding Your Margin
• Clients and Carriers

Data sources