Fieldworker Payroll Management & Reconciliation

Fieldworker Payroll Management & Reconciliation

OctopusPro helps you manage fieldworker payroll (employees or subcontractors) by automatically calculating each worker’s earnings per job—whether you pay hourly, commission, or a hybrid—and then rolling everything into two purpose-built payroll reports:

  • Fieldworker Bookings Summary (job-level earnings and unpaid items)
  • Payment to Fieldworkers (your payout ledger / remittance register)

From these reports you can filter unpaid work, batch-select jobs, group micro-jobs into a single payout, export bank-ready files (ABA/NACHA/BACS/SEPA XML/CPA-005/CSV/Excel), and maintain a clear audit trail. If you use Stripe Connect, OctopusPro can also automate split payouts so worker shares are transferred automatically when customers pay online.

Fieldworker payroll and commission management in OctopusPro


Quick navigation


What this solves

If you run a mobile workforce (technicians, cleaners, therapists, drivers, tutors, subcontractors, etc.), payroll usually becomes messy when you have:

  • Different pay structures (hourly vs commission vs mixed)
  • Different rates per service, per worker, or per region
  • Extra earnings like product commissions, bonuses, or add-ons
  • Lots of small jobs that should be grouped into one payout
  • Disputes/complaints where payment should be held until resolved

OctopusPro centralises these workflows so you can pay accurately, document everything, and keep admins and fieldworkers aligned—without spreadsheets and manual recalculations.


Prerequisites

Before running payroll, make sure you’ve configured the basics:

  • Pay rules (rates/commission) at the service level, worker level, or both (see next section).
  • Bank details for workers if you export bank payment files or pay via transfers.
  • Fieldworker permissions if you want workers to view earnings in the app.
  • Issue/complaint workflow if you plan to withhold payment for disputed jobs.

Set up how fieldworkers get paid (pay rules)

OctopusPro supports layered pay rules, so the most specific rule overrides the general one. This lets you handle everything from “everyone gets 50% commission” to “this specialist gets 60% on installs only”.

Pay-rule layer When to use it How to set it
1) Worker payment agreement (profile-level) One worker’s overall rate differs from the company default. Fieldworkers → [Name] → Profile → Payment Agreement → choose Hourly/Commission/Hybrid → Save.
2) Service default pay rate (service-level) Every worker should earn the same rate on a specific service. Settings → Services → Edit service → Cost & PayrateService Pay Rates → set Hourly/Commission → Save.
3) Worker-specific rate for a single service (override) A specialist needs a unique rate on just one service. Fieldworkers → [Name] → Profile → Job Settings → Services Provided → Pay Rate & Commission → Save.

Rate hierarchy (how OctopusPro decides what applies):

Booking override → Worker × Service override → Worker Payment Agreement → Service default.

Tip: You can also edit a specific booking’s payout (one-off exception) from the booking’s Payment to Fieldworker panel. Overrides are tracked to support payroll auditing.

Product commission (parts / retail items)

If your workers sell products or parts (e.g., HVAC parts, cleaning add-ons, retail items), OctopusPro can calculate product earnings as well. Common models include:

  • Markup-only commission (worker earns a % of profit/markup)
  • Flat fee per item (fixed commission amount)
  • Cost + markup model (useful when a worker supplies items)

Admins can add products during booking creation, and (if permitted) fieldworkers can add products during check-in or job completion. OctopusPro recalculates totals automatically.


Where to view earnings (admin + fieldworker)

OctopusPro shows the worker share in the places it matters most:

Where you’re working Navigation What you’ll see
Booking details Bookings → All Bookings → View booking Payment to Fieldworker panel: service share, product share, and total
Quote details Quotes → All Quotes → View quote Calculated labour cost/commission visibility before approval
Invoice view Invoices → All Invoices → View invoice Final payout figures alongside customer totals for reconciliation
Fieldworker app Menu → My Earnings Weekly/monthly/yearly charts + drill-down per booking

Permission reminder: If you want fieldworkers to see earnings in the app, enable the relevant setting under your fieldworker permissions.


Fieldworker Bookings Summary report (job-level payroll)

This report lists each fieldworker’s individual jobs and earnings. It’s ideal for identifying exactly what needs to be paid and for marking completed jobs as paid.

How to access: Reports → Fieldworker Reports → Fieldworker Bookings Summary

What you can filter by:

  • Trading name (multi-brand setups)
  • Fieldworker status (active/inactive)
  • Fieldworker name
  • Payment status (Unpaid / Paid)
  • Customer payment status
  • Booking status (Completed / In Progress / Failed / etc.)
  • Invoice number
  • Date range (e.g., “last week” for a payroll cycle)

Common payroll workflow example: Filter for Completed + Unpaid within the payroll period → select the rows → proceed with batch actions.

Batch actions you can run:

  • Save as Paid – Mark selected jobs as paid after transferring money (prevents double-paying).
  • Assign Invoice – Group multiple jobs under one subcontractor invoice number and attach invoice files (PDF/image).
  • Calculate Selected Invoices – Sum selected jobs for quick payout verification.
  • Modify Invoice Reference – Adjust the payout reference number to match your payroll run or bank batch ID.

