NFP Divisional Reporting with BI4Cloud

Bi4Cloud help-centre guide for finance, program and ministry reporting

Purpose: Use BI4Cloud to report and budget across entities, programs, ministries, grants, projects, locations, services and funding streams—while retaining access to the transaction detail behind each result.

Who this guide is for

This guide is for not-for-profit organisations whose financial performance and stewardship need to be understood below the whole-organisation level. Common examples include multi-site churches, mission organisations, environmental charities, community-service providers, membership organisations and NFPs operating grant-funded projects or social enterprises.

The exact reporting dimensions available depend on your accounting platform and how transactions are coded. Start with the structure already present in the source data, then use BI4Cloud reporting layouts or GL Tags where an additional management view is required.

1. Decide how the organisation should be viewed

Begin with the accountability questions the report must answer. Avoid reproducing every code from the accounting system simply because it exists.

Recommended starting structure

• One primary responsibility dimension, such as program, ministry or service
• One secondary analysis dimension, such as grant, location or funding source
• A group/entity view where multiple accounting organisations are connected
• A clear owner for the coding and hierarchy used in management reports

2. Map the available divisional data

BI4Cloud retains useful platform-specific fields and makes them available for reporting. Typical mappings include:

Check before building: Confirm which fields are populated consistently, whether historical coding changed, and how parent/child names should be displayed. A reliable reporting hierarchy depends on consistent source data or an agreed mapping rule.

Where programs or activities have not been coded through Jobs, Classes or Tracking Categories, BI4Cloud GL Tags can group general-ledger accounts into a management structure. GL Tags are particularly useful when the chart of accounts identifies ministries, services or activities; they do not create missing grant, project or transaction detail that was never recorded in the source data.

3. Build the management and accountability view

Use a BI4Cloud Base Workbook as the starting point, then adapt the layout to the organisation's operating and funding structure.

1. Select the entities and reporting period.
2. Choose the financial metrics required, such as income, direct costs, operating expenses, surplus or deficit and margin where relevant.
3. Add the primary program, ministry, service or project as rows or columns.
4. Add a funding source, grant, campus or location only where it helps a manager understand responsibility.
5. Group related activities into a hierarchy and enable expand/collapse where appropriate.
6. Add period, year-to-date, Budget, Forecast and variance comparisons.
7. Save the Workbook as the common reporting version.

Example layouts

4. Investigate results at transaction level

An NFP report should help a manager move from “what changed?” to “what caused it?”. Where supported by the report and connector, use BI4Cloud drill-down to open the detailed records behind a value.

1. Identify the program, grant, account or metric with an unexpected result.
2. Expand the hierarchy to isolate the relevant ministry, project, location or funding stream.
3. Drill into the detailed records behind the amount.
4. Check coding, timing, supplier, description and the assigned funding or program dimension.
5. Correct the source transaction in the accounting system if required, then allow the BI4Cloud data to refresh.

Transaction detail improves traceability for managers, boards, funders and auditors, but the accounting platform remains the system of record for corrections.

5. Add monthly budgets and reforecasting

Use separate Budget and Forecast layers so the approved plan remains visible while the expected outcome changes.

• Enter monthly values by account and program, ministry, grant, project or location
• Retain the original approved Budget as the baseline
• Update the Forecast or Reforecast independently
• Compare Actuals with Budget and Actuals with Forecast
• Maintain individual years or a multi-year entry where appropriate
• Use Excel export/import for bulk updates, formulas and review workflows

Practical forecast cycle

1. Copy or prepare the current forecast structure.
2. Update remaining months for grant timing, program delivery, staffing and other current assumptions.
3. Review major movements with program owners and finance.
4. Import the approved forecast values.
5. Publish an Actual vs Budget and Actual vs Forecast view for the same reporting period.

6. Give managers controlled access

A common workbook can be shared while access restrictions limit each user to the companies, reports and data defined in their access profile. This allows finance to maintain a consistent reporting framework without giving every manager unrestricted access.

1. Create or confirm the BI4Cloud user.
2. Assign company and report-area access.
3. Apply detailed restrictions for the relevant jobs, classes, tracking codes or other supported dimensions.
4. Share the approved workbook.
5. Test the result as the intended user before rollout.

7. Automate filtered report delivery

For recipients who need scheduled output, use Address Lists and recipient roles so the schedule applies the relevant filter and produces an appropriately filtered PDF or Excel report.

1. Create the recipient and define the applicable role or reporting responsibility.
2. Add the recipient to an Address List.
3. Create or select the Report Pack.
4. Create the Email Schedule and nominate the Address List.
5. Test the output for each access profile before enabling the schedule.

This approach reduces duplicated reports and manual distribution while helping each recipient receive information relevant to their responsibility.

8. Validate before publishing

• Reconcile the group total to the accounting-system result.
• Confirm every active division appears once and in the correct hierarchy.
• Check uncoded or unassigned transactions.
• Test drill-down on revenue, cost and balance-sheet values.
• Confirm budget and forecast versions and periods.
• Test restricted users and scheduled recipients with representative data.
• Document the owner of mappings, GL Tags and report changes.

Keep the first rollout simple

Start with one high-value report—often a divisional P&L with Actual, Budget, Forecast and variance—and a small group of managers. Add deeper hierarchies, transaction views and automated distribution after the core totals and access rules are proven.

BI4Cloud includes 15 pre-built Base Workbooks covering more than 100 reports, so most organisations can begin with a proven structure and customise only what is needed.

Related BI4Cloud help content

• Monthly Divisional Budgets
• MYOB budget setup
• Xero tracking category hierarchy
• QuickBooks Online class and location budgeting
• Run Divisions Using GL Tags
• Excel budget export and import
• Control User Access
• Address Lists and Recipients