> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lead.bank/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Definitions for Lead-specific terms — Entity, Account, FBO, RFI, TAM, and more — plus common banking and payments terms used throughout this documentation.

[A](/core-concepts/platform/glossary#a) • [B](/core-concepts/platform/glossary#b) • [C](/core-concepts/platform/glossary#c) • [E](/core-concepts/platform/glossary#e) • [F](/core-concepts/platform/glossary#f) • [I](/core-concepts/platform/glossary#i) • [K](/core-concepts/platform/glossary#k) • [N](/core-concepts/platform/glossary#n) • [O](/core-concepts/platform/glossary#o) • [P](/core-concepts/platform/glossary#p) • [R](/core-concepts/platform/glossary#r) • [S](/core-concepts/platform/glossary#s) • [T](/core-concepts/platform/glossary#t) • [W](/core-concepts/platform/glossary#w)

## A

**Account**: A Lead object that represents a deposit or credit product for a customer. Every Account belongs to an Entity and is the parent of one or more Account Numbers and Balances. Identified by the account\_ prefix. See [Object Model](/core-concepts/platform/object-model).

**Account Holder**: An Entity role that grants full control and legal responsibility for an Account. Required before an Account Number can be created or activated for a customer. See [Entity Roles](/api-integrations/entity/roles).

**Account Number**: A Lead object that represents a routing and account number pair assigned to a customer. Used to send and receive payments on external rails. Identified by the acct\_num\_ prefix. See [Object Model](/core-concepts/platform/object-model).

**ACH (Automated Clearing House)**: A batch-payment network operated by Nacha. Lead supports all three same-day windows and all six next-day windows. See [Money Movement](/core-concepts/platform/money-movement).

**Authorized Signer**: An Entity role for an individual authorized to sign on behalf of an Account Holder, typically a control person or beneficial owner of a business. No legal responsibility for the account. See [Entity Roles](/api-integrations/entity/roles).

**Authorized User**: An Entity role for an individual with restricted access to an account, such as a cardholder on a business account. The lightest data requirements of the three roles. See [Entity Roles](/api-integrations/entity/roles).

## B

**Balance**: A Lead object that tracks the financial position of an Account. Types include current, available, and subledger. See [Object Model](/core-concepts/platform/object-model).

**Beneficial Owner**: An individual who owns or controls 25% or more of a business entity. Lead requires beneficial owner data for business Account Holders as part of KYC. Data requirements match those of the Authorized Signer role.

## C

**Charge-Off**: The accounting treatment for a loan or balance written off as a loss due to non-payment or fraud. In Lead's reporting, a charged-off balance is reflected in `charge_off_balance` on the Balances file. The associated Account typically moves to status: `closed` with `status_reason: charged_off`. See [Balances Schema](/file-integrations/balances-and-transactions/balances-schema).

**CTR (Currency Transaction Report)**: A regulatory filing required for cash transactions exceeding \$10,000 in a single day. Filed by Lead on behalf of the program.

## E

**Entity**: A Lead object that represents a person or business in your program. The root object in Lead's hierarchy — every Account, Account Number, and transaction traces back to an Entity. Identified by the `entity_ prefix`. See [Object Model](/core-concepts/platform/object-model).

## F

**FBO (For Benefit Of)**: A bank account structure where Lead holds funds on behalf of your customers. Your program has a single FBO account; individual customer balances are tracked as sub-balances within it. Lead provides your `account_id` during onboarding.

**FedNow**: The Federal Reserve's instant payment network. Lead currently supports FedNow for sending and receiving instant payments. See [Money Movement](/core-concepts/platform/money-movement).

**FedWire**: The Federal Reserve's wire transfer network. Used for domestic wire transfers. Lead has a direct connection to FedWire. See [Money Movement](/core-concepts/platform/money-movement).

## I

**IAT (International ACH Transaction)**: An ACH SEC code used for cross-border entries. Requires additional originator and receiver details via the `iat_details` field. See [ACH](/api-integrations/ach/overview).

**IM (Implementation Manager)**: Your primary Lead contact from kickoff through go-live. Owns timelines, milestones, and cross-functional coordination. See [Programs and Partners](/core-concepts/platform/programs-and-partners).

**Internal Transfer**: A Lead rail for moving funds instantly between accounts held at Lead. Does not touch any external network. Identified by the `xfer_ prefix`. See [Money Movement](/core-concepts/platform/money-movement).

## K

**KYC (Know Your Customer)**: The process of verifying a customer's identity. Lead performs KYC decisioning based on entity data you submit. Required for the Account Holder and Authorized Signer roles.

## N

**Nacha**: The organization that governs the ACH network and sets operating rules for ACH participants, including SEC codes, return windows, and same-day limits.

**NAICS Code**: A 6-digit North American Industry Classification System code used to identify a business entity's industry. Required when creating a business or sole proprietorship Entity. Lead validates that the value is a full 6-digit code — 2-digit sector codes are not accepted. See [Entity](/api-integrations/entity/overview).

## O

**ODFI (Originating Depository Financial Institution)**: The bank that initiates an ACH entry on behalf of the originator. Lead acts as the ODFI for outgoing ACH entries your program originates.

**OFAC (Office of Foreign Assets Control)**: A U.S. Treasury division that administers sanctions programs. Lead screens entities and transactions against OFAC lists automatically.

**Originator**: A Lead object that represents an ACH Company ID used to identify your program on the ACH network. A single program can have multiple Originators. See [Originators](/api-integrations/originators/overview).

## P

**Partner**: Your company — the fintech that has signed an agreement with Lead and is integrating against Lead's platform. See [Programs and Partners](/core-concepts/platform/programs-and-partners).

**Partner Site**: The Lead portal at [partners.lead.bank](http://partners.lead.bank) where operational and compliance resources live, including SLAs, the risk management framework, program policies, and data requirements. Access is provisioned by your IM during kickoff.

**Program**: A specific product you offer to your end customers under your Lead relationship. Each program has its own credentials, rails configuration, and reconciliation files. See Programs and Partners.

## R

**RDFI (Receiving Depository Financial Institution)**: The bank that receives an ACH entry on behalf of the receiver. When your customers receive an incoming ACH, Lead acts as the RDFI.

**RFI (Request for Information)**: A compliance request Lead issues when additional information is needed about a customer or transaction. Delivered via Slack to your program's compliance contact.

**RTP (Real-Time Payments)**: The Clearing House's instant payment network. Support for RTP is coming soon to Lead. See [Money Movement](/core-concepts/platform/money-movement).

## S

**SAR (Suspicious Activity Report)**: A regulatory filing required when a financial institution detects potentially illegal activity. Filed by Lead on behalf of the program.

**SEC Code**: A three-letter Nacha code that classifies an ACH entry by type and authorization method. Examples include PPD (consumer credits/debits), CCD (business credits/debits), WEB (internet-initiated), and IAT (international).

**Subledger Balance**: A Lead Balance type used for lending products to track principal, interest, fees, and repayment schedules at the loan level. See [Object Model](/core-concepts/platform/object-model).

**SWIFT**: The messaging network used for international wire transfers. Lead uses SWIFT for outgoing USD international wires. See Money Movement.

## T

**TAM (Technical Account Manager)**: Your technical Lead contact for sandbox configuration, credential provisioning, SFTP setup, and integration support. Post-launch primary contact. See [Programs and Partners](/core-concepts/platform/programs-and-partners).

**Transaction**: A Lead object that represents a posted or non-posted financial event on an Account. Identified by the `txn_ prefix`. See [Object Model](/core-concepts/platform/object-model).

## W

**Webhook**: An HTTP callback Lead sends to your endpoint when an event occurs, such as a payment status change or an RFI. Used to build real-time, event-driven integrations. See [Webhooks](/api-integrations/webhooks).