The function you actually run, in one system.
Compliance software for a regulated firm with one regulated entity and one Compliance Officer who owns everything: obligations, risk, controls, monitoring, the board pack. Vantage Point runs the whole spine so nothing lives in a spreadsheet that only you understand.
The situation
One regulated entity. One compliance function that owns the obligations register, the risk assessment, the CMP and the committee pack, today spread across files that only reconcile the night before a meeting.
- The obligations register is a spreadsheet last reconciled the night before the audit.
- Monitoring drifts: the schedule lives in one file, the findings in another, the actions in email.
- A rule change means re-reading the Code and hoping nothing was missed.
- The committee pack takes a week to assemble and is stale on arrival.
| Test plan | Completed | Tests | Actions | Status |
|---|---|---|---|---|
| Q1 2026 AML/CFT Testing Programme | 43% | 7 | 2 | Active |
| NAV Accuracy Testing Programme Q1 2026 | 78% | 9 | 0 | Active |
| JFSC Code of Practice Compliance Review | 33% | 3 | 0 | Active |
| Investor Communications Review | 44% | 9 | 0 | Draft |
| Annual Trust Administration Review 2026 | 11% | 9 | 0 | Draft |
How Vantage Point runs it
- 01
Day one: select the licence type. The system populates the obligations register, risk taxonomy and starter controls.
- 02
Week one: review the risk register, tighten the controls that need it, sign off the CMP for the year.
- 03
Each month: scheduled tests run on the calendar. A failed test raises a corrective action automatically, with an owner and a deadline.
- 04
When the regulator updates a Code: the change is flagged line by line, and the action against the affected controls is one click away.
Outcome
One system. One audit trail. The committee pack pulls live, the day before the meeting.
The single-entity firm is where the spreadsheet estate hurts most, because one person carries it. Vantage Point replaces the estate, not the person: the methodology stays yours, the evidence assembles itself.
The spine, in the platform: the regulatory library holds the obligations and flags regulatory change; the risk register scores inherent and residual risk against your appetite bands; controls map to what they satisfy; the compliance monitoring programme tests them and raises actions when they fail; and the committee pack pulls from the same records. Two guides cover the parts most functions get wrong: What a compliance monitoring programme should contain and What the committee pack needs, and what it does not.
- Unlimited users: the whole firm sees the same truth
- Fourteen pre-built registers from day one
- Every change timestamped, attributed, exportable
Your existing registers and data come in during onboarding, and your administered book can sync from the systems you already run. Live in days, not months.
How you get startedQuestions from compliance officers.
- Do we have to move everything at once?
- No. Most single-entity firms start with the registers and the risk assessment, bring the monitoring plan across in the first month, and retire the spreadsheets as each one is superseded. The whole spine is available from day one; the order you adopt it in is yours.
- How long does onboarding take?
- Live in days, not months. Day one models the firm and the licence type populates the library, taxonomy and starter controls; your existing registers, risk assessment and monitoring history come across in the first week, imported for you and checked with you; the CMP is signed off and running by the first month.
- Will it work if I am the whole compliance function?
- Yes. One owner, one system: reminders, calendar and dashboards keep the plan running when the function is one person, and the committee pack pulls itself the day before the meeting.
- What does the board see?
- A pack assembled from live data: risk register, appetite position, controls effectiveness, monitoring plan progress, open actions and coverage, with every number tracing to a record.
- What happens when the Code changes?
- The library flags the change with a line-by-line diff and lists the obligations affected; the action to deal with it is one click away, with an owner and a deadline.
In the platform, and in the guides.
- GuideWhat a compliance monitoring programme should contain
- GuideInherent, residual and appetite: scoring risk in a compliance function
- GuideRegulatory change without re-reading the Code
- ModuleRegulatory library: Pre-built. Kept current.
- ModuleRisks: Inherent. Residual. Entity-scoped.
- ModuleControls: Mapped to what they satisfy.
- ModuleCMP: Doing it right.
- ModuleReports: Live data. Committee-ready.
See it running on your structure.
A 30-minute walkthrough using your entities, your licences and a real workflow you bring to the call. No slide deck.