Payroll

Payroll/compensation: Base pay, Deductions, effective dates.

Payroll/bonuses: apply per Confirmed order or per Delivered order. Choose the Metric: delivered orders, confirmed orders, realized revenue, delivery rate (the rate over the 30 days before the period, best for website closers), or Chat conversion rate (best for WhatsApp closers).

Payroll/bonuses (Bonus rules): it is a kind of bonus rule, chosen in the same Metric list ("Delivery rate: an amount for every delivered order each month" or "one fixed amount each week"), and its rules sit in the same table, with Edit and Switch off, and Delete for a delivery rule that never paid anyone and owes nothing (a rule that has paid or still owes can only be switched off, and an earlier version of a rule is never deleted). What is owed, with the Pay button, is the "Delivery bonuses: what is owed" section at the top of the same page. Two kinds. Each month, an amount for every delivered order: at 70% delivered the person earns 200 for each delivered order, at 80% 300 for each one, so 100 orders taken and 80 delivered earns 80 x 300. Each week, one fixed amount: for example 70% delivered in the week earns 5,000. The delivery rate is delivered orders out of ALL orders taken in the period, rounded down (1,402 of 2,003 is 69.99%, not 70%). An order counts for ONE person. For an order created on or after 1 December 2026 that is the closer it counts for: the closer who had it first, even when the overdue or late rule (or "Send to the policing closer") moved it on, unless they were no longer active at that move, or an Owner, Admin or Manager handed it to someone else by hand; a rescue that fails counts against the first closer too. For an older order it is the one who held it when it was delivered or closed (an order still open: whoever holds it now). Either way, moving a closed order to someone else changes nobody's figures, and the same person counts in the payroll bonus targets (delivered orders, revenue, the delivery-rate gate) and in My earnings. A payroll draft stops and names an order if it cannot tell which closer that order counts for. An Owner, Admin or Manager can choose who such an order counts for by hand (see "Changing who an order counts for" below). Cancelled, failed and returned orders count as taken and not delivered. Imported orders and upsells never count, and only orders taken after the rule was created. A Fewest orders number stops one lucky order earning the top bonus. The period is the calendar month or week in the business's own time zone, fixed when the rule is created, so changing the business time zone later moves nothing. The page lists every person and period with orders taken, delivered, rate, earned, paid and owed. Pay shows the exact amount and the cash account it comes from, and pays only if the amount you saw is still what is owed; pressing it twice pays once. A late delivery that lifts the rate raises the whole period's bonus, and the next Pay pays the difference. A return after payment is never taken back, and a month that is still running can be paid on what has built up so far: if the rate falls later, nothing is taken back. Voiding the expense a payment booked writes the usual reversing entry, but the bonus stays paid and that period cannot be paid again. A weekly bonus can be paid from the day of the week you choose, after the week ends. A payroll run never pays these. Changing what a rule pays starts a new version from the next period; the period that is running is paid as it was. Switch off stops new periods and orders taken after it no longer count. The person sees their rate, the next level and what they have earned, paid and are still owed on My earnings.

Payroll/bonuses. Each active rule has Edit, which opens its form filled in (the tiers are listed in the table too: "50 → NGN 20,000"). Every rate is typed as a plain percent: 80 means 80%, for the tier threshold of a Delivery rate rule, its minimum delivery rate and the chat conversion threshold. A revenue threshold is typed in the rule's currency (500000 in NGN is ₦500,000). Deactivate stops a rule paying from then on; it then sits under Switched off, a collapsed list. A payroll period that had already ended when you switched a rule off is still paid by it, also in a run you draft later, the same way a chat conversion rule works (so a bonus earned in a finished period is never lost). Only periods ending after the switch-off are not paid, and a rule switched off that way cannot be switched on again: create a new rule. Delete removes a rule for good, and only appears for a rule that never paid anyone and owes nothing: a rule is also kept, and can only be switched off, while any day since it was created that has already ended is still in no payroll run (a run you draft later for that day would pay it). Once payroll runs cover all those days, Delete appears again. A rule named in a payroll run, or that settled a chat conversion period, is kept so what staff were paid stays explainable. To switch a rule off and change what it pays, save the change first and switch it off afterwards. A payroll run remembers the settings each rule had when it was drafted, so editing a rule later never changes a run already drafted. An edit that changes what a rule pays never rewrites a period that has already ended. For an ordinary rule, a payroll run for a period that ended before the edit still uses the old settings: the old rule moves to Switched off, marked "(to <date>)", as an earlier version that you cannot edit or delete, and a new rule with your changes applies to runs whose period ends from the edit on. A rename alone just renames it. A chat conversion period that has already ended keeps the tiers it ran under in the same way: when you change what a conversion rule pays (tiers, fewest chats, who it applies to, currency) after a period has ended, the old rule moves to Switched off, marked "(to <date>)", and still pays those periods in the next run, while a new rule with your changes pays from the start of the current period. A rename alone just renames it.

