Skip to main content
The Analysis Queue is your compliance team’s daily work queue — it surfaces every customer who needs a human decision after the automated bureau verification process has completed. Instead of manually searching through the customer registry, you come here first each day to see exactly who requires attention, in what order, and how urgent each case is. The queue is shared across your compliance team, so every analyst sees the same prioritized view.

​
What Appears in the Queue

A customer enters the Analysis Queue when one of the following conditions is true:
  • The bureau run completed and at least one important-phase source returned an INVALID result configured with the pending rule — meaning the system flagged the case for human judgment rather than auto-rejecting it.
  • A PEP (Politically Exposed Person) indicator was found during the bureau run and your tenant’s PEP policy is set to manual_review.
  • An analyst manually moved the customer back to em_analise status from another state.
Customers whose bureau run triggered a critical-phase INVALID result with the block rule are automatically rejected by the system and do not appear in this queue.

​
Queue Columns

Each row in the Analysis Queue shows:
ColumnDescription
CustomerFull name and masked document (CPF or CNPJ)
TypePF (individual) or PJ (company) badge
Time in QueueHow long this customer has been waiting since their bureau run completed or since they were manually flagged
Risk BandThe consolidated risk level from the bureau run: high, medium, or low
Assigned AnalystThe display name of the analyst assigned to this case, if one has been assigned; blank if unassigned

​
Prioritization

The queue groups cases into three urgency tiers so you always work on what matters most first:
  • Overdue — cases where em_analise status has exceeded 48 hours, or pendencia status has exceeded 5 days. These rows are visually highlighted. Resolving overdue cases is critical for meeting BCB Circular 3.978 compliance timelines.
  • In Analysis — cases actively within the normal processing window. Work through these in order, oldest first.
  • Pending — customers who were asked to supply additional documents. These stay visible so you can follow up if the customer has not responded.
Within each tier, rows are sorted oldest-first so cases that have been waiting the longest surface at the top.

​
Reviewing a Case

1

Open the customer profile

Click any row in the Analysis Queue to open that customer’s full compliance profile. You can also right-click and open it in a new tab if you want to keep the queue visible alongside the profile.
2

Review the bureau findings

Scroll to the Bureau Run History section on the customer profile. Expand the most recent run to see the result for each individual data source — Receita Federal, CNJ mandados de prisão, PEP/COAF, international sanctions lists, and any others activated in your bureau template. Each source shows its status (VALID, INVALID, NO_DATA, or ERROR) and the raw data returned, so you can evaluate the specific finding that triggered the review.
3

Check the Risk Console

Open the Risk Console panel on the customer profile. This shows the AI-generated risk narrative — a structured summary of the findings, the risk band rationale, and any specific indicators that were flagged. Use this narrative to contextualize the bureau data before making your decision.
4

Make your compliance decision

Use the action buttons at the top of the customer profile to record your decision: Approve, Reject, or Request Additional Documents (Pendência). Each option opens a confirmation dialog where you must enter your decision reason before confirming.
5

Enter a structured reason

Type or select your decision reason in the reason field. This field is mandatory — you cannot confirm any action without it. The reason, your user identity, and the exact timestamp are written to the immutable audit log immediately upon confirmation.

​
Decisions and Their Effects

DecisionCustomer Status AfterNext Steps
ApproveaprovadoThe customer is immediately cleared for FX operations; your team can register operations linked to this customer
RejectrecusadoThe customer is blocked from all FX operations; an email notification is sent to the customer if outbound notifications are enabled in your tenant settings
PendênciapendenciaThe customer is asked to supply the specified documents; the case returns to the queue when they respond or after the 5-day threshold
Never disclose to a customer that their rejection is related to a COAF finding, a sanctions list hit, or any other specific AML indicator. Brazilian AML law (Lei 9.613/98) prohibits “tipping off” — informing a subject that they are under AML scrutiny. Your rejection notification to the customer must state only that their registration could not be completed, without referencing the underlying reason. Consult your compliance officer if you are unsure how to word a rejection communication.