Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

March 25, 2026 Documentation update Review recommended

​
Affects

Teams reconciling Pix transactions with Matcher. This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.

​
What changed

We published a complete use case guide for reconciling Pix transactions using Matcher: Pix Reconciliation with Matcher. This guide walks you through:
  • Transaction flows — Cash-in and cash-out diagrams showing how Pix transactions move from initiation through SPI settlement to Matcher reconciliation
  • Step-by-step configuration — Creating contexts, sources (LEDGER for Midaz, CUSTOM for BACEN SPI extracts), field maps, and match rules
  • Daily operations — Upload the BACEN extract, run DRY_RUN before COMMIT, review exceptions
  • Match rules — EXACT matching on endToEndId at priority 1, with a DATE_LAG fallback at priority 10 for D+1 settlements
  • Practical example — A worked scenario with four transactions: exact matches, D+1 date lag matches, and exception cases
  • Exception handling — What to do when transactions appear in one source but not the other, or when amounts or dates don’t align

​
Correction

The Matcher source type was corrected from "type": "MIDAZ" to "type": "LEDGER" in the Midaz integration guide.

​
Impact

This is a documentation update. Existing integrations do not need a migration from this release note alone.

​
What you need to do

1
Review the Pix reconciliation use case before configuring Matcher sources, field maps, and match rules for Pix flows.

​
Deadline

None.

​
Why

The guide documents an end-to-end Pix reconciliation workflow and corrects the documented Matcher source type for Midaz integration.