Working the verification queue: approving members

The **Verification Queue** is where your association reviews and confirms membership claims. Operators using Verinode IQ can self-declare that they belong to your association from their own setting…

7 min read·Updated July 14, 2026
On this page

What this is

The Verification Queue is where your association reviews and confirms membership claims. Operators using Verinode IQ can self-declare that they belong to your association from their own settings. That declaration does not do anything on its own. It creates a pending request that shows up here, on your side, for a human to look at and decide.

You'll find it inside Member Directory, under the HQ sidebar, at hq.verinode.ai/members. Member Directory is a single page with four sections stacked top to bottom: the stats row, Import Roster, Verification Queue, and Roster. This article covers Verification Queue. For the roster import itself, see Importing your association roster.

Note

This page is scoped to associations (RIA-style membership bodies), not to multi-location or PE-portfolio HQ groups. If your organization is a franchise network rather than a dues-paying association, you won't see this page.

Where it fits: roster in, claims in, matches suggested

Two independent things feed the queue:

  1. Your roster. You import it as a CSV (see the Import Roster section on the same page). Each row is a person or company you already recognize as a member: a member number, company name, contact email, city, state, dues status, and renewal date. This is your data, your source of truth, and Verinode never invents or edits it. It only reads it to suggest matches.
  2. Self-declared claims. Separately, an operator on Verinode IQ can tell the platform "I'm a member of your association" and optionally enter the member number or email they believe is on file. That creates a pending claim. Nothing is activated at this point. No badge, no benchmark access, nothing.

Verinode compares the two: for every pending claim, it checks whether the claimed member number or claimed email matches a row in your imported roster. If it finds one, that pairing becomes a candidate in your Verification Queue. If it doesn't find any match, the claim simply sits pending with nothing to show you until your roster catches up (for example, next time you import).

Why a match is only ever a candidate

Matching is deliberately narrow and deliberately non-authoritative:

  • A candidate only ever comes from an exact match on member number or exact match on email address, normalized for case and whitespace. There is no fuzzy or partial company-name matching, no guessing.
  • Even when the member number matches exactly, Verinode does not activate anything automatically. Every single candidate, no matter how confident the match looks, waits for a human at your association to click Approve or Reject.
  • This is a deliberate product decision, not a missing feature. Membership carries real benefits (a network badge, benchmark cohort access), and your association is the authority on who actually holds a current membership. Verinode's job is to surface the likely pairing and get out of the way of your judgment.

Tip

If a claim doesn't show up as a candidate, it usually means the operator's declared member number or email doesn't exactly match anything currently on your imported roster. Check for typos in the roster (a stray space, a wrong domain on an email) or re-import a corrected CSV. The claim stays pending until a match appears or you take another action on it.

Reading the queue

Under Verification Queue you'll see:

Operators who self-declared RIA membership and match a roster row. Approve to activate their RIA badge and RIA network benchmarks (dues must be current).

Each row in the queue shows:

  • Company name, the name from your roster row (rosterCompanyName), not whatever the operator typed. This is what you should recognize.
  • Match type, either "Member number match" or "Email match," telling you which field the claim and your roster agreed on.
  • Member number, shown as #1234 style, when the roster row has one.
  • Dues flag, if the roster row's dues status is anything other than current, the row adds "dues not current" right in the description line, so you don't have to open anything else to see it.

If more than one roster row happens to match the same pending claim, the queue shows one row per claim (the first candidate found), so you're never asked to approve the same person twice from two different rows.

Approving a match

Click Approve on a row to confirm the pairing. Approving does four things at once, immediately:

  1. Activates the operator's association membership, which is what turns on their benchmark cohort, the peer comparisons and network data specific to your association.
  2. Grants the operator's account the RIA badge, visible on their own profile and platform surfaces.
  3. Marks the claim as matched, tying it permanently to that roster row.
  4. Marks the roster row as matched to that operator, so it shows "On Verinode" back in your Roster list below.

You'll see a confirmation: "Approved [Company Name]. Membership + RIA badge activated."

Approve is only available when the roster row's dues status is Current. If dues are Lapsed, In grace, or Unknown, the Approve button is disabled on that row until the roster reflects a current status. This isn't a workaround-able suggestion: dues-current is enforced again at the moment you click Approve, not just in the button state, so there's no way to activate a member whose dues aren't current through this screen.

Heads up

If you need to approve someone whose dues you know are current but your roster hasn't caught up yet, fix it at the source: re-import an updated roster CSV (or correct the row) so the dues status reads Current, then approve. Don't try to work around the gate. It exists to keep the badge and the benchmark cohort meaningful.

Rejecting a claim

Click Reject to close out a claim you don't want to pair with that candidate. This simply marks the claim rejected and removes it from your queue. It does not touch the roster row, and it doesn't activate anything. If the operator later corrects their self-declared details and a new match surfaces, or if you believe the rejection was a mistake, that's a case for direct outreach to the operator. There's no automatic "un-reject" from this page.

Dues status and staying in sync

Membership access isn't a one-time decision. Every roster import automatically re-checks dues for members you've already approved: it activates access for anyone whose dues just came back to current, and pulls the badge and benchmark cohort access from anyone whose dues have lapsed since their last approval. This is the same reconciliation you can trigger by hand with the Reconcile dues button next to the CSV importer, if you've corrected dues statuses without a full re-import. It reports back "Dues reconciled: X activated, Y revoked."

Dues status shown throughout Member Directory uses four values:

| Status shown | Meaning | |---|---| | Dues current | Access stays on (or turns on, if this member is later approved) | | Lapsed | Access is pulled: no badge, no benchmark cohort | | In grace | Treated as not current for activation purposes | | Unknown | No dues information on file for this row; treated as not current |

The stats row

Four tiles sit above the CSV importer and summarize your whole roster:

  • Members, total roster rows. Reads "Import your roster to begin" until you've imported anything.
  • Dues Current, the percentage and raw count of roster rows whose dues status is Current.
  • On Platform, the percentage and count of your roster who are verified, active Verinode operators (i.e., an approved match).
  • Pending Review, how many claims are sitting in the Verification Queue right now. Reads "Queue is clear" at zero, and "Awaiting your verification" otherwise.

Empty states

  • Verification Queue, nothing pending: "No members are waiting for verification. New requests appear here as operators declare membership." You don't need to do anything; this page will populate itself as operators self-declare and your roster provides a match.
  • Roster, nothing imported: "Your roster is empty. Import a CSV above and members will appear here."

What HQ can and can't see here

Member Directory only ever shows you roster data you provided (company name, member number, contact email, city, state, dues status, renewal date) plus whether a given roster row is matched to a verified Verinode account. It does not expose the matched operator's private business data: their financials, jobs, vendors, or any other operational detail stay behind the same privacy boundary as everywhere else in HQ. Approving a membership match opens that operator's data into anonymized, aggregated benchmark comparisons; it never opens an individual view into their business for you or your team.

  1. 1Import or update your roster CSV so dues statuses and member numbers are current.
  2. 2Open Verification Queue and review each candidate: company name, match type, member number, and any dues flag.
  3. 3For dues-current rows, click Approve to activate the badge and benchmark cohort, or Reject to close out a claim you don't recognize.
  4. 4If a candidate's dues aren't current yet, fix the roster first (re-import or correct the row), then approve.
  5. 5Use Reconcile dues after any manual roster edits to keep already-approved members' access in sync.
Was this helpful?