10.3 Prepare Compliance Reports

Element 2: Turning Findings into Management Reports

Element 2 Prepare policy compliance report completes the HCS412305 cycle. After you design/update the manual (PC 1.1) and check compliance (PC 1.2), you must communicate results. The Training Regulations state:

• 2.1 Policy compliance reports are prepared in accordance with the internal control system
• 2.2 Policy compliance reports are submitted to management for validation

In workplace and assessment practice, validated reports are then filed for future reference—so later reviews can compare trends, prove monitoring occurred, and support owner decisions. The Evidence Guide’s critical aspects explicitly include preparing compliance reports.

Report purpose: A compliance report is not a journal entry and not a financial statement. It is a management control document that answers: For this period, which internal control policies were followed, which were breached, and what should management do next?

TR Range: Monthly, Quarterly, and Annual Reports

The Range of Variables elaborates accounting/compliance report types that may include, but are not limited to:

Choose the type that matches the assessment brief or the firm’s IC manual monitoring calendar. A monthly report is narrower and more operational; an annual report is strategic and cumulative.

What changes by report horizon

• Monthly: emphasize current exceptions, peso exposure, and immediate corrective actions
• Quarterly: emphasize patterns (repeat OR gaps, recurring unauthorized purchases) and whether prior month recommendations were implemented
• Annual: emphasize overall compliance rating by policy area, proposed IC manual updates (feeds back to PC 1.1), and residual risks for next year’s monitoring plan

Preparing the Report (PC 2.1)

Prepare the report in accordance with the internal control system—meaning your criteria come from the firm’s manual/policies, not from inventing new standards midstream. A clean NC III-ready structure looks like this:

Recommended report outline

1. Header — Business name; title “Policy Compliance Report”; period covered; report type (monthly/quarterly/annual); preparer name/position; date prepared
2. Objective / scope — Which policies were reviewed (sales, HR, cash handling, purchasing) and for what period
3. Reference framework — IC manual version/date used as the compliance standard
4. Procedures performed — Walkthroughs, samples sizes, documents inspected
5. Findings — By policy area, with Compliant / Partially compliant / Non-compliant status
6. Exceptions detail — Document numbers, dates, ₱ amounts, policy clauses violated
7. Risk implications — What could go wrong if uncorrected (loss of cash, ghost payroll, unauthorized buying, misstated sales)
8. Recommendations — Specific, assigned, dated actions
9. Management validation block — Space for manager/owner signature, date, and comments
10. Filing reference — File code / folder location once validated

Sample findings table (monthly excerpt)

Writing style that assessors reward

• Be factual and dated
• Cite documents (OR, CV, PO, timesheet IDs)
• Separate finding from recommendation
• Do not bury non-compliance under vague praise
• Keep peso figures consistent with working papers from PC 1.2

Mini narrative paragraph (acceptable tone)

“For the month ended June 30, 2026, Laguna Parts Trading’s sales documentation was mostly compliant, except for a break in the Official Receipt sequence at OR 1057. Cash handling was non-compliant because ₱48,200 of June 3 collections were deposited only on June 6, contrary to the next-banking-day deposit policy. Purchasing was non-compliant for CV-214 (₱22,500) paid without an approved purchase order above the ₱10,000 authorization threshold. HR payroll sampling for the June 15 payroll showed no exceptions. Management validation is requested on the recommendations below.”

Submit to Management for Validation (PC 2.2)

Submission is part of competence—not an afterthought. “Validation” means management reviews the report, confirms they understand the findings, and formally accepts (or amends) the conclusions and action plans.

Practical submission package

1. Compliance report (signed by preparer)
2. Supporting schedules / sample lists
3. Copies or references of key exception documents
4. Prior report (for quarterly/annual follow-up), if applicable

Management validation evidence

On assessment day, if the project brief says “submit to management,” include a signature block and a short transmittal line (“Submitted to: Owner-Manager, for validation”). Leaving the report unsigned and undirected weakens PC 2.2 evidence.

Scenario: Validation changes the file

Scenario — Owner review. The bookkeeper reports purchasing non-compliance on CV-214. The owner validates the finding but notes that an emergency verbal approval was given by phone. Management comments: “Exception accepted for CV-214; future emergencies require same-day written confirmation.” The validated report now includes that comment, and the IC manual update queue gains a clarifying emergency-purchase rule. That is healthy control governance—not a reason to hide the original exception.

File for Future Reference

Filing closes the monitoring loop. Industry practice for Philippine MSME bookkeeping offices:

• File by period (2026-06 Monthly Compliance; 2026-Q2 Quarterly Compliance; 2026 Annual Compliance)
• Keep validated signed copy, not only the draft
• Cross-reference related bank reconciliations / petty cash counts filed under cash controls
• Retain supporting exception copies with the report or a clear index to their location
• Restrict access if the report contains payroll/HR details

Filing checklist

• Final report includes preparer name and date
• Management validation signature/date present
• Period and report type clearly labeled on the file tab/header
• Exception supporting papers attached or indexed
• Recommendations’ due dates visible for next period follow-up
• Prior open items reviewed and status updated (especially quarterly/annual)

Linking Report Types to Assessment Strategy

Candidates sometimes write a beautiful findings table and then forget the submit and file steps. Element 2 is a three-beat rhythm: prepare → submit/validate → file.

Common Traps on Element 2

Closing Checkpoint for Chapter 10

HCS412305 Element 1 designs and tests the control system; Element 2 reports the truth to management. If your manual is clear, your compliance tests are evidenced, and your monthly/quarterly/annual report is prepared, validated, and filed, you have demonstrated the unit’s critical aspects: prepared internal control manual and prepared compliance reports. Chapter 11 then applies related cash and bank control techniques (petty cash, bank reconciliation, book adjustments) that often supply the detailed evidence behind these policy conclusions.