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.

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.

​
Overview

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).

​
Who it’s for

No explicit permission gate on this route.

​
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.

​
Steps

  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.

​
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.

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