Redfin Lead Assignment in Follow Up Boss
Redfin Follow Up Boss lead assignment automation can route claimed leads to the right agent, capture property details, and scale Gmail authentication.
Wise Recipient IDs for Team Payments
Set up a Wise recipient ID for team payments: point it at a Wise balance, update the payroll ledger, notify your approver, and test before the next payroll run.
TABLE OF CONTENTS
Setting up a Wise recipient ID for team payments takes four steps: create the recipient so it points to the team member’s Wise balance, copy the new ID into the payroll ledger, tell whoever approves payments about the change, and verify a test payment before repeating the process for the next person. This checklist keeps the payment destination and the ledger record aligned.
What a Wise recipient ID does
A recipient ID identifies the account that should receive a transfer. In an automated payroll flow, the ledger stores that ID and passes it to the payment step. If the ID points to a bank account instead of the recipient’s Wise balance, the money will follow the wrong route even if the rest of the workflow is correct.
Create the recipient from the Wise account that sends the payment. Wise checks recipient details against the required account format for that currency when the recipient is created, and the recipient account ID becomes the target for every transfer to that person (as of October 2026). That makes the ID a critical piece of payment configuration, not a label to copy casually.
Wise recipient ID checklist
1. Create a recipient for the Wise balance
Open the recipient setup in the Wise account that will send the money (usually the business account that runs payroll), then:
- Choose the option to add a new recipient.
- Select the recipient’s Wise balance or Wise account destination, rather than a personal bank account.
- Confirm the recipient name, currency, and account details shown before saving.
- Save the recipient and copy the new recipient ID exactly.
- Record the date, currency, and intended payment route alongside the ID.
Do not assume that an old bank recipient and a Wise-balance recipient are interchangeable. Treat each recipient ID as a separate destination and keep the old value available until the first test payment has been reconciled.
2. Update the payroll ledger
Replace the old recipient ID in the payroll ledger with the new value. Before saving, check that:
- The ID belongs to the correct team member.
- The currency matches the payment row.
- The recipient name matches the person being paid.
- No extra spaces or missing digits were introduced during copy and paste.
- The change is recorded so another operator can audit it later.
If the ledger supports a change history, add a short note such as “Switched destination to Wise balance” with the date and the person who made the change. Avoid editing several people’s IDs in one pass. Updating one recipient at a time makes a mismatch easier to isolate.
3. Notify the manual approver
A new recipient ID can still hit a manual step. For some currencies, Wise checks the recipient’s name against the receiving bank’s records, and if that check flags a mismatch, someone on the sending account has to review and accept the result before the recipient can be used. Wise Business accounts can also have payment approval rules, where a payment one team member sets up isn’t funded until another team member approves it (as of October 2026).
After the ledger update, notify the person who completes that manual step. Include the team member, payment currency, effective date, and the fact that the destination now points to a Wise balance. The notification should happen before the next payment run, not after a payment is waiting for approval.
4. Run and reconcile a test payment
Use the next appropriate payment as a controlled test. Check the ledger status, the Wise recipient, the incoming balance, and the payment amount. If the payment needs approval, confirm that the approver can see and approve it in Wise.
Once the payment is complete, compare the ledger entry with the Wise transaction. Record any fee, conversion, delay, or manual action so your accounting team can reconcile it later. Only then should you treat the new ID as the standard destination for future team payments.
When a Wise card may reduce transfer costs
A Wise card can be useful when a recipient needs to spend funds directly from a Wise balance instead of transferring them to a bank first. That removes a transfer step, but it does not make every transaction free. Wise’s card fees depend on the currency, the card’s issuing region, conversions, cash withdrawals, and the type of transaction (as of October 2026, check Wise’s pricing page for current rates).
Before changing the payment policy, compare:
- The fee to transfer the balance to the recipient’s bank.
- The cost of converting into the currency the recipient will spend.
- Any Wise card or ATM fee that applies in the recipient’s region.
- Whether the recipient can use the card for the intended business expense.
- The reconciliation detail needed for payroll and expense records.
A card is a cost-control option, not a substitute for a correctly configured recipient ID. Keep the ledger destination accurate even when a recipient chooses to spend from the Wise balance.
Troubleshooting recipient and acceptance issues
The payment went to the wrong destination
Pause future payments for that recipient. Compare the ledger ID with the recipient record in Wise, verify the currency, and confirm whether the old bank destination is still active. Correct the ledger only after identifying which record is authoritative.
The recipient cannot see the payment
Confirm that the recipient was created in the correct Wise account and that the payment uses the expected currency. Then check whether the payment is still waiting on an approval, or whether a recipient name check needs review. Do not mark the payment as failed until the approval status and recipient details have been checked.
The ledger and Wise show different amounts
Compare the original payment, conversion, and any fee separately. A balance may differ from the ledger because of currency conversion, a receiving fee, or a later card or ATM transaction. Save the Wise transaction reference with the ledger record so the difference can be explained later.
Final pre-payment checklist
The recipient was created in the correct Wise account.
The destination is the recipient’s Wise balance.
The new recipient ID was copied without changes.
The payroll ledger contains the new ID and correct currency.
The manual approver was notified before the payment run.
A test payment was reconciled against the Wise transaction.
Any card, transfer, conversion, or ATM fee was documented.
Get help building this
Wise recipient changes usually break at the hand-off between the ledger and the payment step: an ID gets updated in one place but not the other, or a payment sits waiting on an approver nobody told. If you’re building a payroll flow that has to validate recipients, update the ledger, and route approvals in one controlled process, book a ZoomFlow session. One of our consultants will build it with you live, and you’ll own the workflow when we’re done.
Related Posts
How a Cleaning Company Fixed a Broken Zapier Automation in a Day
A cleaning company's Zapier automation for review requests stopped after a sender-address change. One call traced the fault upstream, and the Zap never changed.
Inbound Calls Into the CRM: A Home Services Case Study
A Virginia landscaping company lost leads because call transcripts never reached JobNimbus. See how Make automations closed the gap over 3.5 years.
