The HQ privacy boundary in Dues & Renewal

Dues & Renewal (HQ sidebar → Dues & Renewal, at hq.verinode.ai/dues) shows an association HQ the financial standing of its membership roster: who is current on dues, who is renewing soon, and who has lapsed. This article explains exactly what kind of data feeds that page, why it is safe for HQ to see, and where the line is drawn against the parts of a member's business that stay off limits entirely.

The boundary in one sentence

Dues & Renewal reads roster-and-status data that your association already owns: the membership roster you maintain and the dues events (paid, lapsed, renewed, waived) recorded against it. That data lives on its own group-scoped path through Verinode's systems, one that is deliberately kept separate from the path used to store an individual operator's private business records (their jobs, financials, clients, vendor relationships). The dues page never touches that private path. It cannot, structurally, no matter which HQ seat is signed in.

Where to find it

HQ sidebar → Dues & Renewal, or go directly to hq.verinode.ai/dues.

Dues & Renewal is an association-only surface. It only appears for HQ accounts configured as an association network, the kind of network that runs a paid-member roster with dues cycles and renewal dates. Franchise networks, multi-location enterprises, and buying groups do not see this entry in their sidebar, because dues tracking is not part of how those network types operate. If you try to reach the page directly without association access, you get a not-found response rather than the page itself.

What data actually feeds this page

Two things, and only two things, feed everything on Dues & Renewal:

1. Your membership roster. The list your association maintains of who belongs: company name, member number, contact email, city and state, current dues status, and renewal date. This is the same roster your association imports and manages from the Member Directory (see /help/hq-member-directory-privacy-boundary for how that roster gets into Verinode and stays association-owned end to end).
2. A log of dues events tied to that roster. Each time a membership's dues status changes, an event is recorded: a payment, a lapse, a renewal, or a waiver, along with the amount and the date it took effect. This is your association's own billing history, not anything pulled from a member's own accounting or operational systems.

A roster row can also carry a quiet third piece of data: a link to a verified Verinode operator account, when that member has gone through the verification flow described in the Member Directory. That link exists purely so a dues status can be tied to the right account holder. It is not a door into anything else on that operator's account. HQ cannot follow that link to see a member's jobs, margin, clients, or any other business data, because Dues & Renewal never reads from the part of Verinode's systems where that data lives. It is a one-way identifier, not a data-sharing channel.

What every element shows, and which side of the boundary it comes from

Every number on this page is computed by summing or filtering the roster and its dues events. Nothing is inferred, estimated, or pulled from elsewhere.

The hero. A single percentage under the eyebrow "Dues current," showing the share of your roster currently paid up (current members divided by total members, rounded to the nearest whole number). Underneath, a pill shows the raw counts (for example, "42 of 50 paid"), or "No roster imported yet" if you have not uploaded one. Below that, a summary line breaks the whole roster down by status, for example: "42 current · 3 in grace period · 4 lapsed · 1 pending" (the pending count only shows when at least one membership has no dues status recorded).

Three secondary figures beside the hero:

• Lapsed: the count of memberships past due, captioned "Members past due" (or "All members in good standing" at zero).
• Renewals due 90d: the count renewing within the next 90 days, with a callout for any of those falling within 30 days.
• Members: the total roster count, captioned "On the association roster."

Renewals Due. Lists individual memberships renewing within 90 days, soonest first. Each entry shows a status label (Current, Lapsed, Grace Period, or Pending), the company name, a plain-language renewal caption ("Renews today," "Renews in 12 days," "Renews in 3 months," or "No renewal date on file"), and either the specific renewal date or the member's city and state. Renewals inside 30 days are visually flagged so your team knows who to reach out to first. Shows up to 12 memberships. Empty state: "Renewals due in the next 90 days will appear here as renewal dates flow in from the roster."

Recently Lapsed. Lists memberships currently in a lapsed dues state, most overdue first when a renewal date is on file. Each entry shows the "Lapsed" status label, the company name, how overdue it is ("Past due 14 days," or the generic "Dues lapsed" when no date is available for the calculation), and either city/state or the last known renewal date. Shows up to 12 memberships. Empty state: "No lapsed members. Lapsed dues will appear here as the roster updates."

Every figure and every row above is a straightforward read of your own roster and your own dues events, recomputed fresh from that same roster snapshot each time the page loads. There is no hidden layer of member business data behind any of these numbers, because none is ever read in the first place.

What Dues & Renewal structurally cannot show you

To be explicit about where the line sits, here is what never appears on this page, in any tile, row, or empty state, no matter which HQ seat is signed in:

• A member's job records, work in progress, or completed-job history.
• A member's revenue, margin, cash position, or any other financial detail beyond the dues amounts your own association charges them.
• A member's client list, vendor relationships, or equipment and fleet data.
• Anything about a member's business that was not entered onto your roster or recorded as a dues event by your own association.

If a roster row is linked to a verified operator account, that link is used only to attribute the dues status correctly. It never opens a path for HQ to browse that operator's Verinode account.

Why the boundary is drawn here

Verinode HQ's value is network intelligence: aggregates, rankings, and compliance status across your membership, never a single member's private business data. Dues & Renewal is a narrow, purpose-built exception to "aggregates only," because membership standing and renewal timing are, by nature, information your association already owns and needs to see at the individual-member level to run its program. That is exactly why the data it reads is capped at what your own roster and your own dues events contain, and nothing more. Members of an association remain memberships on Verinode, not seats with broader visibility granted to HQ, and this page is built so that stays true even as your roster grows.

Related help

• /help/hq-dues-renewal-overview
• /help/hq-member-directory-privacy-boundary
• /help/hq-import-member-roster
• /help/hq-reconcile-member-dues
• /help/hq-dues-status-lifecycle