Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How Do We Stop Chasing Member Firms Every Year to Declare Their Turnover for Subscription Bands?
Problems We Solve

How Do We Stop Chasing Member Firms Every Year to Declare Their Turnover for Subscription Bands?

Trade associations that set subscriptions by turnover or headcount spend months chasing declarations. We build a declaration flow tied to invoicing and records.

Updated 4 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Turnover declarations drag because the request goes to whoever was the contact last year, the form is a PDF, and the answer has to be retyped into the membership database before an invoice can be raised. We build a short online declaration that goes to the right person, checks the answer against published accounts where possible, sets the band automatically and raises the renewal invoice from it.

The form went out in March and half of it is still missing

Your subscriptions are banded by UK turnover, or by headcount, or by the number of sites or vehicles or tonnes produced, depending on the sector. Every year the membership team emails each member a declaration form. Some come back on the day. Some come back with the band ticked but no figure. Some come back from someone in the member's finance team you have never heard of, who asks what the form is for. A good number do not come back at all.

So the team chases. Then chases again. Renewal invoices for the missing ones either wait, holding up cash flow, or go out at last year's band with a note saying 'please tell us if this has changed', which nobody does until a firm that has shrunk complains about the invoice.

Meanwhile the declared figures are typed into a spreadsheet, the spreadsheet is used to update the database, and the band field in the database is used to raise invoices. Three copies, three chances to get it wrong.

The real reason the declarations stall

Member firms are not refusing. The request lands on the wrong desk, at a busy time, in a format that needs printing or a PDF editor, and asks for a figure the recipient has to fetch from someone else. That is before any doubt about who in the association will see a confidential number.

  • The request goes to the main contact, who often is not the person who knows the turnover.
  • The form does not say which financial year or which definition of turnover your rules use, so people ask or guess.
  • Nothing tells the member which band they will land in, so they cannot sense-check the result.
  • There is no link between the return and the invoice, so staff do the join by hand.
  • Chasing is manual, so it happens when someone has time.

The cost of a slow declaration round

Cash arrives later than it should, which matters for an association whose income is mostly subscriptions. Invoices raised at the wrong band create credit notes, awkward calls and, now and then, a member who feels overcharged and starts wondering whether to renew.

The staff cost is the chasing itself, plus the retyping, plus the checking that the retyping was right. And the declared figures are useful data you rarely use, because they sit in a spreadsheet nobody trusts.

A declaration flow that feeds the invoice

We build the round as one flow, from request to invoice, working with the membership database and finance system you already have.

  1. Each member record gets a named finance contact as well as the main contact, and the declaration goes to both.
  2. The request is a short secure web form, pre-filled with the member's name, last year's figure and band, and stating the definition and period your rules use.
  3. As the member types a figure, the form shows which band it falls in, so surprises surface before submission.
  4. Where a firm files full accounts, we can fetch the latest filed turnover from Companies House and flag large gaps for your team to query; we never overwrite what the member declared.
  5. A confirmed declaration updates the band on the member record and creates the renewal invoice in Xero, Sage or your finance system through its API.
  6. Reminders go out on a schedule you set, and the membership team sees a live list of who has declared, who has opened the form and who has not.
Declaration outcomeWhat happens nextWho handles it
Declared, same band as last yearInvoice raised automaticallyNobody, unless finance reviews
Declared, band changesInvoice raised, change noted on the recordMembership team glance
Declared figure far from filed accountsHeld for a query to the memberMembership manager
No response by your cut-offYour rule applies (e.g. last year's band) and member is toldAutomatic, with a note
Member disputes the bandCase opened with the history attachedMembership manager

Declared figures are stored with restricted access, so only the people your policy names can see them.

A calmer renewal spring

The round starts with one click. Most members answer from their inbox without printing anything. The team spends its time on the handful that need a conversation, rather than on every single member. Finance sees invoices appear as declarations arrive instead of in one late batch.

At the end of the round you also have a clean set of turnover and headcount figures by member, which is useful when the board reviews the banding itself.

Does this sound like your declaration round?

  • The declaration form is a PDF or Word document.
  • Chasing runs for weeks after the deadline.
  • Invoices sometimes go out at the wrong band and get credited.
  • Declared figures are retyped from email into a spreadsheet and then into the database.
  • The request goes to a contact who has to forward it to their finance team.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Can the system decide a member's band without asking them?

It can suggest one from filed accounts, but your rules decide whether that is allowed. Most associations keep the member's own declaration as the basis and use filed figures only to spot queries.

Will it work with our membership database?

We connect to it through its API or a scheduled import and export. If it has neither, we talk you through the options before building anything.

Who can see the turnover figures?

Only the roles you choose. Access is restricted on the record, and we can keep the figures out of general CRM views.

What do you need from us?

Your banding rules, last year's declarations, the declaration wording and access to the membership and finance systems.

What drives the cost?

The number of systems we connect, whether you want the Companies House comparison, and how many exceptions your rules create.

Keep reading

More on Problems We Solve

Start here

Tell us where your association's member admin gets stuck

Describe how member firms, subscriptions, surveys or events are run today, which database and finance system you use, and who does the chasing. We will tell you what we would build and what we would leave alone, and if your current membership system can already do it with some set-up work, we will say that instead.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →