Complexity tiers

Limits for bank accounts, business integrations, underwriting records, monthly monitoring records, and analysis scope.

AMLOK assigns complexity based on the full borrower-permissioned workload: bank accounts, business integrations, records processed, and analysis scope. Insights and Signal can use different tiers when their work differs.

Compare the limits

Workload dimension	Standard	Advanced	Complex
Connected bank accounts, up to	2	4	8
Business integrations in addition to banking, up to	5	10	20
Insights: total records per underwriting, up to	75,000	250,000	1,000,000
Signal: newly processed records per borrower/business per month, up to	75,000	250,000	1,000,000
Analysis scope	Routine reconciliation and standard analysis	Multiple entities or channels and deeper reconciliation	Extensive relationships, exceptions, and investigation

These are workload limits. They cover all relevant sources: bank transactions, payment records, commerce orders, accounting records, documents, and separately analyzed line items. Banking connections do not count toward the business-integration limit.

Insights: full underwriting history

A full underwriting analyzes the agreed historical evidence. Banking statements and transactions cover at least 12 months, and all records processed for that history count inside the tier limit.

For Standard, the entire underwriting must fit within 75,000 total records, including the banking history and other business-system data. A longer agreed lookback uses the same total allowance. Missing history is a coverage issue; it is not represented as complete evidence.

Signal: new monthly processing

Signal counts only records newly processed during the month for the monitored borrower/business. It uses the existing underwriting baseline together with new evidence and changes to reassess risk. Each updated version of an existing record counts as a new record when processed. Count a distinct source record and version once in the applicable processing window; retries and repeated reads of that unchanged version do not add records. Unchanged historical records retained in the baseline do not count again merely because Signal consults them. For example, 1,000 new records and 200 updated versions of existing records count as 1,200 newly processed records.

Monitoring and change-driven reassessment are included in the Signal rate. A detected event does not launch a separately billed Insights underwriting. The total monthly workload combines the borrower/business’s monitoring checks and data sources.

How AMLOK assigns the tier

The AMLOK team selects the lowest tier that covers every workload dimension and the required scope. The most demanding dimension determines the tier; limits cannot be mixed across tiers.

For example, two bank accounts, six business integrations, and 40,000 applicable records require at least Advanced because six integrations exceed Standard. A workload of 300,000 applicable records requires at least Complex even when the source counts fit Standard.

If no published tier covers the work, AMLOK provides a custom quote with agreed limits and scope. Reporting represents it as Standard, Advanced, or Complex with a negotiated rate and explicit limits, rather than a fourth tier.

We review tiers, workload limits, and rates at the annual agreement review. Agree a change in scope with AMLOK before running work that exceeds the current limits during the term.

If the workload reaches its limit

Work already within every agreed limit can continue. AMLOK rejects known over-limit requests, or pauses an ongoing assessment before processing newly discovered records beyond the allowance. We agree any expanded scope and effective rate card before processing resumes. There is no automatic tier upgrade or surcharge. Signal record counts combine all monitors for the borrower/business and reset each UTC calendar month. Workload reports show used and remaining capacity and any blocking dimension.