A "Chat conversion rate" rule pays by the share of their chats they won: chats won ÷ ALL the WhatsApp chats given to them in the pay period, open chats included, so leaving a chat open never helps. A chat a Manager, admin or the owner marked as spam is not counted, unless it was won or that person is the closer being paid. A mark by the closer, a colleague or Lazycom support changes nothing, Not spam puts the chat back, and a run already drafted keeps its figures. On the run, under the conversion line, "N chats were left out" says how many such chats were not counted; someone who can read every chat in the Inbox also sees the customers' names, each opening its chat. A chat counts as given to the closer in the period when it was assigned to them (a chat handed to someone else counts for the new closer from the day it was handed over). A chat counts as won when its order is delivered, and wins count if delivered within 7 days after the period ends, because delivery takes days. So the bonus is paid one run late: the conversion bonus for a period is worked out and paid in the first payroll run drafted after the period ends plus 7 days (normally the next period's run), shown on the run as "Chat conversion bonus for <period>". Base pay and every other bonus are not held back, and nothing blocks drafting a run. Each period is paid exactly once for each person: a run that is drafted before the 7 days are over does not pay it, and the next run picks it up; a period that no run has reached yet stays waiting. A person with no pay record in the run's currency, or who is suspended, is not paid in that run and their waiting period is paid by the first later run that includes them. Each period is judged by the roles the person held when that period ended: a WhatsApp closer at that moment is paid even if the role was removed later, and someone given the role afterwards gets nothing for it (no back pay). A rule that is turned off stops future periods only: periods that had already ended are still paid in the next run, and the Bonus rules page lists them beside the Turn off button. Someone who has been removed gets one last payment in the first run after that: the bonus already earned for periods that ended before they were removed, worked out on the chats won so far (the 7 days may not be over). The period they were removed in is not paid. A new rule only pays periods that start after it was created. My earnings shows the current period as "pending, paid in a later run". A chat won even later counts only in the period it is won in, and only if it was also given in that period. The rate is rounded DOWN (a tier is never reached by rounding up). Type the tier thresholds as plain percentages (for example 60 for 60%). "Fewest chats given to the closer in the period to earn this bonus" (new rules start at 10) stops a lucky chat earning a top tier: with fewer chats than that, nothing is paid (empty means at least one). The rule must apply to WhatsApp closers (by role, or named people); website closers have no chats, so it never pays them. This is not the WhatsApp leaderboard's method, which counts chats by the day they arrived and only the ones that finished, so the two can differ.

A rule that reads a delivery rate (the Delivery rate metric, or the "minimum delivery rate" on any rule) has a switch "Only count orders Operations packed", off by default. When on, an order counts toward the closer's delivery rate only if someone other than the closer, with the packing permission, moved it to Packed. An order the closer dispatched without that pack counts as neither delivered nor failed, so the closer is judged only on parcels Operations confirmed. The switch starts when you save the rule with it on: orders created before that count as before. Turning it off, or saving a rule that does not read a delivery rate, clears it.

On a bonus rule that counts Realized revenue, the box "Take refunds off this bonus" is ticked by default: money given back to buyers in the period is taken off the revenue the bonus counts, so a refunded sale does not earn a bonus. Untick it to pay on the full revenue, even sales that were refunded. The list of rules shows "Refunds taken off" or "Refunds not taken off" under the metric. It only applies to the Realized revenue metric. Rules cannot be edited: to change it on a rule you already have, turn the rule off and create it again.

A closer's delivered orders, revenue and delivery rate include every order assigned to them, even when the orders came in through different WhatsApp closers. The delivery rate a rule checks ("minimum delivery rate") is read over the 30 days before the run starts, in the run's currency, so a business that sells in two currencies gets a separate rate for each run.

A website closer or WhatsApp closer sees their own bonus (so far this week or month, and what paid runs paid them) on Orders > My earnings, using the same rules and order figures a payroll run uses (it counts the store's own days, a run counts the run's dates), but never their pay or deductions. It is not a promise: the run decides the amount. The owner can hide it with "Show closers their earnings" in Orders settings.

Payroll/runs: generate a run (Draft), review Gross/Items, "Approve run," then "Pay run" — a paid run shows "Paid on [date] by [name]." Approving/paying needs Approve expenses (who has it: Owner, Admin, Manager, Accountant), a separate permission from Run payroll (who has it: Owner, Admin, Accountant) (which lets someone create/edit but not sign off). The runs list picks dates at the top (This month, Last month, This quarter, Year to date, All time, or your own From and To) and finds a run by the day its pay period starts; the last day you pick is included. Paying books each person's pay as a cash payment and as an expense in the "staff" category; if that category was archived or deleted, a new "staff" category is created automatically.

Payroll/attendance: Check-in records, flags Absent. The page lists everyone's name, email, roles and attendance, so only people who run payroll (Run payroll (who has it: Owner, Admin, Accountant)) can open it; other staff use the Clock in button in the top bar for their own times.

Every staff member (not the owner) has a "Clock in" / "Clock out" button in the top bar. The first clock in of a day creates that day's attendance row as Present with that time as the check-in, and the last clock out sets the check-out. A row a manager already wrote for the day is never overwritten. Each stretch of work is its own session, so stepping out and coming back works: the Attendance page shows "Worked" (the sum of the sessions) and "Breaks" (the time between them). Nothing here marks anyone Late or changes anyone's pay: the attendance row is still what payroll reads, and "Breaks are paid" only labels the break time today. On the Attendance page, people who can manage payroll also set "Clock people out automatically at the end of the day" (off by default) and the end of day time in the business's own time zone: a session left open is closed at that time, never later, so a forgotten clock out is not credited with the night.