Approval Workflows

Route every payment using business rules. Auto-clear the routine, escalate the exceptions, and give approvers the context to decide fast.

POLICY-DRIVEN Payment ROUTING

Your policies, applied to every payment

Hudson checks every payment against your rules before it moves. Routine payments clear on their own. Anything that needs a second look goes to the right approver with full context. Every decision lands in the audit trail.

THE ESCALATION LADDER

The right approval path, for every payment

So the right approval fires on the right transaction, every time.

ROUTINE
HOA dues debit
$385
1
Request • monthly batch run
2
Rule check • amount under $5k, recurring, known payee
3
Auto-cleared • 200 ms
4
Money moves • ACH
No human involvement.
ONE APPROVER
Construction draw
$84,200
1
Request • GC submits Draw #4
2
Rule check • amount over $25k, lien waivers uploaded
3
Treasury Ops approves • 3 min
4
Money moves • Wire
One approver, with context presented.
MULTI-PARTY APPROVAL
M&A holdback release
$4,560,000
1
Request • escrow holdback release
2
Rule check • amount > $1M, dual signatures via release docs
3
Buyer + Seller sign • 30 min
4
Money moves • Wire
Docs uploaded. Both signatures present.

Decisions, not noise

A typical email inbox buries the few decisions that matter under routine noise. Hudson filters decisions to only what your policy flags, each item presented with the full context to disposition in one click.

Common exceptions

What usually triggers a second look.

AMOUNT OFF PATTERN
$84,200 to Pinewood (usually $12,400)

This contract has averaged $12,400 per draw across nine prior payments. Today's request is nearly 7× that.

Auto-hold payment and escalate to the construction officer.
NEW ACCOUNT, KNOWN PAYEE
Riverside Vendor, new account number

You've paid Riverside Vendor twelve times, always to the same account. Today's payment routes to one Hudson hasn't seen before.

Auto-hold payment and escalate to the treasury ops.
Off-schedule request
Creditor payment, 15th of the month

This creditor drafts on the 1st of every month over the last 24 months. A mid-month draft request is unusual.

Auto-hold payment and surface it to the relationship manager.
Velocity flag
Same payee, three payments today

Acme Vendor was paid at 9:02am. Two more requests for this payee landed at 10:14am and 11:42am, both for the same amount.

Approve 1st payment and hold+route the others to treasury ops.
THE PAYOFF

Fewer touches, sharper judgment

When every payment hits the same approval chain, reviewers rubber-stamp everything, including the ones that should have gotten a second look. At scale, Hudson clears over 95% automatically and only escalates exceptions. The payments that require judgment, actually get it.

Why Hudson?

One approval engine that enforces your policies and keeps a tight audit trail of decisions.

Escalate only what needs judgment, and auto-clear the rest
Enforce thresholds and two-person controls by rule, not by memory
Catch exceptions by thresholds, patterns, and document checks
Every approval decision captured in an audit trail

Frequently asked questions

Can we configure the approval chain per transaction type?

Yes. Different transaction types get different chains, with the approvers, thresholds, and sequences.

What happens if an approver is out of office?

Escalation timeouts kick in. If an approval sits too long, Hudson escalates to the next in sequence automatically.

How does this fit our delegation-of-authority matrix?

Thresholds are configurable, so any transaction over an amount you set requires an additional or more senior approver.

Can approvals run in parallel, or only in sequence?

Both. Steps can run sequentially, where one gates the next, or in parallel, where several approvers act at once.

How does Hudson decide what needs approval versus what clears on its own?

We configure the rules during onboarding. Hudson runs every payment against the thresholds and patterns, clears what matches policy, and routes only the exceptions to the named approver.