A SaaS founder's CA needs three trails: customer money in, product and team costs out, and money moving between you and the business. Keep them in a folder per April to March year, and keep the gateway statements alongside the bank statements. The CA decides what is claimable and how to treat the business, and rules and limits change, so confirm the current position with your CA.
What should be in the folder?
- Payment-gateway settlement reports, each matched to a bank credit.
- Customer invoices or receipts, if you issue them, in a numbered series.
- Hosting, database, email and monitoring bills.
- Contractor agreements and invoices, with payment proofs.
- Records of refunds, chargebacks and failed payments.
- A ledger of founder draws, personal-card payments and repayments.
How do you reconcile gateway money to the bank?
The gateway report shows gross collected, fees and the settled amount. The bank shows only the settled amount, often grouped across days. Write the matching on the report: the date, the credit and the difference. If a settlement is held back or reversed, note why. Ask your CA how gateway fees and customer refunds should appear; the treatment can depend on how you are registered.
How do you log founder money in and out?
Keep one sheet with the date, direction and reason: draw, personal card paid for the product, money you put in, repayment. If you put in your own money, say whether it was a loan or capital, because the CA will ask. Do not leave this to memory; two years on, it is impossible to reconstruct.
| Trail | Evidence |
|---|---|
| Customer income | Gateway reports, invoices, bank credits |
| Product costs | Vendor bills, card statements |
| Team costs | Contracts, invoices, payment proofs |
| Founder money | Ledger of draws, loans and repayments |
| Refunds | Gateway record and customer message |
Which mistakes are common for founders?
- Paying product bills from a personal card and not noting that the company owes you
- Counting gateway fees as nothing because the settled amount looks right
- Letting contractors work without an agreement or written scope
- Mixing a second project's costs with the first product's
- Forgetting to record annual plans paid in advance, so one month looks wildly different
How should you treat refunds and chargebacks?
A refund reduces what you kept; a chargeback may also add a fee. Record each with the date, customer reference, reason and any fee. Keep the gateway's notice. If a pattern shows up, such as many refunds right after a particular release, that is a product signal as well as an accounting item. Your CA will want to know how refunds are shown against the original sale.
What should the cover note include?
State how the business is set up, the accounts and cards used, the date you started charging customers, any customer on a custom deal, any refund above a normal level, and any contractor who is also a friend or relative. Tell the CA if a payment was made on the company's behalf and not yet repaid. Honest context saves rework.
Where does a tool fit?
A useful first step is to write the founder ledger from the day you started: money in, draws, personal payments for the product and repayments. Rebuild it now from statements while memory and files still agree.
SpendixAI can import bank and card statements, flag possible duplicate imports, keep receipts and produce a CSV, plus templates for Tally, Zoho Books and QuickBooks. It is a personal workspace, not a multi-user accounting system, and its GST view is an estimate for your CA to confirm.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

