CherryMoney University Training: accounting, invoices, VAT, expenses and AI finance workflows
CherryMoney Training
Log in Open account

Module 11

Accountant Workspaces, Governance And Admin Controls

Control role-aware access, accountant client grants, Analytics admin policy, publishing controls, verification and audit trails.

Start module Simulator practice Sign in to take training

Learning Goals

By the end of this module, learners should be able to complete the workflow in CherryMoney and explain the accounting reason behind each important step.

  • Assign and explain accountant, treasurer and volunteer finance admin roles.
  • Use manual verification responsibly.
  • Use bulk user actions for common settings.
  • Explain report lock-down and audit log value.
  • Explain why accountant workspace access must be explicitly granted per client rather than inferred from an accountant role.
  • Use Analytics admin controls to understand feature switches for workspace, ledger, publishing, forecasts, data sources and connectors.

Lesson Plan

Use these lesson blocks for lecture delivery, live demo and class discussion.

Role-aware access

Different users should only see and approve the work they are responsible for.

Manual verification

Admin verification is a support path when email verification fails, and should be used only after checking identity.

Audit and lock-down

Audit logs and locked reports protect finalised finance outputs from accidental change.

Step-By-Step Lab

This is the student-facing sequence for the practical class. Complete the steps in order, then capture the evidence listed below.

  1. Open Manage Users and review the current users, roles and verification status.
  2. Assign role-aware access for accountant, treasurer and volunteer finance admin examples.
  3. Use manual verification only after checking the simulated user details.
  4. Select multiple users and apply a common admin setting.
  5. Open an audit log entry and identify who performed the action and when.
  6. Publish and lock a report, then try to explain what should happen if someone attempts to edit it.

Classroom Run Sheet

Use this structure to teach the module in a repeatable classroom or lab session.

Explain
Explain this module Introduce the accounting concept first: customer, invoice, VAT, expense, fund, role or audit trail.
Demonstrate
Demonstrate this module Trainer performs the workflow once in CherryMoney using a projected simulator account.
Practise
Practise this module Students complete the same workflow in their own VM tenant using seeded records.
Review
Review this module Students compare system outputs with expected accounting treatment and discuss errors.
Evidence
Evidence this module Students submit screenshots, exports, PDFs or short explanations for assessment.

Simulator Practice

These are the VM practice tasks for this module. They are written as student-facing tasks and can later be wired into a guided simulator checklist.

Practice Brief

  1. Create or review three users with different roles.
  2. Manually verify one training user after checking details.
  3. Use bulk select to apply a common setting to selected users.
  4. Publish and lock a report, then explain why lock-down matters.
  5. Grant a fictional accountant access to one client but not another and compare the workspace result.
  6. Toggle a sandbox Analytics policy control and document the expected access change.

Knowledge Check

Use these questions for in-class review, a short quiz or a reflective workbook entry. Answers are hidden by default — open each one to check your work.

  1. Q1 Why should not every user be an admin? Answer

    Because role-aware access means people should only see and approve the work they're responsible for — giving everyone admin removes that boundary and its audit value.

  2. Q2 What should be checked before manual verification? Answer

    The user's identity should be checked first — manual verification is a support path for when email verification fails, not a routine shortcut.

  3. Q3 How does report lock-down protect completed work? Answer

    A published, locked report can't be silently edited afterwards, protecting a finalised finance output from accidental change.

Assessment And Evidence

Students should submit proof that the workflow was completed and a short explanation of the decisions made.

Student Evidence

  • Submit a role matrix showing who can create, approve, export and administer records.
  • Explain the risk of giving all users admin access.

Trainer Notes

  • Use role-play: one student acts as treasurer, one as volunteer finance admin and one as accountant reviewer.

Continue The Course

Move through the modules in order for a complete accounting, invoicing, compliance and AI finance workflow.

Module 9 2 hours

Payroll Summary Packs

Prepare payroll review packs where the plan includes payroll features.
Module 10 4 hours

Charity, VCSE, Grants And Restricted Funds

Teach fund accounting concepts through charity and VCSE workflows.
Module 12 3 hours

Banking, Open Banking And Reconciliation

Review connected-bank data, matching and reconciliation while keeping consent, provider and payment-execution boundaries explicit.
Module 13 4 hours

Cherry Analytics, KPIs And Management Reporting

Use the Cherry Analytics companion workspace for deterministic reporting, KPI review, commentary and evidence where the organisation has Analytics access.