Business

Records a WordPress developer should keep for the CA

Records a WordPress developer should keep for the CA: build invoices, retainers, licence bills, client pass-through costs and statements in one yearly folder.

Editorial illustration for Records a WordPress developer should keep for the CA

A WordPress developer should hand the CA four sets of records: invoices for builds and maintenance, bills for your own licences and tools, a clear list of costs paid on behalf of clients, and complete statements. Pass-through costs are the part most likely to go wrong. The CA decides what counts and how, and rules and limits change, so confirm the current position with your CA.

What should the folder contain?

  1. Quotes or agreements for each build, with scope and payment stages.
  2. Invoices for each stage, numbered in a single series.
  3. Maintenance retainer invoices, one per client per month or period.
  4. Licence and tool bills, with the renewal date written on them.
  5. A sheet of hosting and domain costs you paid on behalf of clients.
  6. Statements for all accounts, in full months.

How do you document pass-through costs?

Make a sheet with one row per client expense: date, client, what it was, amount you paid, whether you billed it, and the date they repaid. If you add a handling fee, show it as a separate line on your invoice and in your records. Do not let the item disappear into your general costs, because then your income and costs both look different from what happened. Your CA can tell you how it should appear.

What about licences used across many sites?

A multi-site licence is your own cost, not a client's. Keep the vendor invoice and a note of how many client sites it covers. If a client's site depends on a licence you hold, mention that in your agreement so they know what happens if you stop working together. For the books, what matters is that the bill, the payment and your note all agree.

RecordQuestion it answers
Build agreementWhat was promised and for how much
Stage invoicesWhat was billed and when
Retainer invoicesWhich clients paid monthly and for how long
Licence billsWhat you paid for your own tools
Pass-through sheetWhat clients owe or repaid

Which mistakes are specific to WordPress work?

  • Renewing a client's plugin licence from your account and never billing it
  • Forgetting that a monthly maintenance client stopped paying three months ago
  • Mixing your own website's hosting with a client's on the same card line
  • Holding client logins and licence keys in chat messages instead of a record of what you hold
  • Not noting a free-of-charge fix that you promised, so a later dispute has no paper

How long should invoices stay editable?

Once an invoice is sent, treat it as fixed. If a price changes, issue a credit note or a fresh invoice and say which one replaces which. Overwriting a number in a sheet makes it impossible to match against a bank credit later. A tidy change trail is worth more to your CA than a perfect-looking file.

How do you prepare the cover note?

List your active clients, which ones are on retainers, any build that crossed March, any refund you gave, and the accounts used for business. Mention if a client's hosting is in your name and you are still holding it. If you have a team or sub-contractor, say who they are and how you paid them.

When can software help?

Today, list every client site with the licences, hosting and domains tied to it and who currently pays. That one table is the backbone of your pass-through records and the first thing your CA will ask for.

SpendixAI can import statement files, flag possible duplicate imports and keep receipts attached to each transaction, and it can give a CSV for your CA. It does not manage invoices or client billing, so your invoice series and pass-through sheet stay separate.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports