An affiliate payout batch can look correct and still send money to the wrong account. The risk sits in the handoff between commission approval, payout data, and payment release.
Rewardful affiliate payments work with Wise when you treat that handoff as a finance process, not a monthly CSV task. Rewardful prepares commission and recipient data. Wise Business sends the transfers. Your team owns review, approval, and the records after payment.
Set the process once. Then run the same controls every payout period.
Know Where Rewardful Stops and Wise Starts
Rewardful and Wise work through a file-based process. Rewardful does not directly send money from your Wise account. It creates a Wise-formatted payout CSV, which your team uploads to Wise Business Batch Payments.
This distinction matters. A downloaded CSV is not a completed payout. It is a payment instruction that still needs review, approval, funding, and tracking.
Rewardful creates the payable batch
In Rewardful, commissions that meet your minimum payout threshold appear in the Payouts area as Due. Select only the affiliates you plan to pay, then download the file.
Rewardful’s commission payout instructions confirm that the export includes only the selected payout rows. When Wise is your selected payment method, Rewardful formats that export for Wise batch payments.
Keep the commission decision inside Rewardful. Don’t rebuild affiliate balances in a separate spreadsheet. That creates two sources of truth and makes disputes harder to resolve.
Wise controls payment release
Wise Business receives the file, validates recipient and payment fields, shows the cost, and sends the transfers after the batch is funded and approved.
The payment owner should use a verified Wise Business account before payout day. Wise requires a batch upload, review, and payment step. Its batch payments guide also explains that a batch can contain multiple recipient currencies, while the batch itself uses one funding currency.
A CSV export is a payment instruction, not proof that an affiliate has been paid.
Set Terms, Data, and Roles Before Payout Day
Most payout failures begin before the CSV exists. An affiliate has old bank details. A refund has not cleared. A finance user has full payment rights without a second review.
Build the rules before commissions reach the Due queue.
Create one written payout policy
Your policy should state the payout schedule, minimum threshold, approval rule, supported countries, payment currencies, and treatment of refunds or chargebacks. It should also state when a new affiliate is eligible for their first payment.
Use a clear internal cut-off. For example, commissions approved by the last business day of the month enter the next payout batch. Commissions under review, linked to a refund, or missing payout details stay out of the release.
Do not add disputed amounts to a batch because the affiliate is asking for payment. Resolve the source commission first.
Restrict who can create and approve payments
Separate the work between at least two people:
- An affiliate manager reviews commission eligibility and payout details.
- A finance operator exports the selected Due payouts and creates the Wise batch.
- An authorized approver checks totals, recipients, and release details before payment.
- A reconciler closes the batch after Wise status data is available.
Wise lets businesses configure payment permissions and approval rules. Its team permission controls let you limit who can set up, send, or approve transfers.
Don’t share one Wise login across the team. Use named access, multi-factor authentication, and a separate approval role.
Run Rewardful Affiliate Payments Through Wise
The reliable sequence is simple: review Due payouts, export selected rows, validate the file, then upload it to Wise. The detail is where teams avoid duplicate or incorrect payments.
Release only selected Due records
Open Rewardful’s Payouts area and filter to Due payouts. Review each selected affiliate against your internal payout policy.
Check the affiliate name, email, payable amount, currency, prior payout history, and any open refund or fraud review. Look for duplicate affiliate profiles and unusually large commissions before export.
Next, select the approved rows and download the Wise CSV. If you need to pay more than Wise’s batch limit, divide the release before you export. Wise allows up to 1,000 transfers in a batch file, so larger affiliate programs need multiple controlled batches.
Do not export every Due payout by default. A smaller approved selection is easier to check and easier to reverse when a problem appears.
Validate the control totals
Before anyone uploads the file, compare the CSV with a payout control sheet. Record:
- Payout period and Rewardful export date.
- Number of selected affiliates.
- Total commission amount by currency.
- Total expected funding amount.
- Reviewer name and approval decision.
- Rewardful CSV file name and internal batch ID.
Open the CSV as a read-only review copy. Do not change column headers or casually edit rows. Wise can reject files with changed headers, missing required data, or unsupported formatting.
If the recipient data is incomplete, return the record to your affiliate update process. Do not guess a bank code, address, or recipient name from an old email.
Upload, Approve, and Fund the Wise Batch
Go to Wise Business, open Payments, then Batch Payments. Upload the Rewardful file and review each transfer before funding the batch.
Wise accepts CSV and XLSX batch files, with a 5 MB file limit and a maximum of 1,000 payments per batch. Check current requirements in Wise’s batch payment template guidance.
Upload the file without rebuilding it
Use the Wise-formatted file exported from Rewardful. If Wise rejects it, don’t start copying payment rows into an old spreadsheet.
First, check the error message. Confirm that the Rewardful payout method is set to Wise, the file headers are unchanged, and every required recipient field is present. Then correct the source data or use Wise’s current template requirements.
Review the batch screen against your control sheet. Match affiliate count, currency totals, funding currency, recipient amounts, and Wise fees. A correct commission total can still produce a wrong debit if the funding currency or payment amount setting is wrong.
Give approvers a full review view
The approver needs more than a total amount. Give them the batch ID, payout period, control sheet, Wise review screen, and any exceptions removed from the release.
Approval should answer four questions:
- Does the batch total match the Rewardful selection?
- Are all recipients expected affiliates?
- Are the currencies and funding amount correct?
- Has a second person checked unusual or first-time payouts?
Users whose payments require approval may face a lower transfer limit per batch. Plan large releases around your Wise permission setup instead of finding the limit during a deadline.
Reconcile the Batch Before Closing the Period
Rewardful records commission obligations. Wise records payment execution. Your payout register connects the two.
Use internal states so nobody mistakes “uploaded” for “paid.”
| Internal status | Meaning | Next action |
|---|---|---|
| Prepared | Rewardful CSV passed review | Upload to Wise |
| Awaiting approval | Wise batch is ready but not released | Approver reviews batch |
| Funded | Wise has received the batch payment | Track transfer statuses |
| Reconciled | Payment records match the payout register | Mark Rewardful payouts paid |
| Exception | A transfer failed, was canceled, or needs review | Hold and investigate |
After Wise confirms the batch, return to Rewardful and mark the matching payouts as Paid. Rewardful supports this step after you send the selected payouts.
Keep the Wise batch ID, Wise transfer references, funding receipt, fees, FX details, Rewardful export, reviewer decision, and final status in one payout folder. Also record the source file name, capture date, payout period, and operator.
A completed upload proves only that the file reached Wise. A reconciled batch proves that your records match the payment outcome.
Use a Monthly Release Sequence
A fixed timetable stops rushed decisions at month-end. This example works for a SaaS team with an affiliate manager, finance operator, and approver.
- Day 1: The affiliate manager reviews Due commissions, refunds, disputes, and missing payout details.
- Day 2: Finance selects approved Due records in Rewardful, exports the Wise CSV, and prepares the control sheet.
- Day 3: A second reviewer checks recipients, count, totals, currency, and outlier commissions.
- Day 4: Finance uploads the batch to Wise. The designated approver releases the payment after reviewing the batch.
- Day 5 onward: Finance tracks Wise statuses, handles exceptions, marks confirmed Rewardful payouts as Paid, and archives the batch evidence.
Start with a small approved batch if this is a new process. Test normal recipients, a new affiliate, different currencies, incomplete details, and a refund-related exception.
Measure accepted payouts, not completed uploads. If the workflow saves ten minutes but creates thirty minutes of correction work, it has failed its operating test.
Handle Failed, Canceled, and Returned Payments Separately
A pending payment, a failed payment, and a returned payment need different actions. Don’t resend money because an affiliate says they have not received it.
Check status before you act
If Wise shows a transfer as pending, wait for the status to change or contact Wise through the account. A second transfer can create a duplicate payment.
A canceled transfer can result from incorrect recipient details. Wise explains that when a recipient bank rejects a payment because of incorrect information, the money will usually return to Wise. Review Wise’s canceled transfer guidance and confirm the refund status before you reissue anything.
A failed transfer does not prove that funds are already back in your account. Check whether Wise shows a refund, requires more information, or has an active review.
Reissue only a clean exception row
Keep the original payout record unchanged. Create an exception entry with the affiliate ID, Wise transfer reference, failure reason, amount, currency, owner, and next review date.
Ask the affiliate to update details through your approved secure process. Do not accept bank changes through an email reply without identity checks. Once the refund is confirmed and new details pass review, create a replacement payout record.
Tell the affiliate what happened without sending sensitive account details. State that the payout needs updated information, identify the next action, and give a realistic review date.
Keep Security, Tax, and Legal Records in Scope
Rewardful affiliate payments involve personal data, financial records, and cross-border transfers. Treat payout files like finance records, not marketing exports.
Preserve evidence and limit access
Give affiliate staff access to commission review. Give finance access to payout files. Give only authorized approvers the right to release funds. Keep raw CSV files out of general Slack channels, public drives, and email threads.
Store the original Rewardful export separately from control sheets and later corrected versions. Your record should show who prepared, approved, rejected, or returned a batch for correction.
Use a short retention schedule that fits your accounting, privacy, and legal requirements. Remove unnecessary bank data from reports and dashboards.
Check tax and payment obligations early
Your tax treatment depends on the affiliate’s country, entity type, contract terms, and the nature of the payment. A U.S. business may have information-reporting duties for qualifying contractor payments. Review the IRS guidance on reporting payments to independent contractors with your tax adviser.
Don’t assume an affiliate is a contractor in every jurisdiction. Don’t classify payment fees as commissions. Keep separate records for commission earned, payment fee, FX cost, refund, and amount delivered.
Final Thoughts
A reliable payout process has one rule: don’t mark money as paid until the records support it.
Rewardful gives your team the Due queue and Wise-formatted CSV. Wise gives your team batch review, approval, funding, and transfer tracking. Your internal controls connect both systems into a payment process that affiliates can trust.
