A contractor payment schedule template needs two linked parts: a timesheet where hours are logged by client and project and approved, and a pay run that totals approved hours for the period, works out what each contractor is owed, and tracks due date, route, status and reference. The free spreadsheet below does both, with formulas, and includes a completed fictional example.
It is built for U.S. agencies and small teams paying hourly, fixed-fee and milestone contractors, many abroad, on a monthly or twice-monthly cycle. It follows the same steps as a RemiPay pay run (hours, approval, payout, status), so you can start in a spreadsheet and move later without changing how you think about the month.
Download: contractor timesheet and pay-run template (.xlsx)
What a contractor payment schedule covers
A schedule is more than a list of dates. Write these down for every contractor, ideally in their agreement:
| Element | Example | Where it lives in the template |
|---|---|---|
| Pay cycle | Monthly, paid on the 5th | Pay run tab, Due date |
| Work period covered | Previous calendar month | Pay run tab, Pay period start and end |
| Pay type | Hourly, fixed retainer or milestone | Pay run tab, Pay type |
| How the amount is set | Approved hours x rate, or the agreed fee | Pay run tab, Amount owed formula |
| Approval rule | Hours count only once approved | Timesheet tab, Approved by and Approved date |
| Payout route and currency | Wise to EUR, or Payoneer in USD | Pay run tab, Route and Currency |
| Record for the books | Status, paid date, reference | Pay run tab, Status, Paid date, Reference |
How the template works
The file has two tabs, and each starts with a short "How to use" note. Yellow cells with blue text are inputs; black text is a formula; green text is pulled from the Timesheet tab.
Timesheet tab
One row per work entry, with these columns: Date, Contractor, Client, Project, Hours, Rate, Currency, Approved by, Approved date.
An entry only counts toward pay once someone fills in Approved date. Leave it blank for hours that are still being discussed. Logging by client and project, not just by person, is what lets you check hours against estimates and client invoices before paying. The method for that review is in how agencies review contractor hours before paying.
Pay run tab
Set the pay period start, pay period end and due date at the top, then list each contractor once. Columns: Contractor, Country, Pay type, Approved hours, Rate, Amount owed, Currency, Due date, Route, Status, Paid date, Reference.
The formulas do three jobs:
- Approved hours uses SUMIFS to add up the contractor's Timesheet hours that have an approved date and fall inside the pay period. Unapproved hours and hours from other months are left out automatically.
- Amount owed is approved hours x rate when Pay type is Hourly. For Fixed or Milestone, enter the fee in Rate and the formula uses it as is.
- Due date copies the run's due date onto each line, and a summary block totals the run by status (Paid, Pending, Marked paid) and shows how much went through Wise.
Pay type, Route (Wise, Payoneer, Other) and Status (Paid, Pending, Marked paid) are drop-down lists, so the accountant gets consistent values. Currency is the currency the contractor receives; Amount owed is in your source currency (USD in the example). Transfer fees are deliberately not in Amount owed: Wise and Payoneer charge their own fees, and those belong in the books as a separate line from the provider's receipt.
Worked example: a completed October pay run
The template ships with a fictional, illustrative sample already filled in: Northgate Studio, an invented U.S. agency, paying five contractors for October 2026 on November 5. The names, clients and rates are made up. It is the same example as our sample contractor pay run, so you can follow it end to end.
On the Timesheet tab, 14 entries are logged. Four of them show how the filters work:
- Lucía's 6 extra Fieldhouse Running hours have no approved date (they went past a cap and are on hold), so they are not counted.
- One of Ana's entries is dated September 30, outside the October period, so it is not counted.
- Two November entries are logged but not approved yet; they belong to next month's run.
The Pay run tab then calculates:
| Contractor | Country | Pay type | Approved hours | Rate | Amount owed | Currency | Route | Status | Paid date |
|---|---|---|---|---|---|---|---|---|---|
| Ana Ribeiro | Portugal | Hourly | 112 | $45 | $5,040 | EUR | Wise | Paid | 2026-11-05 |
| Dev Malhotra | India | Fixed | 0 | $3,200 | $3,200 | INR | Wise | Paid | 2026-11-05 |
| Lucía Fernández | Mexico | Hourly | 64 | $40 | $2,560 | MXN | Wise | Paid | 2026-11-05 |
| Tomasz Nowak | Poland | Milestone | 0 | $1,800 | $1,800 | USD | Payoneer | Marked paid | 2026-11-05 |
| Mateo Silva | Colombia | Hourly | 40 | $35 | $1,400 | COP | Wise | Pending | |
| Total | 216 | $14,000 |
The summary block shows $10,800 Paid (all through Wise), $1,800 Marked paid (paid through Payoneer and recorded) and $1,400 Pending (Mateo's bank details changed and are being confirmed). Delete the example rows on both tabs before entering your own.
Using it each cycle
- During the period, contractors or leads log hours on the Timesheet tab.
- At period end, review hours by client and project, then fill in Approved by and Approved date for the entries you accept.
- On the Pay run tab, update the period and due date, check each Amount owed, and approve the run.
- Send payments. For Wise, either pay each line or copy names, currencies and amounts into Wise's batch template.
- Close the run. Set each Status, add the Paid date and Reference, and send the file to your bookkeeper.
Wise batch files have fixed column headers you should not rename (Name, sourceCurrency, targetCurrency, Amount, amountCurrency, among others), take up to 1,000 transfers per file, and can pay out in several currencies but from only one source currency (Wise: filling in a batch template). That is why the pay run tab is a planning and record sheet, not an upload file.
Limits of a spreadsheet pay run
A spreadsheet works well for a handful of contractors. The common failure points, and what to do about them:
| Limit | What goes wrong | Mitigation |
|---|---|---|
| Name mismatches | SUMIFS needs the contractor name spelled the same on both tabs | Copy names from the Pay run tab; never retype |
| No approval lock | Anyone can edit an approved row later | Save a dated copy (PDF or locked file) when the run closes |
| Manual status updates | Lines left as Pending after payment | Close the run on payment day, every cycle |
| Retyping into Wise | Amounts or currencies copied wrongly | Check the Wise batch total against the Pay run total before paying |
| Bank detail changes | A changed account is paid without a check | Confirm any change by phone to a known number before paying |
| Fees and FX missing | Books show amount owed, not total cost | Record provider fees and rates from each receipt |
When those start costing time, RemiPay runs the same cycle for you, while you keep paying from your own Wise Business account. Hours come from Hubstaff (auto-approved), the built-in RemiStaff tracker or manual timesheets that the founder approves, and RemiPay shows hours by client and project before you approve. Only the account owner approves the run, with 2FA, and approving starts no transfer: you pay each contractor from your Wise Business account (single transfers or Wise's batch upload) or through Payoneer or PayPal, using the approved amounts, then mark each payment Sent, then Paid, in RemiPay. The accountant gets CSV exports. RemiPay does not import this spreadsheet (there is no CSV time import), so you add contractors in RemiPay or import them from Hubstaff as drafts. The subscription is flat, from $19/mo for up to 3 contractors; Wise transfer fees stay separate and are paid to Wise. See pricing.
Common questions
What is a contractor payment schedule? A contractor payment schedule is the agreed calendar and rules for paying contractors: the pay cycle (for example monthly on the 5th), which work period each payment covers, how the amount is calculated and when an invoice or approved timesheet is due.
How often should contractors be paid? Monthly is common for agencies with retainers and hourly contractors, and some teams pay twice a month. The right cycle is the one written in each contractor agreement and kept consistently.
Does the template include Wise or Payoneer fees? No. Amount owed is what you owe the contractor. Transfer fees are charged by the provider and should be recorded from their receipt, separately from any software subscription.
Can I upload the pay run tab straight into Wise? Not as is. Wise batch uploads use their own template with fixed column headers. You can copy the contractor, currency and amount values into the Wise template, or pay each line as a single Wise transfer. RemiPay does not upload to Wise either: you approve the run in RemiPay, pay from Wise using the approved amounts, then mark each payment paid.
Sources
- Wise, How do I fill in my batch template?: https://wise.com/help/articles/2663302/how-do-i-fill-in-my-batch-template
- Wise, Guide to batch payments: https://wise.com/help/articles/2663240/guide-to-batch-payments
- IRS, About Form W-8BEN (tax form for foreign individual contractors, collected separately from this template): https://www.irs.gov/forms-pubs/about-form-w-8-ben
Checked November 16, 2026
Next steps
- Download the template linked at the top of this page and replace the example rows with your contractors.
- Walk through the same month in the sample contractor pay run.
- Set up the review step with how to review contractor hours before payment.
- Check payout coverage for your contractors' countries on supported countries, and compare costs on pricing.
Posts from the RemiPay editorial team. Have a question or topic request? Email hello@remipay.co.




