Skip to main content
Baobyte AML Suite

Guides

Handbooks for the work, not for the pitch

Long-form guides written for practitioners who have to make a control work on Monday. Each one goes further than the blog article beside it: the full method, the worksheets, and the governance record the exercise should leave behind.

The library

What is planned, and what it will contain

Every guide below is outlined and none is yet written. The outline is what tells you whether it would be worth your time, and registering interest is what decides the order we write them in.

Placeholder — none of these assets has been written; the outlines below are statements of intent and no download exists yet. Replace with sourced, approved content before this page is made public.

  • Planned

    The Nigerian AML/CFT compliance handbook

    An orientation to the Nigerian obligations landscape for a compliance function being built or rebuilt: who supervises what, which duties attach to which licence, and what evidence each one expects.

    Written for: Chief compliance officers and MLROs at CBN-licensed institutions and DNFBPs

    What it will cover

    • Which authority supervises which obligation, and how the supervisory relationships fit together
    • The programme elements a supervisor expects to find, and the evidence each one produces
    • Where the operative thresholds, deadlines and formats are published, and how to keep a copy that is current
    • A gap-assessment worksheet mapping each obligation to an owner, a control and an evidence location
  • Planned

    Transaction monitoring rule tuning guide

    The full method behind the tuning article: how to instrument a rule set, how to run above-the-line and below-the-line testing, and how to document a change so it survives review.

    Written for: Monitoring leads, model owners and internal audit

    What it will cover

    • The per-rule metric set to establish before any parameter is changed
    • Designing a disposition reason vocabulary that produces a diagnosis rather than a queue count
    • Above-the-line and below-the-line test design, including sample sizing and reviewer independence
    • A tuning proposal and approval record template
    • Post-change review: what to compare, when, and who signs it off
  • Planned

    Building a defensible investigation file

    A working handbook on case file quality: narrative structure, evidence hygiene, the language that survives review, and how to run a quality assurance programme that measures decisions rather than throughput.

    Written for: MLROs, investigation team leads and quality assurance reviewers

    What it will cover

    • The narrative skeleton, with worked examples of the same facts written well and badly
    • Evidence snapshotting: what to capture, and why a live link is not evidence
    • A quality assurance scoring sheet and a calibration process for reviewers
    • How to document a decision not to report to the same standard as a decision to report
  • Planned

    Customer risk assessment design workbook

    A step-by-step workbook for designing, weighting, testing and governing a customer risk model, including the validation tests that show whether it discriminates at all.

    Written for: Compliance policy owners, model owners and internal audit

    What it will cover

    • Selecting and justifying factor families against your own book
    • Turning weights into an approved, versioned policy decision with a written rationale
    • Mandatory triggers, and why they belong outside the arithmetic
    • Distribution, back-testing, stability and coverage tests, with worked interpretation
    • An override governance pack: reason codes, approval, expiry and reporting
  • Planned

    Regulatory reporting readiness: what to obtain before you build

    The list of authoritative inputs a reporting build cannot proceed without, why each one is a release blocker rather than a documentation gap, and how to govern them once you have them.

    Written for: MLROs, reporting leads and implementation programme managers

    What it will cover

    • The artefacts to obtain from the receiving authority, and who in the institution owns each request
    • Recording a mapping so it is reviewable: authority artefact, schema version and digest, code lists, transformation, validation, evidence, maker and checker
    • Fixture design: valid, boundary, conditional, rejection and acknowledgement cases
    • Why a reporting pipeline should refuse to submit without external evidence of the submission

    Free to read now

  • Planned

    DNFBP onboarding and SCUML readiness

    How to onboard designated non-financial businesses and professions when the category taxonomy, identifier format and evidence schedule have to come from the supervisor rather than from a vendor.

    Written for: DNFBP compliance officers and the institutions that bank them

    What it will cover

    • Capturing a supervisory registration identifier honestly when no verification interface exists
    • Designing an evidence list that the institution owns and can change under governance
    • Coding Nigerian addresses to a stable state and local-government vocabulary
    • What to confirm with the supervisor before treating any filing duty as settled

    Free to read now

Registering interest tells us which of these to write first, and we will send it when it exists. We will not send you a benchmark figure we have not measured or a template we have not had reviewed — which is the reason this shelf is shorter than it could be.

In the meantime

The blog covers the same ground, free and ungated

Three practitioner articles on monitoring noise, investigation quality and customer risk model design are published in full, with no form in front of them.