Most compliance teams can say that their controls exist. Far fewer can show, with evidence an auditor will accept, that those controls were tested, how the sample was chosen and what was concluded. This Excel-based engine gives a second line compliance team one structured place to plan, test, evidence and report its financial crime monitoring and testing program.
The engine builds a risk-based annual test plan, ranks tests by risk, assigns them to quarters and checks the plan against tester capacity. It calculates statistical sample sizes (for example 59 items at 95 percent confidence and a 5 percent tolerance) and selects the sample using a seeded method with a fingerprint, so a reviewer can reproduce exactly the same sample later.
Test conclusions are calculated from the recorded results, not typed in as opinion. A 13-step sign-off gate blocks any test that is missing evidence, review or approval. Issues are tracked with severity, due dates, escalation to the CCO, risk acceptance expiry and repeat findings across a 24-month look-back.
An assurance map shows which regulatory obligations are covered by which line of defence, and which have no assurance at all. A Command Centre dashboard summarises program health with ten KPI tiles, charts and six ranked action lists, and 45 built-in integrity checks flag broken or missing data. Role-based passwords separate the Owner, Head of Testing and Tester.
Who it is for: compliance officers, MLROs, CCOs, testing and assurance teams, internal audit, and consultants who build monitoring programs for banks, fintechs and other regulated firms.
What is included: the primary file is the full workbook. The secondary file is a ZIP containing a fully populated demo workbook that uses a fictional bank, a user guide, the access keys, the terms of use and a short buyer tutorial video. It runs in Excel 2016 or later on Windows with no macros and no add-ins. It is a testing and documentation tool. It does not connect to core banking, screening or alert systems, and it does not replace professional judgement or legal advice.
Got a question about the product? Email us at support@flevy.com or ask the author directly by using the "Ask the Author a Question" form. If you cannot view the preview above this document description, go here to view the large preview instead.
Source: Best Practices in Audit Management, Compliance Excel: FinGuard Studio Compliance Monitoring & Testing Engine Excel (XLSX) Spreadsheet, FinGuard Studio