Payroll hand-off
Payroll your bookkeeper can drop straight into the provider.
Commissions, tips, clocked hours per staff per period, summed into two CSV shapes: a generic columns-per-pay-component file and a Talenox one-row-per-pay-item file. The hand-off Flowesce does today; native embedded payroll lands region by region.
Built for the salon paying staff every two weeks and re-typing numbers from a spreadsheet into Gusto, Xero Payroll, or a bookkeeper's WhatsApp. The columns line up; the typing stops.
01/
One page sums what each staff member earned.
Reports → Payroll summarizes each staff member's service commission, product commission (broken out by retail / package / service), tips, and clocked hours for the window you pick. The numbers reconcile with the Commissions and Tips tabs in Reports for the same dates so you can sanity-check before exporting.
Service commission.
Per-service or per-variant override, falling back to the staff default percentage. Refund claw-back netted in proportionally.
Product commission.
Broken out by retail, package, and service add-on. Each line carries its own rate so retail-heavy staff don't get under-counted.
Tips.
Service tips and walk-in tips summed per staff. Refund netting applies on the tip axis independently.
Clocked hours.
Clock-in / clock-out timesheet pivot. Total hours per staff for the window. Pairs with the role-and-permissions team layer.
02/
Generic CSV: one row per staff, every component a column.
Service commission, retail commission, package commission, service add-on commission, tips, and hours each as its own column. Ready for Gusto, ADP, Xero Payroll, or a bookkeeper's spreadsheet with light column mapping. The shape that fits the most providers without taking a position on which one you use.
03/
Talenox CSV: one row per pay item.
Talenox's ad-hoc payment import wants one row per pay item with a payment-item code and an amount. The Talenox CSV exports in that exact shape so a salon on Talenox imports without manual reshaping. Map your Talenox payment item codes to the column once; the rest is a copy upload.
04/
Branch filter for multi-branch shops.
Limit commissions and tips to one branch when you run payroll separately per location. Hours stay company-wide for each staff member in v1 because clock-in / clock-out doesn't track which branch the shift was at yet. The page calls that out at the top so you know what you're exporting.
05/
Native payroll is the next step, region by region.
The hand-off CSVs are the universal floor; native embedded payroll inside Flowesce is the next step and it sequences by region. The plan is partner-per-region (Talenox or Payboy for SG, Check for US, PayFit for UK, KeyPay for AU) not a single global vendor. Each region kicks in when the customer base clusters and the demand signal is clear. Building our own payroll engine from scratch is a non-goal; the partner owns tax filing, direct deposit, and the regulatory surface.
Talenox or Payboy for Singapore.
Songer Tech is SG-incorporated; SG is the easiest first region to land native payroll.
Check for the US.
Requires a Delaware subsidiary or a re-think of the legal structure; the partner application is held until the US is confirmed as the dominant customer geography.
PayFit for the UK.
Sequence depends on UK customer cluster timing.
KeyPay for AU.
Same shape, sequence depends on AU customer cluster timing.
06/
What this means for you today.
If you're running Talenox in SG, Gusto in the US, Xero Payroll anywhere, or a bookkeeper with a spreadsheet, the CSV exports already work. If you want fully embedded native payroll inside Flowesce, your region's integration will land in priority order based on where customers cluster. Either way, the math (commission rates, tip splits, hours) lives in one place.
Common questions
Honest answers, including the ones we don't love.
Does this run direct deposit?
No. The hand-off layer exports the numbers; your payroll provider runs the deposits, the tax filings, and the regulatory side. Native embedded payroll (which would include direct deposit) lands region by region post-launch with the right partner.
What if my provider isn't Talenox?
The Generic CSV is the answer for everyone who isn't on Talenox. The columns map cleanly to Gusto, ADP, Xero Payroll, Wagepoint, Rippling, Deel, and most bookkeeper templates with light column renaming on import. We pick Talenox as the named second format because it's the SG provider salons most commonly ask about; more named formats land if demand clusters.
Does it handle hourly staff vs commission staff?
Yes. Hourly staff get a clock-in / clock-out workflow and the Payroll page sums their hours. Commission staff get the commission columns. Mixed-comp staff (a base rate plus commission) live in both lanes; the hand-off CSV ships every component so the provider can do the math.
What about overtime?
Overtime rules vary by jurisdiction (different overtime rates in CA vs TX vs SG vs UK), which is exactly the kind of math the native-payroll partner owns. The hand-off layer reports raw hours and the provider applies the overtime rules. Once native payroll lands per region, the overtime math runs inside Flowesce for that region.
Can I run a payroll on demand?
Yes. Pick the date range (any range, not just bi-weekly) and export. The page is read-only on the underlying data, so nothing changes when you export; you can run two competing date ranges to compare without affecting the books.
Pairs well with
Fourteen days. No card.
Try Flowesce on a real Saturday.
No card required, no auto-charge at the end. If Flowesce isn't for you, export everything in one click and walk.