Your income is one number. The platforms will only ever show you fragments of it, each in its own dashboard, on its own pay cycle, using its own definition of “earnings”. The fix is not another dashboard — it is a ledger you own, where every job from every app lands with the same fields. Once that exists, the questions that actually matter, like which platform deserves your Saturday, stop being unanswerable.
Why can’t the apps tell you what you earn?
Because each one can only see itself, and they do not even measure the same thing. One reports earnings before its fees, another after; one includes tips in the headline figure, another lists them separately; each settles on its own weekly or fortnightly rhythm. Sum the dashboards naively and you double-count some money, miss other money, and misplace all of it in time.
The deeper problem is that your working day does not respect app boundaries. A Tuesday spent bouncing between a delivery app, a rideshare app and a marketplace task exists as a whole day only to you. Each platform records its slice; the day itself — its total pay, its total hours, whether it was worth working — is recorded nowhere, unless you record it.
What goes wrong without a ledger of your own?
Tax time becomes archaeology: a night of downloading statements in five formats, reconciling five definitions of gross, and hoping the pieces cover the year. Platform fees withheld before payout — real deductible costs, as the deductions primer on this blog explains — quietly vanish from your math because no dashboard is motivated to total them for you.
You also lose the connective tissue between apps. The drive from a drop-off for one platform to a pickup for another is business driving that neither platform will ever log, as the drive-classification guide covers — and per-app record-keeping loses it just as thoroughly. Your business is the sum; fragments systematically understate it.
What should you record for every job?
The same fields regardless of which app the job came from — the uniformity is what makes the records comparable later. Per job or per platform-block of a shift, that means:
None of this is bookkeeping in the intimidating sense. It is a handful of taps made while you still remember the shift, and each field earns its keep the first time you ask the ledger a question.
- Date and, roughly, the hours worked
- The platform the work came from
- What it paid, before fees, in the currency it paid in
- Fees or commission withheld, so the cost is visible rather than vanished
- Tips — especially cash tips, which exist nowhere except your record
- The driving attached to the work, if you drive
How do you keep five apps’ worth of records without a nightly accounting session?
By recording at the end of each shift, in one place, while the numbers are one glance away in each app. The end-of-shift routine post on this blog makes the case in full: two minutes at the kerb beats twenty on Sunday, and the records made now are the trustworthy kind. Multi-app days add one small refinement — record per platform-block rather than one merged figure, so the per-platform picture stays intact.
For the history you did not keep this way, import rather than retype. Most platforms let you download statements; a ledger that accepts CSV brings the past in cleanly, and from then on the habit only has to cover the present.
What questions can a unified ledger finally answer?
The ones you have been answering by feel. What each platform really pays per hour once fees and dead time between jobs are counted. Whether the app that feels busiest actually pays best, or just pings the most. What a Saturday is worth compared with a Tuesday, and whether that gap justifies working it. Which platform’s fee load quietly outgrew its usefulness.
These are decisions, not curiosities — where to log in tomorrow, which platform to drop, what an hour of yours is currently worth. The effective-hourly-rate post on this blog leans on exactly these numbers, and the goal-setting post turns them into a target with a pace. Fragmented records cannot power any of it; one ledger powers all of it.
What about the currencies?
If all your platforms pay in one currency, ignore this section. If they do not — a delivery app paying in your local currency and a freelance marketplace paying in another — then every record must carry its currency explicitly, and merged totals across currencies are a trap. The one-line rule: never store an amount without its currency, and never overwrite the original with a conversion — a converted figure can always be derived later from the original, and the original can never be recovered from the conversion.