A GP locum invoice generator built around your sessions
airGP helps GP locums create invoice records from session data, email invoice PDFs, track unpaid invoices, and record payment dates in one workflow.
airGP helps GP locums create invoice records from session data, email invoice PDFs, track unpaid invoices, and record payment dates in one workflow.
The invoice generator is built around the way GP locum work actually happens: sessions are logged, practices are selected, fees and expenses are checked, and invoice records are created from that source data.
A practical workflow for keeping records current.
How this feature fits into the wider airGP workflow.
Most invoice errors begin before the document is created. A date is copied from the wrong diary, a revised rate is missed, parking is entered twice or one completed session never reaches the invoice register. Starting with a reviewed session record reduces that repeated entry and preserves the link between the work and the bill.
In airGP, the calendar and session record can hold the organisation, date, fee, expenses and pension context used by the invoice workflow. You can then create a PDF, download it or email it, while retaining the invoice record for payment follow-up. The generator improves the process; you still approve the underlying facts and final document.
The practice should be able to identify the supplier, match every line to its rota, confirm the agreed amount and make payment without another email. Include the correct supplier and customer details, a unique invoice number, invoice and due dates, dated work descriptions, rates, separately stated expenses, total, terms and payment details.
Additional legal details depend on whether you invoice personally, as a sole trader or through a company. Pension notes and purchase-order references depend on the arrangement. airGP does not determine those requirements, so confirm them with the practice and your accountant before relying on a standard setup.
| Field | Why it matters | Common mistake |
|---|---|---|
| Supplier details | Identifies who provided the work | Mixing personal and company identities |
| Practice details | Routes approval to the correct customer | Using only a branch nickname |
| Unique number | Supports a traceable invoice register | Reusing a cancelled number |
| Session lines | Lets the practice verify work | Combining dates into a vague description |
| Expenses | Explains additions to the fee | Including unagreed or duplicate costs |
| Due date and reference | Makes payment action clear | Relying on ambiguous terms alone |
Log the booking with the right organisation and agreed rate. After working, update any genuine variation and add only expenses that belong in the record. Select the relevant uninvoiced sessions for that organisation, create the invoice, inspect every line and open the PDF before sending.
If the practice accepts a monthly batch, several sessions can be grouped when the organisation and arrangement match. Do not group unrelated customers or obscure different rates. Once sent, keep the status as unpaid until bank evidence confirms receipt, then record the actual paid date.
A controlled template is reasonable for a locum who sends very few invoices. A spreadsheet can add a register and calculations. Both depend on careful manual links between the diary, invoice file, sent email and bank. The administrative risk rises as the number of practices, sessions and payment terms grows.
A connected generator is strongest when the same data needs to support the calendar, invoice, unpaid list, earnings report and tax export. airGP is designed for that operational workflow. It is not a full statutory accounting ledger and does not replace the bookkeeping or company accounts your structure may require.
| Capability | Document template | Spreadsheet | airGP workflow |
|---|---|---|---|
| Uses session source data | Manual | Usually manual | Connected |
| Generates invoice PDF | Manual save | Separate template or automation | Supported |
| Emails invoice | From your inbox | From your inbox | Supported in the invoice workflow |
| Shows paid/unpaid status | Separate list | If maintained | Supported |
| Keeps reminder/email log | Search inbox | Manual notes | Supported |
| Tax/accountant source export | Manual collation | Possible | Structured exports |
An invoice is not paid merely because it was emailed. Review unpaid records regularly and check the due date, recipient and any response before chasing. A first reminder should be concise: identify the invoice, work dates, amount and due date, reattach it if useful and ask for confirmation or an expected payment date.
airGP keeps invoice email logs and supports payment reminder emails, so you can see relevant follow-up before sending another message. When the money reaches your bank, record the paid date. If the amount differs, investigate a partial payment, combined receipt, deduction or error rather than marking the invoice fully paid without explanation.
At month end, compare completed calendar sessions with invoiced sessions, then compare paid invoices with bank receipts. Review cancelled invoices rather than deleting history, and investigate gaps between work performed, invoices issued and cash received. Those three totals can legitimately differ, but every difference should be explainable.
Connected session, invoice, mileage and expense data can feed airGP earnings summaries, dashboard reporting and tax exports. Supported MTD workflows can use structured records for quarterly preparation. The generator does not decide the accounting basis, allowable expense or tax treatment; confirm those decisions with your adviser.
Frequently asked questions
Yes. airGP creates invoice records and PDFs from selected session data. Review the organisation, dates, fees, expenses, payment details and final PDF before downloading or emailing it.
Yes, where the sessions are for the same organisation and a combined invoice matches the agreed process. Show every date and applicable rate clearly.
Yes. Invoice emailing is supported, and relevant email history is retained in the invoice workflow. Always verify the recipient and attachment first.
No. airGP records the pension context you use, including Form A and B, GP SOLO or No Pension workflows, but you must establish the correct treatment with the organisation and relevant guidance.
Yes. Invoice status, reminders and paid dates can be maintained. Use your bank as the final evidence of payment.
No. It provides a connected GP locum administration, invoicing and source-record workflow with exports. Your legal structure may still require formal bookkeeping, accounts and professional advice.