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

# Finance & Revenue Vendors

> Manage, view, and edit vendor records from the Accounts Payable hub with payment terms, deactivation, and inline create/edit dialog.

The Vendors route (`/fa/vendors`) redirects to the Payables Hub (`/fa/payables?tab=vendors`). The vendors list is managed from within that hub.

## Overview

Navigating to `/fa/vendors` redirects to `/fa/payables?tab=vendors` via a `<Navigate>` redirect in `src/routes/fa.tsx`.

The `VendorsPage` component is rendered within the Payables Hub tab. It provides a full vendor list with search, create (`VendorDialog`), edit, and delete capabilities. Keyboard shortcuts are registered via `useFAKeyboardShortcuts`.

Vendor records are backed by `fa_vendors` via hooks `useVendorList`, `useCreateVendor`, `useUpdateVendor`, `useDeleteVendor`, and `useGenerateVendorNumber`.

Individual vendor detail is accessible at `/fa/vendors/:id`.

## Who it's for

Access follows your organization's role and module configuration.

## Before you start

* An organization must be selected.
* To create a new vendor, navigate to **Finance & Revenue → Payables & Expenses** and select the **Vendors** tab.

## Steps

**Access vendor management**

1. Navigate to `/fa/vendors` (auto-redirects) or `/fa/payables?tab=vendors`.
2. Browse the vendors table.

**Create a vendor**

1. Click **New Vendor** (or use the keyboard shortcut).
2. Complete the `VendorDialog` and save.

**Edit a vendor**

1. Locate the vendor and click its edit action.
2. Update fields in the dialog.

**Delete a vendor**

1. Use the delete action and confirm the alert dialog.

**View vendor details**

1. Click a vendor row to navigate to `/fa/vendors/:id`.

## Key concepts

* **Vendor number**: Auto-generated via `useGenerateVendorNumber`.

## Viewing a vendor

The Vendor Details page (`/fa/vendors/:id`) shows the full profile of a single vendor and provides edit capabilities.

The page loads a vendor via `useVendor` (keyed by `:id` and organization) and sets the breadcrumb label from the vendor name via `useEntityBreadcrumb`. The layout is a two-column card grid showing general information and payment/contact details.

Edit actions open a `VendorDialog` (using `useUpdateVendor`). Payment terms are reverse-mapped from numeric day values to human-readable labels: `0` → "Due on Receipt", `15` → "Net 15", `30` → "Net 30", `60` → "Net 60", `90` → "Net 90".

A deactivation action is also present (observed via `UserX` icon).

Key concepts:

* **Payment terms**: Stored as integer days in `fa_vendors`; displayed as human-readable labels.
* **Vendor status**: The `badge` display on the detail page reflects the vendor's current active/inactive state.

**View vendor details:**

1. Navigate to `/fa/vendors/:id` (or click a vendor from the Payables Hub).
2. Review the general information and payment details cards.

**Edit vendor information:**

1. Click the **Edit** button.
2. Update fields in `VendorDialog`.
3. Save.

**Deactivate a vendor:**

1. Use the deactivation action.

## Creating a vendor

The route `/fa/vendors` is a legacy redirect to `/fa/payables?tab=vendors`. There is no dedicated `/fa/vendors/new` route in the current routing configuration. Vendor creation is accessed from within the Payables Hub Vendors tab.

1. Navigate to `/fa/payables?tab=vendors` or go to **Finance & Revenue → Payables & Expenses → Vendors**.
2. Use the vendor creation action available in that view.

## Related

<Columns cols={2}>
  <Card title="Finance & Revenue" icon="building-columns" href="/fa/overview">
    Finance & Revenue core overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  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.
</Note>

<Accordion title="Documentation sources">
  * src/routes/fa.tsx
  * src/cores/fa/pages/VendorsPage.tsx
  * src/cores/fa/pages/VendorDetailPage.tsx
  * src/cores/fa/pages/PayablesHubPage.tsx
  * src/cores/fa/hooks/useVendors.ts
  * src/cores/fa/components/VendorsTable.tsx
  * src/cores/fa/components/VendorDialog.tsx
</Accordion>