How to keep track of client payments in one place
Recording a payment is quick. Answering who owes you what means opening three tools. Here is how to keep client payments and client history in one record.
Syncek Team · CRM reference library
/ 6 min read / Art. #95
Recording a payment takes five seconds. The hard part arrives later, when someone asks who owes you money right now, and you open the invoicing tool, then the bank feed, then the sheet where you noted that one client asked for an extra two weeks.
Nothing in that setup is broken. The invoice exists. The payment landed. The note is exactly where you left it. The answer is spread across three places, and you are the only thing connecting them.
What the question is really asking
"Keep track of client payments" sounds like bookkeeping. It is not. Your accountant already holds the numbers, reconciled and filed, and they are not the person you are trying to answer.
The question you actually need to answer is about the client:
- Which clients owe you something today.
- How long it has been outstanding.
- Whether you already chased, and what they said.
- Whether this client is late every time, or late once.
The last two are the ones an invoicing tool holds only in part, and only if somebody types them in. Xero, for one, tracks how long each customer takes to pay and keeps notes on the contact. Stripe knows an invoice is unpaid. It does not know the client emailed you in March asking to move to 45 days, and that you agreed.
Where the answer gets split
Most setups scatter one question across three systems, and each one is doing its job correctly.
The invoicing tool (QuickBooks, Xero, FreshBooks, Stripe) knows amounts, dates, and paid or unpaid. It does not know what was agreed outside it, like the extension granted by email.
The bank feed knows money moved. It often does not know which invoice the money was for, especially when a client pays two at once or rounds the transfer.
Your inbox holds the part that matters most and is hardest to query. Agreed extensions, disputed line items, the "we pay on the 15th" that was never written into the contract. This is the only place the terms live, and you cannot sort it.
Put the payment on the client record
The repair is not another tool. It is deciding that the payment and the client are one record rather than two.
In practice that means every client row carries its own payment history, so opening the client answers the question without a second tab. You see the three invoices, which one is 20 days out, the note from March about 45 days, and the fact that you chased on the 2nd.
If you keep track of clients in one tool and payments in another, every question makes you join them by hand.
This is why a spreadsheet gets you further than people expect. A sheet with one row per client and a linked tab of payments answers the question fine at 30 clients. It stops answering when you need the same view sorted by days outstanding, filtered to unpaid, and current for two people at once. Those are the same two triggers that decide when the client list itself outgrows the sheet.
What to track per payment
A client payment tracker needs six fields. Adding more usually means nobody fills any of them:
| Field | Why it earns its place |
|---|---|
| Amount | The figure you are chasing |
| Invoice date | Starts the clock |
| Due date | The agreed date, not the default one |
| Status | Draft, sent, paid, disputed |
| Paid date | Gives you the real payment behaviour per client |
| What it was for | Ties the money to the work |
Paid date is the field people skip and the one that pays off. Due date tells you whether a client is late today. Paid date, kept over a year, tells you which clients are always late, which is the thing you actually act on at renewal.
When a payment is officially late
Worth knowing before you chase an invoice, because "late" has a legal definition in the EU rather than a felt one.
Directive 2011/7/EU caps the payment period a business-to-business contract can fix at 60 calendar days under Article 3(5). A longer period has to be expressly agreed in the contract, and it cannot be grossly unfair to the creditor. Where the contract fixes no date at all, Article 3(3)(b) puts it at 30 calendar days from the invoice or from delivery.
Two things follow that most people never act on. Interest starts running automatically, "without the necessity of a reminder", under Article 3(1). Article 2(6) sets the rate at the reference rate plus at least eight percentage points. In the UK the same right comes from the Late Payment of Commercial Debts (Interest) Act 1998, still in force.
So a client who pays on day 75 with nothing in writing is not slow. They are late, you are already owed interest on it, and you have standing to say so plainly. What to send, and in what order, is its own six-rung ladder.
Where a CRM fits, and where it does not
A CRM is the answer people arrive at, rarely the question they started with. The honest version: you do not need one to track payments. You need one when the client record and the payment record have to be the same record, for more than one person, at the same time.
Tools split on exactly that. Notion and Airtable let you build the linked structure yourself and expect you to maintain it. HubSpot and Pipedrive are built around the deal before the invoice. Syncek keeps the spreadsheet editing you already use and puts structured fields and the client history on the same record, which is the shape this problem has. It is in early access, so the waitlist is the way in today.
Whatever you use, the test is the same. Open one client. If you can see what they owe you, since when, and what they said last time you asked, the tracking is working.
Frequently asked questions
How do I keep track of client payments?
Record six things per payment: amount, invoice date, due date, status, paid date, and what it was for. Keep them attached to the client rather than in a separate ledger, so opening a client shows their full payment history. The point is answering who owes you what today, which needs the client and the money in one view rather than two systems you reconcile by hand.
What is the best way to keep track of clients and payments together?
Store payments as rows that belong to a client record, not as a standalone list. A spreadsheet does this with one tab per purpose and a shared client ID. A CRM does it with a linked field. Either works. What fails is keeping clients in one tool and payments in another, because every question then needs you to join them manually.
Should I track client payments in a spreadsheet?
Yes, until two things happen. A spreadsheet handles 30 clients comfortably and costs nothing. It starts to strain when more than one person edits it at once, or when you need the same data sorted several ways, by days outstanding, by client, by status, without rebuilding the view each time. Volume is rarely the trigger. Shared access and multiple views usually are.
What fields should a client payment tracker have?
Amount, invoice date, due date, status, paid date, and a short description of the work. Six is enough. Trackers with 15 fields get abandoned because filling them is slower than the task they support. Add a chased date if you follow up regularly, since knowing you already asked on the 2nd prevents the awkward second email and tells you when to escalate.
When is a client payment officially late in the EU?
Under Directive 2011/7/EU, Article 3(5), a business-to-business contract may not fix a payment period longer than 60 calendar days unless the longer term is expressly agreed and is not grossly unfair to the creditor. Where the contract fixes no date, Article 3(3)(b) makes it 30 days. Interest then runs automatically under Article 3(1), without you having to send a reminder first.
How do I know which clients are always late?
Record the paid date, not only the due date. Due date tells you who is late today. Paid date, kept across a year, gives you the gap between agreed and actual per client, and that average is what separates one bad month from a pattern. It is the number worth having in front of you at renewal, and it takes one extra field to collect.
Do I need a CRM to track client payments?
No. An invoicing tool plus a spreadsheet covers it for a single person. A CRM earns its place when the client record and the payment record have to be one record, visible to more than one person, updated at the same time. If you are the only one who ever opens the file, the spreadsheet is doing the job and replacing it buys you very little.