/fa/bills redirects to the Payables hub at /fa/payables?tab=bills and is not a standalone screen.
Overview
This path is a legacy redirect. The route/fa/bills is registered in fa.tsx as <Navigate to="/fa/payables?tab=bills" replace />. Navigating to this URL will immediately redirect the browser to the Payables Hub with the bills tab active. Individual bill create and detail routes remain available at /fa/bills/new and /fa/bills/:id.
Who it’s for
Access follows your organization’s role and module configuration. The Payables Hub has no top-levelRequirePermission wrapper.
Viewing a bill
Selecting a bill opens its detail view at/fa/bills/:id. The header shows the bill status badge (draft, pending_approval, approved, paid, cancelled) and an edit button navigating to the edit route. A BillApprovalActions component provides approval/rejection controls. A GLPostingIndicator shows the GL posting state for the bill. Bill line items are displayed in a data table with columns for line number, PO line reference, account, fund, department, description, quantity billed, unit price, and amount. The breadcrumb is set to the bill’s identifying fields.
Before you start:
- The bill must already exist (created at
/fa/bills/new). - An organization must be selected.
statusvalues:draft,pending_approval,approved,paid,cancelledBillApprovalActions— approval/rejection controls componentGLPostingIndicator— shows GL posting statebalance_due— remaining unpaid amount on the bill
- Open the Payables Hub at
/fa/payables?tab=billsand click a bill, or navigate to/fa/bills/:iddirectly. - Review the bill header: status badge and edit button.
- Use
BillApprovalActionsto approve or reject the bill if inpending_approvalstatus. - Check the
GLPostingIndicatorto see whether the bill has been posted to the general ledger. - Review line items: account, fund, department, and amount details per line.
Creating a bill
The New Bill page (/fa/bills/new) creates a vendor bill in the accounts payable module. The page renders BillForm with data loaded for vendors (active only), accounts (active, ordered by account_number), funds (active, ordered by fund_number), departments (type cost_center or both, active), and programs (active).
On submit, useCreateBill is called with bill header fields (including organization_id and created_by) and an array of BillLine items. On success, navigates to /fa/bills/:id.
Before you start:
- At least one active vendor must exist.
- GL accounts should be configured.
- Optionally: funds, departments, and programs for line-item coding.
- Navigate to
/fa/bills/new. - Complete the Bill Details card using
BillForm: vendor, bill date, due date, bill number (or reference), notes. - Add line items with description, account, quantity, amount, and optional fund/department/program coding.
- Submit. On success, you are redirected to the new bill’s detail page.
Related
Finance & Revenue
Finance & Revenue core overview.
Governance & parity
Documentation coverage and governance.
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.
Documentation sources
Documentation sources
- src/routes/fa.tsx
- src/cores/fa/pages/BillDetailPage.tsx
- src/cores/fa/pages/BillCreatePage.tsx
- src/cores/fa/hooks/useVendorBills.ts
- src/cores/fa/hooks/useBillLines.ts
- src/cores/fa/hooks/useVendors.ts
- src/cores/fa/components/BillForm.tsx
- src/cores/fa/components/BillLineEditor.tsx