Skip to main content
The Overview page is the first thing an operator sees after signing in. It is a single screen that answers three questions: how big is the current workload, where is reconciliation breaking down, and which open items deserve attention right now.
The dashboard is one consumer of the ReconLayer API, not the platform boundary. Every metric on this page is also available directly from GET /v1/dashboard/overview, so you can build your own internal dashboards, Slack alerts, or scheduled reports against the same data.

​
Data source

The page is backed by a single call to Get dashboard overview: 
GET /v1/dashboard/overview
The response is a DashboardOverviewResponse with seven top-level sections, and each widget on the page maps directly to one of them:
WidgetResponse fieldWhat it shows
Operational summarymetricsEight summary counters across cases and data quality
Case Workload & Resolution TrendworkloadTimelineDaily counts of cases created, imports created, open, resolved, in review, and exceptions
Case Verdict DistributionverdictDistributionCount of recent cases grouped by verdict
Exception Root CausesexceptionRootCausesCount of open exceptions grouped by exceptionType
High-Priority ExceptionshighPriorityExceptionsThe top unresolved cases ranked by unexplained delta
Recent Import FailuresrecentImportFailuresImport batches from the last 24 hours that produced failed rows
Coverage WarningscoverageWarningsCases missing one or more required evidence sources
If the request fails, the page falls back to whatever was last loaded; there is no separate “offline” state beyond the empty-state messaging on each widget.
A Demo data toggle in the dashboard shell lets you preview the layout with sample data before your organization has live cases or imports. Every screen described in this page behaves identically once live data is enabled — the toggle only changes where the numbers come from.

​
Operational summary

The top widget is a row of metric cards pulled from metrics:
MetricFieldMeaning
Total casestotalCasesAll ReconciliationCase records for the organization
Open casesopenCasesCases with status = open
Reconciled casesreconciledCasesCases with verdict = matched
Needs reviewneedsReviewCasesCases with verdict = needs_review
Unreconciled casesunreconciledCasesCases with verdict = unreconciled
ExceptionsexceptionCasesCases with verdict = matched_with_exception
Invalid evidenceinvalidEvidenceCountEvidence records that failed signature or validation checks
Failed file rowsfailedFileRowsRows from import batches that failed validation
This is the fastest way to gauge whether the queue is growing or shrinking and whether data quality issues are accumulating.

​
Case Workload & Resolution Trend

A time series chart built from workloadTimeline. Each entry in the array is one day and includes:
  • date
  • casesCreated and importsCreated — new volume entering the system
  • open, resolved, review, and exceptions — how that day’s cases broke down by state
Use this chart to see whether the team is keeping pace with incoming volume or whether a backlog of open and review cases is building up.

​
Case Verdict Distribution

A breakdown of recent cases by verdict, taken from verdictDistribution ({ verdict, count } pairs). The verdicts that can appear are:
VerdictLabel
matchedReconciled
matched_with_exceptionMatched with exception
needs_reviewNeeds review
unreconciledUnreconciled
sla_riskSLA risk
delayedDelayed
This widget gives a proportional view of outcomes — for example, whether most cases resolve cleanly (matched) or whether a large share are landing in needs_review or unreconciled.

​
Exception Root Causes

exceptionRootCauses returns { exceptionType, count } pairs for cases currently flagged with an exception. This widget ranks the reasons cases are not reconciling cleanly — for example, missing evidence, amount mismatches, or timing issues — so the team can prioritize fixing the underlying source rather than triaging cases one at a time.

​
High-Priority Exceptions

highPriorityExceptions is a ranked list of the cases most worth looking at right now. Each entry includes:
  • caseId
  • externalReference (nullable)
  • exceptionType (nullable)
  • unexplainedDelta (nullable) — the dollar (or token) amount that does not reconcile
  • updatedAt
The list is ordered by the size of the unexplained delta, so the cases with the largest financial impact surface first. From here an operator can jump straight into Cases to investigate a specific case.

​
Recent Import Failures

recentImportFailures lists import batches from roughly the last 24 hours that produced failed rows. Each entry includes:
  • batchId
  • originalFileName
  • failedRows
  • createdAt
This widget is the early-warning signal for a malformed file or a broken import profile — if a new batch suddenly produces a large failedRows count, it shows up here immediately rather than only in the Imports failed-rows tab.

​
Coverage Warnings

coverageWarnings lists cases that are missing one or more pieces of required evidence. Each entry includes:
  • caseId
  • externalReference (nullable)
  • missingCoverage — an array of evidence sources that have not been received (for example provider, chain, bank, or file)
A case can be open and not yet flagged as an exception while still appearing here — this widget surfaces structural gaps in evidence coverage before they turn into SLA breaches or unresolved cases.

​
Page layout and customization

The Overview grid is a draggable, resizable widget layout. Operators can:
  • Drag widgets to reorder them
  • Resize widgets to prioritize the ones most relevant to their role
  • Use Edit cards to enter layout-editing mode
  • Use Reset layout to return to the default arrangement
These layout preferences are local to the browser session and do not change the underlying data or API contract — they only change how the same DashboardOverviewResponse is presented.

​
From here

Open case queue

Jump into the full reconciliation case queue, filter by verdict, and investigate exceptions.

Import center

Review the batch behind a recent import failure or upload a corrected file.

Configuration

Adjust import profiles and canonical field mappings if failures trace back to a mapping issue.

Get dashboard overview

Call the same endpoint directly to build your own reporting on top of these metrics.