Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Customer Payments lists all accounts-receivable customer payments for the organization with status filters and summary metric cards. Route: /fa/customer-payments

​
Overview

The route /fa/customer-payments redirects to /fa/receivables?tab=payments in the router. The CustomerPaymentsPage component fetches payments via useCustomerPayments(organizationId, statusFilter). Status filter options: all, unapplied, partially_applied, fully_applied. Summary cards show: total received (payment_amount sum), total unapplied (unapplied_amount sum), and received today. The New Payment button navigates to /fa/customer-payments/new. The apply-payment dialog (PaymentApplicationDialog) can be opened per row.

​
Who it’s for

No explicit permission gate on this route.

​
Before you start

  • Customers and invoices must exist before payments can be recorded.

​
Steps

1

Navigate to Customer Payments

Go to /fa/customer-payments or the Payments tab in the Receivables hub.
2

Review summary cards

Check total received, unapplied balance, and today’s received amounts.
3

Filter by status

Select a status filter to narrow to unapplied, partially applied, or fully applied payments.
4

Apply a payment to an invoice

Use the apply action on a payment row to open PaymentApplicationDialog.
5

Open a payment detail

Click a payment row to navigate to /fa/customer-payments/:id.
6

Record a new payment

Click New Payment to navigate to /fa/customer-payments/new.

​
Key concepts

  • useCustomerPayments — Primary list hook; accepts organizationId and optional { status } filter.
  • unapplied_amount — Payment amount not yet applied to invoices.
  • PaymentApplicationDialog — Inline dialog for applying a payment to invoices.
  • useDeleteCustomerPayment — Mutation hook for deleting a payment with confirmation.

Finance & Revenue

Finance & Revenue core overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/fa.tsx
  • src/cores/fa/pages/CustomerPaymentsPage.tsx
  • src/cores/fa/hooks/useCustomerPayments.ts
  • src/cores/fa/components/CustomerPaymentsTable.tsx
  • src/cores/fa/components/PaymentApplicationDialog.tsx