ACNC Crackdown: Turn Governance Proof Into Cash-Flow Certainty
Regulatory expectations on governance and funding transparency are tightening for charities and NFPs. Here’s what the shift means for your cash flow, grants, and reputation—and how to get audit-ready fast.
1) The signal: Why this update matters now
The ACNC’s Governance Standards and recent audit scrutiny are converging with tougher funder due diligence. In practice, this means your next grant drawdown may hinge on evidence that you actively manage conflicts (Standard 5), stay accountable to members (Standard 2), demonstrate your charitable purpose and NFP status (Standard 1), and report accurately and on time (AIS and financials). Weak minutes or missing registers can pause payments, strain cash flow, and invite follow-up.
- Situation type: New compliance obligations and an industry-wide trend—creating an emerging cash-flow risk.
- Immediate stakes: Delayed grant payments, hiring freezes, project re-scoping, and reputational drag.
- Upside: Strong governance proof accelerates funding, simplifies audits, and builds trust.
2) The pause: A quick narrative you can avoid
A mid-sized charity wins a multi-year grant. The funder asks for proof of conflict disclosures, related-party approvals, and procurement checks. Minutes are thin, the conflicts/related-party register is outdated, and files are scattered. Result: payment paused for eight weeks. Cash is tight, hiring stalls, delivery is reshaped—and confidence takes a hit.
This was preventable with a single source of truth and audit-grade documentation.
3) The root causes: Gaps that trip good organisations
- Fragmented records: Conflicts, related parties, and procurement evidence spread across email, personal drives, and legacy folders.
- Light minutes: Discussions captured, but not the decision basis, who voted, abstentions, and conflict management steps.
- Unclear delegation: Related-party payments approved ad hoc without documented thresholds or pre-approval.
- Reporting drift: AIS and financial statements not reconciled to grant acquittals quarterly—errors surface at the worst time.
- Remote variability: Hybrid teams execute processes differently because SOPs are missing or outdated.
4) The 14-day stabilisation sprint
Day 1–3: Build the single source of truth
- Consolidate a combined Related Party & Conflicts Register (board and key management). Include nature of interest, dates, approvals, and management actions.
- Centralise governance evidence in one controlled repository (board pack PDFs, approvals, procurement checks, acquittals). Assign an owner and access rules.
Day 4–7: Lock critical controls
- Mandate board pre-approval for any related-party payments, with documented thresholds and exception handling.
- Standardise minutes to capture: motion, options considered, conflict declarations, how conflicts were managed, vote result, and rationale.
Day 8–14: Prove alignment
- Map evidence to Governance Standard 5 (conflicts) and Standard 2 (member accountability). Append registers and minutes to the board file each meeting.
- Reconcile quarterly AIS/financial statements with grant acquittals; maintain a variance log and remediation notes.
- Document control: version numbers, document owner, last reviewed date, approval signature, and retention period.
“Document your business or get out.” If people leave or work remotely, the system must still run exactly as designed.
5) Make minutes and approvals audit-grade
What “good” looks like
- Conflict protocol: Agenda prompts for disclosures; attendees re-declare standing interests; chair documents management (e.g., leave, observe, abstain).
- Decision clarity: Record the decision, criteria, options, data sources, and accountability (who owns follow-up actions by when).
- Related-party approvals: Cite policy clause, market price checks, and why this option beats alternatives. Attach quotes or benchmarking.
- Member accountability: Summarise how decisions reflect charitable purpose (Standard 1) and how outcomes will be communicated to members (Standard 2).
Template prompts to embed
- Disclosure recorded? Conflict managed? Abstentions noted?
- Evidence attached (quotes, due diligence, comparative analysis)?
- Decision rationale and risks logged?
- Action owner, due date, and reporting line set?
6) Close the loop: Finance, procurement, and grants working as one
Funders are testing related-party transactions, procurement, and acquittals together. Treat them as a single control chain.
- Procurement tiers: Define thresholds for 1/3 quotes and board sign-off; document exceptions with rationale.
- Vendor due diligence: ABN/ACNC checks, sanctions/terrorism risk screening (noted by the ACNC Commissioner), and related-party lookups.
- Acquittal pack: Budget vs actuals, variance log, contract milestones, procurement evidence, and conflict/related-party approvals—kept in one folder.
- Monthly control tests: Randomly sample payments for policy compliance; report findings to the board audit & risk committee.
When this chain is demonstrably tight, grant payments resume faster and audits get easier.
7) Strategy: From reactive compliance to an operating system
Make governance a repeatable, team-wide habit—especially with dispersed teams.
- Policy + SOP library: One authoritative hub for board governance, conflicts, procurement, grants, and reporting. Remote workers follow the same steps every time.
- RACI and control owners: Name who approves, who records, and who tests. Avoid “everyone owns it” (which means no one does).
- Cadence calendar: Board meetings, register refresh, quarterly reconciliations, acquittal due dates, and AIS deadlines.
- Continuous controls monitoring: Small monthly tests beat last-minute audit scrambles.
8) Action: Start small, move fast
This week, pick three artefacts to make bulletproof: your Related Party & Conflicts Register, your minutes template, and your procurement thresholds. Next week, run a mini control test on five payments and fix what you find. Use ACNC’s free Governance Hub resources, webinars, and Charity Chat to train your team. Your goal is simple: cash-flow certainty through governance proof.
