What Verinode did with your upload: the ingestion receipt

What the ingestion receipt is

Every time you hand Verinode a document, a photo, a pasted paragraph, a voice note, or a forwarded email, something happens to it: it gets read, classified, matched to a vendor or carrier or job, and saved, or it doesn't quite get there and needs a second look. The ingestion receipt is Verinode telling you, in plain language, which of those things actually happened. Not "success," not a generic checkmark, the specific fields it found, the specific records it touched, and the specific parts that didn't make it through.

This matters because Verinode is an independent data trust. It never quietly guesses at a document and moves on, and it never lets a partial import read as a clean one. If you send over a book of 300 jobs and only 30 came through cleanly, the receipt says so, in those numbers, before anything downstream (a benchmark, a margin figure, a decision) gets built on the other 270 you never actually saved. You decide what to do about a gap; Verinode's job is to make sure you can see it.

There isn't one single "receipt" screen. There are three moments where Verinode shows you its work, and this article walks through all three:

1. The result pane, right inside the Send it over modal, the instant a single document finishes processing.
2. The card that follows you, a small persistent surface that tracks the same result even after you've closed the modal and moved on.
3. The import quality score, a separate pre-save checkpoint that appears only when you bring in a bulk book of job data, so you can catch a problem before hundreds of rows get written at once.

For how to actually send Verinode something in the first place, the five tabs, the keyboard shortcut, the review queue for anything Verinode can't confidently place, see Adding data: the Add Data capture flow. This article picks up right after that, at the moment the result comes back.

Where to find it

There's no dedicated page for the receipt; it appears at the moment it's earned, wherever you happen to be:

• Open Vault from the sidebar (/data, still reachable at the older /documents link) and click Add Data in the header, or press Cmd+U / Ctrl+U from anywhere. Drop a file, paste text, or record a voice note, and the result pane renders directly inside the same modal once processing finishes.
• If you close the modal before that (normal for a file drop, which closes the modal immediately so you're not stuck waiting), the same result reaches you as a small card in the corner of the screen (bottom right on a laptop, above the tab bar on a phone), and it stays there whether the modal is open or not.
• On the Jobs page, dropping a bulk CSV export routes through its own flow: a data-prep guide, then a drop zone, then the import quality score, before anything is saved.

The result pane: what came back from a single document

The moment a file, photo, pasted paragraph, or voice recording finishes processing, whichever surface you're looking at (the modal, if it's still open) shows:

• A status icon. Green means a clean, complete result. Amber means something needs your review. Blue means the item was queued (a bulk batch still being worked through in the background).
• "Got it: {a one-line summary of what Verinode read.}" This is Verinode's own plain-language read of the document, not a generic acknowledgment.
• Matched entities. If Verinode tied the document to something you already track, a line lists exactly what: for example "Matched: Liberty Mutual (carrier), Acme Restoration (vendor)," one entry per resolved record, with the kind of record in parentheses. If nothing matched yet, this line simply doesn't appear.
• Warnings, in an amber box, only when something is genuinely off: a partial bulk import, a carrier name Verinode couldn't resolve, a row that failed to save. These are covered in full in the next section, because they're the part of the receipt that keeps a partial success from ever looking like a complete one.
• Insights, Verinode's own observations about what it just read, each marked by how serious it is: a double exclamation mark for something critical, a single exclamation mark for a warning, an asterisk for a plain observation. If there's nothing to flag, this section doesn't show.
• A next-step suggestion, tailored to whatever section you're working in. On Vendors it might read "forward a carrier scorecard to unlock compliance analysis," on Margin, "send over more invoices to see margin trends," on Clients, "forward a job export to see revenue by client." If Verinode doesn't have a specific nudge for the page you're on, it points you at setting up email forwarding on the Connect page instead.
• Two buttons: Send another resets the pane so you can hand over the next document immediately, and Done closes it.

The very first time a document comes back clean, a one-time banner appears above all of this: "Your intelligence is starting to build" / "Every document you send makes your insights sharper." It only shows once, the first time your account has a completed result.

Reopen Add Data later in the same visit and, below the tabs, a Recent list shows your last five results from that session: a short mark (a clean check, a question mark for needs review, an ellipsis for queued) next to a one-line summary of what each one was, so you can confirm the last few things you sent actually landed.

The card that follows you: the persistent tracking surface

