The Matcher UI is not part of Lerian Console. It ships as its own web application, deployed alongside the Matcher API, and does not require a Console installation. If you operate other Lerian products through the Console, Matcher is the exception: it brings its own work surface.
Accessing the Matcher UI
Your platform team deploys the Matcher UI alongside the Matcher API and shares the URL for your environment. Sign in with the credentials your identity provider issues; every action in the UI is authorized against the Matcher API with your identity and tenant — the UI has no separate permission model. Once signed in, the active context shown in the sidebar controls which reconciliation context you’re working with. The active context applies across Matcher’s pages.
Main work surfaces
Dashboard
Reconciliation health at a glance — match rate, cash exposure, SLA compliance, and setup progress for the active context.
Reconciliation setup
Create contexts and manage their sources, match rules, and schedules from each context’s detail page.
Runs & imports
Import transaction files and start reconciliation runs, then track their progress.
Matches
Review confirmed match groups and confidence scores inside each run’s detail page, or pair remaining transactions in the Unmatched workbench.
Exceptions & disputes
Work the queue of transactions that didn’t match automatically — resolve, dispatch, or escalate them into formal disputes.
Reporting
Operational history, immutable audit logs, and downloadable archives for compliance.
Beyond the UI
Everything the Matcher UI does runs through the Matcher API, so you can mix surfaces freely:
- API — automate any workflow programmatically. Start with the developer quick start.
- MCP server — let an AI assistant operate Matcher through the Model Context Protocol.