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.

Customers lists and manages accounts-receivable customer records with search, customer-type, and active/inactive filters. Route: /fa/customers

​
Overview

The route /fa/customers redirects to /fa/receivables?tab=customers in the router. The CustomersPage component fetches customers via useCustomerList(organizationId, { search, type, isActive }). Filters: text search, CustomerType dropdown (from fa_customer_type enum), and active/inactive toggle (default: active). The New Customer button and the edit action per row open CustomerDialog. Delete calls useDeleteCustomer.

​
Who it’s for

No explicit permission gate on this route.

​
Before you start

  • The current organization must be set.
  • Customer type definitions come from the fa_customer_type database enum.

​
Steps

1

Navigate to Customers

Go to /fa/customers or the Customers tab in the Receivables hub.
2

Search and filter

Enter a search term, select a customer type, and toggle between active and inactive customers.
3

Create a customer

Click New Customer to open CustomerDialog with a blank form.
4

Edit a customer

Click the edit action on a row to open CustomerDialog pre-populated.
5

Delete a customer

Click delete on a row to call useDeleteCustomer.
6

View customer detail

Click a customer name to navigate to /fa/customers/:id.

​
Key concepts

  • useCustomerList — Primary list hook; accepts organizationId and { search, type, isActive }.
  • CustomerType — From fa_customer_type database enum.
  • useDeleteCustomer — Mutation hook for customer deletion.
  • CustomerDialog — Create/edit dialog for customer records.

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/CustomersPage.tsx
  • src/cores/fa/hooks/useCustomers.ts
  • src/cores/fa/components/CustomersTable.tsx
  • src/cores/fa/components/CustomerDialog.tsx
  • src/integrations/supabase/types.ts