Custom Framework lets you bring any compliance framework — an industry regulation, an internal standard, or a client requirement — into ComplyJet and track it the same way you would SOC 2 or ISO 27001. You define the requirements, map your controls, and attach evidence.

Custom Framework is a paid add-on. Before proceeding, confirm that it's enabled in your account. Go to Compliance → Frameworks and look for Custom Framework in the list. It should show as Enabled.

If it shows Request Access instead, reach out to your ComplyJet customer success rep to get it added to your subscription.

Click on Custom Framework from the Frameworks page to open it. Initially, it will be empty with no requirements or controls added.

Before importing anything, update the framework name and description to reflect the actual framework you're implementing. Click the three-dot menu (⋯) in the top right and select Edit Framework. Update the name and description, then click Save changes.

Use the exact name of the framework as it appears in the regulation or standard — this is what auditors will see.

Click Import Framework. This opens the import modal where you upload CSV files that define your framework structure.

There are three required files and two optional files.

Required files

1. Sections CSV
These are the requirements that the framework defines — the actual obligations or rules you need to comply with. Copy the exact wording from the law, regulation, or standard you're working from.

Expected columns: uid, name, displayId, description, principle

2. Controls CSV
These are your internal controls — the things your organisation does to satisfy each requirement. You can either download and reuse controls from ComplyJet's built-in control library, or define your own from scratch.

Expected columns: uid, name, displayId, description

3. Section-Control Mapping CSV
This tells ComplyJet which controls satisfy which sections. A single section can map to multiple controls.

Expected columns: sectionId, controlUId

Optional files

4. Control-Document Mapping CSV
Maps controls to specific policy documents or evidence files that prove the control is in place. You can skip this now and attach documents directly to controls later.

5. Control-Monitor Mapping CSV
Maps controls to automated tests (monitors) that run and verify the control continuously. Again, you can do this later from individual control pages.

Sample files for all five formats are below. Your CS rep can also help you prepare the files if you're unsure how to structure them.

Once all required files are uploaded, click Import. The framework will be initialised with your sections and controls.

After the import, your framework will show all sections with their mapped controls and a Controls Readiness score.

From here you can:

Delete sections you don't need
Click the delete icon next to any section that doesn't apply to your situation.

Remap controls to a section
Click Map Controls next to any section to open the control library and add or replace controls. You can search across all 600+ controls in ComplyJet's library and select the ones that best apply.

Map tests and documents to individual controls
Click on any control to open its detail page. Under the Tests tab, you can map automated tests and policy documents that act as evidence for that control. This is how ComplyJet knows whether a control is passing or failing.