Skip to main content

Billing

What it does​

Billing tracks invoices, payments, insurance claims, and subscriptions for patients and services at your facility. Patient-specific billing is also linked from the patient record.

Where to find it​

  • Billing home — /billing
  • Invoices — /billing/invoices
  • Payments — /billing/payments
  • Insurance claims — /billing/insurance-claims
  • Subscriptions — /billing/subscriptions
  • On a patient — /patients/[patientId]/billing

📸 Screenshot: invoices list (billing-invoices).

Billing invoices

Common tasks​

Find an invoice​

  1. Open Billing → Invoices.
  2. Search or page through invoices for the active facility/tenant context.
  3. Open an invoice to see lines, status, and linked payments.

Record a payment​

  1. Open Billing → Payments (or open an invoice and record payment from there when offered).
  2. Enter amount, method, and reference fields your site requires.
  3. Save. Successful payments move the invoice toward partially paid / paid according to totals. Failed gateway attempts are stored as failed payments rather than silent errors.

Work an insurance claim​

  1. Open Billing → Insurance claims.
  2. Create or open a claim linked to the encounter/invoice context your process uses.
  3. Track status through submission / response fields exposed in the UI.

Manage subscriptions​

  1. Open Billing → Subscriptions.
  2. Create or update a patient/service subscription (period, amount, status).
  3. Cancelled or terminal subscriptions cannot be edited further.

Open billing from a patient​

From Patients → [patient] → Billing, review invoices and related rows for that person only.

Tips & limitations​

  • Billing screens require billing permissions and an active facility session.
  • Some list views historically used demo mocks; against a live backend, empty lists mean no data yet, not a broken menu. If create/save fails with network/API errors, confirm OpenAPI alignment (FE-103) with your administrator.
  • Provider payouts / commissions APIs exist on the platform; dedicated cashier UI may be limited until those screens are fully wired.
  • Card data is never stored in the app — payment flows use references / gateway responses only.