Every closed week. One file you can trust.
Versioned payroll files, a record of who signed what, and one sign-in for every restaurant you keep books for.
Your client invites you
You get a role made for accountants: closed weeks and their payroll files, the hours, rates and tips behind them, and the labor summary.
Price changes, the list of things to fix and user admin stay with the restaurant.
Add a second restaurant and it shows up under the same sign-in.
Every download, on the record
| Week | File | Signed | Downloaded |
|---|---|---|---|
| Oct 5 to 11 | Version 2 | Owner Tue 9:02 AM | You Tue 10:02 AM |
| Oct 5 to 11 | Version 1, replaced | Owner Mon 9:14 AM | You Mon 4:40 PM |
| Sep 28 to Oct 4 | Version 1 | Manager Mon 8:51 AM | You Mon 11:20 AM |
Sample data.
When a week has to change
Nothing is edited in place. A correction becomes the next version, with a reason and the owner's sign-off, and the old file is marked as replaced.
- Version 1 Signed Mon 9:14 AM Replaced Tue 9:02 AM
- Version 2 Signed Tue 9:02 AM The current file
What changed in version 2
-
Line cook, Saturday
Hours
9.70to 9.20 Missed clock-out fixed in the POS after close. Approved by the owner. -
Week totals
Regular hours
1,184.6to 1,184.1. Overtime unchanged.
Nothing is emailed
Payroll files never travel as attachments. You sign in with your password and a one-time code or a passkey, and download from one place.
Each restaurant's records are kept in their own database, apart from every other restaurant's.
Questions?
Kura Fox is being built now, with its first restaurant. If a client has mentioned it, or you want to know how a file is put together, write to accounts@kurafox.com.