Beam Machine Assurance and Advisory Manual

User manual for practice, statutory, ESG, audit, controls, valuation, transfer pricing, documents, and approvals.

publicusers

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

  1. Start in Practice when the main object is the engagement itself.
  2. Review or create the client-facing engagement.
  3. Use Timesheets for time capture where relevant.
  4. Use Billing when 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

  1. Open Statutory.
  2. Review directors and shareholders.
  3. Check deadlines before filing dates pass quietly.
  4. Review B-BBEE status and related records.
  5. 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

  1. Open ESG.
  2. Review the summary cards.
  3. Use Emissions for emissions records.
  4. Use Targets for target tracking.
  5. Use Reports for output preparation.

Checkpoint: ESG numbers should stay tied to source evidence, not only final reports.

Run audit work

  1. Open Audit.
  2. Create or review Engagements.
  3. Use Findings to track issues.
  4. Use Working Papers for structured workpaper packs.
  5. Use Evidence and Field Evidence to keep support attached.
  6. Use Walkthroughs, Audit Plans, Monitoring, and PBC Assembly as the engagement progresses.

Checkpoint: Findings, evidence, and engagement status should all agree with each other.

Run control assessments

  1. Open Controls.
  2. Review Risks.
  3. Review the Control Matrix.
  4. Use Gaps to track remediation.
  5. Use Compliance for 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

  1. Open Valuation when the work is a valuation list, DCF flow, or comparables-based process.
  2. Open Transfer Pricing when the work is an engagement or document pack for TP support.
  3. Keep draft, in-review, approved, filed, and amended states clear.

Stay honest about maturity

  1. Use the current specialist modules for live work.
  2. 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.
  3. Treat Auto_todo_P3.md, Auto_todo_P4.md, and Auto_todo_P5.md as 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

Related Pages

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?

Was this page helpful?

[Yes] [No]