Subcontractor invoice handling (best practice): If a subcontractor must provide an invoice before payment, use Assign Invoice to bundle the selected jobs under one invoice reference and store the contractor’s invoice file inside OctopusPro for audit and accounting.


Payment to Fieldworkers report (payout ledger)

Think of this as your payout ledger (also known as a payroll remittance register). Every payout you make—single job, grouped invoice, or Stripe Connect transfer—creates a record here.

How to access: Reports → Payment Reports → Payment to Fieldworkers

What you can filter by: Fieldworker, status, location/state, date range (Today / This Month / custom range), and more.

Typical columns include:

  • INV# / Payout Reference (the system payout ID)
  • Bookings Count (how many jobs are included in the payout)
  • Payment Date
  • Invoice Total Amount (total value included)
  • Payment Method / Reference (bank batch ID, Stripe payout ID, cheque number, etc.)
  • Cash received vs bank transfer amounts (where applicable)
  • Amount Paid / Amount Due (supports partials)
  • Notes (e.g., “Week 3 payout”)

Key actions:

  • Save as Paid – Finalises the payout record for reporting and audit.
  • Email report / remittance advice – Share a payout summary with a fieldworker or finance team.
  • Edit – Correct legitimate details (references, attachments, notes). Keep edits minimal for clean audit trails.
  • Delete – Only if the payout record was created in error. For real reversals, preserve the audit trail via adjustments/voiding instead of deleting.

Exporting payroll data (bulk payments)

OctopusPro supports exporting payroll data in bank-ready formats so you can upload one file and pay many workers at once.

Where: In Fieldworker Bookings Summary or Payment to Fieldworkers, click Export and choose your format.

Supported formats commonly include:

  • CSV / Excel (universal export for finance teams)
  • ABA (Australia – direct credit / BECS batch file)
  • NACHA (USA – ACH file)
  • BACS (UK – bank transfer format)
  • SEPA XML (Europe – credit transfer format)
  • CPA-005 (Canada – electronic payment format)

Typical bulk-pay process:

  1. Filter for Unpaid items in the payroll period.
  2. Select the jobs/payouts you are paying.
  3. Export the bank file (or CSV/Excel for review).
  4. Upload the file to your banking portal and complete the transfers.
  5. Return to OctopusPro and click Save as Paid for the relevant rows (to lock the audit trail and prevent duplicate payments).

Manual vs automated payouts (Stripe Connect)

Option A: Manual payroll runs (bank transfer / batch file)

If you pay workers yourself (e.g., EFT/bank transfers), use exports + Save as Paid to keep OctopusPro aligned with your bank statement. You can also attach remittance confirmations (PDFs) or add notes to payout records for audit.

Option B: Stripe Connect (automated split payouts)

With Stripe Connect, OctopusPro can automatically route each worker’s share of a customer payment directly to the worker’s connected Stripe account (and then to their bank account on Stripe’s payout schedule). OctopusPro still records each payout in the Payment to Fieldworkers ledger, so finance teams keep a complete audit trail.

Important: Even with automated payouts, your team should still reconcile regularly and finalise records as required by your workflow (e.g., using Save as Paid when transfers are confirmed/settled, depending on how your business audits payments).


Best practices (avoid duplicate or missed payments)

  • Reconcile on a schedule: Run payroll weekly or bi-weekly so issues are caught early.
  • Use the “Unpaid” filter first: This reduces noise and lowers the risk of double-paying.
  • Group micro-jobs: Bundle small jobs into a single payout/invoice to reduce bank fees and simplify bookkeeping.
  • Keep a backup: Export CSV/Excel each cycle for external storage or accounting uploads.
  • Hold payments for disputes: If a job has an issue/complaint, use a payment hold/withhold workflow so the job is not paid out until resolved.
  • Enable transparency: Let fieldworkers view earnings in the app to reduce payroll queries and improve trust.

FAQ

Can I pay one fieldworker for multiple bookings in one payout?

Yes. Use Assign Invoice (in Fieldworker Bookings Summary) to group multiple jobs into a single payout reference/invoice, then pay once and mark it paid.

Can I adjust commission for one job only?

Yes. Open the booking and edit the Payment to Fieldworker figures for that job. This is useful for one-off bonuses, corrections, or special agreements.

What if the customer paid cash on-site?

OctopusPro can still track the worker’s share and show how much was cash received vs bank transfer in payout reporting, depending on how your business records payments.

How do I handle disputes or quality issues?

Log the issue/complaint and use a payment hold/withhold process so the job is excluded from payroll until it’s approved and closed. This is especially important for subcontractor workflows.

Does this replace my accounting/payroll system?

OctopusPro manages earnings calculations, payout tracking, exports, and audit trails. Many businesses still push totals into accounting/payroll tools (or sync) for full financial reporting, tax, and compliance workflows.


To stay updated, please subscribe to our YouTube channel.

Scroll to top