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.

May 14, 2026 Documentation update No migration required

​
Affects

Customers and teams reading the public Matcher documentation to configure reconciliation sources. This update applies to the public documentation portal. It does not change the runtime API behavior.
The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.

​
What changed

​
Source payload fields

The Matcher source documentation now reflects the supported source fields. The previous documentation showed feeScheduleId as if it were part of the source payload. That was incorrect. Matcher sources do not use feeScheduleId directly. A source describes the reconciliation input itself, such as its name, type, side, and optional configuration metadata. Before 
{
  "name": "Bank statement",
  "type": "TRANSACTION",
  "side": "LEFT",
  "feeScheduleId": "0194f6..."
}
After 
{
  "name": "Bank statement",
  "type": "TRANSACTION",
  "side": "LEFT",
  "config": {
    "provider": "bank"
  }
}

​
Fee behavior

Fee schedule behavior should be configured through Matcher fee rules, not through source payload fields.

​
Impact

This is a documentation correction. It prevents readers from using feeScheduleId as a Matcher source field. No migration is required if your current Matcher integration is already working. Use the updated documentation when creating, updating, or reviewing source configuration.

​
What you need to do

1
Do not include feeScheduleId when creating, updating, or reading Matcher sources.
2
Use the documented source fields: name, type, side, and config.
3
Configure fee behavior with Matcher fee rules instead of source fields.
4
Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.

​
Deadline

None.

​
Why

This correction keeps the public documentation aligned with the Matcher source API and avoids guiding readers toward a field that is not part of the source payload.

​
Resources