Beam Machine Assurance and Advisory Manual
User manual for practice, statutory, ESG, audit, controls, valuation, transfer pricing, documents, and approvals.
Managing Assurance and Advisory Work in Beam Machine
This page shows specialist and review-heavy users where to manage engagements, evidence, statutory records, audit work, controls, and advisory delivery in Beam Machine.
Product: Beam Machine
Module: Assurance and Advisory
Role: Audit User, Reviewer, Advisory Lead, Compliance User, Specialist
Difficulty: Intermediate to Advanced
Time: 15 minutes first read
Last Updated: 2026-03-10
Version: Current Beam Machine app build in this repo
Before You Start
- You should know whether you are working on an engagement, a legal entity record, a compliance review, or a specialist deliverable.
- You should know which client or entity the work belongs to.
- Keep 15-payroll-audit-controls-and-advisory.md and 98-screen-map.md open if you need detail.
What is assurance and advisory work in Beam Machine?
This is the part of Beam Machine used for structured review work, professional delivery, evidence gathering, and specialist governance processes. On paper, this would be your engagement files, working papers, review notes, statutory registers, control matrices, ESG packs, valuation files, and transfer-pricing document sets.
In Beam Machine, that work is split across Practice, Statutory, ESG, Audit, Controls, Valuation, Transfer Pricing, Documents, and Approvals.
When do you use this?
Use this page when the work needs evidence, review discipline, deadlines, governance, or specialist output instead of simple transaction processing.
If these workflows are managed in scattered folders and side conversations, teams lose review visibility fast.
Where do you find assurance and advisory work?
Primary path: Use the specialist modules in the left sidebar.
Support paths: Use Documents and Approvals when an output needs supporting files or controlled review.
Reference: Use 98-screen-map.md for route-level detail.
How to run assurance and advisory work safely
Module map
| Area | Main routes | Main use |
|---|---|---|
| Practice | /dashboard/practice/* |
Clients, engagements, timesheets, billing |
| Statutory | /dashboard/statutory/* |
Directors, shareholders, deadlines, B-BBEE, resolutions |
| ESG | /dashboard/esg/* |
Emissions, targets, reports |
| Audit | /dashboard/audit/* |
Engagements, findings, working papers, evidence, plans, monitoring, PBC |
| Controls | /dashboard/controls/* |
Risks, matrix, gaps, compliance |
| Valuation | /dashboard/valuation/* |
Valuation lists, DCF and comparables direction |
| Transfer Pricing | /dashboard/transfer-pricing/* |
TP engagements and document packs |
| Documents | /dashboard/documents |
Shared library for evidence and outputs |
| Approvals | /dashboard/approvals |
Pending approval queue |
Manage advisory or engagement work
- Start in
Practicewhen the main object is the engagement itself. - Review or create the client-facing engagement.
- Use
Timesheetsfor time capture where relevant. - Use
Billingwhen the engagement needs charging workflows.
✅ Checkpoint: The work should be traceable by client and engagement, not only by invoice or private notes.
Manage statutory records
- Open
Statutory. - Review directors and shareholders.
- Check deadlines before filing dates pass quietly.
- Review B-BBEE status and related records.
- Use resolutions where the workflow needs formal governance output.
✅ Checkpoint: Governance records should be visible in the system and easy to explain to a reviewer.
Run ESG work
- Open
ESG. - Review the summary cards.
- Use
Emissionsfor emissions records. - Use
Targetsfor target tracking. - Use
Reportsfor output preparation.
✅ Checkpoint: ESG numbers should stay tied to source evidence, not only final reports.
Run audit work
- Open
Audit. - Create or review
Engagements. - Use
Findingsto track issues. - Use
Working Papersfor structured workpaper packs. - Use
EvidenceandField Evidenceto keep support attached. - Use
Walkthroughs,Audit Plans,Monitoring, andPBC Assemblyas the engagement progresses.
✅ Checkpoint: Findings, evidence, and engagement status should all agree with each other.
Run control assessments
- Open
Controls. - Review
Risks. - Review the
Control Matrix. - Use
Gapsto track remediation. - Use
Compliancefor higher-level control status views.
✅ Checkpoint: Risks, controls, gaps, and remediation should stay connected. If they are split, no one can tell whether the environment is improving.
Work in valuation and transfer pricing
- Open
Valuationwhen the work is a valuation list, DCF flow, or comparables-based process. - Open
Transfer Pricingwhen the work is an engagement or document pack for TP support. - Keep draft, in-review, approved, filed, and amended states clear.
Stay honest about maturity
- Use the current specialist modules for live work.
- Do not document automation, AI explainability, capacity planning, or continuous-monitoring depth as if it is already standard user behavior unless it is visible in your environment.
- Treat
Auto_todo_P3.md,Auto_todo_P4.md, andAuto_todo_P5.mdas roadmap input, not current end-user truth.
Common Questions & Issues
"The route exists, so the full specialist rules library must already be working"
Why this happens: The route tree is broad, and the wider source material describes deeper business logic than the current UI alone proves.
Fix: Use the live workflow and check 99-functionality-gap-map.md before promising advanced behavior.
"We kept the evidence separately and only updated the status in Beam Machine"
Why this happens: Teams often split delivery work from evidence management.
Fix: Use Documents, Evidence, Working Papers, or the relevant module record so the review trail stays attached to the work.
"We manage controls in one place, remediation in another, and approvals in email"
Why this happens: Cross-functional work gets fragmented quickly.
Fix: Keep the risk, control, evidence, and approval trail linked as far as the live module set allows.
What's Next
- Read 15-payroll-audit-controls-and-advisory.md for deeper audit, control, payroll, and specialist SOPs.
- Read 05-admin-and-system-setup.md if the block is approval routing, templates, or documents.
Related Pages
- 05-admin-and-system-setup.md
- 15-payroll-audit-controls-and-advisory.md
- 98-screen-map.md
- 99-functionality-gap-map.md
SA Compliance Reference
- Statutory, audit, controls, tax, ESG, and governance workflows may support South African legal, regulatory, and client-reporting obligations depending on your firm’s mandate.
- Use the module that matches the record you must defend later: statutory register, audit evidence, control remediation, or specialist report pack.
- Do not assume the presence of a route means the full regulatory rules engine is complete.
Still Stuck?
- Check the route in 98-screen-map.md.
- Check module maturity in 99-functionality-gap-map.md.
- Contact support:
support@veva.co.za
Was this page helpful?
[Yes] [No]