Tenant Settings
Configure tenant behavior per environment—matching, locale, jobs, LedgerMatch, cache.
What are tenant settings
Tenant settings control how the system behaves for a given tenant and environment. They are stored per tenant and environment—e.g. production can have a higher confidence threshold than staging. Update via PATCH /tenants/:id/settings with X-Environment set to the target environment.
Setting categories
| Category | Purpose |
|---|---|
| Matching | matchingConfidenceThreshold (0–1), matchingMode, autoMatchEnabled |
| Locale | locale, timezone, currencyCode, dateFormatPref, numberFormat — used by field mappings and parsing |
| Job scheduling | matchingSchedule, stripeSyncSchedule, retention (audit logs, completed jobs, expired matches) |
| LedgerMatch | matchStrategy (rest vs grpc), timeout, retries, circuit breaker |
| Cache | matchCacheEnabled, expectedCacheEnabled — Redis-backed caching for matches and expected transactions |
Key settings
- matchingConfidenceThreshold — Minimum confidence (0–1) to auto-accept a match. Default 0.8.
- autoMatchEnabled — When true, new incoming transactions trigger automatic matching. Uses REST only; gRPC bulk match disables auto-match.
- matchStrategy —
rest(default) orgrpc. gRPC is for bulk matching; see LedgerMatch Integration. - localePreferences — Affects number parsing and date formatting in field mappings.
API Reference
- Update tenant settings — Full operation with parameters and samples
Configuration Reference
For all attributes and nested structures: