Add staff, prepare a month’s salaries, check the wallet, pay people, and retry anyone who failed.
Merchants already moved money in FloatMerchant, but paying staff still meant spreadsheets and other bank apps. There was no clear place to manage employees, see if there was enough money for salaries, approve a month’s pay, or fix it when one person’s transfer failed.
Paying staff is a monthly job merchants cannot get wrong. If the product does not show who gets paid, whether the money is there, or what went wrong last month, they leave and do payroll somewhere else. The goal was a payroll flow that feels as clear as sending a normal transfer: the people, the amounts, the wallet, and an honest status when something breaks.
Merchants can add employees with bank details and regular bonuses or deductions. Each month they review a draft of everyone’s pay, change amounts if needed, approve when ready, and watch payments go out. The main screen shows wallet balance (including money held aside), the next pay date, what last month looked like, and alerts when a payment failed or someone is paused. Settings cover pay day and whether approval should stop if the wallet is short.
Payroll was designed as one continuous job, not a pile of separate screens. The same wallet merchants already trust for transfers funds salaries. Drafts appear ahead of payday so there is time to review. If some people get paid and one fails, that mixed result stays visible so the failed ones can be retried without guessing. Paused staff stay out of the month’s draft so they are not paid by mistake.