All or nothing
A file is accepted whole or not at all, so a batch never half-sends. Fix the rows that are listed and upload it again.
Bulk payouts from a file
Upload a payout file. We pay every row once.
Send hundreds of payouts from one spreadsheet. amusemonk checks the whole file before anything moves, lets you review every row, sends each payout exactly once and follows it until it settles.
- Whole-file checks
- One payment per reference
- Live status to settlement
supplier-payouts.csv
Accepted
- Amara OkaforPAY-0411 $1,250.00 Paid
- Northwind SuppliesPAY-0412 $8,400.00 Paid
- Lucas MeyerPAY-0413 $12,000.00 Processing
- Sofia RossiPAY-0414 $3,725.50 Pending
2 of 6 paid
Total$48,750.00
How it works
From spreadsheet to settled in four steps
No integration to build. If you can export a spreadsheet, you can send a batch.
-
Upload the file
CSV or Excel, one row per payout: reference, account, bank code, amount, date and beneficiary.
-
Every row is checked
Columns, formats, limits, dates and duplicates. If one row fails, the whole file is held back and each problem is listed by row.
-
Review, then confirm
See every payout and the total before anything is sent. One confirmation sends the batch.
-
Track until settled
Each payout moves from processing to paid on its own. If the bank returns one, you see why.
Safeguards
Built so a payout can't go out twice
Exactly once per reference
Every row is keyed by your own reference. The same file uploaded twice, or the same payment under a new reference, is stopped before it's sent.
Rules you set
Limits per payout and per file, date windows and allowed accounts. Change them without touching the file format.
Status you can trust
Each payout is followed until it settles. If a response is lost, the payout is looked up, never sent again blind.
Try it
Watch a file go from upload to paid
Pick a sample file, or drop in your own CSV. The demo runs in your browser with made-up data: nothing is uploaded or sent.