Skip to main content
A bureau run is the complete record of a KYC verification — which sources were checked, what each one returned, and the final compliance decision. Runs are immutable: once a run completes, neither you nor kycert can alter its content. This immutability is a regulatory requirement under BCB Circular 3.978/2020, and it means every run is a reliable piece of your audit trail that you can produce for an inspection without caveats.

​
Viewing runs

Navigate to Bureau → Runs in the dashboard sidebar to see your run history. The table shows:
ColumnDescription
CustomerFull name and masked document number (CPF or CNPJ)
TemplateName and version of the KYC template used
StatusCurrent execution status (see status table below)
Risk bandOverall risk decision: high, medium, or low
TimestampDate and time the run was initiated
You can filter by status, risk band, date range, and subject type (PF/PJ). Use the search bar to find a specific customer by name or document.

​
Run detail console

Click any row to open the run detail console. This is your primary workspace for understanding what the engine found and deciding how to act. Risk Profile The top section displays the overall risk band — high, medium, or low — alongside key risk findings that elevated it. If the run resulted in a manual review referral, the highest-priority findings are highlighted in amber so your analyst can start there. Findings A curated list of every source that returned INVALID or produced a meaningful signal. Each finding shows the source name, a plain-language description of the issue (e.g., “Active arrest warrant found in CNJ BNMP”), and the associated risk weight. This section gives your analyst a fast summary without having to expand every source individually. Source results An expandable list of every source that ran, in the order it executed. Each entry shows:
  • Source name and provider
  • Status (VALID / INVALID / NO_DATA / ERROR)
  • Check-level details — for example, situacao_cadastral: VALID, registro_obito: VALID, mandados_ativos: INVALID
  • Raw data summary where available (e.g., the name returned by Receita Federal for similarity comparison)
Partner graph (PJ only) For company runs, the partner graph visualises the company’s QSA (Quadro de Sócios e Administradores) — its ownership structure and the individual partners’ compliance status. Each node in the graph is colour-coded by risk level. Click a node to see the individual KYC result for that partner if QSA chaining was active in your template. Processes If sources such as cnj_mandados_prisao, cnj_seeu_processos, or trf_processos returned data, the Processes tab lists each legal process found with the court, case number, and status.

​
Triggering a manual run

You can start a bureau run for any CPF or CNPJ at any time without waiting for a customer to complete their onboarding form. Go to Bureau → Lookup. Enter the CPF or CNPJ, select the template you want to apply, and click Run. For most templates, the result appears within seconds. If your template includes sources with longer response times (such as antecedentes_pf, which can take up to 30 seconds), kycert processes the run asynchronously and sends you a notification when it completes.

​
Run statuses

StatusMeaning
pendingThe run is queued and waiting to start
runningSources are actively being queried
completedAll sources returned a result — review the risk band and findings
failedA system-level execution error prevented the run from completing — contact support if this status persists
A run status of completed does not mean the customer passed. It means the engine finished executing. A completed run may have an overall decision of rejected (if a critical-phase source triggered a block) or pending review (if an important-phase source returned INVALID). Check the risk band and findings section to understand the outcome.

​
PDF compliance report

From the run detail page, click Download Report to export a compliance PDF. Two formats are available: Summary (Resumido) A 3-page executive summary containing the overall compliance decision, risk band, key findings, and a signed timestamp. This format is appropriate for quick internal sign-offs or sharing with a relationship manager. Complete (Completo) A full compliance dossier of 20 or more pages, including all source results, raw data excerpts, the partner graph (for PJ runs), any legal processes found, and the template snapshot that governed the run. This is the format you should retain for regulatory inspections and produce when auditors request your BCB 3.978 documentation.
Completed runs are permanent records. You cannot delete or modify a run under any circumstances — this is a hard requirement of BCB Circular 3.978/2020. If a run contains incorrect input data (for example, a typo in the CPF), create a new run with the corrected document. Both runs remain in your audit log.
  • Bureau Overview — how the engine processes a run end to end
  • Templates — configure the sources and rules that drive each run
  • Data Sources — details on every source available in kycert