Skip to main content
The route /fa/payments is a legacy redirect to /fa/payables?tab=payments. The Payments list (payment batches) is now part of the Payables & Expenses hub.

Overview

Navigating to /fa/payments triggers a <Navigate to="/fa/payables?tab=payments" replace />. The Payments tab loads PaymentBatchesPage lazily within the Payables & Expenses hub, showing the list of payment batches with their status and totals.

Who it’s for

Access follows your organization’s role and module configuration.

Before you start

No setup required. To create a payment batch, identify the bills to pay and confirm the payment date and method.

Steps

  1. Navigate to Finance & Revenue → Payables & Expenses → Payments, or go to /fa/payables?tab=payments.
  2. Review the list of payment batches.
  3. Select a batch to view its details at /fa/payments/:id.
  4. Use New Payment Batch (at /fa/payments/new) to create a new batch.

Viewing a payment

The Payment Details page at /fa/payments/:id shows the details of a payment batch including its status, individual payments within the batch, and a posting action. /fa/payments/:id — Payment Batch Detail: Loads PaymentBatchDetailPage. Displays batch status (draft, posted, or cancelled), batch-level fields, and a table of individual payments with columns: Payment #, Vendor, Check #, and Amount. A Post Batch action is available when status is draft, guarded by a confirmation dialog. Uses usePaymentBatch and usePayments hooks. /fa/expenses/payments/:id — Reimbursement Payment Detail: Loads ReimbursementPaymentDetailPage (requires permission fa.expenses.process). Documents expense reimbursement payments rather than vendor payments. Batch status lifecycledraftposted (or cancelled). Posting is finalized via usePostPaymentBatch. batch_number — The human-readable identifier for the payment batch.
  1. Navigate to Finance & Revenue → Payables & Expenses → Payments and select a batch, or go to /fa/payments/:id.
  2. Review the batch header (batch number, status, payment date, method).
  3. Review the individual payments table.
  4. If the batch is in draft status, select Post Batch and confirm to post it.

Creating a payment

The New Payment page at /fa/payments/new renders a form for creating a payment batch against selected vendor bills, grouping payments by vendor and applying each payment to its corresponding bill. The route /fa/payments/new loads PaymentBatchCreatePage. The form collects batch-level settings (payment date, payment method, notes) and a bill selector. On submit, the page creates a batch record, groups selected bills by vendor, creates one payment per vendor, and applies each payment to the relevant bills. On success, the user is redirected to /fa/payments/:id (batch detail). Before you start:
  • Identify the bills you need to pay. Bills must exist in the system and have a non-zero balance_due.
  • Confirm the payment date and preferred payment method.
Key concepts:
  • Payment batch — A grouping of one or more vendor payments created in a single transaction. Each vendor in the batch gets its own fa_payments record.
  • Payment application — Each selected bill has an application record created linking the payment to the bill for the full balance_due amount.
  1. Navigate to Finance & Revenue → Payables & Expenses → Payments and select New Payment Batch, or go to /fa/payments/new.
  2. Set the Payment Date and Payment Method (Check, ACH, Wire, or Credit Card).
  3. Optionally add notes.
  4. Use the Bill Selector to choose one or more bills to include.
  5. Review the selected bill count and total amount displayed below the form.
  6. Select Create Batch. The platform creates a batch, one payment per vendor, and applies each payment to the selected bills.
  7. You are redirected to the payment batch detail page.

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/PaymentBatchesPage.tsx
  • src/cores/fa/pages/PayablesHubPage.tsx
  • src/cores/fa/pages/PaymentBatchDetailPage.tsx
  • src/cores/fa/pages/PaymentBatchCreatePage.tsx
  • src/cores/fa/hooks/usePaymentBatches.ts
  • src/cores/fa/hooks/usePayments.ts
  • src/cores/fa/hooks/usePaymentApplications.ts