Map the customer records
Organize KYC, CDD, risk rating, transaction, monitoring, and exception files into a reviewable customer evidence set.
Nigeria / CBN / AML, CFT, and KYC records
CBN AML/CFT work is an evidence problem, not another spreadsheet.
We deploy private workflows that organize KYC and CDD files, transaction monitoring evidence, return inputs, and review packs for CBN reporting cycles. The workflow prepares the file; the licensed compliance owner and the institution decide what gets submitted.
KYC / CDD filesTransaction evidenceReturn calendarCompliance review
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
The work behind a CBN return
The institution already holds the records.
The expensive part is proving that the records, controls, and evidence line up when a return is due or a reviewer asks.
Prepare the return inputs
Combine the institution's figures, narrative, source evidence, and open questions into a pack for the compliance owner.
Maintain the calendar
Track monthly and other reporting cycles, owners, evidence status, and follow-ups across the institution's segments.
The CBN boundary
The system prepares evidence. It does not declare compliance.
The compliance officer validates
The workflow flags gaps and prepares drafts. The institution's responsible officer and advisers decide whether the record is sufficient.
Official channels stay official
No submission happens automatically. Filing, portal access, and regulator communication remain with the authorized owner.
Use current terms
CBN circulars and letters are checked against the current official publication before an obligation enters the workflow.
A first AML/CFT workflow
Pick the record set that keeps returning.
Choose the segment
Start with the institution type and the CBN letter or circular that creates the return, such as the statutory monthly returns letters.
Map the evidence
List the customer files, monitoring records, exceptions, and reports that support the obligation and the responsible owner.
Run a completeness check
Compare the evidence set against the current official requirement and review missing, stale, or uncertain items.
Build the review pack
Prepare the summary, source index, exceptions, and open questions for the compliance owner and any required adviser.
AML/CFT records are useful when the obligation, evidence, and owner stay connected.
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Common questions.
Can it submit a CBN return?
No. It prepares and checks the evidence pack. Submission and responsibility stay with the institution and its authorized compliance owner.
Does it decide whether a customer file is compliant?
No. It organizes records and flags gaps. The compliance officer and the institution's advisers make that judgment.
Which CBN terms does this use?
The page starts from the statutory monthly returns letters and the baseline standards circular for automated AML/CFT/CPF solutions, but the current official version is confirmed before any build.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with one obligation
Which AML/CFT record set is hardest to keep current?
Tell us the institution type, the CBN return, the evidence you hold, and the review owner. We will scope the first workflow around the records you already trust.