Skip to content

Case Management Platform (CMP)

The Case Management Platform (CMP) is the Decision Desk of the Guardline Suite. It orchestrates the lifecycle of cases that require human analysis: fraud alerts, compliance reviews, KYC assessments, risk escalations, and committee deliberations.

The CMP centralizes backoffice work on a single platform, with configurable queues, regulatory SLAs, approval authorities, case distribution, and an immutable audit trail. It works both as an integrated module of the Guardline Suite and standalone, compatible with third-party decision engines.


Cases are organized into queues tied to areas of responsibility. Each queue operates independently, with its own analysts, SLAs, and distribution rules.

QueueAreaScope
OnboardingOnboarding reviewDocument validation, profile data, biometrics
ComplianceAML/CFTRestrictive lists, PEP, UBO, financial compatibility
FraudFraud preventionAdverse media, suspicious patterns, device intelligence
CommitteeCollegiate decisionCases escalated for formal deliberation
CommercialAdvisory opinionCommercial context (advisory voice, no veto power)

The institution can configure additional queues to match its organizational structure.

Each queue and case type operates under configurable deadlines, with defaults based on BACEN/BCRA Circular 3.978:

Risk levelResolution deadlineReference
Low4 hoursFirst response
Medium24 hoursStandard resolution
High48 hoursMandatory collegiate decision
Critical72 hoursExecutive board or committee

Deadlines are configurable by the institution. The system monitors SLAs automatically:

  • SLA at risk: visual and email alert when the deadline is approaching
  • SLA breached: automatic escalation to the next tier
  • Breach rate metrics: real-time operational visibility

Decision authorities define who can make which type of decision. Each authority has a configurable score range. Cases above the limit are automatically escalated to the higher authority. Escalation happens before the decision, not after: the system prevents an analyst from deciding outside their authority.

Risk levelScore rangeAuthorityDecision type
AutoDefined by the institutionSystemAutomatic approval or rejection
LowDefined by the institutionAnalystIndividual decision
MediumDefined by the institutionSenior AnalystIndividual decision, may request joint analysis
HighDefined by the institutionSupervisorMandatory collegiate decision
CriticalDefined by the institutionExecutive Board / CommitteeCollegiate decision with executive board approval

The CMP offers four distribution modes, configurable per queue:

ModeHow it worksWhen to use
By riskRoutes automatically based on scoreDefault configuration, ensures regulatory compliance
Round-robinDistributes sequentially among available analystsBalances load within each tier
By availabilityDistributes based on each analyst's real-time availabilityTeams with varying schedules or seniorities
ManualA manager assigns individually or an analyst self-assignsSpecial cases and reassignments

The modes can be combined. The recommended configuration is by risk as the primary criterion, round-robin as secondary, and manual as an override available at any time.

When the analyst opens a case, they have access to the single-pane dossier:

  • Customer data (profile, score, segment)
  • Transaction history
  • Onboarding result (when the customer came in through the ONP)
  • Alerts and triggered rules
  • Behavioral baseline (UBA)
  • Counterparties involved
  • Position on restrictive lists
  • Prior decisions on the same customer
  • Audit timeline with every event recorded

For each case, the analyst has six available actions:

ActionDescription
ApproveRelease the transaction or onboarding
RejectBlock with a recorded justification
Place pendingRequest additional information from the customer or another area
EscalateForward to a higher decision authority
Request joint analysisRequest an opinion from another area (Compliance, Fraud, Commercial)
Convene the committeeForward to a collegiate deliberation session

Every action requires a written justification and is recorded in the audit trail.

When a case requires input from multiple areas, the analyst requests joint analysis. The case receives independent opinions from each consulted area. Until the opinions are recorded, the case stays locked.

If the opinions diverge (for example, Compliance recommends rejection and Onboarding recommends approval), the system automatically escalates the case to the committee.

For high-risk cases or those with divergence between areas, the CMP runs formal committee sessions with quorum, voting, and minutes.

Committee flow:

Committee rules:

RuleDefinition
Minimum quorum3 members: Compliance/AML + Desk Manager + additional member
VotingSimple majority. In a tie, Compliance/AML's vote prevails (tie-breaking vote)
RecordEach member records vote and justification. Minutes generated automatically
Deadline48h for convocation and deliberation
Conflicts of interestA member with a conflict of interest recuses themselves. The system convenes a substitute
CommercialAdvisory voice, no vote. May present context, no veto power

The system automatically forwards a case to the committee when:

  1. Risk score reaches a critical level (per the configured threshold)
  2. Joint analysis opinions diverge
  3. The customer is a PEP or related to a PEP
  4. The customer is classified as strategic or VIP (a flag set during onboarding)
  5. The SLA is breached without a decision
  6. A manager manually convenes the committee

Every action on the Decision Desk is recorded automatically and immutably:

  • Case creation and source (rules engine, manual, external system)
  • Calculated score and assigned risk
  • Analyst assignment and reassignment
  • Start and end of each analysis
  • Technical opinions from joint analysis
  • Escalations with reason, priority, and destination
  • Committee votes with individual justifications
  • Final decision with a written justification
  • Timestamp for every event

The record is directly accessible by the institution for export, serving as a regulatory dossier for COAF/UIF and internal audits, in compliance with BACEN/BCRA Circular 3.978.

When a case results in a mandatory report, the CMP organizes and formats the data into XML compatible with SISCOAF, making submission easier for the institution.


The CMP does not require the use of Guardline's decision engine. Institutions that already have their own fraud or AML engine can adopt the Decision Desk independently, receiving cases through integration and operating queues, decision authorities, SLAs, and the committee on top of any alert source.


ProfileAccessDescription
AnalystDecision DeskAnalyzes cases within their decision authority
ManagerOperations, queues, settings, dashboardsConfigures flows, monitors SLAs, reassigns cases
DirectorCommittee + everything from ManagerParticipates in committees, creates sessions, approves high-authority decisions
AdministratorSystem managementConfiguration of queues, decision authorities, SLAs, and access profiles