They clocked in. Payroll already knows.
DailyBrew records who worked. BasilBook turns that into days worked, fills in a payroll period, and posts the wages journal once you have checked it — so the month does not end with someone counting shifts off a photo of a paper roster.
Attendance sync is a Pro feature.
What comes across
Attendance, in a form payroll can use
One API key, and the shifts your team actually worked stop living in two places.
Attendance records
Clock-ins and clock-outs for the dates you ask for, per employee, kept alongside the staff records you already have in BasilBook.
Days worked
The number payroll actually needs. A payroll period pre-fills from it instead of from someone's memory of who was in on the 14th.
Late and absent
Flagged per day, and never for a day that has not finished yet — a shift still in progress is not an absence.
Employees you have not linked
Anyone DailyBrew reports who is not yet matched to a BasilBook staff record is listed by name after each sync, so a new hire surfaces immediately rather than going quietly missing from payroll.
Setup
A key, then a one-time match
You need an owner or manager role in BasilBook, and API access in DailyBrew.
- 1
Create an API key in DailyBrew
DailyBrew, Settings, API. Copy the key — BasilBook encrypts it before storing and never shows it back in full.
- 2
Paste it and test
A successful test names the workspace it connected to, so you know the key belongs to the right team before anything imports.
- 3
Sync a few days
Start with a short range. The result tells you how many records arrived and, more usefully, who did not match.
- 4
Link the unmatched people
Match each name to a staff record once. The link is stored against the employee's stable DailyBrew ID rather than their display name, so it survives someone changing what they are called.
Have it ready before you need it
Set a cadence and attendance arrives on its own, so the payroll period is populated before you open it rather than after. Each run re-reads the last three days — a shift corrected the day after is a shift that needs correcting here too. Nothing is posted without you: automatic sync fills in days worked, and running payroll is still a decision you make and approve.
What it does to your books
Attendance ends up in the ledger
Not directly, and that is the point — attendance feeds payroll, and payroll is what posts.
A payroll period you review
Days worked, overtime and advances come together into a period you check line by line. Nothing reaches the ledger until you say so.
The wages journal, written for you
Approving the period posts the entry — wages expense against what you owe staff — balanced, and without anyone opening a journal screen.
Labour as a number you can act on
With hours in the same system as sales, labour as a percentage of revenue stops being a monthly guess and becomes something you can look at on a Tuesday.
Questions
The things people ask first
How does BasilBook know which employee is which?
By the employee's stable DailyBrew ID, not their username or display name. This matters: usernames get edited, and a match built on one silently breaks the moment someone corrects a spelling. You link a person once and the link holds.
Someone is missing from the sync. What now?
They will be listed as unmatched after the sync that found them. Open Staff, match the name to the right person, and the next sync picks them up — including the days already imported.
Does it run payroll automatically?
No, and it will not. Attendance fills in days worked; approving a payroll period and posting the wages journal stays a deliberate act. Paying people is not a thing to automate behind someone's back.
Does BasilBook change anything in DailyBrew?
No. It reads attendance and nothing else. Corrections belong in DailyBrew, and the next sync brings them across.
Is it on the free plan?
No. Attendance sync and payroll are Pro, at $39.99 a month or $399 a year per location.