Because file drops close the modal right away (so you aren't stuck watching a spinner for the 10 to 30 seconds a read typically takes), the same result also lands in a small card that lives outside the modal, in the corner of the screen. It's what lets you keep working while Verinode reads your document, and still get the full result when it's ready.

While a document is processing, the card shows a spinning ring and a line like "Analyzing {filename}," with the note that Verinode is reading it now and you can keep working, it'll surface the impact when it's done. If a completion never arrives (a dropped connection, a stalled pipeline), this processing card clears itself after about a minute and a half rather than spinning forever.

When the result lands, the processing card is replaced, in place, by the finished one. A newer upload always replaces whatever card is currently showing, you see feedback on the document you just sent, not one from ten minutes ago. Collapsed, the card shows:

• A colored badge naming the outcome: Impact (a concrete, high-value change, a job updated, a client record created), Filed (added to your data, but nothing dramatic yet), Need more (Verinode has this but needs a few more like it before it can say anything useful), Review (needs your input on where it belongs or what it means), or Failed (the read didn't complete).
• The document's humanized type next to the badge, for example "Vendor Invoice" or "Carrier Scorecard."
• A one-line headline, for example "Liberty Mutual · $18,400 collected," and a second line with the concrete outcome, for example "3 records updated."

Tap the card (or its chevron) to expand it. The expanded view adds:

• Saved to, up to three pill labels naming which parts of your business changed: Jobs, Margin, Clients, Carriers, TPAs, Team, Vendors, Equipment, Certifications, Compliance, Safety, Audits, Supplements, Benchmarks. This is the concrete answer to "what did this actually touch."
• What I noticed, up to two of Verinode's own observations from the read.
• A Tip, on Need more and Filed results, a short line on what to send next to unlock more (for example "Send a couple more invoices from this vendor and I can give you a cost comparison").
• Up to two buttons, the primary one always opens the section the document actually fed (Margin, Jobs, Clients, Vault, and so on), the second nudges further action, uploading another document of the same kind, or opening the Vault for the full history. A Failed card's button opens Failed Uploads directly; a Review card's opens the review queue.

A collapsed card that you don't touch clears itself after about 30 seconds. An expanded one stays until you close it or tap one of its buttons. Either way, closing it just returns the corner to empty, nothing about the underlying document changes.

Partial-import warnings: the honest core of the receipt

This is the piece that matters most for trust. When Verinode can save some, but not all, of what you sent, it never lets that read as a clean success. Three specific patterns show up as amber warnings, in both the result pane and the expanded card:

• A partial bulk import. If a batch was supposed to bring in 300 rows and only 30 actually saved (a sampling limit, a column that didn't map, a handful of rows that failed to validate), the warning reads exactly: "Imported 30 of 300 rows. Review the rest before trusting these numbers." The item is also routed to your review queue so you have somewhere to act on it, rather than a warning you read once and lose track of.
• A second opinion flagged a discrepancy. When Verinode runs a document through a cross-check and the two reads disagree on a field, the warning starts with "Second-opinion check:" followed by exactly which field and which two values didn't match, for example "Second-opinion check: Total Amount: $4,200 vs $4,850."
• Verinode couldn't classify the document with confidence. In that case the detail line reads: "Verinode couldn't classify this confidently. Confirm the suggestion or reassign, your call takes 10 seconds." This is the same item you'd resolve from the review queue, described in full in Adding data: the Add Data capture flow.

The design intent behind all three: a partial result is never dressed up as a full one. If the receipt shows a warning, treat the numbers behind it as provisional until you've looked at what it's flagging.

Before you import a job book: the pre-import guide

Bringing in a bulk export of job data (a CSV pulled from your ERP, an estimating tool, or a plain job list) is different enough from a single document that Verinode gives it its own short checklist first, so the file you send back arrives shaped for the richest possible read. Each line is tappable to reveal what it unlocks:

• Use full carrier names, "State Farm," not "SF," because consistent names produce better carrier scorecards.
• Include dates (any you have), assigned, completed, billed, paid: unlocks payment velocity, cycle time, and cash flow prediction.
• Include financials (any you have), estimated, approved, billed, collected: unlocks margin analysis, the revenue waterfall, and collection rates.
• Include supplements (if tracked), count, amount requested, amount approved: unlocks supplement return-on-investment by carrier.
• Include job category, water, fire, mold, storm, reconstruction: unlocks IICRC benchmark comparison and category analysis.

The footer is honest about partial data: "Don't have all this? Import what you have, Verinode shows what unlocks at each level." An I'm ready button dismisses the guide and moves you to the drop zone.

The import quality score: the pre-save receipt for a job book

Once a job CSV is parsed, and before a single row is written permanently, Verinode shows you exactly what it found in the file and what that means, so an obvious problem, a carrier name typed three different ways, gets fixed before it becomes three separate carriers in your data instead of one.

The header reads "Import Preview: {N} jobs found" with "Review your data quality before importing" underneath, and a single overall Data quality percentage on the right, backed by a progress bar: green from 80% up, copper from 60 to 79%, amber below that.

Five dimensions, each a row with a check or warning icon, a count, and its own percentage:

• Carrier names, how many rows have one.
• Job categories, how many rows have one.
• Date fields, how many rows have at least one of assigned, completed, billed, or paid.
• Financial fields, how many rows have at least one of estimated, billed, or collected amount.
• Supplement data, how many rows record a supplement count greater than zero.

Each row's own percentage carries a green check at 80% and above, an amber warning from 50 to 79%, and a rose warning below that.

Carriers Identified lists every distinct carrier name the file contained, with a header noting the total and, if any need a second look, how many. Each one gets a status dot and a label:

• Exact (green), matched one of your existing carriers precisely.
• High confidence (copper), matched, but not a perfect string match.
• Needs review (amber), Verinode isn't sure.
• Unresolved (gray), no match found at all.

When a name was normalized to an existing record, an arrow shows what it resolved to, for example a row typed "Farmers Ins." resolving to "Farmers Insurance." Only the first eight carriers show by default, with a "+N more" note if the file has more than that.

What this unlocks ties the five dimensions above to actual platform capability, so a thin import tells you exactly what to add next instead of just scoring low:

• Carrier scorecards, needs carrier names.
• Margin analysis, needs financial data on a meaningful share of rows.
• Payment velocity, needs payment dates on a meaningful share of rows.
• Cash flow prediction, needs both dates and financials.
• Supplement intelligence, needs supplement data on a meaningful share of rows.
• IICRC benchmarks, needs job categories.

A green checkmark means that capability is live from this import; a gray open circle means it isn't yet, with the specific gap named beside it in parentheses.

Three actions close it out: Cancel walks away without saving anything. Review carrier names (N) appears only when at least one carrier needs a second look. Import now saves the batch as-is, letting the platform-wide review queue catch any individual rows that still need a decision.

After you click Import now: the final receipt

Clicking Import now shows a brief "Importing jobs…" state ("Resolving carriers, computing analytics, detecting signals"), then one of two outcomes:

• A clean import shows a green confirmation banner naming exactly what happened, for example "Imported 40 jobs, updated 3. 6 signals detected," alongside a toast with a shorter version of the same line. The banner clears itself after a few seconds, or you can dismiss it with the X.
• An import with problems shows a rose box titled "Import encountered issues," listing the specific problems it ran into, with a Try again button that takes you back to the start of the flow rather than leaving you stuck.

Either way, nothing about this final step is silent: you get the actual counts, not just a "done."

Empty states and guardrails

• No matched entities yet. The result pane simply omits the Matched line, it doesn't show "0 matches."
• No warnings. The amber warning box only renders when warnings actually has content, a clean read shows nothing there.
• No insights. Same pattern, the "What I noticed" list is skipped entirely when Verinode has nothing to flag.
• A CSV with nothing readable. If a job import parses to zero usable rows, the flow stops before it ever reaches the quality score, with a message asking you to check the file has column headers, rather than presenting an empty score as if it succeeded.
• First card of a session. The corner card only appears once something has actually been sent. Nothing shows there until your first upload of the visit.
• Processing that never resolves. If a completion never arrives, the processing card clears itself automatically rather than spinning indefinitely.

None of these are broken states. They mean exactly what they say: nothing to flag, nothing sent yet, or a file that needs a second look before Verinode can even attempt the read.

Best-practice example

You forward a batch of ten completed water jobs as a CSV export from your ERP. The pre-import guide reminds you to include job category, so you check the export has it before sending. The import quality score comes back at 74%: carrier names and financials are both strong, but three of ten rows show a carrier typed two different ways, "Liberty Mutual" and "Liberty Mut." You click Review carrier names, confirm the shorter one resolves to the same carrier, then Import now. The confirmation banner reads "Imported 10 jobs. 2 signals detected." Ten jobs land as one carrier identity instead of two, and the next carrier scorecard you look at reflects that carrier's full volume. If instead the batch had been 300 rows and only 40 came through, the receipt would say so plainly, "Imported 40 of 300 rows," rather than letting you build a margin view on 260 jobs that were never actually saved.

Related reading

• Adding data: the Add Data capture flow
• Reading the extraction receipt
• Reading the Vault hero: documents, completeness, signals
• Connecting your data
• Forwarding documents
• Clients and carriers
• The decision workspace

Data sources