Membership report by date interval
- Mattias Jacobsson
https://brpsystems.atlassian.net/wiki/x/YgHliw Documentation for the report in BRP Cloud.
The key difference between the report “Membership report by date interval” in BRP Cloud and the numbers displayed in Embedded BI for the Members' outgoing balance lies in how frozen memberships are handled.
In BRP Cloud, the logic dictates that the outgoing balance should match the ingoing balance for the next period. As a result, subscription freezes that begin on the 1st day of a new month are excluded from the outgoing balance of the previous month.
In contrast, Embedded BI is more dependent on calendar-based selections. The outgoing balance is always reported as of the last day of each month, meaning it does not account for changes occurring the following day (i.e., the 1st of the next month).
This leads to a difference in how a membership freeze starting on the 1st of a month is handled in BRP Cloud versus Embedded BI:
System | Outgoing Balance (Members) | Outgoing Balance (Frozen Members) |
|---|---|---|
BRP Cloud | 0 | 1 |
Embedded BI | 1 | 0 |
This logic means that the outgoing balance (active members) in BRP Cloud for January 20XX will correspond to the ingoing balance (IB) of members in Embedded BI for February 20XX.
The same principle applies to frozen memberships—the outgoing balance (frozen members) in BRP Cloud for January 20XX should align with the ingoing frozen balance (IB) in Embedded BI for February 20XX.
In BRP Cloud, the option "Allow change of facility" should be ticked to align with the logic in Embedded BI, where a facility change is not treated as a membership termination or a new membership within the given period.