Gig Work Pays Weekly. Your Invoicing Records Shouldn't Live in a Shoebox.

Gig Work Pays Weekly. Your Invoicing Records Shouldn't Live in a Shoebox. Gig work has a rhythm regular employment does not: money arrives in small amounts, from several directions, often before you have finished thinking about the job that earned it. A delivery app pays out on Tuesday, a marketplace releases a booking fee on Thursday, a private client texts a photo of a receipt on Friday. That rhythm is why so many gig workers have no reliable record of what they earned. The payment arrives without an invoice, so the habit never forms. Then a client disputes a charge, a platform asks for proof of a job, or a filing deadline appears, and the answer lives in four apps and one camera roll. Three kinds of gig income, three record types Platform-collected work. The customer pays the platform, the platform pays you, a commission comes out in between. You usually cannot invoice the customer, but keep the platform's earnings statement: it is the only document showing gross, fees and net per job. Direct clients. Someone found you through a marketplace, then hired you privately, or you picked up the work yourself. Here the document is your responsibility, and it is where most gig workers are unprotected, because the work feels casual and an invoice feels formal. Mixed arrangements. The platform supplies the client but you invoice them directly, or you invoice the platform for a bonus or reimbursement. These are the ones where a missing document is hardest to reconstruct. If you are unsure which applies, ask who decides when you get paid. That party needs either your invoice or your record of their statement. An invoice that survives being questioned Gig invoices are short because the jobs are short. That is fine, as long as five things are on the document: Who you are, under the name your client knows. A unique number, sequential across everything you issue — not restarted per client. The date of service, not just the date you wrote the invoice. For gig work these differ, and the gap is what disputes turn on. A reference the client recognises: booking ID, job number, address, platform order reference. What was done, in units: hours, trips, deliveries, rooms. "Services rendered" is not a description. Add a payment method and a due date. For a private client, a due date is the difference between "I will send it over" and a payment you can point at. Bill the same day, from the same place Gig work has one natural advantage: you are already holding the phone. Create the invoice at the end of the job, before accepting the next one, while you still remember the extra hour, the reimbursed parking, the Thursday second visit. A week later you are estimating, and estimating rounds in the client's favour. Two things make this fast enough to actually happen: saved client details, and reusable line items for work you do repeatedly. When a job recurs, the invoice is a quantity change rather than a typing exercise. Track what the invoice does not show An invoice records what you charged, not what the work cost. Gig income is unusually cost-heavy — fuel, mileage, parking, tolls, equipment, platform fees, data. Capture those as they happen: Mileage per job, with start, end and destination. Platform fees, recorded separately from the gross. Tips and cancellation charges as their own lines rather than folded into the base fee; mixing them makes reconciliation harder than it needs to be. Job-specific materials, with the receipt photographed on the day. Unglamorous, and the difference between a filing season that takes an evening and one that takes a fortnight. One ledger, many payers The defining feature of gig work is plurality: rideshare Monday, deliveries Wednesday, two private cleaning clients Friday, event shifts once a month. Do not build a separate system for each. One ledger, one numbering sequence, every document tagged by payer and work type. Then numbering stays unique, you can see which stream actually pays once costs are subtracted, and a payer's history is a filter rather than an excavation. Multiple currencies, multiple platforms Gig platforms are increasingly cross-border, and payouts can arrive in two currencies in the same week. Three rules keep it honest: write the currency code, because $400 is four different amounts depending on where the reader sits; record what actually landed, not what the platform said it would send; and keep the statement with the payout, so gross-to-net is reproducible rather than remembered. Where the tool fits The workflow needs three things: fast documents from saved data, a payment status per document, and records you can filter by payer. Invoice Maker covers that narrow set on iPhone and Android, free to download from Caractiv Tech: saved clients and reusable line items, 34 currencies, PDF export, and paid, unpaid and partially paid status per invoice. Manual invoicing works offline, which suits job sites and basements; the AI drafting, which turns a typed or dictated description into an editable draft you confirm before issuing, needs a connection. Premium templates and branding sit behind a subscription. What no app can do is decide the invoice gets written at all. That is the habit. The twenty-minute weekly close Once a week, same day: Issue invoices for work already done. Anything older than seven days is a risk, not a receivable. Reconcile platform payouts against the jobs they represent, noting fees. Mark status: paid, unpaid, partial. A half-paid invoice is not paid. Log the week's mileage and job-specific costs. Note one thing that went wrong — a no-show, a chargeback, a client who haggled after the fact — and which term or deposit would have prevented it. Twenty minutes weekly replaces a weekend in April. That is the trade: a little admin while the job is fresh, in exchange for never reconstructing your own year. Disclosure: I work with the team behind the app mentioned above, which is why it appears as an example. This is general information, not tax, legal or accounting advice; record-keeping requirements and how gig income is treated vary by country and platform, so confirm the rules that apply to you. Appendix: distribution assets (not part of the article body) Social summaries X: Gig work breaks the invoicing habit because the money arrives without a document. Three payer types, one numbering sequence, five fields on the invoice, twenty minutes a week. That is the whole system. LinkedIn: The reason gig workers have poor records is structural, not personal: platforms pay out without ever asking for an invoice, so the habit never forms. Then a dispute or a filing deadline arrives and the answer is spread across four apps. The fix is a single ledger, one numbering sequence, a date-of-service field, and a weekly twenty-minute close. dev.to: The most useful field I added to my gig invoices was the date of service, separate from the invoice date. For short jobs, that gap is what every dispute actually turns on — and it is the field most templates leave out. Image suggestion Concept: A kitchen table with a phone showing an invoice, a paper diary open to a week of mileage notes, a fuel receipt and a delivery bag in the background; warm evening light, deliberately unstyled. Alt text: Phone showing a gig work invoice beside a mileage log, fuel receipt and delivery bag. Notes: 1200×800 for blog header, 1080×1080 for LinkedIn. Keep the on-screen client as "Sample Client" and blur any real receipt details.