Separate entities. Separate boundaries. One consolidated read.

What goes wrong today

One system per entity, one spreadsheet to rule them

Each organization picked its own tools at a different time. Group reporting turns into a quarterly exercise: collect exports of different shapes and hope the definitions match.

Consolidation that quietly breaks isolation

The usual shortcut to group reporting is to put everything in one pot and filter afterwards. That is exactly the arrangement a governance review will question, because a filter is a convention, not a boundary.

Access that is impossible to explain

A programme director needs one entity. A shared finance function needs several. An auditor needs read-only evidence for one year of one organization. Without per-entity roles, the honest answer is that everyone has more access than they should.

Different providers, incomparable numbers

One entity is on Stripe, another on Redsys, a third still records bank transfers by hand. Until those are normalized to the same transaction shape, group totals and the analytics built on them are an estimate.

What connects, and on whose authorization

Each source below is read only after your organization configures and authorizes it.

Stripe

Entities hold their own processor accounts and credentials. The data lands normalized to the same shape, whichever entity it belongs to.

Redsys

Common where entities operate in Spain. Gateway operations are reconciled into the same transaction model as every other provider.

Bank transfers & offline gifts Limited

Entities that still take real giving by transfer keep those gifts in the same ledger as card giving, not in a parallel record. Recorded by your team or brought in by import today. Direct bank connections are on the roadmap.

CSV & spreadsheet imports

Historical giving from each entity’s previous system is imported into that entity’s own workspace, never into a shared pool.

Power BI Limited

Where your board already reviews group finances in Power BI, consolidated fundraising figures can sit there alongside the built-in analytics. Optional, on top of the reporting that is already built in. Licensed separately.

The operating loop for this work

1. Connect per entity

   Each organization authorizes its own providers, website and forms inside its own workspace.

2. Unify and normalize

   Different providers and different currencies resolve to one transaction shape, which is what makes comparison and consolidated analytics possible at all.

3. Keep boundaries

   Supporters, campaigns and configuration stay scoped to the entity that owns them. Access is granted per entity and per role.

4. Analyze and consolidate

   Group-level fundraising performance and opportunities are read across entities without co-mingling the underlying records.

5. Evidence

   Recorded activity and provider references give each entity the trail its own auditors and trustees expect.

How consolidated analytics work without mixing entity data

What matters here is the difference between separation by boundary and separation by filter. A filter is applied by whoever writes the query. A boundary applies whether or not anyone remembers to.

In Donativus, each entity is a tenant-scoped workspace. Its supporters, transactions, campaigns, provider connections, templates and settings belong to that workspace, and a request is answered inside the entity context it was made for. Consolidation reads across those workspaces for people whose role grants group-level access. It does not get to group analytics by putting several organizations’ supporters into a shared table and filtering afterwards.

This is what lets a foundation answer two questions at once that it usually cannot: what did the group raise this year, and can you prove the smaller entity’s donor list was never visible to the larger one.

Access you can describe to a trustee in one sentence

Multi-entity governance usually fails not because permissions are missing but because nobody can state what they currently are. The test is whether you can describe, without opening the system, who can see which entity and what they can do there.

Roles are granted per entity, so a shared finance function can get reconciliation access to three organizations while a programme lead sees only their own. Someone reviewing a single year of a single entity can be given exactly that. When a person changes role, you make the change where the grant lives, not across several disconnected systems, which is the usual reason stale access survives a reorganisation.

Making entities comparable without flattening them

Group analytics only mean something if the underlying facts mean the same thing in every entity. When one organization counts a pledge, another counts a settled payment and a third counts a bank transfer whenever someone gets round to typing it in, the consolidated figure is arithmetic done on incompatible definitions.

Every provider feeds the same normalized transaction model, carrying its provider reference, status, and campaign and supporter links. That makes entities comparable without making them identical. A small entity running two appeals a year and a large one running continuous recurring giving still produce transactions of the same shape, so group recurring health, campaign performance and year-on-year movement can be read across them.

Evidence that survives an audit and a leadership change

Foundations carry a heavier evidential burden than a single charity: several sets of accounts, several boards, often a public reporting obligation on top. The recurring difficulty is not producing a figure but reproducing it a year later, after whoever assembled it has moved on.

Transactions keep their provider evidence and recorded status changes, so a figure traces back to the events that produced it, not to a spreadsheet nobody can rerun. Combined with per-entity role grants, that gives each organization an account of what happened and who could have touched it.

What changes

Isolation you can evidence

Each entity operates in its own tenant-scoped workspace, not a shared pool with a filter.

Group view without co-mingling

Consolidated fundraising analytics are read across entities, not achieved by merging them.

Per-entity, per-role access

Shared functions get exactly the entities they need. Nobody gets the rest by default.

Comparable numbers

Different processors and channels normalize to one transaction shape, so totals mean the same thing everywhere.

How it fits with what you run

• Consolidated analytics read across separate entity workspaces. They do not merge supporters, transactions or configuration into a shared pool.
• Donativus is not a payment processor. Each entity’s own providers capture and settle payments and charge their own fees.
• Each entity’s sources are ingested only after that entity configures and authorizes them. Authorization in one workspace grants nothing in another.
• Built-in analytics cover group and entity fundraising reporting. Power BI is optional for boards that already review finances there.