From tipped invoice to payroll entry — automatically.

When a customer pays an invoice that includes a tip — through an emailed invoice link, an on-site card reader, or a tap-to-pay terminal — your FSM platform records it. CrewSplit is listening via a real-time webhook connection.

Your FSM platform sends CrewSplit a notification the moment an invoice is paid. CrewSplit confirms receipt immediately (so no events are dropped), then hands the processing off to a background queue. This is the step that breaks every basic automation: webhook threads that run for more than a second get dropped. Ours never do.

If the same payment event fires twice — which happens — CrewSplit identifies the duplicate and discards it. Technicians cannot be paid twice for the same tip due to a retry or a network hiccup.

For a single-visit job, the crew list is straightforward. For recurring jobs where different crew members showed up on different weeks, CrewSplit retrieves the full visit history: every date, every assigned technician, every shift.

This is the failure point of every Zapier or Make.com attempt at this problem. Stateless automations only see the current state of a job — not its history. CrewSplit is stateful by design.

If you're using the hours-worked split model, timesheet records are pulled here as well, one per technician per relevant visit.

During onboarding, you review every imported team member and mark each one as eligible or ineligible to receive tip allocations. That roster is your decision. CrewSplit enforces it mechanically — it does not make eligibility determinations on your behalf. You can update eligibility at any time from your team settings. Changes take effect on the next tip event.

CrewSplit supports three split models. You set a default during onboarding and can configure per-job-type overrides.

All calculations are done to the cent. Any rounding remainder is assigned explicitly to one technician — it doesn't disappear.

CrewSplit connects to your payroll system, finds the current open payroll run, and writes each allocation as a tip line item. Your payroll platform handles all tax withholding from there — CrewSplit doesn't touch that.

CrewSplit always writes the cumulative total of all unpaid tip allocations for each worker — never a partial delta. This prevents reconciliation drift when tips from multiple invoices accumulate across a pay period.

If someone edited payroll manually between CrewSplit's last check and the write attempt, some payroll systems reject the write due to a version conflict. CrewSplit detects this, re-fetches the current state, and retries — instead of failing silently.