Business

Records a DevOps contractor should keep for the CA

Records a DevOps contractor should keep for the CA: contracts, invoices, client cloud pass-throughs, certification bills and statements through the year.

Editorial illustration for Records a DevOps contractor should keep for the CA

A DevOps contractor should keep records of every contract and invoice, the money received against each, the cloud and tool bills that are truly yours, and a separate trail for client bills you paid first. The CA decides what is claimable and how pass-through items appear, and rules and limits change, so confirm the current position with your CA.

What should the yearly folder hold?

  1. Contracts or statements of work with rates, hours and notice terms.
  2. Invoices, numbered in sequence, each naming the period or hours it covers.
  3. Hour logs or on-call logs that match what you billed.
  4. Bank statements showing each payment received, in full months.
  5. Bills for your own cloud lab, tools and certifications.
  6. A pass-through sheet for client bills paid from your own account.

How do you handle tax deducted by clients?

Some clients deduct tax before paying and give you a certificate for it. Keep every certificate with the invoice it relates to, and note the amount actually credited to your bank. If a certificate is late or missing, ask the client early. Your CA will want to reconcile the two, and gaps are easier to chase while the project is fresh.

Why is on-call work worth logging?

On-call pay, night incidents and weekend deployments often differ from standard hours. A short log, with date, start, end and a line on what was done, supports the invoice. If a client disputes an hour or a retainer's scope, the log is your answer. It also gives you real data on how much unplanned work a retainer carries.

ItemKeep with it
Hourly invoiceHour log and contract rate
Retainer invoiceScope note and any incident log
Client cloud billVendor invoice, your payment, repayment date
CertificationExam receipt and renewal date
Tax certificateMatching invoice and bank credit

Which mistakes are typical in DevOps contracting?

  • Paying a client's cloud account from your card and recording it as your own cost
  • Leaving a client's tooling subscription on your card long after the contract ended
  • Forgetting that an incident-night invoice was never raised
  • Mixing your lab account with a client's sandbox on the same billing profile
  • Not noting the date a contract changed rate, so older invoices look wrong

What about gaps between contracts?

If you were between engagements for a month or two, say so in the cover note, and list any costs you still carried, such as certifications or lab accounts. A quiet month with expenses can look like a missing file unless it is explained. Also note any contract that overlapped another, so the CA can see why two sets of invoices cover the same weeks.

How do you prepare the cover note?

Name the clients you worked for and the dates, any rate change, which cloud accounts are yours, which belong to clients, and any bill still waiting to be repaid. Mention unusual purchases such as a laptop, and any month you were on a salary or between contracts. Ask your CA for the format they prefer for cost lists.

Where can software help?

To begin, take each client and write three lines: contract rate, invoices raised this year and any bill of theirs you paid. Gaps in those three lines are exactly where your CA will ask questions.

SpendixAI can import statements, flag possible duplicate imports and keep receipts attached to each transaction. Its Export centre has Tally, Zoho Books and QuickBooks templates plus a standard all-transactions file. It does not file returns, so the CA still makes the call on treatment.

SPENDIXAI JOURNAL

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

Explore your reports