Finance Automation

Routing matrix and health

Search/filter rules and jobs by enabled state, trigger/domain, action, destination, health, last result, owner, date, and provider. Six health signals summarize rule/job state without replacing row detail. The routing matrix shows priority/order, typed conditions, action, destination, enabled/version state, and latest execution.

Rule actions

Create/edit requires name, typed trigger/conditions, action, destination, priority/order, enabled state, current version, and optional policy limits. Test/dry-run reports matched scope and proposed action without performing the authoritative action. Run executes through the canonical job path. Enable/disable and replay are accountable commands.

Job detail and provider safety

Job detail retains lease owner/expiry/token class, attempts, next retry, result, redacted error, provider receipt, quarantine/dead-letter reason, idempotency, related finance record, and audit history. Telegram/Discord actions require a currently linked identity and the same capability as the equivalent dashboard command.

Never expose bot tokens or raw destination secrets. Provider delivery occurs after the authoritative finance transaction; failure cannot roll it back or create a second transition.

Recovery

Inspect lease and idempotency before replay. Fix rule/mapping or reauthorize destination, test safely, then replay the canonical job only when duplicate action is excluded. Escalate stale leases that cannot be reclaimed, repeated terminal failure, or a provider message inconsistent with the authoritative record.