What this patient has actually paid, at a glance

The Payments tab shows the payment history for this one patient — every payment received from them, which method was used, when it happened, and which invoice it was applied to — without having to search the clinic-wide payment list or open each of their invoices individually.

It's the natural companion to the Billing tab: where Billing covers settings and credit, Payments covers the concrete, dated record of money actually received from this patient. Front-desk staff reach for this tab constantly — confirming a payment cleared, answering a patient's question about what they've paid so far, or double-checking before following up on an outstanding balance.

In this article
  • What appears in each row of a patient's payment history
  • How each payment links back to the invoice it covered
  • Where to go to record a new payment or dig into payment detail
Patient record Payments tab
The Payments tab of a patient record listing individual payments with date, method, amount, and the linked invoice for each row.

Reading the payment list

Each row represents one payment made by the patient, typically showing the payment date, the method used (such as cash, card, or an online payment method), the amount, and the invoice it was recorded against. This gives you a quick, patient-specific answer to "what has this person paid, and when" without pulling up their invoices individually.

  • Payments are specific to this patient — clinic-wide payment activity lives in the main Payments list.
  • Each payment shown here is linked to the invoice it was applied to, so you can trace a payment back to what it covered.

Recording a new payment happens in the main billing tools

This tab is a read-focused history, not where a payment is actually taken. To record a new payment, or to see full detail on how payments work across the clinic — payment methods, the payment recording flow, and the payment detail view — use the main Payments tools.

Frequently asked questions

Was this article helpful?
Your feedback helps us improve our documentation.
Rate this article: