Invoice Payment History: Track Multiple Payments on One Invoice

Invoice Payment History: Track Multiple Payments on One Invoice
One invoice does not always equal one payment.
A customer may pay:
£500 today
then:
£400 next week
and finally:
£600 later
against the same £1,500 invoice.
At that point, simply knowing that the invoice is eventually Paid is not enough.
You may also need to know:
- how much each payment was
- when each payment was recorded
- how the customer paid
- what remained outstanding after each payment
- whether the invoice is still partially paid
- when the final balance was settled
That is where invoice payment history becomes useful.
Love Invoicing lets you keep recorded payments connected to the invoice they belong to instead of reducing the entire payment journey to a single Paid or Unpaid label.
And because Love Invoicing works across its web portal and mobile app, you can review invoice and payment information whether you are working at your desk or from your phone.

What Is Invoice Payment History?
Invoice payment history is the record of payments associated with a particular invoice.
Imagine an invoice for:
£1,500
The customer pays it in three transactions:
Payment
Amount
Balance Remaining
First payment
£500
£1,000
Second payment
£400
£600
Final payment
£600
£0
The final result is straightforward:
Paid in full
But the payment history tells you how you reached that position.
That distinction becomes important when:
- customers pay in several instalments
- you receive money on different dates
- payments arrive through different methods
- a customer queries what they have already paid
- you need to check why an invoice still has a balance
- you return to an invoice weeks or months later
Instead of reconstructing the story from your bank account, the payment record stays connected to the invoice.
Why a Paid Status Alone Is Not Always Enough
A simple Paid label answers one question:
Has this invoice now been settled?
It does not necessarily answer:
How was it settled?
For a £1,500 invoice, these two situations both result in a final status of Paid:
Customer A
Pays £1,500 in one transaction.
Customer B
Pays:
£500
£400
£600
Both invoices eventually reach a £0 outstanding balance.
But their payment histories are completely different.
If Customer B later asks:
“Didn't I already pay you £900?”
you need more information than a green Paid label.
You need the underlying payment trail.
Keep Every Recorded Payment Connected to the Invoice
Love Invoicing allows individual payments to remain associated with the invoice against which they were recorded.
For example:
Invoice INV-2026-0010
Invoice total:
£1,500
First recorded payment:
£500 — Cash
Second recorded payment:
£400 — Bank Transfer
The invoice payment history can therefore retain separate records rather than combining everything into one unexplained £900 figure.
That gives you a much clearer audit trail of what actually happened.

Track Payments Made on Different Dates
Customers do not always make payments on the same day.
For example:
17 August — £500
23 August — £400
30 August — £600
When each payment is recorded separately, the invoice history gives you a chronological record.
That makes it easier to answer questions such as:
When did we receive the first payment?
Was the second transfer already recorded?
Which payment reduced the invoice to £600 outstanding?
When was the invoice finally settled?
This becomes far more useful than a spreadsheet containing only:
Invoice £1,500 — Paid
Record Different Payment Methods Against the Same Invoice
The same customer may also use different ways to pay.
For example:
First payment: Cash
Second payment: Bank Transfer
Final payment: Card
Where the payment is being manually recorded in Love Invoicing, the Record Payment interface provides payment-method options including:
- Cash
- Bank Transfer
- Card
- Cheque
- Other
You can also add an optional reference and notes where useful.
This means the payment record can contain more context than simply an amount.

See the Invoice Balance Reduce as Payments Are Recorded
The history is useful, but you also need the current position to stay obvious.
Suppose the invoice starts at:
£1,500 due
After the first £600 is received:
£600 paid
£900 due
After the remaining £900 is settled:
Paid in full
Love Invoicing updates the invoice's payment position as payments are recorded.
That means you can see both:
The history
What payments have already been recorded.
The current position
What the customer still owes now.
Those are different pieces of information, and both matter.

