The Tracking Tab: What Verinode Knows Per Entity

What it is

Every document that flows into Verinode, an invoice, a certificate of insurance, a job export, a scorecard, gets attached to one thing: a vendor, a client (which in this rollup also covers carriers and TPAs), or a job. The Uploads tab shows you that traffic one document at a time. The Tracking tab asks a different question: for a given vendor, client, or job, what has Verinode learned across all of its documents put together, how many came in, how completely were they read, and exactly which fields does Verinode now hold on file for that entity.

It is the entity-level rollup of the same extraction work covered in Reading an extraction receipt, which explains what completeness means for one document. Tracking takes that per-document number and averages it across every document tied to one vendor, client, or job, then unions every field ever captured across those documents into a single list. Click any row and you see that list directly, no black box: exactly which fields Verinode has captured for that entity, and from how many documents.

Verinode does not decide what any of this means for your business. It reads what came in, shows you exactly what it captured, and leaves the judgment call, whether a vendor's documentation is thin, whether a job needs a document chased down, to you.

Where to find it

Open Vault from the My Data section of the sidebar (iq.verinode.ai/data). Bookmarks to the old /invoices and /documents paths still work, they redirect through to /data automatically.

The Vault home shows a hero panel, a row of Explore tiles, and a Most Recent row. Click the Tracking tile in the Explore row (its value is a count of tracked entities, its sub-label something like "78% Avg Completeness") and an overlay opens with four tabs across the top: Uploads, Tracking, Lists, Notifications. Verinode lands you on Tracking. The URL updates to /data?tab=tracking as you do this, so the tab is bookmarkable and back/forward navigation works normally.

How rows are grouped

One row per vendor, per client (this bucket also covers carrier and TPA relationships), or per job that has at least one document on file. A document that Verinode could not link to a specific vendor, carrier, or job record still gets grouped and shown, under a label built from its document type or the category you filed it under, rather than disappearing from the rollup. Rows are ordered by which entity has the most recently updated document, so whatever changed most recently sits at the top.

The columns

• Entity. The vendor, client, or job name, as a link through to that entity's own page (Vendors, Clients, or Jobs). If a document behind this row could not be confidently matched to a specific carrier, TPA, or job record, an amber Needs Review label appears next to the name.
• Type. A pill reading Vendor, Client, or Job.
• Docs. How many documents feed this entity in total.
• Completeness. A colored percentage pill: green at 80% and above, amber from 40% up to 80%, red below 40%. This is the average of the extraction-receipt completeness score across every document tied to this entity that actually has a receipt. Documents without a receipt yet (typically older ones) are left out of the average rather than counted as zero, so one old, un-receipted document does not drag a well-documented entity down. If none of an entity's documents carry a receipt yet, the pill reads no receipt in muted gray instead of a percentage.
• Fields. The count of distinct fields Verinode has ever captured for this entity, unioned across every one of its documents. This is not "fields on the latest document," it is everything captured across the whole history: if one invoice supplied the total amount and a later one supplied the reference number, both count here.
• Signals. How many downstream platform signals this entity's documents have fed in total, meaning something extracted from one of its documents changed a benchmark, a finding, or a decision elsewhere in Verinode. A number greater than zero renders in bold copper. Zero renders as a faint dash instead of a number.
• Last update. How long ago the most recently processed document for this entity landed: "just now," a minute count, an hour count, a day count, or, past a week, the date it was processed.
• A chevron on the far right that flips when you expand the row.

Filtering and searching

Above the table, a search box and two dropdowns:

• Search, placeholder "Search by vendor, client, or job…". Matches against the entity's display name.
• Entity filter, "All entities (N)," "Vendors (N)," "Clients (N)," "Jobs (N)," each count live against your current data.
• Completeness filter, "All completeness," "High (≥ 80%)," "Medium (40–79%)," "Low (< 40%)," or "No receipt" for entities whose documents have not produced a completeness score yet.

Expanding a row: the actual fields captured

Click anywhere on a row (other than the entity name link, which navigates instead) and it expands in place, chevron rotating, to show a heading reading Fields Verinode has captured (N), followed by every field name as a small green chip, humanized and sorted alphabetically, for example "Total Amount," "Period Start," "Reference Number," "Line Items." This is the same list the Fields column counts, shown in full rather than as a single number.

If the entity has documents but none of them carry an extraction receipt yet, the expanded row instead reads: "No extraction receipt yet, fields appear as documents are processed."

Empty states

With nothing tracked at all (no documents processed yet, so no entity rollup exists), the table is replaced with:

"Tracking fills as documents flow in and Verinode extracts fields"

followed by three supporting lines: each invoice, certificate, and statement is parsed by capability; captured fields stack up per vendor, client, or job; and clicking any row shows exactly which fields are tracked.

With documents on file but your current search or filter combination matching nothing, the message narrows instead to "No entities match these filters," with a prompt to try clearing the search or switching the completeness filter.

How to use this tab day to day

1. 1Open Vault from the sidebar, then click the Tracking tile.
2. 2Use the Entity filter to narrow to Vendors, Clients, or Jobs if you are checking one bucket at a time, or leave it on All entities to scan everything at once.
3. 3Use the Completeness filter to jump straight to your weakest entities: set it to Low, and work down the list.
4. 4Click a row to expand its captured field list and see exactly what Verinode has and has not pulled from that entity's documents so far.
5. 5If an entity shows a low Docs count or "no receipt," that is a documentation gap, not a Verinode error, more of what that vendor, client, or job sends in will fill it in over time.
6. 6Click the entity name to jump to its own page, where the same fields and figures feed into that entity's benchmarks, findings, and decisions.

Best-practice example

Say a subcontractor vendor has five documents on file: three invoices, a certificate of insurance, and a scorecard. In Tracking, that vendor's row shows Docs: 5, Completeness: an amber 62%, Fields: 9, and Last update: 3 days ago. Expanding the row shows the certificate contributed the expiration date and the coverage amount, the invoices contributed the total amount, the document date, and line items, but no document so far has surfaced a reference number. That gap tells you exactly what to chase next time you are in touch with that vendor: not "send more paperwork" in general, but specifically a document that carries a claim or PO reference. As that document lands, the Fields count and the completeness pill both move, live evidence the gap closed.

Related reading

• Where invoices live: the Vault, the section this tab lives inside, and how Tracking fits alongside Uploads, Lists, and Notifications
• The Uploads tab, the document-by-document view Tracking rolls up from
• Reading an extraction receipt, what completeness and captured fields mean for a single document
• Clients and carriers, the entity pages a Tracking row's name links through to
• Understanding your margin, where the amounts captured here surface downstream as cost and revenue figures
• Connecting your data and Forwarding documents, the channels that feed the documents this tab rolls up

Data sources