Contractor payroll across the markets we serve is part of Fasset Business, and each payout on local rails has a per-transfer price, stated per plan on the pricing page and shown before you approve the run. Building it took longer than the payments product did, which surprised us, because a payroll run is the same transfer repeated.
It is not. Payroll is a schedule, a set of local expectations and a paper trail that happens to end in a transfer. This is what that cost us to learn.
What this guide will cover
- Why payroll is a calendar problem before it is a payments problem
- The markets we built for, and what contractors in each one expect to receive
- Local currency against dollars, and who should carry the conversion
- Failed payouts: the four reasons a name and an account number do not match
- Batch runs, approvals, and the second pair of eyes
- Invoices and receipts, and what a contractor needs at their own year end
- What we cut from the first version, and why
- What we would build differently if we started again
Pakistan is the market where this was hardest, and it gets its own guide: paying contractors in Pakistan.
The full guide ships soon. Meanwhile the product is live, and the application runs entirely online.