BCMS

Ensure Annual Financial Statements Are Approved Reviewed Submitted and Published

2 min read

Objective

Ensure annual financial statements provide a true and fair view and are independently reviewed, properly approved, submitted to CBCS and published within current requirements.

Control Activity

For each financial year, Finance completes a reconciled statement and disclosure pack. The Board reviews it, an appointed independent expert or auditor performs the applicable work, the general meeting approves the final statements, and the approved version is submitted and published by the controlled deadlines. Compliance verifies version identity and evidence.

Evidence

  • Expected evidence: Annual-account timetable and current obligation confirmation
  • Expected evidence: Year-end close, reconciliations and disclosure checklist
  • Expected evidence: Draft and signed financial statements
  • Expected evidence: Expert or auditor statement and management letter
  • Expected evidence: Board and general-meeting approval
  • Expected evidence: CBCS submission and acceptance
  • Expected evidence: Website and other required publication evidence
  • Expected evidence: Finding and correction log
  • Evidence location: source evidence in SYS-FIN-001 Odoo Accounting ERP, SYS-ECM-002 Compliance Reporting and Evidence Repository; target Hermes assessment record in Odoo under ISS-HERMES-001.
  • Retention: according to the applicable approved policy and Bitkaya record-retention requirements.
  • Testing method: inspect the complete annual cycle for reconciliation, independent review, approval, deadline, version identity, submission, publication and follow-up
  • Testing frequency: annual and after correction or resubmission

Assurance

Runtime effectiveness results are maintained in Odoo and assessed through the Hermes workflow tracked in ISS-HERMES-001. This note defines design, ownership, evidence expectations and testing method; it does not contain a manually maintained operation, evidence or overall effectiveness rating.

  • Design status: implemented

History

  • 2026-07-26: Normalized evidence metadata and separated design status from runtime effectiveness.
  • 2026-07-26: Created from the approved FIN Manual.

Graph View

Backlinks