Vendors ACH Entry (NACHA compliance)

Problem Statement

To automate vendor payouts via ACH, the system needs a secure, standardized place to store and validate banking information. Today, there is no canonical source of truth for vendor payout details, making bulk payment exports unreliable and manual.

User Story

As a finance user,

I want to store and manage ACH payout details on a vendor,

so the system can automatically generate payment batches and ACH exports.

Scope / Behavior

Vendor Payout Details

Extend Vendor records to support ACH payout configuration.

Stored fields (example for ACH):

Account holder name
Bank name
Routing / transit number
Account number (securely stored / tokenized)
Account type (Checking / Savings)
Currency
Country
Payout method status (Enabled / Disabled / Invalid)
Vendor internal identifier (Used as NACHA Individual Identification Number/ System-generated (no manual input))
Transaction type: Credit only (vendor payouts)

The system must store the following authorization metadata per vendor:

- Authorization status (Authorized / Revoked / Pending)

- Set explicitly by authorized admin users

- Authorization timestamp

- System-generated when status becomes Authorized

- Authorization method

- Selected by admin from a predefined list (e.g. Written, Electronic)

The ACH entry form should live on the Vendor create/edit page, under Personal Settings → Financial Settings.

"ACH Ready / Not Ready" indicator should be surfaced in vendor list/ vendor profile.

Exact field set may vary by region (US, CA), but must support ACH-NACHA exports.
To support NACHA exports, Pelcro must store vendor bank details plus ACH authorization metadata and vendor identification,

Definition of Done (DoD)

✔ Vendor records support storing ACH payout details
✔ Sensitive banking data is securely stored and masked
✔ System can determine if a vendor is ACH-payable
✔ Vendors without valid ACH info are excluded from payment batches
✔ ACH details are referenced (not duplicated) in payment batches and exports