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

# Matcher: source documentation field correction

> The public Matcher documentation now shows source payloads without feeScheduleId, aligning source examples with the supported source fields.

<Badge stroke icon="calendar-days" iconType="regular">May 14, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="green" size="lg" stroke icon="circle-check" iconType="regular">No migration required</Badge>

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

<Note>
  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.
</Note>

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

```json theme={null}
{
  "name": "Bank statement",
  "type": "TRANSACTION",
  "side": "LEFT",
  "feeScheduleId": "0194f6..."
}
```

**After**

```json theme={null}
{
  "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

***

<Steps>
  <Step>
    Do not include `feeScheduleId` when creating, updating, or reading Matcher sources.
  </Step>

  <Step>
    Use the documented source fields: `name`, `type`, `side`, and `config`.
  </Step>

  <Step>
    Configure fee behavior with Matcher fee rules instead of source fields.
  </Step>

  <Step>
    Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.
  </Step>
</Steps>

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

***

* [Source configuration guide](/en/matcher/configuration/matcher-contexts-and-sources)
* [Create source](/en/reference/matcher/create-source)
* [Fee rules guide](/en/matcher/configuration/matcher-fee-rules)