Associations

Separate identities, one back office

Several organisations ran every process separately. Today they share technology and workflows and still appear independently to the outside world.

Similar plans?

Client

Association group

In the system

  • Multi-tenant
  • Accountant export
  • Bank feed
  • Travel expenses
  • Document storage

What stood in the way.

  • Member records lived in several lists. An address change rarely reached every place.
  • The dues run was manual: calculate, invoice, match payments, mostly in spreadsheets.
  • Events ran on forms and email. Attendee lists were assembled by hand, invoices separately again.
  • Because several organisations exist side by side, every one of these steps happened more than once.

What we built.

One member record

Master data, dues, attendance and correspondence hang off a single record. What changes, changes everywhere.

The member list across all organisations, filterable by status, type, guild and role.
The member list across all organisations, filterable by status, type, guild and role.

Dues run with bank matching

Dues are calculated, invoices produced and payments matched through the direct bank feed. Open items are visible.

The overview puts receivables, payables and the bank balance side by side.
The overview puts receivables, payables and the bank balance side by side.

Events in the same system

Registration, attendee list, billing and travel expenses hang off the member instead of a form service.

Every event carries its own registrations and capacity.
Every event carries its own registrations and capacity.

A portal for members, and an app

Every member sees their own open invoices, their registrations and the next event. The same interface ships as an app on the App Store and Google Play. The shell wraps only the portal, not the internal administration.

Four screens of the portal on a phone: overview, invoices, events and the ticket with its QR code.
Four screens of the portal on a phone: overview, invoices, events and the ticket with its QR code.

Multi-tenant from the ground up

Each organisation has its own letterhead, number ranges and invoices. A recipient only ever sees their own organisation. The technology underneath is shared.

Similar plans?

What changed

  • The dues run is one process instead of manual work in spreadsheets.
  • Payments are matched through the bank feed, not retyped.
  • The accountant receives an export instead of a collection.
  • An additional tenant does not cost an additional administration.

What happens next

  1. Analysis, freeWe look at how you work today.
  2. ConsultationWhat is worth it and what is not.
  3. Demo, freeA system with your processes, ready to click through.
  4. ProposalPrice and scope. Then you decide.

Pick what applies. More than one is fine.

Email or phone is enough.

or

WhatsApp opens with your enquiry. Then we do not need an email.

Hosting in Germany or the EU, GDPR compliant