Business

Records a freelance developer should keep for the CA

A records checklist for a freelance developer: invoices, foreign receipts, hardware, subscriptions and how to hand it all to your CA.

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

A freelance developer should keep a numbered invoice for every client payment, the bank's record of each foreign credit, bills for tools and hosting, invoices for hardware, and a note of shared items. Hand them to the CA monthly. The records that cause most trouble are foreign receipts that credit less than the invoice, and dollar subscriptions paid on a personal card. Rules and limits change, so your CA decides what is claimable.

What do I keep for the money coming in?

  • A numbered invoice for each client payment, in the currency you billed.
  • The bank credit for each payment, with the amount actually received.
  • The bank's inward remittance advice for foreign credits, where your bank provides one.
  • The payment platform's statement, if a platform sits between you and the client.
  • The contract or work order, so milestones can be tied to invoices.
InvoiceBilledCreditedGap to explain
First milestone$500₹41,200Rate and charges at conversion
Monthly retainer₹60,000₹60,000None
Bug-fix hours₹12,000₹0 so farPending, unpaid

The gap column is the part your CA will ask about. Fill it in at the time, not a year later.

Which bills belong in the folder?

  • Hosting, cloud and API bills, with the project each belongs to.
  • Tool subscriptions, including those that bill in dollars.
  • Hardware invoices with serial numbers and warranty details.
  • Co-working or rent receipts.
  • Internet and power backup bills with your business share noted.
  • Subcontractor invoices for anyone you hired.

How should I treat costs I pay for a client?

You may pay a domain, a plug-in licence or a hosting plan on the client's behalf and bill it back. Keep the bill, note the client and project, and put the invoice number it was billed on beside it. Say you pay ₹3,000 for a client's yearly hosting and bill ₹3,000 on your next invoice. That should read as pass-through, not as your own ₹3,000 cost. Ask your CA how to show it.

A short written note for each large payment saves long email threads. Write the client, the project, the invoice number, the amount billed, the amount credited and the date. Two lines per payment is enough, and the list becomes the first thing your CA reads. If a payment is split across two credits, note both. If a client deducts something before paying, say what and why.

Keep a second copy of everything in a place separate from your laptop. A developer's laptop is both the main tool and the main record store, and a failed disk can take both away at once.

How do I hand it over?

  1. Bank and card statements for the month, in PDF or CSV.
  2. The invoice register with received or pending status.
  3. Foreign credit advice for any dollar payment.
  4. A folder of bills for tools, hosting and hardware.
  5. A note on what is billable to clients.
  6. A list of questions.

Which mistakes are specific to developers?

  • Recording a foreign payment at the amount credited without the invoice amount beside it.
  • Not keeping the invoice for a laptop bought in one month and used for years.
  • Leaving a client's hosting bills inside your own running costs.
  • Missing a renewal because the bill went to an old email address.
  • Not recording a subcontractor's payment because it was a quick UPI transfer.

When a sheet stops being enough

If statements and bills are growing, SpendixAI can import statements, hold receipts with transactions, and keep each expense in its own currency. Its Export centre has a standard all-transactions file for your CA. It does not raise invoices, so your invoice register stays in your sheet.

SPENDIXAI JOURNAL

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

Explore your reports