The operations layer for paying everyone you owe.
Track what you owe, approve it, move it, and reconcile it — with financial controls and a double-entry ledger underneath.
Rout is the software and control layer. A regulated payment provider executes the money movement — Rout never custodies funds.
Track obligations, approvals, payouts, and reconciliation in one source of operational truth.
Retries resolve uncertain provider outcomes before anything can be issued again.
Privileged actions carry an actor, reason, and timestamp for a defensible audit trail.
Payout operations, end to end.
Everything between “we owe this” and “it’s paid and reconciled” belongs in one controlled system.
Recipients
Onboard individuals and businesses, track payout readiness and tax status, while sensitive details remain provider-hosted.
Obligations
Record exactly what the organization owes and to whom, separate from the payout used to settle it.
Approvals
Maker-checker and threshold approvals ensure required sign-off exists before money movement.
Batches & payouts
Group payments into controlled payout runs while preserving exact per-payment state.
Double-entry ledger
Balances derive from immutable posted entries rather than mutable payout records.
Reconciliation & audit
Match Rout records against provider and bank activity, surface exceptions, and preserve attribution.
A controlled process from obligation to reconciliation.
Rout owns the operations, controls, and ledger. A regulated provider owns the regulated movement of money — a clean boundary, by design.
Obligation
What the organization owes is recorded first.
Approval
Required maker-checker or threshold approvals are collected.
Payout
A stable internal payout record exists before an external provider call.
Provider executes
A regulated provider performs the actual movement of money.
Reconciled
Provider and bank activity is matched back to Rout and posted to the ledger.
Correctness is a product feature.
Rout is designed so money movement is controlled, attributable, and reconcilable from the start.
Retries never double-pay
Unknown provider outcomes resolve before anything is re-issued.
Posted entries are immutable
Corrections use reversals rather than rewriting financial history.
Records are organization-scoped
Every record belongs to one organization; cross-tenant access is treated as a critical incident.
Privileged actions are attributable
Each carries an actor or named system process, with reason and timestamp.
Sensitive data stays provider-hosted
Rout stores status and masked references — never bank numbers or full TINs.
Money is represented exactly
Integer minor units and a real accounting ledger — never floating-point.
Bring your payouts under one system of record.
Rout is onboarding early organizations. Tell us who you pay and how your payout operation works.