Send expense reimbursements as payouts
Each expense claim creates a PayPal payout to the employee for the amount claimed, with the merchant and purpose in the note.
New submission on your "Expense reimbursement" form
Create a PayPal payout to the employee for the claimed amount and note
One-directional. A submission triggers the action — nothing is written back into your form.
Small claims — a taxi, a domain renewal, coffee for a client meeting — cost more in chasing than they are worth. A remote team can push them through a form and let PayPal move the money the same day, with the amount and a reference already attached.
The audit trail survives either way. The claim stays in responses with its category, merchant, purpose and approver; PayPal's payouts report holds what was actually sent. Anything above a threshold you set still goes to a person before it is paid.
Setting it up
- 1
Publish the reimbursement form with Amount ($) as a number field, and describe Employee Email as the address attached to the person's PayPal account.
- 2
Agree a ceiling for automatic payment. In Zapier, add a filter that only continues when Amount ($) is at or below it.
- 3
In Zapier, choose formformform, the New Submission trigger and the reimbursement form, then load a real claim as test data.
- 4
Add PayPal's Create Payout action, connect the account finance funds, and set the currency on the action rather than leaving it to the account default.
- 5
Map Employee Email to the payout recipient and Amount ($) to the amount, adding a Formatter step to strip currency symbols in case someone types one.
- 6
Build the payout note from Expense Category, Vendor or Merchant Name and Date of Expense, so the line on the employee's PayPal statement explains itself weeks later.
- 7
Send claims over the ceiling down a second Zapier path that posts to your finance channel naming the person in Approving Manager Name, and pay those by hand.
- 8
Test with a real low-value claim, check it against PayPal's payouts report, then turn the Zap on.
What maps where
Using the Employee Reimbursement Request as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | PayPal |
|---|---|
| Employee Email | Payout recipient email |
| Amount ($) | Payout amount |
| Employee Full Name | Personal message on the payout email |
| Expense Category | First line of the payout note |
| Vendor or Merchant Name | Payout note, alongside the date of the expense |
| Date of Expense | Payout note, and your reconciliation reference |
Variations worth knowing
Add a Digest by Zapier step that collects approved claims and releases them once a week. Finance funds the account on a known day and reconciles a single batch. Employees wait a few days longer, which is usually a fair trade for a team that would otherwise fund the account twice a week.
Add a Zapier Paths step on Department, each path writing the department name into the sender item ID or paying from that cost centre's own PayPal account. The claim form stays a single form, so employees never have to work out which version of it applies to them.
If something isn't arriving
Someone has typed a currency symbol or a comma decimal separator into Amount ($) — "42,50" and "£42.50" both break it. Add a Formatter step that strips non-numeric characters and normalises the separator, and set the form field to accept numbers only.
Approving Manager Name is a name typed by the claimant, not an approval step. The flow pays whatever passes the filter. Lower the automatic ceiling until you are comfortable, and route everything above it to a person, which is where a genuine approval decision belongs.
Frequently asked questions
Do employees need a PayPal account to be reimbursed?
To receive the money, yes. A payout to an address with no account is held while PayPal invites them to claim it. That is why the form should ask for the email attached to their PayPal rather than defaulting to a work address.
Can we reimburse in a different currency to the claim?
The currency is set on the PayPal action, and PayPal converts at its own rate if the recipient's account holds another. Pay in the currency the expense was incurred in where you can, and use separate paths if your team spans several.
Where does the audit trail actually live?
In two places. The submission keeps category, merchant, purpose and approver; PayPal's payouts report keeps what was sent and when. Nothing is written back into the form, so reconciliation means exporting responses and matching on the reference in the note.
Related automations
- Draft an invoice from every quote request
A quote request builds a draft PayPal invoice with the service and a starting figure, ready to adjust once scope is agreed.
- Invoice a customer the moment they order
Every submitted order sends the buyer a PayPal invoice for the item and quantity they chose, with a pay-now link.
- Invoice attendees for the tickets they choose
Each registration sends a PayPal invoice for the ticket tier chosen, priced per seat including any guests.
- Pay a referral reward when a claim comes in
A verified referral claim sends the advocate a PayPal payout for a fixed reward, with the referral named in the note.
- Pay contractors from their weekly timesheets
An approved weekly timesheet creates a PayPal payout to the contractor for the hours logged at their agreed rate.
- Add counter signups to your Customer Directory
A signup at the till or on your site becomes a Square customer profile straight away, spelled the way the customer typed it.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free