Sanctions screening software does not have one standard price structure. One vendor may bundle access and checks into a subscription, while another separates platform access, users, customer onboarding, API calls and ongoing monitoring. The useful question is not simply “Which headline price is lowest?” It is “What does each quote cover for the same population and workflow?”
This guide helps buyers normalise vendor quotes without pretending that every cost in a compliance programme belongs to the software. It starts after you have defined requirements and shortlisted suppliers. For product requirements, testing and procurement questions, use the sanctions screening software buyer guide. For current Checklynx prices, use the Checklynx pricing page.
Sanctions screening cost comparisonCompare vendor charges, evaluation access and contract terms on the same basis.1. Vendor and platform invoice costs
Begin with charges that will appear on the vendor's invoice. Ask the supplier to define every term in writing and use the same expected population and screening activity across all quotes.
Define the billing unit
“Per check” is not a universal unit. A quote may use several distinct units at once: monthly platform access, each team member, each customer onboarded, each portal check, each batch row or file, each API call or each customer placed in ongoing monitoring. A transaction containing several parties could also be treated differently from an individual customer screen.
Record:
- the exact event that creates a charge;
- whether a retry or duplicate request is billed;
- how batch rows, transaction parties and customers in ongoing monitoring are counted;
- whether the same unit applies across portal, API and file workflows; and
- which product or dataset is covered by that unit.
This definition matters more than the apparent unit price. Compare current Checklynx billing terms only through the maintained pricing page, rather than copying figures from this guide.
Separate screening category from delivery channel
Screening category and delivery channel are independent quote dimensions. A vendor may charge different rates for sanctions, PEP, wanted-list and adverse-media checks regardless of whether the check is submitted through a portal, customer-onboarding workflow, batch file or API. Another vendor may bundle categories but charge differently by channel.
Record each category once:
| Screening category | What to record |
|---|---|
| Sanctions | Bundled, included, separately priced or not applicable; billing-unit or unit-price structure; applicable channels; any category-specific allowance or overage |
| PEP | The same four fields, without assuming the sanctions rate applies |
| Wanted lists | The same four fields, including which wanted-list product or source group is covered |
| Adverse media | The same four fields, including any source or usage limits |
Then record channel-specific access or processing charges and the buyer's expected volume:
| Delivery channel | What to compare |
|---|---|
| Customer onboarding | One-time processing charge or channel-specific unit, plus expected customers onboarded; distinct from vendor implementation/setup |
| Portal or manual screening | Portal-specific access or processing charge and expected searches, requests or screened parties |
| Batch or file screening | Charge by vendor-defined row, record, file, run or another unit, plus expected volume |
| API | API-specific access or processing charge and expected calls; category pricing remains in the category section |
| Ongoing monitoring | Annual price per customer, included monitored-customer allowance and expected monitored population |
If a category price varies by channel, explain the variation in Notes/Source rather than multiplying four categories across five channels. In the worksheet, enter “Included” where a charge is covered by another fee and cite the relevant quote section.
Identify the pricing model
The billing unit tells you what is counted. The pricing model tells you how those counted units become a charge. Real quotes often combine several models, so record the structure before comparing totals.
| Pricing model | What the buyer should clarify |
|---|---|
| Fixed subscription, unlimited or fair-use | Billing period, included scope and any fair-use restriction, rate limit or exceptional-usage term |
| Pure pay-as-you-go | Unit price, whether any platform fee applies and when usage is invoiced |
| Subscription with allowance and overage | Included usage, overage method and whether unused allowance carries forward |
| Prepaid credits or committed volume | Credit unit, purchase commitment, expiry, rollover, refund and top-up terms |
| Volume-tier pricing | Tier thresholds and whether rates are marginal or reaching a tier reprices the whole volume |
| Per customer or entity | Which customer/entity state creates the charge and whether onboarding and ongoing monitoring are separate |
| Per user or seat | User type, included seats and how additions or removals are billed |
| Module or data package | Which capability, source group or environment each add-on covers |
| Minimum commitment plus usage | Minimum spend or volume, usage calculation and any true-up |
| Enterprise or custom | Negotiated scope, measurement method, limits and price-change process |
| Hybrid | Every component above that contributes to the invoice |
No model is universally cheaper. Normalise each quote against the same products, user access, populations, workflows, expected volumes, contract period and support requirements. A minimum commitment is normally a floor under the relevant agreement, not another fee to add automatically; confirm its treatment in writing.
Make optional items visible
A low base price may exclude capabilities or services needed for the intended workflow. Check whether the quote includes or separately prices:
| Item | Question to answer |
|---|---|
| Data or source packages beyond usage prices | Which sources or product categories require a separate subscription? |
| Ongoing monitoring | What is included in the annual per-customer price and what change or event affects the charge? |
| Test-environment access | Are production and sandbox environments included in the platform fee? |
| Case and evidence functions | Are review users, storage or export functions separately priced? |
| User access | Are named, concurrent, read-only or administrator seats charged differently? |
| Support and service levels | What support is standard, and which response or service terms require another package? |
| Additional legal entities or environments | Does the quote cover the buyer's full organisation and deployment model? |
The presence of a real-time screening API, CSV batch screening, ongoing monitoring or case management on a product page does not by itself establish the commercial terms. Verify the current quote.
2. One-time implementation costs
Keep implementation separate from recurring platform charges. This allows procurement to see which costs happen once, which may recur during material changes and which belong to the vendor rather than the buyer.
Vendor implementation charges may include:
- implementation or setup services;
- data migration or import support;
- configuration workshops;
- integration or solution-design services;
- training; and
- project support during acceptance and launch.
Ask what deliverable each fee covers, what the buyer must provide and what would trigger a change request. Confirm whether a sandbox or trial is included and whether usage during testing is billable.
Your organisation may also need engineering, data preparation, security review, configuration and user-acceptance testing. These are important planning considerations, but they are not automatically part of the platform price. Estimate them in your implementation plan rather than adding an arbitrary salary allocation to a vendor-cost headline.
There is no safe universal implementation duration. Compare vendors against the same written scope and test representative workflows. Availability of an API or CSV import is a capability, not proof that a particular migration will be quick or inexpensive.
3. Optional customer operational workload
Analyst workload can affect a business case, but it should remain a separate buyer-owned assessment. A software quote cannot establish what your compliance team will cost to operate, and a generic industry false-positive rate is not a reliable substitute for testing.
During a controlled pilot, record:
- the number of screening requests;
- the number of candidate alerts returned;
- average first-line review time;
- the number and type of escalations;
- whether unchanged, previously resolved candidates require repeat work; and
- evidence or reporting work required outside the platform.
Use these observations to compare workload under the same test population and configuration. Do not convert them into a promised saving unless the measurement method, baseline and scope support that conclusion.
A screening request is not the same as a candidate alert, and a candidate alert is not a confirmed sanctions match. Fewer alerts alone do not demonstrate a better control: a less sensitive configuration may also reduce candidates. The false-positive reduction guide explains how to assess candidate quality and review work without relying on one unsupported accuracy figure.
The downloadable worksheet covers vendor charges, evaluation access and contract terms. Keep workload observations in the pilot record so they cannot be mistaken for invoice items.
4. Contractual and exit considerations
Commercial comparison should cover how the agreement behaves over time, not only the first invoice.
Record:
| Contract term | What to verify |
|---|---|
| Minimum commitment | Minimum monthly or annual spend, committed volume and any true-up |
| Contract period | Initial term, renewal process and notice periods |
| Price changes | Indexation, usage-band changes and renewal pricing |
| Overage controls | Notifications, hard limits and treatment of unexpected volume |
| Data retention and export | What can be exported, in which format and at what point |
| Termination | Notice, outstanding commitments and continued access to evidence |
| Exit assistance | Any vendor charges for export, archive, migration or transition support |
Do not assume that a contractual exit charge captures the buyer's full switching effort. Parallel running, migration and re-integration may require a separate internal plan outside the vendor-price worksheet.
5. Evaluate access before committing
A guided demonstration is not the same as testing the product independently. A vendor-led session can explain the intended workflow, but buyers also need to see how the software behaves with representative names, screening categories, delivery channels and review cases.
Record the conditions attached to evaluation access:
| Evaluation question | What to verify |
|---|---|
| Access model | Self-service trial, restricted sandbox, guided demonstration or another arrangement |
| Steps before access | Whether an NDA, discovery calls, commercial qualification or procurement steps are required |
| Trial duration and billing | Number of days, credit-card requirement and whether access converts automatically into a paid subscription |
| Product scope | Which screening categories, sources, workflows and environments can actually be tested |
| Representative testing | Whether the buyer can use suitable test data and its own representative edge cases |
| Integration access | Whether portal, batch and API workflows are available during evaluation |
| Results and evidence | Whether candidates, review history, reports or evidence can be exported |
| Support | What help is available while configuring and testing the evaluation |
| Time to usable access | How long it takes from the initial request to a working test environment |
These conditions do not establish product quality by themselves. They determine how much independent evidence the buyer can collect before signing a contract.
The evaluation process should also clarify the requirement rather than collapsing every control into generic “AML screening.” Sanctions, PEP, wanted-list and adverse-media screening have different purposes, sources and possible pricing structures. The vendor should document which categories and workflows the buyer needs before producing a quote.
6. Assess control quality separately from cost
The lowest comparable vendor invoice is not automatically the appropriate choice. Price comparison cannot determine:
- whether the required sanctions sources and populations are covered;
- how matching behaves with the buyer's names, scripts and identifiers;
- whether candidates can be investigated and evidenced adequately;
- whether changes to data, lists or configuration are controlled; or
- whether the design fits the organisation's applicable sanctions obligations.
Test these questions independently using buyer-owned requirements and representative cases. OFAC describes sanctions compliance as risk-based rather than one-size-fits-all. The Wolfsberg Group describes screening as one element of a wider financial-crime risk-control framework and discusses technology selection, configuration, testing and continuing resources. Neither source prescribes a vendor pricing model or cost formula.12
Use the CSV to compare vendor charges, evaluation access and contract terms. Keep proof-of-concept results and the control assessment in the buyer guide or evaluation record; they answer a different question.
How to use the comparison worksheet
The downloadable CSV provides Vendor A, Vendor B and Notes/Source columns. Duplicate the vendor columns if more suppliers are shortlisted.
- Use current quotes, order forms and vendor documentation.
- Record the pricing model, billing period, minimums, credit or tier rules and fair-use terms.
- Record category pricing for sanctions, PEP, wanted lists and adverse media, including the channels to which each rate applies.
- Apply the same expected onboarding, portal, batch, API and ongoing-monitoring volumes to both vendors.
- Enter “Included,” “Not included” or “Not applicable” where appropriate instead of leaving a bundled charge ambiguous.
- Cite the quote section, document and date behind each entry, then assess workload and control quality separately.
Where Checklynx fits
Checklynx publishes current prices, included access and a usage estimator on its pricing page. Checklynx also offers a 30-day free trial with full access and no credit card required; registration requires a business email. Buyers can therefore test the product directly before committing. Use the same volumes, representative cases and questions from this guide when comparing Checklynx with another option. Verify current limits, trial terms, contractual terms and workflow behaviour against the live site, product documentation and your quote.
Review current Checklynx pricing