Compendium
Every obligation, in one versioned library.
Every requirement from the rulebooks that apply to you, versioned and maintained centrally. Mark applicability per entity and licence, with reasons.
What it replaces
A spreadsheet of rulebook extracts copied from the regulator's website, with no record of which version it came from or when it last changed.
How it works
Step 1
Start from maintained content
Requirements are loaded centrally. Each carries its regulator, rulebook, section reference, text, obligation type, frequency, effective dates, source link and version.
Step 2
Decide what applies
For each entity and licence, mark every requirement Applicable, Not applicable with a reason, or Under review.
Step 3
Stay current
A changed requirement becomes a new version. If you had the old version marked applicable, you get a change task to review it.
Why it exists
A compliance monitoring programme starts from a complete, current list of obligations. Without it, every policy, test and report rests on an assumption.
The compendium makes that list explicit, dated and reviewable. You can show an inspector which version of a rule applied on a given date, what you decided about it, who decided and why.
Compendium content is global and versioned. Your applicability decisions are your own data and sit alongside it. Each obligation is typed as something to do, not do, report, keep a record of, or notify, so the right kind of control and test follows from it.
New regulator content is loaded through a CSV or JSON import and reviewed on a review screen before it is published. VARA content is loaded first. FSRA and DFSA follow in the same structure.