"The Tracking tab: what Verinode knows about each entity"

What the Tracking tab shows

Every document you forward or upload gets read by Verinode and matched to a vendor, a client, or a job. The Tracking tab is where you see that matching add up, one row per entity. For each vendor, client, or job Verinode has touched, the row shows how many documents have come in, how thoroughly Verinode was able to read them, how many distinct pieces of information it has captured, and when it last heard something new. Click the row and it opens into the actual list of fields Verinode is holding for that entity, no black box.

This is the honesty layer behind everything else the platform shows you. When a benchmark, a decision, or a margin number leans on a vendor's contract terms or a client's payment history, the Tracking tab is where you check what that number is actually built on, and how solid the ground under it is.

Verinode does not decide what to do with this information. It surfaces what it has captured and how confident it is in the capture; you decide whether that is enough to act on.

Where to find it

Open Vault from the My Data section of the sidebar (/data). The Vault home shows a row of tiles: Uploads, Tracking, Playlist, Reading, Saved, and Notifications.

The Tracking tile itself gives you a preview before you even open it: the number of entities being tracked, and either the average completeness across all of them or, if none has a completeness figure yet, a prompt that data will unlock the view. Click the tile to open the Tracking tab.

Inside the tab you get a filter bar and a table:

• Search by vendor, client, or job name.
• A dropdown for entity type: All entities, Vendors, Clients, or Jobs, each with a live count.
• A dropdown for completeness band: All completeness, High (80% or higher), Medium (40 to 79%), Low (under 40%), or No receipt.

The table, column by column

Each row is one entity Verinode has linked at least one document to.

• Entity. The vendor, client, or job name, as a link. Clicking it takes you to that entity's own page (Vendors, Clients, or Jobs) instead of expanding the row, so you can jump straight to the full profile. If Verinode auto-created the entity from a document and hasn't matched it to something you've confirmed, you'll see a Needs Review flag next to the name.
• Type. A pill reading Vendor, Client, or Job.
• Docs. The count of documents Verinode has processed for this entity: invoices, certificates, statements, whatever has come in and been linked to it.
• Completeness. How much of what Verinode tried to extract from those documents actually came back populated, averaged across every document with a receipt, shown as a percentage pill. This is not the AI's confidence in its own reading; it's a straightforward ratio of fields it found values for versus fields it looked for. Green (80% and up) means the documents are giving Verinode most of what it needs. Amber (40 to 79%) means a meaningful chunk of the picture is filled in but there are real gaps. Red (under 40%) means the documents on file leave most of the picture blank. If none of the entity's documents carries an extraction receipt yet, the pill reads "no receipt" instead of a percentage. That's common for anything ingested before extraction receipts existed, or for documents that were filed but not run through capability extraction.
• Fields. The count of distinct data fields Verinode has captured across every document tied to this entity, union'd so a field only counts once even if five invoices all reported the vendor's payment terms.
• Signals. How many downstream signals (the atomic units that feed benchmarks, findings, and decisions elsewhere in Verinode) this entity's documents have contributed. A copper number means the documents are doing real work beyond just sitting in the Vault; a dash means none yet.
• Last update. How recently a document touching this entity was processed: "just now," in minutes, hours, or days, or a date once it's over a week old.
• The chevron on the right expands or collapses the row.

Rows sort by most recently updated first, so the entities Verinode has heard from most recently sit at the top.

Expanding a row: the field list

Click anywhere on a row (other than the entity name link) to expand it. Underneath, a panel opens headed "Fields Verinode has captured (N)," and lists every distinct field as a chip, in alphabetical order, with the raw column name turned into a plain label (for example, a stored field like "period_end" reads as "Period End").

This is the actual audit trail. If a vendor's completeness reads Medium, the field list tells you exactly what's present and, by implication, what's missing, rather than leaving you to guess. If the entity has no extraction receipt yet, the panel reads: "No extraction receipt yet, fields appear as documents are processed."

How to use it

Use the entity-type and completeness filters together when you're auditing a specific slice, for example filtering to Vendors + Low to find which vendor relationships Verinode is reading thinly, before you rely on a vendor-cost comparison. Use search when you already know which entity you want to check.

A rising Docs count with a flat or falling Fields count usually means you're getting repeat documents of the same type (say, the same kind of invoice every month) rather than new kinds of documents that would round out the picture. If you want Verinode to know more about an entity, the fastest lever is forwarding a document type it hasn't seen from that entity yet, not just more of the same one.

Empty states

If nothing has been tracked yet, the table is replaced by a message: "Tracking fills as documents flow in and Verinode extracts fields," with three supporting notes: each invoice, certificate, and statement is parsed by capability; captured fields stack up per vendor, client, or job; and you can click any row to see exactly which fields are tracked. Nothing to do here except start forwarding or uploading documents. See connecting your data.

If you have tracked entities but your current search or filters match none of them, the message instead reads "No entities match these filters," with a prompt to try clearing the search or switching the completeness filter.

Best-practice example

Say you're about to lean on a vendor comparison for a pricing decision and want to trust the numbers behind it. Open Vault, click the Tracking tile, filter to Vendors, and sort by eye for anything red. You spot one vendor at 28% completeness with three documents on file. Expanding the row shows Verinode has captured the invoice total and date but nothing on payment terms or line-item detail, the fields the pricing comparison actually needs. Rather than treat that vendor's numbers as equal footing with a vendor sitting at 90% completeness, you forward that vendor's last statement (the document type missing from the file) before finalizing the comparison. The row updates, the field list fills in, and the comparison rests on ground you've actually checked instead of assumed.

Related reading

• Forwarding documents
• Connecting your data
• Clients and carriers
• How benchmarks work
• Benchmarks overview

Data sources