LedgerMatch Preferences
How Payment Reconciler calls LedgerMatch—REST vs gRPC, timeout, retries.
What are LedgerMatch preferences
LedgerMatch preferences control how the API communicates with the LedgerMatch service. They are part of TenantSetting.ledgerMatchPreferences. Use them to tune performance, reliability, and matching strategy.
matchStrategy
| Value | Use case |
|---|---|
| rest | Single REST call per transaction (default). Used for auto-match and single-transaction jobs. |
| grpc | Bulk gRPC for batch/scheduled jobs with 2+ transactions. When set, autoMatchEnabled is automatically set to false (auto-match uses REST only). |
Choose grpc when you have high volume and run batch matching. See LedgerMatch Integration for details.
Timeout and retries
- timeoutMs — 1000–60000. Request timeout per LedgerMatch call.
- retryAttempts — 1–10. Retries on transient failure.
- retryDelaysMs — Comma-separated delays in ms (e.g.
1000,2000,4000) for exponential backoff.
Attributes
| Attribute | Purpose |
|---|---|
| matchStrategy | rest or grpc. rest = per-tx; grpc = bulk |
| autoAcceptForBulkMatch | When grpc: auto-accept top-ranked |
| retryAttempts | 1–10. Default from env |
| retryDelaysMs | Comma-separated (e.g. 1000,2000,4000) |
| timeoutMs | 1000–60000 ms |
Related
- LedgerMatch Integration — REST vs gRPC, scoring
- Tenant Settings — Parent structure