> ## 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.

# July 2026

> Documentation updates and release notes published in July 2026, organized by customer impact and product area.

Updates are grouped by required customer action. Product filters show only the areas that affect your integration. See [News](/en/news/news) for impact definitions.

## No action

***

<Update label="July 7th, 2026" tags={["Matcher"]}>
  ### [Matcher v4.3.0 — AI-assisted ingestion, discovery connectors, and Console rebrand](/en/news/2026/july/matcher-v430)

  **What changed**

  Matcher adds AI-assisted document extraction, field-mapping proposals, and match-rule suggestions — each with a human-in-the-loop review step before anything is applied. A new discovery-connector platform onboards sources from aggregators (Pluggy, Belvo), file formats (CNAB240, CNAB400, OFX, camt.053 preview), and SFTP. API error responses are now a consistent problem shape (`type`, `title`, `status`, `detail`). The Console adopts the new ink-blue theme with refreshed navigation and breadcrumbs. Seven customer-facing reliability fixes are included.

  **Who is affected**

  Teams using Matcher for reconciliation — operators uploading and mapping statements, teams building match rules, and integrations that parse Matcher API error responses.

  **What you need to do**

  Review the new AI extraction, mapping, and rule-suggestion flows and assign an owner to the approval step. Explore the discovery connectors if you onboard sources via aggregators or files. Confirm that any code parsing Matcher error responses handles the new problem shape. No migration is required for existing integrations.
</Update>

<Update label="July 7th, 2026" tags={["Midaz"]}>
  ### [New reference: Receiving Midaz events — RabbitMQ vs Streaming Hub](/en/news/2026/july/receiving-midaz-events-guide)

  **What changed**

  A new reference guide, Receiving events from Midaz, documents the two supported ways to consume the Midaz event stream — binding your own queue directly to Midaz's RabbitMQ (AMQP 0-9-1) topic exchanges, or subscribing through Lerian's managed Streaming Hub (Webhook, Pull, SQS, RabbitMQ, or EventBridge) — with a side-by-side comparison to help you choose.

  **Who is affected**

  Teams integrating with Midaz that react to ledger events — reconciliation, notifications, downstream projections, and analytics — instead of polling the REST API, including both self-hosted deployments and external / SaaS integrators.

  **What you need to do**

  No migration is required. No endpoints, event schemas, or delivery behavior changed. Self-hosted teams should review the RabbitMQ direct section and self-hosted environment flags; external consumers should review the Streaming Hub section and pick a delivery transport.
</Update>

## Product index

***

| Product area | July updates                                                                                                                                                                                                                                                                                                                                        |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Matcher**  | v4.3.0 adds AI-assisted document extraction, mapping proposals, and match-rule suggestions (all with human-in-the-loop review), a new discovery-connector platform (Pluggy, Belvo, CNAB240/400, OFX, SFTP, camt.053 preview), standardized API error responses, an ink-blue Console rebrand with refreshed navigation, and seven reliability fixes. |
| **Midaz**    | A new reference guide, Receiving events from Midaz, explains the two supported ways to consume Midaz ledger events — direct RabbitMQ (AMQP) exchange binding for self-hosted deployments, or the managed Streaming Hub for external / SaaS integrators — and how to choose between them.                                                            |