A CSV file is not payment proof. It is only the handoff between your affiliate ledger and the bank transfer process.
Rewardful Wise payouts work well when your team controls approvals, recipient data, and reconciliation. The payment run is manual by design, which gives finance a final review point before money leaves the business.
Use a fixed monthly or biweekly process. That prevents late reversals, duplicate payments, and missing affiliate records.
Rewardful Wise payouts: the documented setup
Rewardful tracks affiliate commissions and identifies payouts that are due. Wise moves the money after you upload the export and fund the batch.
This is not a direct, native money-moving connection between Rewardful and Wise. Rewardful’s documented Wise flow is a CSV export from Rewardful, followed by a batch upload in Wise Business. Its Wise mass-payout workflow describes that handoff.
Rewardful says its mass payout process can support programs with up to 5,000 affiliates in one export. Your Wise account can still apply its own file, recipient, currency, or funding checks.
Treat Rewardful and Wise as separate records
Rewardful is your commission ledger. Wise is your payment execution record. A payout becomes complete only when both systems agree.
Keep the Rewardful payout ID, affiliate ID, export date, Wise batch reference, payment amount, currency, and status in one internal record. This gives your finance team a clean trail when an affiliate asks about a missing commission.
Do not mark a payout as paid when you download the file. Do it after Wise confirms the transfer outcome.
Set payout rules before commissions become due
A payout process starts before the export. Your affiliate terms and internal policy should state when commissions become payable, what happens after refunds, and which payment details affiliates must provide.
Pick a clear schedule. Monthly is common because it gives your team time to review refunds, chargebacks, and disputed transactions before payment.
Set a cutoff, threshold, and approval owner
Define the close date for each commission period. For example, commissions earned in June may close after the refund window, then enter the July payment run.
Set a minimum payout threshold that matches your program economics. Small balances can remain in Rewardful until they reach the threshold. This reduces transfer work and prevents a long list of uneconomical payments.
Assign one person to approve the final payout total. A second person should submit the Wise batch when payment volume or risk warrants it.
Collect payout data through a controlled process
Ask affiliates for the details needed by the Wise payment route. Depending on the destination, that can include a legal payee name, email address, bank details, country, and preferred currency.
Keep those details out of Slack threads and email replies. Store them in the approved affiliate profile or secure finance system with restricted access.
Payout obligations, tax forms, invoices, and withholding rules depend on your company and the affiliate’s jurisdiction. Use a qualified accountant or legal professional for jurisdiction-specific requirements.
Run the manual CSV payout workflow
The manual workflow is short. The controls around it matter more than the button clicks.
Rewardful’s commission payout instructions direct merchants to download due payouts, upload the Wise file, and mark the commissions complete after payment confirmation.
- Close the payout period and approve the due commissions. Resolve refunds, disputes, duplicate accounts, and missing payout details before creating the file.
- Open Rewardful’s Payouts area. Filter for due payouts, select the approved records, and download the CSV formatted for Wise.
- Sign in to Wise Business and open
Send money, thenBatch payments. Upload the Rewardful CSV rather than rebuilding the payment list by hand. - Review every flagged row, recipient name, destination, currency, fee, and batch total. Choose the funding source, then submit the batch only after the totals match your approved payment register.
- Save the Wise batch reference and confirmation. Return to Rewardful and mark only the confirmed payouts as paid.
If Wise rejects a row, remove it from the payment run and log the reason. Correct the source record before the next export. Do not change a bank field in a downloaded CSV without updating the controlled affiliate record.
An uploaded CSV is not proof of payment. Treat a batch as paid only after Wise confirms its outcome and the total matches your payment register.
Check recipient, currency, and route restrictions
Wise can pay recipients without requiring them to hold a Wise account. The recipient still needs payment details that work for the destination route.
Country and currency rules can change. Some routes have different rules for personal and business recipients. Others need local bank details or limit the available payment currencies.
Check the route before payout day
Review Wise’s supported send currencies when you add a new affiliate country or currency. Do not assume a payment route available for one affiliate will work for another.
Test new countries with a small approved payment run. This catches incorrect account formats and recipient restrictions before a large affiliate batch depends on them.
If an affiliate changes banks, ask them to update their details before the cutoff. A last-minute change is an exception, not a reason to skip review.
Review the live quote, not last month’s cost
Currency conversion fees and transfer timing depend on the route, funding method, and payment amount. Wise shows the fee and expected delivery details before you submit a transfer. Review Wise’s transfer quote flow at the point of payment.
Record the amount in your base currency and the recipient currency. That distinction matters when affiliates earn commissions in USD but receive a local-currency payment.
Use a pre-payout checklist for every batch
A short Rewardful Wise payouts checklist catches most preventable errors before funds leave the account.
- The commission period is closed and an authorized owner approved the total.
- Refunds, chargebacks, and disputed referrals are removed or held for review.
- Each row has a Rewardful payout ID and a current affiliate identifier.
- Recipient names, bank details, email addresses, countries, and currencies match the approved profile.
- The exported total matches the approved payment register before upload.
- Wise flags, rejected rows, fees, and funding requirements have been reviewed.
- The team has named an owner for failed, pending, returned, or missing payments.
Check the available Wise balance before the run. Funding failures create extra work and can leave part of the batch unresolved.
Also check the recipient experience. Wise’s guidance on receiving fees and limits explains that receiving conditions can vary by currency and transfer type.
Reconcile payment evidence before closing the month
A payout run is not finished when Wise shows a submitted batch. Finance still needs to match the result against Rewardful and the business bank record.
Store the original Rewardful export, the final uploaded file, Wise confirmation, transaction reference, payout period, and reviewer approval together. Restrict editing after approval.
Match every confirmed payment to a Rewardful record
Use the Rewardful payout ID as the matching key. Do not rely on affiliate names alone. Names can be duplicated, shortened, or changed after an affiliate updates their profile.
A clean reconciliation record shows:
- The amount approved in Rewardful.
- The amount sent through Wise.
- The transfer currency and date.
- The Wise batch or transaction reference.
- The final payment status.
Count accepted payouts, not exported rows. A 200-row CSV is not a successful payment run if five transfers failed and three records need correction.
Keep pending and failed payments separate
A pending transfer and a failed transfer need different actions. A failed message does not prove the money has returned to your account.
Check whether Wise shows the payment as pending, completed, cancelled, or refunded. Keep support messages and transfer receipts with the batch record. Do not issue a replacement payment until you know the status of the first one.
Keep the last trusted payment register available. If a file upload fails or a payout record changes unexpectedly, your team still has a known-good record to work from.
Keep automation outside the money release
Automation can help with reminders, payout calendars, approval requests, file storage, and reconciliation reports. It should not release affiliate payments without a named approver.
Start with a small approved batch if you change the workflow. Compare the Rewardful export, uploaded file, Wise result, and final ledger status. Track rejected rows, correction time, and the time each batch takes to reconcile.
Automate preparation, not approval
A recurring calendar reminder can start the run. A finance form can collect signoff. A secure folder can retain exports and confirmations.
The final Wise review should remain a controlled human action. Payment files contain sensitive data and direct money movement. A broken automation can create duplicate or misdirected payouts at scale.
Compare Managed Payouts as a separate option
Rewardful also offers Managed Payouts, where the merchant funds Rewardful and Rewardful distributes affiliate commissions. Review the current Managed Payouts merchant FAQ before changing your payment process.
Managed Payouts and Wise batch uploads solve different operational problems. Do not treat Managed Payouts as a native Wise batch connection.
If your team needs a payout approval matrix, exception process, or reconciliation workflow across several markets, Book A Call to map the operating process.
Build a payment run your affiliates can trust
Reliable affiliate payments come from controlled records, not a fast export. Rewardful calculates what is due. Wise sends the approved batch. Your team owns the review between those two steps.
Use the same cutoff, checklist, approval record, and reconciliation process every cycle. Rewardful Wise payouts become predictable when every payment has an owner, a confirmation, and a matching ledger record.
