The Tracking tab: what Verinode knows about each entity

What the Tracking tab shows

Every document you forward or upload gets read by Verinode, extracted, and matched to the vendor, client, or job it belongs to. The Tracking tab is where that matching adds up into one row per entity. For each vendor, client, or job Verinode has linked at least one document to, 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 across all of them, how many signals those documents have produced, and when it last heard something new. Click the row and it expands into the actual list of fields Verinode is holding for that entity: no black box, no summary standing in for the real data.

This is the honesty layer behind everything else the platform tells you. When a benchmark, a finding, or a decision leans on a vendor's contract terms or a client's payment history, the Tracking tab is where you check what that figure is actually built on, and how solid the ground under it is. Verinode does not decide whether that ground is solid enough to act on. It surfaces what it has captured and how complete the capture is; you decide.

Where to find it

Open Vault from the sidebar, under the My Data section, at /data. The Vault home page shows a row of six Explore tiles: Uploads, Tracking, Playlist, Reading, Saved, and Notifications.

The Tracking tile gives you a preview before you open anything. Its number is the count of entities being tracked. Underneath, the subtitle reads one of three things: the average completeness across all tracked entities (for example "72% Avg Completeness"), "Entities Tracked" if you have entities but nothing to average yet, or "Add Data To Unlock" if there is nothing tracked at all. A small gauge under the number colors the same tile green at 80% average completeness or higher, amber from 40 to 79%, or red below 40%.

Click the Tracking tile (or any tile in the row) and a full-screen detail view opens with four tabs across the top: Uploads, Tracking, Lists, Notifications. Clicking the Tracking tile lands you on the Tracking tab specifically; you can swipe or click between the other three from there.

The filter bar

Above the table sits a search field and two dropdown filters.

• Search reads "Search by vendor, client, or job…" and matches against the entity's name as you type.
• The entity type dropdown offers All entities, Vendors, Clients, or Jobs, each option showing a live count in parentheses, for example "Vendors (14)." These counts are entities, not documents: a vendor with six invoices on file still counts once.
• The completeness dropdown offers All completeness, High (80% or higher), Medium (40 to 79%), Low (under 40%), or No receipt.

All three combine: narrow by type, then by completeness band, then search by name, and the table reflects every filter at once.

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 straight to that entity's own page (Vendors, Clients, or Jobs) instead of expanding the row. If Verinode auto-created the entity from a document and hasn't matched it to something you've confirmed, a Needs Review flag appears next to the name in amber.
• Type. A pill reading Vendor, Client, or Job.
• Docs. How many documents Verinode has processed and linked to this entity: invoices, certificates, statements, whatever has come in.
• Completeness. A percentage pill, the average of the extraction-receipt completeness score across every document this entity has with a receipt. This is a straightforward ratio of fields Verinode looked for versus fields it actually found values for, not the AI's self-reported confidence in its own reading. Green means 80% or higher, amber means 40 to 79%, red means under 40%. If none of the entity's documents carries an extraction receipt yet, the pill reads "no receipt" instead of a number, common for anything ingested before extraction receipts existed, or for documents filed without going through capability extraction.
• Fields. The count of distinct fields Verinode has captured across every document tied to this entity. It is a union, not a sum, so a field only counts once even if five separate invoices all reported the same 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 produced in total. A copper number means the documents are doing real work beyond sitting in the Vault; a dash means none yet.
• Last update. How recently a document touching this entity was processed: "just now," in minutes, in hours, in days, or a date once it's over a week old.
• The chevron on the far right expands or collapses the row. Clicking anywhere on the row other than the entity name link does the same thing.

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. A panel opens underneath, headed "Fields Verinode has captured (N)," and lists every distinct field as a chip, alphabetized, with the stored column name turned into a plain label (for example a field stored as "period_end" reads as "Period End").

This is the literal audit trail. If an entity's completeness pill reads Medium, the field list tells you exactly what came through and, by implication, what didn't, instead of leaving you to guess. If the entity has no extraction receipt on any of its documents 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. Filtering to Vendors plus Low, for instance, surfaces exactly which vendor relationships Verinode is reading thinly, before you lean on a vendor-cost comparison built from them. Use search when you already know which entity you want to check.

A Docs count that keeps climbing while Fields stays flat usually means you're receiving repeat documents of the same kind (the same invoice format every month) rather than new document types that would round out the picture. If you want Verinode to know more about a specific entity, the fastest lever is forwarding a document type it hasn't seen from that entity before, not sending more of what it already has.

1. 1Open the Tracking tile from the Vault home, or click Tracking from inside the four-tab detail view.
2. 2Filter to the entity type you're relying on for a decision, benchmark, or margin figure, and set the completeness filter to Low or No receipt to isolate the thin spots.
3. 3Click into any flagged row to see exactly which fields are missing.
4. 4Forward or upload the document type that would fill the gap. See Forwarding documents.
5. 5The row updates the next time that document is processed, completeness climbs, and anything downstream that depended on that entity gets steadier ground to stand on.

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 underneath: 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. There's nothing to configure here, tracking rows appear on their own as real documents flow in. 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 scan 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, exactly the fields the pricing comparison needs. Rather than treat that vendor's numbers as equal footing with one 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.

Data sources

Related reading

• The Vault: your Documents section
• The Uploads tab: your document table
• The Vault hero panel and Explore tiles
• Forwarding documents
• Connecting your data
• Clients and carriers
• Understanding your margin
• How benchmarks work
• Reading a benchmark
• The decision workspace