Payment History Is Particularly Useful for Instalment Payments
Higher-value work may not always be settled with one transfer.
Consider a £3,000 invoice.
The customer might pay:
£1,000
then:
£750
then:
£500
then:
£750
Without a proper payment record, you may end up checking bank transactions and adding numbers manually just to answer:
How much is left?
With payments associated with the invoice, the calculation becomes part of the invoice workflow.
After the first payment:
£2,000 remaining
After the second:
£1,250 remaining
After the third:
£750 remaining
After the fourth:
Paid in full
This is exactly the type of situation where payment history becomes more important than a simple invoice status.
Payment History Is Different From the Invoice Status
It helps to separate these two concepts.
Invoice status
Tells you the invoice's current position.
For example:
- Sent
- Partial
- Overdue
- Paid
- Credited
Payment history
Tells you what happened to reach that position.
For example:
- £500 Cash recorded
- £400 Bank Transfer recorded
- £600 final payment recorded
The status gives you the answer quickly.
The history gives you the detail when you need it.
Love Invoicing provides both views.
See Partial Payment Progress From the Invoice List
You should not have to open the full payment history every time you want a quick answer.
From the invoice list, a partially paid invoice can show:
£600 paid · £900 due
alongside a visual payment progress bar.
That means the invoice list provides the immediate picture.
If you need more detail, you can then open the invoice and review its activity.
This is a much more practical workflow than forcing you to inspect every payment record individually.

The Customer-Facing Invoice Can Show What Has Already Been Received
The payment record is not useful only internally.
Where applicable, the invoice document can also reflect payments already received and the amount still due.
For example:
Invoice total: £1,500
Paid: £900
Amount due: £600
The payments received section can show the payments making up that £900.
This gives the invoice recipient a clearer picture of the current balance rather than presenting the original invoice value as though nothing has been paid.

The Payment Record Is Also Part of the Invoice Activity Trail
Payments do not happen in isolation.
An invoice may go through several events:
Invoice created
↓
Invoice sent
↓
First payment recorded
↓
Second payment recorded
↓
Final payment recorded
The Love Invoicing activity area can keep these events together.
That means the invoice becomes more than the document originally sent to the customer.
It becomes a timeline of what happened afterward.
For a tradesperson returning to an old job or customer, that context can be extremely useful.
See What the Customer Owes Across More Than One Invoice
Eventually you need to move beyond the individual invoice.
A customer may have four invoices:
Invoice 1
£108 — Paid
Invoice 2
£600 — £250 paid — £350 outstanding
Invoice 3
£48 — Paid
Invoice 4
£48 — Outstanding
The question becomes:
What does this customer owe us overall?
Love Invoicing's Customer area brings the wider account position together.
An individual customer can have an outstanding balance, while their Statement provides visibility of the invoices contributing to that balance.
So invoice payment history gives you the detailed transaction view.
The Customer area gives you the wider relationship view.

Customer Statements Give You the Wider Account Picture
Payment history answers:
What happened on this invoice?
A customer statement answers:
What is happening across this customer's account?
That distinction matters for repeat customers.
The statement can show several invoices with their:
- total value
- amount paid
- remaining balance
- payment status
and then provide a wider summary including the net balance due.
This is particularly valuable when a customer has a mixture of:
Paid invoices
Partially paid invoices
and
Outstanding invoices
Instead of calculating their total balance yourself, the account information stays organised around the customer.

Use the Web Portal When You Want the Full Activity View
Love Invoicing is available through both its mobile app and web portal.
The mobile app is useful when you are away from your desk and need to:
- view invoices
- record payments
- check balances
- see invoice statuses
- review customers
The web portal gives you a larger workspace when you want to inspect information such as the full invoice activity timeline or manage several records.
You do not have to choose between running your business from your phone or from your computer.
You can use whichever environment makes sense for the job you are doing.

