5.1(a)
Customer identification and verification
Customers are identified and verified through vendor KYC checks with deterministic pass or fail results.
A checklist built around the Central Bank of Nigeria (CBN) baseline standards for automated AML solutions, showing what OneView provides and how your installation uses it.
5.1(a)
Customers are identified and verified through vendor KYC checks with deterministic pass or fail results.
5.1(b)
Customers are rated for risk by scoring policies that are configurable per customer type.
5.1(c), 5.1(d)
Customers are screened against sanctions, watchlists and PEP lists, and every match needs an analyst to confirm or reject it.
5.1(e)
Transactions are monitored as they are received with configurable rules and thresholds.
5.1(f)
Cases carry evidence, ownership and decisions, and closing, reopening and exporting a case can need approval from a second person.
Instead of answering a long questionnaire from memory, open one page that lays the circular out requirement by requirement.
Each row carries the Central Bank of Nigeria circular reference it answers, with a plain statement of what OneView provides, from customer verification and screening to monitoring, case handling, reporting and the audit trail.
Every requirement shows whether OneView has the capability built, so your team, your auditors and your board can see the product position without a workshop or a spreadsheet.
Search by reference or requirement wording, and filter by status, so a reviewer can go straight to the row they are asked about.
The checklist is a disclosure. Reading it never edits a setting, and access is limited to the people your administrators allow.
Each row keeps two answers apart, so the product's capability is never confused with how your team has set it up.
Whether OneView has the capability. A requirement reads Compliant when the feature exists in the product, and a requirement OneView does not cover yet reads Not compliant, stated plainly in one sentence.
How your own deployment uses the capability: In use, Needs attention, Not set up, or Not available in your license. The summary is one factual line, with the evidence behind it.
Where something is not yet set up, the row offers a direct action to the right settings page, shown only to people whose role allows them to make the change.
Some obligations are not product features, and the checklist says so honestly. They sit in their own group, are not scored, and are marked as the institution's responsibility.
Confirm your institution's compliance with the Nigeria Data Protection Act.
Confirm that your institution maintains its governance documentation, covering ownership, access controls, model validation and periodic audits.
Confirm the obligations that are yours to carry out, such as risk assessments, closed case reviews, staff training, data retention, vendor management, cybersecurity arrangements and roadmap submission to the Central Bank of Nigeria.
When an audit or a regulator review comes, the checklist leaves the screen as a finished document your team can hand over.
Export the checklist whenever an auditor, the board or a regulator relationship team asks to see it. Each export carries the date it was generated, so you can show exactly where your institution stood at that point in time.
The PDF uses your institution's name, logo and brand colour, with a cover page showing the document title, the date generated and who prepared it. It reads as your record, not a vendor brochure.
Exporting follows the same access rule as opening the checklist, so only people your institution has granted access can produce the document.
See the CBN Baseline Standards checklist with your own modules and settings, and how it turns the circular into a page your team can work from.