Pay a US contractor and a Berlin studio in the same batch
Upload a file or call the API, review payee readiness and route options, apply your approval policy, and keep release and finance records together.
One record from invite to posted journal entry
You stop wiring four tools to send one payment. Payee onboarding, onboarding status, approval chains, and the finance handoff live on the same record. One batch closes one review trail.
CSV today, API next quarter
Overview
US, EU, and India in one batch
Overview
Payees onboard themselves
Overview
Finance signs off once per batch
Overview
Four pieces that close a batch from invite to posted
The release schedule, payee documentation, approval chain, and finance handoff sit on one record. One batch closes one review trail.
Scheduled runs and threshold releases
Set a release window, amount threshold, and required approvers. Ops sees which batches are ready for review and which exceptions still need an owner.
W-8, W-9, and 1099 on the payee record
Tax forms live on the payee, not in a shared Google Drive folder. When 1099 season arrives, the data is already current and where finance needs it.
Choose from enabled payout methods
Capture the payee preference, confirm corridor eligibility, and show the route estimate and current status on the payout record.
Prepare a finance-ready close package
Package payouts, fees, FX inputs, source references, and journal details for the accounting destination enabled during implementation.
Gruv AI helps review the batch before money moves
Use configured checks and source context to prepare exceptions for review. Ops keeps the approval decision; finance keeps the supporting record.
Rule engine for commission and schedule logic
Save commission, schedule, and approval rules for the program, then review which rule applies to each prepared run.
Pre-release gates with reason codes
Run the tax, screening, and policy checks enabled for the program before approval. Holds carry a reason code and a clear review owner.
Exception queue with the next step suggested
Returns and mismatches enter an exception view with a suggested next step, source record, and owner.
Ask Gruv AI
Ask why a batch is held or where a payee stands. The answer cites the record. Faster than pinging the integrations team.
From CSV import to closed books
Releasing money is one click. The work around it (payee onboarding review, tax-document status, approval routing, exception handling, and the finance handoff) is what makes the program scale.
Pull payment data from where it lives
- Drop a CSV this week; switch to REST API and webhooks when engineering is ready
- Save approved source-field mappings and review changes when an input format shifts
- Keep the source reference on each payment so ops can trace an item without switching systems
Get payees verified before payday
- Collect the bank, tax, and identity inputs required by the approved onboarding path
- Track invited, missing-information, under-review, ready, and blocked states
- Show the missing field or review reason so ops and the payee know the next step
Release the batch and post to your ERP
- Apply the configured amount thresholds, dual-control sign-off, and release windows to the batch
- Route failed items to the configured retry, fallback, or exception queue
- Prepare payouts, fees, FX inputs, and journal details for the enabled finance destination
Built for teams where paying others is the product
When one missed payout triggers churn, ad-hoc spreadsheets stop scaling. Affiliates, creators, publishers, and promo winners all pay out on the same rails underneath.
Affiliate Marketing
Import approved earnings from your source ledger, attach the recipient and tax status, then review the available method for each corridor before release.
Ad Networks
Turn approved campaign spend into payout-ready rows with source references attached. Publishers and finance can review the same amount and status record.
Creator Economy
Prepare creator withdrawals, rev-share splits, and brand-deal payments in one workflow. Show each creator the enabled method and current payout status.
Influencer Marketing
Turn approved deliverables into a reviewable payout run. The brand sees approval status, the creator sees the route estimate, and account managers see what blocks release.
Podcasts
Host and guest splits release every Tuesday with the records you need at year-end. Talent in the US, UK, and Australia get paid on time without a manual tracker.
Gaming & Promotions
Prepare tournament prizes, loyalty rewards, and rebates with recipient eligibility, dual-control approval, and a finance review trail.
A payout run, end to end
Five steps from defining the payout program to handing finance a reviewable close package.
Example rail configuration
DNS resolution
Name match · Treasury LLC
Daily limit · $5M
Sandbox round-trip
Production permissions
Go deeper on routing, methods, and finance close
Use these guides to turn a payout-batch plan into the route review and finance handoff your team needs.
Review fiat payout methods
Compare the method details, beneficiary inputs, and status trail to confirm before launch.
Plan provider routing
See how account policy, retry identity, provider status, and references fit together.
Prepare finance close
Connect payout results, fees, references, and exceptions to the reconciliation workflow.
Frequently Asked Questions
Which countries and payout methods do you support?+
How do payees onboard?+
How do you prevent duplicate payments?+
Can finance set approval rules?+
What does reconciliation look like?+
Ready to pay your first batch?
Bring your sender entities, recipient corridors, currencies, payout frequency, approval policy, and accounting requirements. We will turn them into a rollout checklist.
Your rollout plan records the open provider, compliance, data, and finance decisions before a production release.