Payment Notifications Can Keep Important Changes Visible
When a payment changes the state of an invoice, that information is important.
For example, after a £500 payment is recorded against a £1,500 invoice:
£500 has been received
and:
£1,000 remains due
Love Invoicing's mobile experience can surface payment-related notifications, helping important changes remain visible while you are away from the web portal.
That supports the wider principle behind the platform:
The invoice should remain active business information until the money has actually been received.

Keep the Payment Information Updated Across the Business
This is one of the more important parts of the Love Invoicing workflow.
A payment does not need to exist only inside a payment screen.
Once invoice information changes, the updated financial position can be visible in the places where you manage the business.
That includes the invoice itself and the wider customer account.
For example:
Invoice starts
£1,500 due
First payments recorded
£600 paid · £900 due
Final balance received
Paid in full
At the same time, the customer's wider account can continue to reflect other money that is paid, outstanding or overdue.
The objective is not just to record a payment.
It is to make the updated information useful elsewhere.

Why This Is Better Than Keeping Payment Notes Separately
A business can track payments manually.
You could write:
BMV — invoice 0011 — £600 received
in your notes app.
Then add:
Another £900 received
later.
But now the information exists separately from:
- the invoice
- the customer
- the job
- the invoice balance
- the wider customer statement
A spreadsheet creates the same problem.
Every payment means another manual update.
The payment history inside the invoicing workflow removes that unnecessary separation.
From Customer to Payment History
The payment is the final financial stage of a much larger business process.
For a tradesperson, that journey may look like:
Customer → Quote → Job → Invoice → Payment
But even the word Payment can contain several events.
So the full story may actually become:
Customer
↓
Quote
↓
Job
↓
Invoice
↓
First payment
↓
Second payment
↓
Final payment
↓
Paid in full
Love Invoicing keeps those stages connected rather than forcing you to reconstruct the story afterward.
Frequently Asked Questions
Can one invoice have multiple payments?
Yes. Multiple payments can be recorded against the same invoice as money is received.
Can I see the payment history for an invoice?
Love Invoicing's invoice activity history can show recorded payment events associated with the invoice.
Can I record payments on different dates?
Yes. Individual payment records can retain their associated dates so you can understand when payments were recorded.
Can payments use different payment methods?
Yes. When manually recording a payment, available methods include Cash, Bank Transfer, Card, Cheque and Other.
Can I record a payment reference?
Yes. Love Invoicing provides an optional reference field when recording a payment.
Can I add notes to an invoice payment?
Yes. An optional notes field is available when recording the payment.
Can I see how much remains after each payment?
A partially paid invoice can show what has already been paid alongside the remaining balance.
Does Love Invoicing show partial payment progress?
Yes. Partially paid invoice cards can include a visual payment progress bar.
Can the invoice PDF show payments already received?
Payment information and the remaining amount due can be reflected on the invoice document where applicable.
Can I see the customer's overall outstanding balance?
Yes. The Love Invoicing Customer area provides wider account information, including the customer's outstanding balance.
Does Love Invoicing provide customer statements?
Yes. Customer statements provide a view of invoices, amounts paid, individual balances and the wider net balance due.
Can I use Love Invoicing on web and mobile?
Yes. Love Invoicing includes both a web portal and mobile app, allowing invoice and customer information to be managed across different working environments.
What is the difference between payment history and invoice status?
Invoice status shows the invoice's current position, such as Partial or Paid. Payment history shows the individual payment events that contributed to that position.
Don't Just Know That an Invoice Was Paid — Know How It Was Paid
Eventually, many invoices end in the same place:
Paid in full.
But the journey matters.
A £1,500 invoice may have been settled with one payment.
Or three.
When you can see each recorded payment, the payment method, the dates and the remaining balance, you have a much clearer record of what happened.
And when that information connects back to the customer, you can move from:
What happened to this invoice?
to:
What does this customer currently owe us?
without rebuilding the answer from bank transactions and spreadsheets.
Love Invoicing brings the workflow together across web and mobile:
Customer → Quote → Job → Invoice → Payment
Run the job. Send the invoice. Get paid.
Explore Love Invoicing