No customer logos. Not yet.
Closepact is new. No customer has yet agreed to be named, and we are not filling the gap with invented companies, invented job titles and invented percentages. What is here instead is what the system does, worked through on numbers you can check yourself.
Three jobs, run through the rules.
These are arithmetic, not customers. Nobody said any of it and no company is named, because none has agreed to be.
- 01
A bathroom, with ROT
Labour 20 000 kr plus 25 per cent VAT is 25 000 kr. ROT is 30 per cent of labour including VAT: 7 500 kr. Materials of 12 000 kr plus 3 000 kr VAT do not qualify, and are excluded by the line type rather than by somebody remembering to untick a box. The invoice totals 40 000 kr, the customer transfers 32 500 kr, and the remaining 7 500 kr is posted to 1513 as its own receivable — outstanding from the state, not from the customer, so the ageing report does not chase Skatteverket as though it were one.
The annual ceiling per buyer is not deducted: it depends on what every other company has claimed for that person this year, which this system cannot see. Once the customer has paid, the 7 500 kr goes into the claim file Closepact builds for Skatteverket’s e-service, where you sign it, and the decision is booked when it comes.
Read about the module - 02
A split shift
A booking from 07:00 to 11:00 and another from 12:00 to 16:00 is one shift, not two. A break of 60 minutes or less is merged before the conflict check counts anything, so a split shift does not raise a false warning. Four checks, two severities — and not one of them refuses the booking. They report, and the planner decides.
A recurrence rule the system does not support is refused at save time with a 422, rather than expanded wrongly across months nobody looks at until they are here.
Read about the module - 03
A basement with no signal
A clock-in or clock-out gets its id and time on the device at the moment of the tap, not when the queue finally drains. The IndexedDB outbox sends serially in the order the events happened, and treats 409, 422 and 404 as settled rather than retrying them for ever. The server keeps the tap's time — within limits that catch a wrong clock — with the arrival beside it, and flags a stretch that synced more than 15 minutes late. The clock in the basement is the one that counts, not the clock when the van reaches the main road.
Position is verified at the moment of the tap, not in the background — an iOS PWA has no background geolocation, so there is no automatic clock-in and we do not claim one. With no reading at all, within_geofence is null rather than false.
Read about the module
When there is a story, it will be theirs.
The first named case goes up when a customer has read the text and agreed to it. Until then this page stays empty of logos on purpose — a page of invented ones is the thing a buyer finds out about later.
Be the first one.
Book twenty minutes and we will set the module up with one of your own jobs. If it works we will ask whether you want to say so — and we publish nothing you have not read.
Book a demo