April 28th, 2026 Updated Matcher documentation has been fully audited and aligned with the currentDocumentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
main branch. This release includes 27 guide pages, 119 API reference pages, 19 console pages, and a verified OpenAPI 3.1 spec.
What changed
Guides
Overview
- What is Matcher — Product overview, architecture, and where Matcher fits in the Lerian platform
- Matcher concepts — Core concepts: contexts, sources, rules, field mapping, matching runs, exceptions, and disputes
- Matcher architecture — System architecture, domain modules, and data flow
Getting started
- Prerequisites — Requirements and dependencies
- Installing Matcher — Setup and deployment
- Getting started with Matcher — End-to-end walkthrough from context creation to first reconciliation
Configuration
- Contexts and sources — Defining reconciliation scope and connecting systems
- Match rules — Rule types (exact, tolerance, date lag), priority ordering, and reordering
- Field mapping — Mapping source fields to Matcher’s canonical model
- Fee rules — Fee validation and tolerance configuration
- Exception routing — Routing unmatched transactions for review
- Multi-tenant mode — Tenant isolation and configuration
- Runtime configuration (Systemplane) — Runtime parameters and system-level settings
Daily reconciliation
- Uploading files — Importing transaction data via API
- Reviewing matches — Inspecting match results and groups
- Resolving exceptions — Exception workflows and resolution
- Generating reports — Dashboard, matched/unmatched/variance reports, and exports
Integrations
- Midaz integration — Using Matcher with Midaz ledger data
- External sources — Connecting bank statements and third-party systems
- Discovery — Auto-discovery of external data connections
- Webhooks and callbacks — Event-driven notifications
Reference
- Confidence scoring — How Matcher calculates match confidence
- Multi-currency — Cross-currency reconciliation
- Split and aggregate — 1:N and N:M matching patterns
- Security — Authentication, authorization, and data protection
Use cases
- Pix reconciliation — Step-by-step guide for reconciling Pix transactions
Lerian Console
- Using Matcher in Lerian Console — Overview of the console integration
- 19 console pages covering the full Matcher module:
- Contexts — Managing contexts, sources, rules, and schedules
- Reconciliation — Uploading data, executing runs, reviewing matches
- Exceptions & disputes — Managing exceptions, exception details, disputes
- Governance — Actor mappings, audit logs, archives
- Operations — Dashboard, fee schedules, manual matching, operational history
API reference
- Developer quick start — API walkthrough from context setup to reconciliation
- Error list — Complete error code reference
- 119 endpoint reference pages covering the full API surface:
- Configuration — Contexts, sources, rules, field maps, schedules, fee rules, fee schedules
- Ingestion — Import jobs, transaction search
- Matching — Runs, match groups
- Exceptions — Exception management, comments, history
- Disputes — Dispute lifecycle
- Reporting — Dashboard metrics (match rate, volume, SLA, cash impact, source breakdown), matched/unmatched/variance reports with export
- Discovery — Connections, schema introspection, extraction bridge
- Governance — Audit logs, actor mappings, archives
- Export — Export jobs with download
OpenAPI specification
- Matcher OpenAPI 3.1 spec — Machine-readable specification with all 117 endpoints, schemas, and examples — verified against source code
Key fixes in this release
- API paths corrected — Route prefixes aligned with actual Fiber route registration
- Deprecated fields removed —
rateIdremoved from all schemas (rejected by the API since deprecation) - Missing schemas added — Inline
sourcesandrulesarrays added toCreateReconciliationContextInput - YAML spec hardened — Colon-containing enum values (
1:1,1:N,N:M) properly quoted to prevent parser misinterpretation - Guide examples fixed — Incorrect endpoint URLs in curl examples corrected across all languages

