Afternoon careApproved
2:30 pm to 6:00 pm · 15 min break
- Actual
- 3 h 15 m
- Travel
- 8.4 km
- Gross pay
- $115.48
In development · not yet on the App Store
A shared care record
Care is personal.
The record stays exact.
Nanny Invoice helps parents and caregivers plan recurring care, record actual hours and kilometres, issue an invoice or employee pay record, and confirm payment. The whole week stays in one shared iPhone record.
A page from the shared care ledger
Tuesday, 25 August
Care record
- Actual work confirmedCaregiver · 6:04 pm
- Timesheet approvedParent · 7:12 pm
- Payment to confirmBoth people close the loop
One record for both people
The same work. The same numbers. The same status.
A planned shift becomes a prefilled draft. The caregiver confirms what actually happened. A parent approves it, records payment, and the caregiver confirms receipt. Every transition stays visible.
Where care admin breaks down
Good relationships still need a clear record.
The plan might be in a calendar, changes in messages, hours in a note and payment in a banking app. Nanny Invoice joins those steps without pretending to move money or run payroll.
The plan is not always the shift.
A late finish, a break or travel can get separated from the original booking. Planned care and actual work stay connected, with the difference visible.
An edited total loses the story.
Approval freezes the issued invoice or pay-record snapshot. A later correction becomes a separate adjustment instead of silently changing history.
“Paid” can mean two different things.
The parent records an external payment and the caregiver confirms receipt. The record closes only after both sides have completed their part.
How the record moves
Know what happened and who acts next.
Reusable shift types, recurring schedules and three ways to record actual work support the whole weekly cycle.
- 01Planned
Plan one shift or a recurring pattern
A parent or caregiver uses a reusable shift type to add upcoming care.
- 02Draft
Confirm actual work
The caregiver confirms the plan, enters the work manually or uses the timer. Each path records the real start, finish, break and kilometres.
- 03Issued
Submit, review and issue
A parent approves the period or requests a change. Approval creates an unchanged invoice or employee pay-record snapshot, with an on-device PDF.
- 04Paid
Confirm both sides of payment
The parent records the external payment, then the caregiver confirms it arrived. No money moves through the app.
Designed for trusted households
Each person can see their role and the current status.
Version one uses app-level household roles. It does not claim tamper-proof role enforcement.
Parent
Own the arrangement and close the pay loop.
- The owner manages members and finance settings.
- Parent collaborators can approve timesheets.
- Parent collaborators can record payments.
Caregiver
Record the work and confirm the outcome.
- Create planned shifts and record their own actual work.
- Submit a timesheet and respond to requested changes.
- Confirm that a recorded payment was received.
Numbers that can be explained
See how every total was calculated. Keep approved history unchanged.
Each caregiver has an independent record for shifts, timesheets, documents and payments. Gross pay comes from recorded time, rates and supported kilometres. Approval locks a snapshot. A later correction becomes a separate adjustment with its own submission and approval, so the old record stays intact.
Illustrative calculation
- 3 h 15 m × $33.00
- $107.25
- 8.4 km × $0.98
- $8.23
- Gross pay
- $115.48
Privacy
Share through private iCloud records.
The current build keeps the working copy on iPhone and syncs the owner's record through private iCloud storage. Participant sharing still needs two-account device testing. No developer-run server holds household care or pay data.
- Private iCloud recordsInvited household participants only
- Protected local snapshotsUseful records remain available on device
- Deliberate limitsNo bank transfers, payroll filing, ads or analytics in the current build
Current release status
The version-one workflow is built.
Release proof is still in progress.
Private iCloud sharing still needs a two-account device canary. Build 6 is valid and active for internal TestFlight testing; physical iPhone accessibility and installation checks are still outstanding.