# Accounting integrations
Source: https://getlemma.com/docs/accounting-integrations

Connect Lemma directly to your accounting software.

Lemma integrates directly with your practice's accounting software. The integration reads and writes financial data — transactions, invoices, and bills — without any manual export or import steps.

If you prefer to move data manually, the [Export transactions](/docs/guides/export-transactions) guide covers CSV and QuickBooks `.qbo` file exports.

## Supported platforms

Lemma integrates with the following accounting platforms:

* Acumatica
* Exact Online
* Fortnox
* FreeAgent
* FreshBooks
* Fulfil
* Holded
* Kashflow
* Lexware
* Microsoft Dynamics 365 Business Central
* Microsoft Dynamics 365 Finance & Operations
* Microsoft Great Plains
* Moneybird
* MYOB
* NetSuite
* Odoo
* Oracle Fusion ERP Cloud
* Pennylane
* QuickBooks Desktop
* QuickBooks Online
* Sage Business Cloud Accounting
* Sage Intacct
* SAP Ariba
* SAP Business One
* SAP S/4HANA
* Visma
* Wave
* Xero
* Zoho Books

## Get connected

Connect your accounting software from the [integrations page](https://app.getlemma.com/_/settings/integrations). If you don't see your platform listed, contact Lemma and we'll turn it on for your account.


# Charge a virtual card yourself from Move money
Source: https://getlemma.com/docs/acquiring/charge-a-card

Charge a payer's virtual card directly in Lemma when you receive the card by payer portal, fax, or phone instead of lockbox mail.

<Note>
  Reach out to Lemma to get self-serve card charging enabled for your entity.
  It also requires [card acquiring](/docs/acquiring).
</Note>

When a virtual card arrives in your [lockbox](/docs/guides/lockbox) mail, Lemma detects and charges it for you. But payers sometimes hand you a card directly instead: in a payer portal, over fax, or read out over the phone. Charge those cards yourself from [Move money > Charge a card](https://app.getlemma.com/_/move-money/charge-card).

## Before you start

* **Self-serve charging is enabled.** The **Charge a card** option only appears on the Move money page after Lemma enables it for your entity. Reach out to us to turn it on.
* **You have a banking role.** Any [banking role](/docs/guides/team-management#banking-permissions) can charge a card, including Read Only. Charging a card only brings money in, the same as depositing a check.
* **You have the card details.** Have the card number, expiration date, and security code exactly as the payer provided them.

## Charge a card

<Steps>
  <Step title="Open the charge page">
    Go to [Move money](https://app.getlemma.com/_/move-money) and select
    **Charge a card**.
  </Step>

  <Step title="Enter the amount">
    Enter the amount to charge. A single charge can be up to \$50,000. Payer
    virtual cards typically carry an exact authorized amount, so enter it
    precisely.
  </Step>

  <Step title="Enter the card details and charge">
    Enter the card number, expiration date, and security code exactly as the
    payer provided them, then select **Charge**. If the card is declined, no
    money moves. If the card was already charged, Lemma tells you instead of
    charging it twice.
  </Step>
</Steps>

## After you charge

The card is charged immediately and the funds appear in your account in 24 to 36 hours. The charge shows up on your [Card Processing](https://app.getlemma.com/_/acquiring) page alongside the cards Lemma charges from your lockbox, and you can follow its status there.

Like every card payment, a self-serve charge produces two line items: an **Acquiring** transaction for the gross amount and a separate **Fee** transaction for the processing cost. See [how card payments show up](/docs/acquiring#payments-and-fees-are-separate-transactions) and the [pricing page](/docs/billing/pricing) for card processing fees.

## Related

<CardGroup>
  <Card title="Card payment transactions" icon="credit-card" href="/docs/acquiring">
    How Lemma charges cards from your lockbox and how payments appear.
  </Card>

  <Card title="Chargebacks" icon="rotate-left" href="/docs/acquiring/chargebacks">
    What happens when a payer disputes a card charge.
  </Card>
</CardGroup>


# Chargebacks
Source: https://getlemma.com/docs/acquiring/chargebacks

Understand the chargeback lifecycle on Lemma, when funds are debited, what fees apply, and how disputed money is returned when you win.

A chargeback happens when a cardholder disputes a charge with their card issuer instead of paying it. Visa and Mastercard arbitrate the dispute, and while it runs the disputed funds are held back from your account.

Chargebacks are rare when your card volume comes from payers reimbursing a clinic. They come up more often when a patient disputes a bill they don't want to pay.

## The chargeback lifecycle

<Steps>
  <Step title="An inquiry may come first">
    Some disputes open as an inquiry — the issuer asks for information before
    anything is formally disputed. Your money is untouched at this stage.
  </Step>

  <Step title="The dispute is filed">
    The \$25 dispute fee is charged as soon as the chargeback opens. The disputed
    amount itself is not debited yet.
  </Step>

  <Step title="Lemma reaches out for evidence">
    We contact you for documentation supporting the charge — typically the
    invoice, proof of service, patient consent, and any correspondence with the
    cardholder. Respond within the window we give you; the card networks enforce
    tight deadlines.
  </Step>

  <Step title="The disputed amount is debited">
    Once the dispute is formally opened, the disputed amount is debited from your
    account and appears as its own transaction. Lemma packages your evidence and
    submits it to Visa or Mastercard on your behalf.
  </Step>

  <Step title="The dispute resolves">
    * **You win.** The disputed amount is credited back to your account as a
      separate transaction.
    * **You lose.** The debit stands and the funds stay with the cardholder.
  </Step>
</Steps>

<Note>
  A dispute can be provisionally decided in your favor before it's final. Your
  funds stay held until the issuing bank makes its final decision — a
  provisional win doesn't credit you back.
</Note>

## Fees

The **\$25 dispute fee** is charged as soon as a chargeback is filed, regardless of who eventually wins, and appears as a **Fee** transaction.

The disputed amount is separate from that fee. It stays debited while the dispute is open, is credited back in full if you win, and stays debited if you lose.

## What you'll see

A single chargeback can produce up to three transactions, each on its own line:

* The **dispute fee**, when the chargeback opens.
* The **disputed amount**, debited when the dispute is formally opened.
* The **credit back**, if you win.

Together with the original card payment, that gives your billing team the full history of a disputed payment without stitching statements together.

## Related

* [How card payments show up](/docs/acquiring)
* [Transaction types](/docs/guides/transactions#transaction-types)


# How card payments show up
Source: https://getlemma.com/docs/acquiring/index

Understand how Lemma charges virtual cards from your lockbox and how the resulting transactions appear.

<Note>Reach out to Lemma to get card acquiring enabled.</Note>

Payers increasingly reimburse clinics by virtual card instead of check or ACH — a single-use card number printed on the remittance advice that you're expected to key into a terminal yourself. Lemma does that for you: we detect the card in your [lockbox](/docs/guides/lockbox) mail, charge it, and deposit the money into your account as itemized transactions.

## How a card payment happens

<Steps>
  <Step title="The payer mails a virtual card">
    A payer sends an explanation of benefits with a virtual card on it, or a
    standalone virtual card, to your lockbox address.
  </Step>

  <Step title="Lemma detects the card">
    We scan and classify every piece of lockbox mail. When a document carries a
    virtual card, we extract the card details and the amount to charge.
  </Step>

  <Step title="Lemma runs the card">
    We charge the card on your behalf. Nothing is required from you — there's no
    terminal to key the number into and no portal to log into.
  </Step>

  <Step title="The money lands in your account">
    Once the payment settles, the funds are deposited into your account and the
    payment appears on your [Transactions
    page](https://app.getlemma.com/_/transactions).
  </Step>
</Steps>

## Tracking a card payment

Each card payment carries a status you can follow from the mail item in your [lockbox](/docs/guides/lockbox):

| Status         | What it means                                                                  |
| -------------- | ------------------------------------------------------------------------------ |
| **Processing** | The card has been charged and the payment is settling.                         |
| **Deposited**  | The funds have landed in your account.                                         |
| **Failed**     | The card was declined and no money moved.                                      |
| **Refunded**   | The payment was refunded back to the payer.                                    |
| **Chargeback** | The payer disputed the charge. See [Chargebacks](/docs/acquiring/chargebacks). |
| **Canceled**   | The charge was canceled before it went through.                                |

## Charge a card yourself

Not every virtual card arrives by mail. When a payer gives you a card directly, in a payer portal, by fax, or over the phone, you can charge it yourself from [Move money > Charge a card](https://app.getlemma.com/_/move-money/charge-card). See [Charge a card](/docs/acquiring/charge-a-card) for requirements and steps.

## Payments and fees are separate transactions

Every card payment produces two transactions:

* **The card payment**, as an **Acquiring** transaction — the gross amount charged to the card.
* **The processing fee**, as a **Fee** transaction — what it cost to process that payment.

Splitting them is deliberate. A typical processor sends one lump-sum ACH every day or two and leaves your billing team to work out which payments and which fees it covers. Because Lemma is also your bank, we drop a labeled line item straight into the account for every economic event instead — so the reconciliation is already done when you open the page.

Refunds and chargebacks follow the same rule: each gets its own transaction, and each carries its own fee.

<Tip>
  On the [Transactions page](https://app.getlemma.com/_/transactions), filter by
  the **Acquiring** type to see the payments you collected and by the **Fee**
  type to see what they cost. Combined with a date range, that makes month-end
  reconciliation of card revenue against processing fees straightforward.
</Tip>

## Next steps

* Charge a card a payer gave you directly in [Charge a card](/docs/acquiring/charge-a-card).
* Learn how disputes work in [Chargebacks](/docs/acquiring/chargebacks).
* See how card payments arrive in [Lockbox](/docs/guides/lockbox).
* Review the full list of [transaction types](/docs/guides/transactions#transaction-types).


# Authentication
Source: https://getlemma.com/docs/api-reference/authentication

Integrate with the Lemma API as a platform and authenticate your requests.

<Note>
  The Lemma API is currently in beta. If you're interested in integrating with
  Lemma as a platform, reach out to the Lemma team at
  [contact@getlemma.com](mailto:contact@getlemma.com) to get started.
</Note>

## How it works

The Lemma API is designed for **platform integrations**. As a platform, you integrate with Lemma directly and receive API keys from the Lemma team. Your customers — the businesses that hold Lemma accounts — then grant your platform permission to access their data through Lemma.

Here's the flow:

1. You receive an API key from Lemma
2. Your customer logs in with their Lemma credentials and grants your platform permission to view their accounts
3. You use your API key to access the customer's data on their behalf

### Customer-granted permissions

Your platform can only access data that the customer has explicitly authorized. When a customer grants access, they choose which accounts your platform can see.

For sensitive actions like moving money, customers are required to limit the permission to specific accounts. This means:

* If a customer creates a new account on their Lemma dashboard (e.g., a savings account), your platform will **not** automatically have access to it — the customer must explicitly grant access.
* However, you **will** still see transactions on accounts you do have access to, including transfers made to or from accounts you cannot see. For example, if a customer moves money from an account you can access into a savings account you cannot, the outgoing transaction will still be visible.

## Getting an API key

API keys are issued directly by the Lemma team as part of your platform onboarding. Contact [contact@getlemma.com](mailto:contact@getlemma.com) to begin the integration process.

<Warning>
  Store your API key securely. Do not share it or commit it to source control.
  If you believe a key has been compromised, contact the Lemma team immediately
  to revoke it and issue a new one.
</Warning>

## Using your API key

Include the key in the `Authorization` header of every request using the `Bearer` scheme:

```bash theme={null}
curl https://api.getlemma.com/v0/accounts \
  -H "Authorization: Bearer your_api_key"
```

## Rate limits

The API allows up to **500 requests per minute** per API key. If you need higher limits, [contact us](mailto:contact@getlemma.com) and we're happy to increase them. See the [introduction](/docs/api-reference/introduction#rate-limits) for more details.

## Revoking a key

If you need to revoke an API key, contact the Lemma team at [contact@getlemma.com](mailto:contact@getlemma.com). Revoked keys stop working immediately and any requests using that key will begin receiving `401` responses.


# Create card
Source: https://getlemma.com/docs/api-reference/create-card

POST /v0/cards
Issue a virtual debit card with custom spending limits.

Issues a virtual debit card on a bank account, with the spending limits you specify. The card's `authorization_controls.usage.category` must be `multi_use`, and at least one limit is required.

Every limit matching a payment is checked and the most restrictive one applies, so a payment is declined once it exceeds the per-transaction cap, or once the day's spend would pass the daily cap, even while the weekly and monthly caps still have room.

Card payments will be rejected when there's insufficient balance on the bank account regardless of the limits you set.

## Headers

<ParamField type="string">
  A key that prevents issuing a duplicate card if the same request is retried.
  Reusing a key returns the originally created card instead of issuing a second
  one. See [Idempotency](/docs/api-reference/idempotency).
</ParamField>

## Request body

<ParamField type="string">
  The bank account this card draws from.
</ParamField>

<ParamField type="string">
  A human-readable label for this card. Between 1 and 50 characters.
</ParamField>

<ParamField type="object">
  Controls that restrict how this card can be used.

  <Expandable title="Authorization controls fields">
    <ParamField type="object">
      How many times this card can be used, and the controls for that usage.

      <Expandable title="Usage fields">
        <ParamField type="enum">
          Whether the card is for a single use or multiple uses.

          <Expandable title="Available options">
            <ResponseField name="multi_use" type="string">
              The card can be used for multiple authorizations. The only
              category issuable today.
            </ResponseField>
          </Expandable>
        </ParamField>

        <ParamField type="object">
          Controls for multi-use cards. Required if and only if `category` is
          `multi_use`.

          <Expandable title="Multi-use fields">
            <ParamField type="object[]">
              The spending limits to enforce on this card. Must contain at least
              one limit and at most one limit per interval. Where several limits
              apply to a transaction, the most restrictive one wins.

              <Expandable title="Limit object">
                <ParamField type="enum">
                  The window this limit is enforced over.

                  <Expandable title="Available options">
                    <ResponseField name="all_time" type="string">
                      Applies over the lifetime of the card.
                    </ResponseField>

                    <ResponseField name="per_transaction" type="string">
                      Applies to each individual transaction.
                    </ResponseField>

                    <ResponseField name="per_day" type="string">
                      Resets nightly at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_week" type="string">
                      Resets weekly on Mondays at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_month" type="string">
                      Resets on the first of the month at midnight UTC.
                    </ResponseField>
                  </Expandable>
                </ParamField>

                <ParamField type="integer">
                  The cap on settled spend in this window, in cents. Must be
                  positive, and at least as large as the cap on every narrower
                  interval — a wider window capped below a narrower one can
                  never be reached, so it is rejected.
                </ParamField>
              </Expandable>
            </ParamField>
          </Expandable>
        </ParamField>
      </Expandable>
    </ParamField>
  </Expandable>
</ParamField>

## Response

Returns the created card object.

<ResponseField name="id" type="string">
  Unique identifier for the card, prefixed with `card_`.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the card was created.
</ResponseField>

<ResponseField name="entity_id" type="string">
  The ID of the entity that owns this card.
</ResponseField>

<ResponseField name="bank_account_id" type="string">
  The bank account this card draws from.
</ResponseField>

<ResponseField name="nickname" type="string">
  The human-readable label for this card.
</ResponseField>

<ResponseField name="last_4" type="string">
  The last 4 digits of the card number.
</ResponseField>

<ResponseField name="status" type="enum">
  The card's status.

  <Expandable title="Available options">
    <ResponseField name="active" type="string">
      The card can be used for payments.
    </ResponseField>

    <ResponseField name="disabled" type="string">
      The card is temporarily disabled.
    </ResponseField>

    <ResponseField name="canceled" type="string">
      The card is permanently canceled.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="authorization_controls" type="object">
  Every control restricting how this card can be used, including the ones Lemma
  applies to every card it issues.

  <Expandable title="Authorization controls object">
    <ResponseField name="usage" type="object">
      How many times this card can be used, and its controls.

      <Expandable title="Usage object">
        <ResponseField name="category" type="enum">
          Whether the card is for a single use or multiple uses.

          <Expandable title="Available options">
            <ResponseField name="multi_use" type="string">
              The card can be used for multiple authorizations. The only
              category issuable today.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="multi_use" type="object">
          Controls for multi-use cards.

          <Expandable title="Multi-use object">
            <ResponseField name="spending_limits" type="object[]">
              Every spending limit enforced on this card, including the ones
              Lemma applies automatically.

              <Expandable title="Limit object">
                <ResponseField name="interval" type="enum">
                  The window this limit is enforced over.

                  <Expandable title="Available options">
                    <ResponseField name="all_time" type="string">
                      Applies over the lifetime of the card.
                    </ResponseField>

                    <ResponseField name="per_transaction" type="string">
                      Applies to each individual transaction.
                    </ResponseField>

                    <ResponseField name="per_day" type="string">
                      Resets nightly at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_week" type="string">
                      Resets weekly on Mondays at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_month" type="string">
                      Resets on the first of the month at midnight UTC.
                    </ResponseField>
                  </Expandable>
                </ResponseField>

                <ResponseField name="amount" type="integer">
                  Cap in cents.
                </ResponseField>

                <ResponseField name="merchant_category_codes" type="string[] | null">
                  Merchant category codes this limit applies to. `null` applies
                  to all merchants.
                </ResponseField>
              </Expandable>
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_acceptor_identifier" type="object | null">
      Restricts which Merchant Acceptor IDs this card may transact with. `null`
      when this dimension is unrestricted.

      <Expandable title="Merchant acceptor identifier object">
        <ResponseField name="allowed" type="string[] | null">
          The only Merchant Acceptor IDs this card may transact with. `null`
          when this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant Acceptor IDs this card may never transact with. `null` when
          this dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_category_code" type="object | null">
      Restricts which merchant categories this card may transact with, including
      the categories Lemma blocks on every card it issues. `null` when this
      dimension is unrestricted.

      <Expandable title="Merchant category code object">
        <ResponseField name="allowed" type="string[] | null">
          The only merchant category codes this card may transact with. `null`
          when this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant category codes this card may never transact with. `null` when
          this dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_country" type="object | null">
      Restricts which merchant countries this card may transact with, as [ISO
      3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) codes.
      `null` when this dimension is unrestricted.

      <Expandable title="Merchant country object">
        <ResponseField name="allowed" type="string[] | null">
          The only merchant countries this card may transact with. `null` when
          this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant countries this card may never transact with. `null` when this
          dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": "card_Bx5nTm8hKw3pVd7c",
    "created_at": "2026-07-28T18:45:00Z",
    "entity_id": "entity_k7mXp2vR9nTfBw4s",
    "bank_account_id": "account_maple_ridge_cigna_01",
    "nickname": "Acme ops card",
    "last_4": "4242",
    "status": "active",
    "authorization_controls": {
      "usage": {
        "category": "multi_use",
        "multi_use": {
          "spending_limits": [
            { "interval": "per_transaction", "amount": 25000, "merchant_category_codes": null },
            { "interval": "per_day", "amount": 100000, "merchant_category_codes": null },
            { "interval": "per_day", "amount": 300000, "merchant_category_codes": ["6010", "6011"] }
          ]
        }
      },
      "merchant_acceptor_identifier": null,
      "merchant_category_code": { "allowed": null, "blocked": ["7995", "6051"] },
      "merchant_country": null
    }
  }
  ```

  ```json 400 theme={null}
  {
    "statusCode": 400,
    "error": "Bad Request",
    "message": [
      "authorization_controls.usage.multi_use.spending_limits amounts must not decrease as the interval widens (per_transaction, per_day, per_week, per_month, all_time)"
    ]
  }
  ```
</ResponseExample>


# Create external account
Source: https://getlemma.com/docs/api-reference/create-external-account

POST /v0/external-accounts
Save an external bank account as a recipient for outbound transfers.

Creates a saved external account that can be used as a destination for [transfers](/docs/api-reference/move-money-externally). External accounts represent bank accounts outside of Lemma, such as a vendor, payroll provider, or another financial institution.

External accounts cannot be edited after creation. If you need to change account details, archive the existing external account and create a new one. See [Saved recipients](/docs/api-reference/saved-recipients) for more on why.

<Warning>
  The `nickname` is visible to the account owner on their Lemma dashboard.
  Choose something descriptive and recognizable (e.g., "Owner's Personal
  Account" rather than "Acct 4821"). We recommend making nicknames unique within
  an entity.
</Warning>

## Headers

<ParamField type="string">
  A key that prevents creating a duplicate external account if the same request
  is retried. Reusing a key returns the originally created account instead of
  saving a second one. See [Idempotency](/docs/api-reference/idempotency).
</ParamField>

## Request body

<ParamField type="string">
  The ID of the entity this recipient belongs to.
</ParamField>

<ParamField type="string">
  A human-readable label for this recipient. Displayed on the Lemma dashboard
  and in transaction history.
</ParamField>

<ParamField type="string">
  Whether the account holder is a business or an individual. One of `business`
  or `individual`.
</ParamField>

<ParamField type="string">
  The 9-digit ABA routing number of the recipient's bank.
</ParamField>

<ParamField type="string">
  The bank account number. Digits only.
</ParamField>

<ParamField type="string">
  The legal name of the account holder.
</ParamField>

<ParamField type="object">
  The account holder's mailing address. Must be a US address.

  <Expandable title="Address fields">
    <ParamField type="string">
      Street address.
    </ParamField>

    <ParamField type="string">
      Apartment, suite, or unit number.
    </ParamField>

    <ParamField type="string">
      City name.
    </ParamField>

    <ParamField type="string">
      Two-letter US state code.
    </ParamField>

    <ParamField type="string">
      ZIP code.
    </ParamField>

    <ParamField type="string">
      ISO 3166-1 alpha-2 country code. Must be `US`.
    </ParamField>
  </Expandable>
</ParamField>

## Response

Returns the created external account object.

<ResponseField name="id" type="string">
  Unique identifier for the external account, prefixed with `external_account_`.
</ResponseField>

<ResponseField name="entity_id" type="string">
  The ID of the entity that owns this external account.
</ResponseField>

<ResponseField name="nickname" type="string">
  The human-readable label for this external account.
</ResponseField>

<ResponseField name="holder_type" type="string">
  `business` or `individual`.
</ResponseField>

<ResponseField name="routing_number" type="string">
  The routing number of the account holder's bank.
</ResponseField>

<ResponseField name="account_number" type="string">
  The external account's account number.
</ResponseField>

<ResponseField name="status" type="string">
  The external account's status. Always `active` on creation.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the external account
  was created.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "external_account_Bx5nTm8hKw3pVd7c",
    "entity_id": "entity_k7mXp2vR9nTfBw4s",
    "nickname": "Quest Diagnostics Operating Account",
    "routing_number": "021000021",
    "account_number": "123456789",
    "status": "active",
    "created_at": "2026-03-20T18:45:00Z"
  }
  ```

  ```json 400 theme={null}
  {
    "error": "holder_address.line1 is required"
  }
  ```
</ResponseExample>


# Delete a card
Source: https://getlemma.com/docs/api-reference/delete-card

DELETE /v0/cards/{card_id}
Permanently cancel a card so it can no longer be used.

Cancels a card so it can no longer be used for payments. Cancelling a card cannot be undone: if you only need to pause spending temporarily, freeze the card instead.

You can only cancel cards issued by your platform. A card issued by the entity’s staff in the Lemma app returns a 404.

## Path parameters

<ParamField type="string">
  The card's unique identifier.
</ParamField>

## Response

Returns the canceled card object.

<ResponseField name="id" type="string">
  Unique identifier for the card, prefixed with `card_`.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the card was created.
</ResponseField>

<ResponseField name="entity_id" type="string">
  The ID of the entity that owns this card.
</ResponseField>

<ResponseField name="bank_account_id" type="string">
  The bank account this card draws from.
</ResponseField>

<ResponseField name="nickname" type="string">
  The human-readable label for this card.
</ResponseField>

<ResponseField name="last_4" type="string">
  The last 4 digits of the card number.
</ResponseField>

<ResponseField name="status" type="enum">
  The card's status. After a successful `DELETE` this is `canceled`.

  <Expandable title="Available options">
    <ResponseField name="active" type="string">
      The card can be used for payments.
    </ResponseField>

    <ResponseField name="disabled" type="string">
      The card is temporarily disabled.
    </ResponseField>

    <ResponseField name="canceled" type="string">
      The card is permanently canceled.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="authorization_controls" type="object">
  Every control restricting how this card can be used, including the ones Lemma
  applies to every card it issues.

  <Expandable title="Authorization controls object">
    <ResponseField name="usage" type="object">
      How many times this card can be used, and its controls.

      <Expandable title="Usage object">
        <ResponseField name="category" type="enum">
          Whether the card is for a single use or multiple uses.

          <Expandable title="Available options">
            <ResponseField name="multi_use" type="string">
              The card can be used for multiple authorizations. The only
              category issuable today.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="multi_use" type="object">
          Controls for multi-use cards.

          <Expandable title="Multi-use object">
            <ResponseField name="spending_limits" type="object[]">
              Every spending limit enforced on this card, including the ones
              Lemma applies automatically.

              <Expandable title="Limit object">
                <ResponseField name="interval" type="enum">
                  The window this limit is enforced over.

                  <Expandable title="Available options">
                    <ResponseField name="all_time" type="string">
                      Applies over the lifetime of the card.
                    </ResponseField>

                    <ResponseField name="per_transaction" type="string">
                      Applies to each individual transaction.
                    </ResponseField>

                    <ResponseField name="per_day" type="string">
                      Resets nightly at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_week" type="string">
                      Resets weekly on Mondays at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_month" type="string">
                      Resets on the first of the month at midnight UTC.
                    </ResponseField>
                  </Expandable>
                </ResponseField>

                <ResponseField name="amount" type="integer">
                  Cap in cents.
                </ResponseField>

                <ResponseField name="merchant_category_codes" type="string[] | null">
                  Merchant category codes this limit applies to. `null` applies
                  to all merchants.
                </ResponseField>
              </Expandable>
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_acceptor_identifier" type="object | null">
      Restricts which Merchant Acceptor IDs this card may transact with. `null`
      when this dimension is unrestricted.

      <Expandable title="Merchant acceptor identifier object">
        <ResponseField name="allowed" type="string[] | null">
          The only Merchant Acceptor IDs this card may transact with. `null`
          when this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant Acceptor IDs this card may never transact with. `null` when
          this dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_category_code" type="object | null">
      Restricts which merchant categories this card may transact with, including
      the categories Lemma blocks on every card it issues. `null` when this
      dimension is unrestricted.

      <Expandable title="Merchant category code object">
        <ResponseField name="allowed" type="string[] | null">
          The only merchant category codes this card may transact with. `null`
          when this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant category codes this card may never transact with. `null` when
          this dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_country" type="object | null">
      Restricts which merchant countries this card may transact with, as [ISO
      3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) codes.
      `null` when this dimension is unrestricted.

      <Expandable title="Merchant country object">
        <ResponseField name="allowed" type="string[] | null">
          The only merchant countries this card may transact with. `null` when
          this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant countries this card may never transact with. `null` when this
          dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "card_Bx5nTm8hKw3pVd7c",
    "created_at": "2026-07-28T18:45:00Z",
    "entity_id": "entity_k7mXp2vR9nTfBw4s",
    "bank_account_id": "account_maple_ridge_cigna_01",
    "nickname": "Acme ops card",
    "last_4": "4242",
    "status": "canceled",
    "authorization_controls": {
      "usage": {
        "category": "multi_use",
        "multi_use": {
          "spending_limits": [
            { "interval": "per_transaction", "amount": 25000, "merchant_category_codes": null },
            { "interval": "per_day", "amount": 100000, "merchant_category_codes": null }
          ]
        }
      },
      "merchant_acceptor_identifier": null,
      "merchant_category_code": { "allowed": null, "blocked": ["7995", "6051"] },
      "merchant_country": null
    }
  }
  ```

  ```json 403 theme={null}
  {
    "statusCode": 403,
    "error": "Forbidden",
    "message": "Insufficient permissions to cancel cards for this entity"
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not Found",
    "message": "Card not found"
  }
  ```
</ResponseExample>


# Entities
Source: https://getlemma.com/docs/api-reference/entities

Legal entities that hold accounts on Lemma.

An entity is a healthcare practice or legal entity that holds accounts on Lemma. Every account, transfer, check, and external account in Lemma belongs to an entity. Entities are the top-level organizational unit in the API — most endpoints require an `entity_id` or are scoped to a single entity.

<Tip>
  The Lemma dashboard URLs include the entity ID (e.g.
  `app.getlemma.com/entity_abc123`). If you have dashboard access for an entity,
  paste their ID into the URL to jump straight to that entity.
</Tip>

## What Lemma tracks

When an entity is onboarded, Lemma captures and verifies several pieces of information:

* **Legal entity details** — the entity's legal name, structure (e.g., professional LLC, sole proprietorship), and state of incorporation. These determine which banking products the entity is eligible for.
* **NPI number** — the entity's 10-digit [National Provider Identifier](https://www.cms.gov/medicare/enrollment-renewal/providers-suppliers/national-provider-identifier-standard), issued by CMS. Lemma uses the NPI to uniquely identify healthcare entities and to match incoming insurance payments to the correct account.
* **KYC information** — Lemma collects Know Your Customer details (beneficial owners, EIN, address) as part of onboarding to satisfy regulatory requirements. This information is not exposed through the API.

## Legal structures

Each entity has a `structure` field that reflects its legal entity type. Lemma supports:

| Structure                | Value                      |
| ------------------------ | -------------------------- |
| Corporation              | `corporation`              |
| LLC                      | `llc`                      |
| Nonprofit                | `nonprofit`                |
| Partnership              | `partnership`              |
| Professional association | `professional_association` |
| Professional corporation | `professional_corporation` |
| Professional LLC         | `professional_llc`         |
| Sole proprietorship      | `sole_prop`                |

## Listing and finding entities

The [List entities](/docs/api-reference/list-entities) endpoint returns all entities that have granted access to your platform. An entity can limit access to only certain bank accounts.

To find a specific entity, pass the `npi` query parameter. NPI numbers are not guaranteed to be unique across entities — multiple legal entities can share the same NPI (e.g., when a group practice reorganizes or when separate entities bill under a shared organizational NPI), so the endpoint may return more than one result.

```bash theme={null}
curl "https://api.getlemma.com/v0/entities?npi=1234567890" \
  -H "Authorization: Bearer lm_key_your_api_key"
```

## Lockbox address

Every entity is assigned a lockbox mailing address. Payers send checks and correspondence to this address, and Lemma automatically scans and deposits them. Retrieve an entity's lockbox address with the [Get entity lockbox](/docs/api-reference/get-entity-lockbox) endpoint.


# Get settlement instructions
Source: https://getlemma.com/docs/api-reference/get-account-settlement-instructions

GET /v0/accounts/{account_id}/settlement-instructions
Download a bank account's settlement instructions as a PDF.

Downloads a PDF containing the settlement instructions for a bank account: the account and routing numbers, beneficiary name and address, and the receiving bank's details. The response body is the raw file, not a JSON object.

Share this PDF with a payer who needs to send funds to the account — for example, a payer setting up a wire or ACH credit.

## Path parameters

<ParamField type="string">
  The unique identifier of the bank account.
</ParamField>

## Response

Returns the file as `application/pdf`, downloaded with a `Content-Disposition: attachment` header. The filename is `{account_id}_settlement_instructions.pdf`.

<ResponseExample>
  ```bash 200 theme={null}
  GET /v0/accounts/account_Rv4nBt8xKw2pMh6s/settlement-instructions

  Content-Type: application/pdf
  Content-Disposition: attachment; filename="account_Rv4nBt8xKw2pMh6s_settlement_instructions.pdf"
  Cache-Control: private, no-store

  <binary PDF data>
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "Account not found"
  }
  ```
</ResponseExample>


# Get ACH transfer
Source: https://getlemma.com/docs/api-reference/get-ach-transfer

GET /v0/ach-transfer/{ach_transfer_id}
Retrieve a single ACH transfer by its ID.

Returns a single ACH transfer object.

## Path parameters

<ParamField type="string">
  The unique identifier of the ACH transfer to retrieve.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the ACH transfer.
</ResponseField>

<ResponseField name="account_id" type="string">
  The Lemma account the transfer moves money from or to.
</ResponseField>

<ResponseField name="external_account_id" type="string | null">
  The [external account](/docs/api-reference/saved-recipients) on the other side of
  the transfer.
</ResponseField>

<ResponseField name="amount" type="integer">
  The transfer amount in cents. A positive amount indicates a credit transfer
  pushing funds to the receiving account. A negative amount indicates a debit
  transfer pulling funds from the receiving account (an ACH pull).
</ResponseField>

<ResponseField name="status" type="string">
  Current status of the ACH transfer.

  <Expandable title="possible values">
    * `pending` — in flight.

    * `submitted` — sent to the ACH network. When the Federal Reserve settles the transfer, the status stays `submitted` and `settled_at` is populated.

    * `canceled` — we canceled the transfer after holding it for manual review.

    * `rejected` — the ACH network rejected the transfer.

    * `returned` — the transfer was returned.
  </Expandable>
</ResponseField>

<ResponseField name="statement_descriptor" type="string">
  The statement descriptor shown to the counterparty.
</ResponseField>

<ResponseField name="transaction_id" type="string | null">
  The settled transaction, once the transfer posts.
</ResponseField>

<ResponseField name="settled_at" type="string | null">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer settled.
</ResponseField>

<ResponseField name="submission" type="object | null">
  Submission details, once the transfer reaches the ACH network.

  <Expandable title="Submission object">
    <ResponseField name="submitted_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer was
      submitted to the ACH network.
    </ResponseField>

    <ResponseField name="expected_funds_settlement_at" type="string | null">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the funds are
      expected to settle.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="return" type="object | null">
  Return details, if the transfer was returned.

  <Expandable title="Return object">
    <ResponseField name="raw_return_reason_code" type="string">
      The raw ACH return reason code.
    </ResponseField>

    <ResponseField name="return_transaction_id" type="string | null">
      The transaction created when the transfer was returned.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "ach_transfer_Lk7nQx4mVp9bRt3d",
    "account_id": "account_Rv4nBt8xKw2pMh6s",
    "external_account_id": "external_account_Bx5nTm8hKw3pVd7c",
    "amount": -150000,
    "status": "submitted",
    "statement_descriptor": "Acme payroll",
    "transaction_id": null,
    "settled_at": null,
    "submission": {
      "submitted_at": "2026-03-15T14:30:00Z",
      "expected_funds_settlement_at": "2026-03-17T14:30:00Z"
    },
    "return": null
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not Found",
    "message": "ACH transfer not found"
  }
  ```
</ResponseExample>


# Get bank account
Source: https://getlemma.com/docs/api-reference/get-bank-account

GET /v0/accounts/{account_id}
Retrieve a single bank account by its ID.

Returns a single bank account.

## Path parameters

<ParamField type="string">
  The unique identifier of the bank account to retrieve.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the account, prefixed with `account_`.
</ResponseField>

<ResponseField name="entity_id" type="string">
  The ID of the entity that owns this account.
</ResponseField>

<ResponseField name="name" type="string">
  The name of the account.
</ResponseField>

<ResponseField name="account_number" type="string">
  The bank account number.
</ResponseField>

<ResponseField name="routing_number" type="string">
  The ABA routing number.
</ResponseField>

<ResponseField name="total_balance" type="integer">
  The total balance of the account in cents, including funds that are not yet
  available.
</ResponseField>

<ResponseField name="available_balance" type="integer">
  The balance available for use in cents. This excludes any held funds from
  pending transactions.
</ResponseField>

<ResponseField name="opened_at" type="string">
  The timestamp when the account was opened, in ISO 8601 format.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "account_Rv4nBt8xKw2pMh6s",
    "entity_id": "entity_k7mXp2vR9nTfBw4s",
    "name": "Operating Account",
    "account_number": "987654321",
    "routing_number": "101050001",
    "total_balance": 2450000,
    "available_balance": 2350000,
    "opened_at": "2026-01-15T09:30:00Z"
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "Account not found"
  }
  ```
</ResponseExample>


# Get book transfer
Source: https://getlemma.com/docs/api-reference/get-book-transfer

GET /v0/book-transfer/{book_transfer_id}
Retrieve a single book transfer by its ID.

Returns a single book transfer object.

## Path parameters

<ParamField type="string">
  The unique identifier of the book transfer to retrieve.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the book transfer.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the book transfer was
  created.
</ResponseField>

<ResponseField name="source_account_id" type="string">
  The Lemma account money moves from.
</ResponseField>

<ResponseField name="destination_account_id" type="string">
  The Lemma account money moves to.
</ResponseField>

<ResponseField name="amount" type="integer">
  The transfer amount in cents.
</ResponseField>

<ResponseField name="status" type="string">
  Current status of the book transfer.

  <Expandable title="possible values">
    * `complete` — settled. Most book transfers are complete the moment they're
      created.

    * `pending_approval` — held for manual review by our team for fraud
      prevention.

    * `canceled` — blocked after that manual review.
  </Expandable>
</ResponseField>

<ResponseField name="description" type="string">
  Description of the transfer.
</ResponseField>

<ResponseField name="source_transaction_id" type="string | null">
  The settled transaction on the source account, once the transfer posts.
</ResponseField>

<ResponseField name="destination_transaction_id" type="string | null">
  The settled transaction on the destination account, once the transfer posts.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "book_transfer_Hm3pWx9nKv4bQt7d",
    "created_at": "2026-03-15T14:30:00Z",
    "source_account_id": "account_Rv4nBt8xKw2pMh6s",
    "destination_account_id": "account_Tz8mKp3xLw5nVh9c",
    "amount": 250000,
    "status": "complete",
    "description": "Quarterly intercompany settlement",
    "source_transaction_id": "transaction_Wp5mRx3nKv8bTh2d",
    "destination_transaction_id": "transaction_Qk2nJx7mLv9bRt4c"
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not Found",
    "message": "Book transfer not found"
  }
  ```
</ResponseExample>


# Get card
Source: https://getlemma.com/docs/api-reference/get-card

GET /v0/cards/{card_id}
Retrieve a card and its spending limits.

Returns a card, the spending limits set on it, and the merchants it may transact with.

Only cards your platform issued over the API are visible here. A card issued by the entity's staff in the Lemma app returns a 404.

## Path parameters

<ParamField type="string">
  The card's unique identifier.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the card, prefixed with `card_`.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the card was created.
</ResponseField>

<ResponseField name="entity_id" type="string">
  The ID of the entity that owns this card.
</ResponseField>

<ResponseField name="bank_account_id" type="string">
  The bank account this card draws from.
</ResponseField>

<ResponseField name="nickname" type="string">
  The human-readable label for this card.
</ResponseField>

<ResponseField name="last_4" type="string">
  The last 4 digits of the card number.
</ResponseField>

<ResponseField name="status" type="enum">
  The card's status.

  <Expandable title="Available options">
    <ResponseField name="active" type="string">
      The card can be used for payments.
    </ResponseField>

    <ResponseField name="disabled" type="string">
      The card is temporarily disabled.
    </ResponseField>

    <ResponseField name="canceled" type="string">
      The card is permanently canceled.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="authorization_controls" type="object">
  Every control restricting how this card can be used, including the ones Lemma
  applies to every card it issues.

  <Expandable title="Authorization controls object">
    <ResponseField name="usage" type="object">
      How many times this card can be used, and its controls.

      <Expandable title="Usage object">
        <ResponseField name="category" type="enum">
          Whether the card is for a single use or multiple uses.

          <Expandable title="Available options">
            <ResponseField name="multi_use" type="string">
              The card can be used for multiple authorizations. The only
              category issuable today.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="multi_use" type="object">
          Controls for multi-use cards.

          <Expandable title="Multi-use object">
            <ResponseField name="spending_limits" type="object[]">
              Every spending limit enforced on this card, including the ones
              Lemma applies automatically.

              <Expandable title="Limit object">
                <ResponseField name="interval" type="enum">
                  The window this limit is enforced over.

                  <Expandable title="Available options">
                    <ResponseField name="all_time" type="string">
                      Applies over the lifetime of the card.
                    </ResponseField>

                    <ResponseField name="per_transaction" type="string">
                      Applies to each individual transaction.
                    </ResponseField>

                    <ResponseField name="per_day" type="string">
                      Resets nightly at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_week" type="string">
                      Resets weekly on Mondays at midnight UTC.
                    </ResponseField>

                    <ResponseField name="per_month" type="string">
                      Resets on the first of the month at midnight UTC.
                    </ResponseField>
                  </Expandable>
                </ResponseField>

                <ResponseField name="amount" type="integer">
                  Cap in cents.
                </ResponseField>

                <ResponseField name="merchant_category_codes" type="string[] | null">
                  Merchant category codes this limit applies to. `null` applies
                  to all merchants.
                </ResponseField>
              </Expandable>
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_acceptor_identifier" type="object | null">
      Restricts which Merchant Acceptor IDs this card may transact with. `null`
      when this dimension is unrestricted.

      <Expandable title="Merchant acceptor identifier object">
        <ResponseField name="allowed" type="string[] | null">
          The only Merchant Acceptor IDs this card may transact with. `null`
          when this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant Acceptor IDs this card may never transact with. `null` when
          this dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_category_code" type="object | null">
      Restricts which merchant categories this card may transact with, including
      the categories Lemma blocks on every card it issues. `null` when this
      dimension is unrestricted.

      <Expandable title="Merchant category code object">
        <ResponseField name="allowed" type="string[] | null">
          The only merchant category codes this card may transact with. `null`
          when this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant category codes this card may never transact with. `null` when
          this dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="merchant_country" type="object | null">
      Restricts which merchant countries this card may transact with, as [ISO
      3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) codes.
      `null` when this dimension is unrestricted.

      <Expandable title="Merchant country object">
        <ResponseField name="allowed" type="string[] | null">
          The only merchant countries this card may transact with. `null` when
          this dimension is not an allow list.
        </ResponseField>

        <ResponseField name="blocked" type="string[] | null">
          Merchant countries this card may never transact with. `null` when this
          dimension is not a block list.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "card_Bx5nTm8hKw3pVd7c",
    "created_at": "2026-07-28T18:45:00Z",
    "entity_id": "entity_k7mXp2vR9nTfBw4s",
    "bank_account_id": "account_maple_ridge_cigna_01",
    "nickname": "Acme ops card",
    "last_4": "4242",
    "status": "active",
    "authorization_controls": {
      "usage": {
        "category": "multi_use",
        "multi_use": {
          "spending_limits": [
            { "interval": "per_transaction", "amount": 25000, "merchant_category_codes": null },
            { "interval": "per_day", "amount": 100000, "merchant_category_codes": null },
            { "interval": "per_day", "amount": 300000, "merchant_category_codes": ["6010", "6011"] }
          ]
        }
      },
      "merchant_acceptor_identifier": null,
      "merchant_category_code": { "allowed": null, "blocked": ["7995", "6051"] },
      "merchant_country": null
    }
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "Card not found"
  }
  ```
</ResponseExample>


# Get a card iframe
Source: https://getlemma.com/docs/api-reference/get-card-iframe

GET /v0/cards/{card_id}/iframe
Get a short-lived iframe URL for displaying a card's sensitive details.

Returns a PCI-compliant URL that can be embedded in an `<iframe>` to securely display a card's sensitive details (card number, CVV, expiration date) without those values ever passing through your servers.

The URL expires after a short time, so request a new one each time you display the card.

You can only generate an iframe for a card your platform created. A card issued by the entity's staff in the Lemma app returns a 404.

## Path parameters

<ParamField type="string">
  The ID of the card, prefixed with `card_`.
</ParamField>

## Response

<ResponseField name="iframe_url" type="string">
  The URL to embed in an iframe.
</ResponseField>

<ResponseField name="expires_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the iframe URL expires.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "iframe_url": "https://increase.com/iframes/card_details/ifr_04text7hcbjtjs4wo3ig",
    "expires_at": "2026-04-10T15:00:00Z"
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not Found",
    "message": "Card not found"
  }
  ```
</ResponseExample>


# Get a check deposit
Source: https://getlemma.com/docs/api-reference/get-check-deposit

GET /v0/check-deposits/{check_deposit_id}
Retrieve a single check deposit by its ID.

Returns the details of a check deposited into a Lemma account, including its current status, hold information, and MICR data. Use this endpoint to poll a check's status after discovering it via the [List entity mail](/docs/api-reference/list-entity-mail) endpoint.

## Path parameters

<ParamField type="string">
  The ID of the check deposit, prefixed with `check_deposit_`.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the check deposit.
</ResponseField>

<ResponseField name="amount" type="integer">
  The check amount in cents.
</ResponseField>

<ResponseField name="status" type="string">
  The processing status of the check. One of `pending`, `submitted`, `returned`,
  or `rejected`.
</ResponseField>

<ResponseField name="transaction_id" type="string | null">
  The ID for the transaction created by the check deposit. Null if no
  transaction has been created yet.
</ResponseField>

<ResponseField name="inbound_mail_item_id" type="string | null">
  The mail item this check was found in. Null if the check was not received via
  lockbox mail.
</ResponseField>

<ResponseField name="hold" type="object | null">
  Fund hold details. Present when deposited funds are held before becoming
  available. Null if there is no hold.

  <Expandable title="Hold object">
    <ResponseField name="status" type="string">
      The hold status. One of `held` or `complete`.
    </ResponseField>

    <ResponseField name="automatically_releases_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the hold will
      automatically release.
    </ResponseField>

    <ResponseField name="released_at" type="string | null">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the hold was
      released. Null if the hold has not been released yet.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="return" type="object | null">
  Return details, if the check deposit was returned.

  <Expandable title="Return object">
    <ResponseField name="returned_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the check deposit
      was returned.
    </ResponseField>

    <ResponseField name="reason" type="string | null">
      Why the check deposit was returned.
    </ResponseField>

    <ResponseField name="return_transaction_id" type="string | null">
      The transaction created when the check deposit was returned.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="micr" type="object | null">
  Fields read from the check's [MICR
  line](https://en.wikipedia.org/wiki/Magnetic_ink_character_recognition). Null
  when we have not submitted the check for deposit.

  <Expandable title="MICR object">
    <ResponseField name="routing_number" type="string">
      The routing number printed on the check.
    </ResponseField>

    <ResponseField name="account_number" type="string">
      The account number printed on the check.
    </ResponseField>

    <ResponseField name="auxiliary_on_us" type="string | null">
      An additional identifier from the MICR line. Business checks typically
      encode the check number here rather than in `serial_number`.
    </ResponseField>

    <ResponseField name="serial_number" type="string | null">
      The check number. For business checks, this may be null — look at
      `auxiliary_on_us` instead.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "check_deposit_Tm6bXn9hRw3pFk7c",
    "amount": 100000,
    "status": "submitted",
    "transaction_id": "transaction_Ab5cDx3nKv8bTh2d",
    "inbound_mail_item_id": "inbound_mail_item_Kv7nWp3hTx9cBd5m",
    "hold": {
      "status": "held",
      "automatically_releases_at": "2026-03-19T14:00:00Z",
      "released_at": null
    },
    "return": null,
    "micr": {
      "routing_number": "021000021",
      "account_number": "9876543210",
      "auxiliary_on_us": null,
      "serial_number": "00012345"
    }
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not Found",
    "message": "Check not found"
  }
  ```
</ResponseExample>


# Get entity
Source: https://getlemma.com/docs/api-reference/get-entity

GET /v0/entities/{entity_id}
Retrieve details for a specific entity.

Returns detailed information about a single entity. To retrieve the entity's lockbox mailing address, use the [Get entity lockbox](/docs/api-reference/get-entity-lockbox) endpoint.

## Path parameters

<ParamField type="string">
  The ID of the entity. You can find entity IDs using the [List
  entities](/docs/api-reference/list-entities) endpoint.
</ParamField>

## Response

Returns an entity object.

<ResponseField name="id" type="string">
  Unique identifier for the entity, prefixed with `entity_`.
</ResponseField>

<ResponseField name="created_at" type="string">
  ISO 8601 timestamp of when the entity was created.
</ResponseField>

<ResponseField name="name" type="string">
  The name of the entity or practice.
</ResponseField>

<ResponseField name="structure" type="string">
  The entity's legal structure. One of `fqhc`, `govt`,
  `professional_corporation`, `professional_llc`, `professional_association`,
  `llc`, `corporation`, `partnership`, `sole_prop`, or `nonprofit`.
</ResponseField>

<ResponseField name="npi" type="string | null">
  The entity's 10-digit National Provider Identifier.
</ResponseField>

<ResponseField name="address" type="object">
  The entity's business address.

  <Expandable title="address">
    <ResponseField name="line1" type="string">
      Street address line 1.
    </ResponseField>

    <ResponseField name="line2" type="string">
      Street address line 2, or an empty string if not set.
    </ResponseField>

    <ResponseField name="city" type="string">
      City.
    </ResponseField>

    <ResponseField name="state" type="string">
      Two-letter state code.
    </ResponseField>

    <ResponseField name="postalCode" type="string">
      ZIP code.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "entity_k7mXp2vR9nTfBw4s",
    "created_at": "2026-07-01T09:30:00Z",
    "name": "Riverside Family Medicine",
    "structure": "professional_llc",
    "npi": "1234567890",
    "address": {
      "line1": "2261 Market St",
      "line2": "Ste 1234",
      "city": "San Francisco",
      "state": "CA",
      "postalCode": "94114"
    }
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "Entity not found"
  }
  ```
</ResponseExample>


# Get entity lockbox
Source: https://getlemma.com/docs/api-reference/get-entity-lockbox

GET /v0/entities/{entity_id}/lockbox
Retrieve the lockbox mailing address for a specific entity.

Returns the mailing address for the entity's lockbox. Use this address to direct payers to send checks and correspondence for this entity. Mail sent to this address is automatically scanned and available via the [mail](/docs/api-reference/list-entity-mail) endpoint.

## Path parameters

<ParamField type="string">
  The ID of the entity. You can find entity IDs using the [List
  entities](/docs/api-reference/list-entities) endpoint.
</ParamField>

## Response

Returns a lockbox address object.

<ResponseField name="name" type="string | null">
  Recipient name, if applicable.
</ResponseField>

<ResponseField name="line1" type="string">
  Street address line 1.
</ResponseField>

<ResponseField name="line2" type="string | null">
  Street address line 2, if applicable.
</ResponseField>

<ResponseField name="city" type="string">
  City.
</ResponseField>

<ResponseField name="state" type="string">
  Two-letter state code.
</ResponseField>

<ResponseField name="postalCode" type="string">
  ZIP code.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "name": "ATTN: ABC123",
    "line1": "2261 Market St",
    "line2": "Ste 1234",
    "city": "San Francisco",
    "state": "CA",
    "postalCode": "94114"
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "Entity lockbox not found"
  }
  ```
</ResponseExample>


# Get external account
Source: https://getlemma.com/docs/api-reference/get-external-account

GET /v0/external-accounts/{external_account_id}
Retrieve a single external account by ID.

Returns the full details of an external account, including account and routing numbers. This endpoint returns the external account regardless of its status, so you can use it to look up archived external accounts.

## Path parameters

<ParamField type="string">
  The ID of the external account to retrieve, prefixed with `external_account_`.
</ParamField>

## Response

Returns the external account object.

<ResponseField name="id" type="string">
  Unique identifier for the external account, prefixed with `external_account_`.
</ResponseField>

<ResponseField name="entity_id" type="string">
  The ID of the entity that owns this external account.
</ResponseField>

<ResponseField name="nickname" type="string">
  The human-readable label for this external account.
</ResponseField>

<ResponseField name="routing_number" type="string">
  The 9-digit ABA routing number of the account holder's bank.
</ResponseField>

<ResponseField name="account_number" type="string">
  The external account's bank account number.
</ResponseField>

<ResponseField name="status" type="string">
  The external account's current status. One of `active` or `archived`.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the external account
  was created.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "external_account_Bx5nTm8hKw3pVd7c",
    "entity_id": "entity_k7mXp2vR9nTfBw4s",
    "created_at": "2026-03-20T18:45:00Z",
    "nickname": "Quest Diagnostics Operating Account",
    "routing_number": "021000021",
    "account_number": "123456789",
    "status": "active"
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "External account not found"
  }
  ```
</ResponseExample>


# Get inbound ACH transfer
Source: https://getlemma.com/docs/api-reference/get-inbound-ach-transfer

GET /v0/inbound-ach-transfers/{inbound_ach_transfer_id}
Retrieve a single inbound ACH transfer by its ID.

Returns a single inbound ACH transfer object. Inbound ACHs can be credits (like a payment from an insurance company) or debits (like an ACH pull for payroll). Use the [outbound ACH transfer](/docs/api-reference/get-ach-transfer) endpoint for ACHs initiated inside Lemma.

## Path parameters

<ParamField type="string">
  The unique identifier of the inbound ACH transfer to retrieve.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the inbound ACH transfer.
</ResponseField>

<ResponseField name="account_id" type="string">
  The Lemma account the transfer moves money into or out of.
</ResponseField>

<ResponseField name="amount" type="integer">
  The transfer amount in cents. A positive amount indicates a credit pushed
  into the account. A negative amount indicates a debit pulled from the
  account.
</ResponseField>

<ResponseField name="status" type="string">
  Current status of the inbound ACH transfer.

  <Expandable title="possible values">
    * `pending` — awaiting action, will resolve automatically if none is taken.

    * `declined` — we declined the transfer.

    * `accepted` — the transfer was accepted.

    * `returned` — the transfer was returned.
  </Expandable>
</ResponseField>

<ResponseField name="standard_entry_class_code" type="string">
  The Standard Entry Class code for the transfer.
</ResponseField>

<ResponseField name="effective_date" type="string">
  The date the transfer is effective.
</ResponseField>

<ResponseField name="automatically_resolves_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer
  automatically resolves if we take no action.
</ResponseField>

<ResponseField name="originator_company_name" type="string">
  The name of the company or person that sent the transfer.
</ResponseField>

<ResponseField name="originator_company_entry_description" type="string">
  A description of the transfer set by the originator.
</ResponseField>

<ResponseField name="trace_number" type="string">
  A 15 digit number set by the sending bank; used with the amount and date to
  identify the transfer.
</ResponseField>

<ResponseField name="transaction_id" type="string | null">
  The settled transaction, once the transfer posts.
</ResponseField>

<ResponseField name="settled_at" type="string | null">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer
  settled.
</ResponseField>

<ResponseField name="accepted_at" type="string | null">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when we accepted the
  transfer.
</ResponseField>

<ResponseField name="declined" type="object | null">
  Decline details, if we declined the transfer.

  <Expandable title="Decline object">
    <ResponseField name="declined_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when we declined the
      transfer.
    </ResponseField>

    <ResponseField name="reason" type="string | null">
      Why the transfer was declined.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="returned" type="object | null">
  Return details, if the transfer was returned.

  <Expandable title="Return object">
    <ResponseField name="returned_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer was
      returned.
    </ResponseField>

    <ResponseField name="reason" type="string | null">
      Why the transfer was returned.
    </ResponseField>

    <ResponseField name="return_transaction_id" type="string | null">
      The transaction created when the transfer was returned.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="addenda" type="string[]">
  The raw freeform addenda lines carried by the transfer (for example the
  835/837 `TRN` and `REF` claim-payment segments), in the order the payer sent
  them. To reconcile a healthcare claim payment, match the TRN carried here
  against the TRN in your 835 ERA. Present only when the transfer includes
  addenda.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "inbound_ach_transfer_Wp5mRx3nKv8bTh2d",
    "account_id": "account_Rv4nBt8xKw2pMh6s",
    "amount": 12500,
    "status": "accepted",
    "standard_entry_class_code": "corporate_credit_or_debit",
    "effective_date": "2026-05-01",
    "automatically_resolves_at": "2026-05-02T00:00:00Z",
    "originator_company_name": "Acme Insurance",
    "originator_company_entry_description": "HCCLAIMPMT",
    "trace_number": "021000021000001",
    "transaction_id": "transaction_Ab5cDx3nKv8bTh2d",
    "settled_at": null,
    "accepted_at": "2026-05-01T12:00:00Z",
    "declined": null,
    "returned": null
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not Found",
    "message": "Inbound ACH transfer not found"
  }
  ```
</ResponseExample>


# Get PDF
Source: https://getlemma.com/docs/api-reference/get-pdf

GET /v0/files/{id}
Download a file.

Downloads a PDF. The response body is the raw file, not a JSON object.

This is useful for viewing the original scanned mail that a check arrived with — for example, to see the EOB or correspondence that accompanied a payment.

## Path parameters

<ParamField type="string">
  The ID of the file, prefixed with `file_`. You can find file IDs in responses
  from the [List entity mail](/docs/api-reference/list-entity-mail) endpoint.
</ParamField>

## Response

Returns the file as `application/pdf`, streamed inline with a `Content-Disposition: inline` header. The response is cacheable for 5 minutes (`Cache-Control: private, max-age=300`).

<ResponseExample>
  ```bash 200 theme={null}
  GET /v0/files/file_Xt7nRv3hBw9pKm4s

  Content-Type: application/pdf
  Content-Disposition: inline; filename="statement.pdf"

  <binary PDF data>
  ```
</ResponseExample>


# Get a remittance's 835 Electronic Remittance Advice (ERA)
Source: https://getlemma.com/docs/api-reference/get-remittance-era

GET /v0/remittances/{id}/era
Retrieve a remittance's electronic remittance advice as raw X12 835.

Returns the electronic remittance advice for a remittance as a raw X12 835 document. Use the `id` from [List remittances](/docs/api-reference/list-remittances); every listed remittance is ready to fetch.

The response body is the 835 in X12 wire format, served as `application/edi-x12`. Files conform to the HIPAA 5010 ASC X12 835 (Health Care Claim Payment and Remittance Advice) standard, governed by Technical Report Type 3 (TR3) identifier 005010X221. See the [official X12 specification](https://ecommerce.x12.org/products/health-care-claim-payment-advice-005010-x221) for details.

## Path parameters

<ParamField type="string">
  The remittance ID, as returned by [List remittances](/docs/api-reference/list-remittances).
</ParamField>

## Query parameters

<ParamField type="string">
  Pass `1` to receive the 835 as a file download (sets a `Content-Disposition` attachment header). Omit to receive it inline.
</ParamField>

## Response

The 835 document in X12 wire format.

<ResponseField name="body" type="string">
  The raw X12 835, with `~` segment terminators.
</ResponseField>

<Info>
  An ID with no servable 835 — unknown, still under review, or not yet materialized — returns 404. An ID belonging to an entity outside your granted scope returns 403.
</Info>

<ResponseExample>
  ```edi 200 theme={null}
  ISA*00* *00* *ZZ*LEMMA *ZZ*RECEIVER *260320*1200*^*00501*000000001*0*P*:~
  GS*HP*LEMMA*RECEIVER*20260320*1200*1*X*005010X221A1~
  ST*835*0001~
  BPR*I*1728*C*ACH*CCP*01*021000021*DA*9081726354*1512345678**01*104902114*DA*2200002222*20260320~
  TRN*1*EFT202603200042*1512345678~
  CLP*PATIENT001*1*2000*1728*272*12*EFT202603200042*11~
  SE*6*0001~
  GE*1*1~
  IEA*1*000000001~
  ```
</ResponseExample>


# Get transaction
Source: https://getlemma.com/docs/api-reference/get-transaction

GET /v0/transactions/{transaction_id}
Retrieve a single transaction by its ID.

Returns a single transaction object.

## Path parameters

<ParamField type="string">
  The unique identifier of the transaction to retrieve.
</ParamField>

## Response

<ResponseField name="id" type="string">
  Unique identifier for the transaction.
</ResponseField>

<ResponseField name="account_id" type="string">
  The ID of the bank account this transaction belongs to.
</ResponseField>

<ResponseField name="amount" type="integer">
  The transaction amount in cents. Positive for credits (money in), negative for
  debits (money out).
</ResponseField>

<ResponseField name="card_id" type="string | null">
  The ID of the card that produced this transaction. `null` for transactions
  that did not originate from a card.
</ResponseField>

<ResponseField name="occurred_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transaction
  occurred.
</ResponseField>

<ResponseField name="source" type="object">
  Information about the origin of the transaction.

  <Expandable title="Source object">
    <ResponseField name="category" type="string">
      The type of transaction source. We will add additional values for this
      enum over time; your application should be able to handle such additions
      gracefully. Not every transaction source will have additional details.
    </ResponseField>

    <ResponseField name="account_transfer_intention" type="object">
      <Expandable title="Account Transfer Intention object">
        <ResponseField name="description" type="string">
          The description given to this internal transfer between accounts.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="ach_transfer_intention" type="object">
      <Expandable title="ACH Transfer Intention object">
        <ResponseField name="statement_descriptor" type="string">
          The statement descriptor for this ACH transfer.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="ach_transfer_return" type="object">
      <Expandable title="ACH Transfer Return object">
        <ResponseField name="trace_number" type="string">
          The ACH trace number.
        </ResponseField>

        <ResponseField name="raw_return_reason_code" type="string">
          The raw return reason code.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="acquiring_card_payment" type="object">
      A payment received from a patient or payer via credit card.
    </ResponseField>

    <ResponseField name="acquiring_card_payment_fee" type="object">
      A fee charged for processing a card payment.
    </ResponseField>

    <ResponseField name="acquiring_chargeback" type="object">
      A chargeback dispute initiated by the cardholder.
    </ResponseField>

    <ResponseField name="acquiring_chargeback_fee" type="object">
      A fee charged by the card processor for handling a chargeback dispute.
    </ResponseField>

    <ResponseField name="acquiring_chargeback_reversal" type="object">
      A reversal of a chargeback that was previously filed by the cardholder.
    </ResponseField>

    <ResponseField name="acquiring_refund" type="object">
      A refund issued to a patient or payer who paid via credit card.
    </ResponseField>

    <ResponseField name="acquiring_refund_fee" type="object">
      A fee charged by the card processor for handling a refund.
    </ResponseField>

    <ResponseField name="card_authorization" type="object">
      <Expandable title="Card Authorization object">
        <ResponseField name="merchant_category_code" type="string">
          The merchant category code (MCC).
        </ResponseField>

        <ResponseField name="merchant_country" type="string">
          The merchant's country.
        </ResponseField>

        <ResponseField name="presentment_amount" type="string">
          The amount in the presentment currency.
        </ResponseField>

        <ResponseField name="presentment_currency" type="string">
          The presentment currency.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="card_financial" type="object">
      <Expandable title="Card Financial object">
        <ResponseField name="merchant_category_code" type="string">
          The merchant category code (MCC).
        </ResponseField>

        <ResponseField name="merchant_country" type="string">
          The merchant's country.
        </ResponseField>

        <ResponseField name="presentment_amount" type="string">
          The amount in the presentment currency.
        </ResponseField>

        <ResponseField name="presentment_currency" type="string">
          The presentment currency.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="card_refund" type="object">
      <Expandable title="Card Refund object">
        <ResponseField name="merchant_category_code" type="string">
          The merchant category code (MCC).
        </ResponseField>

        <ResponseField name="merchant_country" type="string">
          The merchant's country.
        </ResponseField>

        <ResponseField name="presentment_amount" type="string">
          The amount in the presentment currency.
        </ResponseField>

        <ResponseField name="presentment_currency" type="string">
          The presentment currency.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="card_settlement" type="object">
      <Expandable title="Card Settlement object">
        <ResponseField name="merchant_category_code" type="string">
          The merchant category code (MCC).
        </ResponseField>

        <ResponseField name="merchant_country" type="string">
          The merchant's country.
        </ResponseField>

        <ResponseField name="presentment_amount" type="string">
          The amount in the presentment currency.
        </ResponseField>

        <ResponseField name="presentment_currency" type="string">
          The presentment currency.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="check_deposit_acceptance" type="object">
      <Expandable title="Check Deposit Acceptance object">
        <ResponseField name="account_number" type="string">
          The check issuer's account number.
        </ResponseField>

        <ResponseField name="routing_number" type="string">
          The check issuer's routing number.
        </ResponseField>

        <ResponseField name="serial_number" type="string | null">
          The check number.
        </ResponseField>

        <ResponseField name="auxiliary_on_us" type="string | null">
          The auxiliary on-us field from the check.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="check_deposit_return" type="object">
      <Expandable title="Check Deposit Return object">
        <ResponseField name="return_reason" type="string">
          The reason the check deposit was returned.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="inbound_ach_transfer" type="object">
      <Expandable title="Inbound ACH Transfer object">
        <ResponseField name="trace_number" type="string">
          The ACH network trace number, assigned by the ACH network. To
          reconcile a healthcare claim payment, match on the TRN carried in
          `addenda` instead — the network trace is not known until after the
          payment is sent.
        </ResponseField>

        <ResponseField name="originator_company_name" type="string">
          The name of the originating company.
        </ResponseField>

        <ResponseField name="originator_company_id" type="string">
          The ID of the originating company.
        </ResponseField>

        <ResponseField name="originator_company_entry_description" type="string">
          The entry description set by the originator.
        </ResponseField>

        <ResponseField name="originator_company_descriptive_date" type="string | null">
          The descriptive date set by the originator.
        </ResponseField>

        <ResponseField name="originator_company_discretionary_data" type="string | null">
          Discretionary data set by the originator.
        </ResponseField>

        <ResponseField name="addenda" type="string[]">
          The raw freeform addenda lines carried by the transfer (for example
          the 835/837 `TRN` and `REF` claim-payment segments), in the order the
          payer sent them. To reconcile a healthcare claim payment, match the
          TRN carried here against the TRN in your 835 ERA. Present only when
          the transfer includes addenda.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="inbound_check_adjustment" type="object">
      <Expandable title="Inbound Check Adjustment object">
        <ResponseField name="reason" type="string">
          The reason for the check adjustment.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="inbound_real_time_payments_transfer_confirmation" type="object">
      <Expandable title="Inbound Real-Time Payments Transfer Confirmation object">
        <ResponseField name="debtor_name" type="string">
          The name of the sender.
        </ResponseField>

        <ResponseField name="creditor_name" type="string">
          The name of the creditor.
        </ResponseField>

        <ResponseField name="transaction_identification" type="string">
          The RTP transaction ID.
        </ResponseField>

        <ResponseField name="unstructured_remittance_information" type="string | null">
          Free-form remittance information.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="inbound_wire_reversal" type="object">
      <Expandable title="Inbound Wire Reversal object">
        <ResponseField name="input_message_accountability_data" type="string">
          The Fedwire input message accountability data (IMAD).
        </ResponseField>

        <ResponseField name="return_reason_code" type="string | null">
          The return reason code.
        </ResponseField>

        <ResponseField name="return_reason_additional_information" type="string | null">
          Additional information about the return reason.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="inbound_wire_transfer" type="object">
      <Expandable title="Inbound Wire Transfer object">
        <ResponseField name="input_message_accountability_data" type="string | null">
          The Fedwire input message accountability data (IMAD).
        </ResponseField>

        <ResponseField name="debtor_name" type="string | null">
          The name of the sender.
        </ResponseField>

        <ResponseField name="debtor_address_line1" type="string | null">
          The sender's address.
        </ResponseField>

        <ResponseField name="creditor_name" type="string | null">
          The name of the creditor.
        </ResponseField>

        <ResponseField name="unstructured_remittance_information" type="string | null">
          Free-form remittance information.
        </ResponseField>

        <ResponseField name="end_to_end_identification" type="string | null">
          The end-to-end ID.
        </ResponseField>

        <ResponseField name="unique_end_to_end_transaction_reference" type="string | null">
          The unique end-to-end transaction reference (UETR).
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="invoice_payment" type="object">
      A payment of an invoice between Lemma accounts.
    </ResponseField>

    <ResponseField name="lemma_adjustment" type="object">
      A manually initiated adjustment, including a fee charged or funds credited
      by Lemma.
    </ResponseField>

    <ResponseField name="lemma_customer_deposit_bonus" type="object">
      A deposit bonus credited by Lemma.
    </ResponseField>

    <ResponseField name="lemma_customer_fee" type="object">
      A fee charged by Lemma.
    </ResponseField>

    <ResponseField name="lemma_customer_spot_bonus" type="object">
      A one-off bonus credited by Lemma.
    </ResponseField>

    <ResponseField name="lemma_customer_subscription_fee" type="object">
      A recurring subscription fee charged by Lemma.
    </ResponseField>

    <ResponseField name="lemma_loan" type="object">
      A loan draw from or a payment toward a Lemma loan.
    </ResponseField>

    <ResponseField name="real_time_payments_transfer_acknowledgement" type="object">
      <Expandable title="Real-Time Payments Transfer Acknowledgement object">
        <ResponseField name="unstructured_remittance_information" type="string | null">
          Free-form remittance information.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="wire_transfer_intention" type="object">
      <Expandable title="Wire Transfer Intention object">
        <ResponseField name="message_to_recipient" type="string">
          The message to the recipient.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="counterparty" type="object | null">
  The other party in the transaction, if known.

  <Expandable title="Counterparty object">
    <ResponseField name="type" type="string">
      The kind of account the counterparty is. One of `bank_account`,
      `external_account`, or `fixed_fee_loan`.
    </ResponseField>

    <ResponseField name="bank_account" type="object | null">
      <Expandable title="Bank account object">
        <ResponseField name="id" type="string">
          The Lemma bank account ID of the other account in the transfer.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="external_account" type="object | null">
      <Expandable title="External account object">
        <ResponseField name="id" type="string">
          The [saved recipient](/docs/api-reference/saved-recipients) ID the money
          was sent to.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="fixed_fee_loan" type="object | null">
      <Expandable title="Fixed fee loan object">
        <ResponseField name="id" type="string">
          The Lemma fixed fee loan ID of the other account in the transfer.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "transaction_Wp5mRx3nKv8bTh2d",
    "account_id": "account_Rv4nBt8xKw2pMh6s",
    "amount": -325000,
    "card_id": null,
    "occurred_at": "2026-03-12T16:45:00Z",
    "source": {
      "category": "ach_transfer_intention"
    },
    "counterparty": {
      "type": "external_account",
      "external_account": {
        "id": "external_account_Bx5nTm8hKw3pVd7c"
      }
    }
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "error": "Not found",
    "message": "Transaction not found"
  }
  ```
</ResponseExample>


# Idempotency
Source: https://getlemma.com/docs/api-reference/idempotency

Safely retry requests without performing the same action twice.

Idempotency lets you retry a request without risk of performing the same action twice. This matters most for two kinds of requests: those that create a resource, such as saving an external account, and those that move money, such as an ACH transfer. If a network error interrupts either one, you can't always tell whether the server received it. Retrying with an idempotency key guarantees the action runs at most once.

## Using an idempotency key

An `Idempotency-Key` header is mandatory on every `POST` request. A request without one is rejected with an error.

A key must be between 10 and 256 characters long (inclusive) and may contain only letters, numbers, dashes (`-`), underscores (`_`), and colons (`:`). A request whose key is too short, too long, or includes any other character is rejected with an error.

Choose a key that stays the same across retries of the same action. The best key is a meaningful identifier from your own database, such as the ID of the payout or invoice the transfer settles. Reusing that identifier when you retry is what lets us recognize the retry and return the original result. You can pass a random version 4 UUID instead, but a new random key on each attempt provides no idempotency at all, because there is nothing for us to match against.

```bash theme={null}
curl https://api.getlemma.com/v0/ach-transfer \
  -H "Authorization: Bearer your_api_key" \
  -H "Idempotency-Key: payout_8f21c3a9" \
  -H "Content-Type: application/json" \
  -d '{
    "source_account_id": "account_Rv4nBt8xKw2pMh6s",
    "destination_external_account_id": "external_account_Bx5nTm8hKw3pVd7c",
    "amount": 150000
  }'
```

## How it works

The first request made with a given key is processed normally, and we store the key against the resource it created. Any later request that reuses the same key returns that resource without running the action again.

A replayed request returns the **latest state** of the resource, not a snapshot of the original response. If the resource has changed since the first call (for example, a transfer that has moved from `pending` to `completed`), the replay reflects that current state rather than what was returned the first time.

A response served this way includes an `Idempotency-Replayed: true` header so you can tell it apart from a freshly processed request.

Keys are stored permanently, so a replay works no matter how much time has passed.

## Retries

The reason to send an idempotency key is to retry safely when you can't tell whether we received the first request — a dropped connection or a timeout. When the outcome is unknown, retry with the same key. We resolve it one of three ways:

* The first request **succeeded**: we return the modified object's latest state and set `Idempotency-Replayed: true` in the header.
* The first request is **still in progress**: you get `409 Conflict`. Wait a moment and retry the same key.
* The first request **failed**: you get `500`, with a message that something went wrong on the previous request for this key.

A request you already know failed — you received an error response — should not be retried with the same key. Because we can't be certain a failed request had no effect, we never re-run it: the key is spent and keeps returning `500`. Use a **new** idempotency key to make a fresh attempt.

## One action per key

A key is bound to the endpoint it was first used on. Reusing it on a different endpoint returns `422 Unprocessable Entity`. Within the same endpoint we do not compare request bodies, so reusing a key returns the original resource even if you send a different body. Always use a distinct key for each distinct action so a changed request is never mistaken for a retry.

## Idempotency keys are mandatory

Every `POST` request requires an `Idempotency-Key`, and a request sent without one is rejected with an error. The endpoints where this protects you from costly duplicates include:

* [Move money externally](/docs/api-reference/move-money-externally): avoid sending the same ACH transfer twice
* [Move money internally](/docs/api-reference/move-money-internally): avoid duplicate internal transfers
* [Create external account](/docs/api-reference/create-external-account): avoid saving the same recipient twice

`GET` and `DELETE` requests are already idempotent and do not take the header. A repeated `DELETE` on an already-canceled card succeeds as a no-op, so retrying it can never perform the action twice.


# Introduction
Source: https://getlemma.com/docs/api-reference/introduction

The Lemma API allows platforms to programmatically interact with entity's accounts and reconciliation data.

<Note>
  The Lemma API is only available to approved platforms. To request access,
  reach out to the Lemma team at
  [contact@getlemma.com](mailto:contact@getlemma.com).
</Note>

The Lemma API is a REST API that returns JSON responses. It gives you read access to your bank accounts and transaction history so you can build integrations with your practice management software, accounting tools, or internal systems. It's also a good fit if you're building your own EHR for your business and want banking data available alongside your clinical workflows.

## Base URL

All API requests are made to:

```
https://api.getlemma.com/v0
```

## Request format

All requests must include an `Authorization` header with your API key. See [Authentication](/docs/api-reference/authentication) for details.

For endpoints that accept a request body (POST, PUT, PATCH), you must set the `Content-Type` header to `application/json`. Requests with a body that are missing this header will receive a `415 Unsupported Media Type` response. Every `POST` request must also include an `Idempotency-Key` header so you can safely retry it. Requests without one receive a `400` response. See [Idempotency](/docs/api-reference/idempotency) for how to choose a key.

```bash theme={null}
curl https://api.getlemma.com/v0/accounts \
  -H "Authorization: Bearer lm_key_your_api_key" \
  -H "Content-Type: application/json"
```

## Response format

Most responses are returned as `application/json`. The only exception is when the endpoint is returning a PDF or an 835 file.

List endpoints return a `data` array along with `meta` and `links` objects for [pagination](/docs/api-reference/pagination). Single-resource endpoints return a JSON object directly.

## Errors

The API returns standard HTTP status codes. Error responses include a `message` field.

```json Example error message theme={null}
{
  "message": "Account not found",
  "error": "Not found",
  "status": 404
}
```

| Status | Meaning                                                       |
| ------ | ------------------------------------------------------------- |
| 200    | Success                                                       |
| 400    | Bad request — check your parameters                           |
| 401    | Unauthorized — invalid or missing API key                     |
| 404    | Not found — the resource does not exist                       |
| 415    | Unsupported media type — set `Content-Type: application/json` |
| 429    | Too many requests — slow down and retry                       |
| 500    | Server error — try again later                                |

## Rate limits

The API allows up to **500 requests per minute** per API key. If you exceed this limit, you'll receive a `429` response. Wait and retry after a brief pause.

Need higher limits? [Contact us](mailto:contact@getlemma.com) and we're happy to increase them.

## Amounts

All monetary amounts are integers representing **cents**. For example, `150000` represents \$1,500.00.

## SDK

We are planning to ship a TypeScript SDK very soon. Message us if you're interested in an SDK for another language.


# List bank accounts
Source: https://getlemma.com/docs/api-reference/list-bank-accounts

GET /v0/accounts
Retrieve all bank accounts associated with a specific entity.

Returns a paginated list of bank accounts belonging to an entity. Results are
[paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField type="string">
  The ID of the entity. You can find entity IDs using the [List
  entities](/docs/api-reference/list-entities) endpoint.
</ParamField>

<ParamField type="integer">
  Maximum number of accounts to return per page. Maximum is 100.
</ParamField>

<ParamField type="string">
  Pagination cursor for retrieving the next page of results. Returned as
  `cursor` in the response. See [pagination](/docs/api-reference/pagination) for
  details.
</ParamField>

## Response

<ResponseField name="has_next" type="boolean">
  Whether more accounts exist beyond this page. Use the `cursor` field to
  retrieve the next page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Cursor to retrieve the next page of results. Null if this is the last page.
  Pass this value as the `cursor` query parameter in a subsequent request. See
  [pagination](/docs/api-reference/pagination) for details.
</ResponseField>

<ResponseField name="data" type="object[]">
  The list of account objects.

  <Expandable title="Account object">
    <ResponseField name="id" type="string">
      Unique identifier for the account, prefixed with `account_`.
    </ResponseField>

    <ResponseField name="entity_id" type="string">
      The ID of the entity that owns this account.
    </ResponseField>

    <ResponseField name="name" type="string">
      The name of the account.
    </ResponseField>

    <ResponseField name="account_number" type="string">
      The bank account number.
    </ResponseField>

    <ResponseField name="routing_number" type="string">
      The ABA routing number.
    </ResponseField>

    <ResponseField name="total_balance" type="integer">
      The total balance of the account in cents, including funds that are not
      yet available.
    </ResponseField>

    <ResponseField name="available_balance" type="integer">
      The balance available for use in cents. This excludes any held funds from
      pending transactions.
    </ResponseField>

    <ResponseField name="opened_at" type="string">
      The timestamp when the account was opened, in ISO 8601 format.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "account_Rv4nBt8xKw2pMh6s",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "name": "Operating Account",
        "account_number": "123456789",
        "routing_number": "021000021",
        "total_balance": 2450000,
        "available_balance": 2350000,
        "opened_at": "2026-01-15T09:30:00Z"
      },
      {
        "id": "account_Hn9wFj3cTd7yXk5v",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "name": "Collections Account",
        "account_number": "987654321",
        "routing_number": "021000021",
        "total_balance": 875430,
        "available_balance": 875430,
        "opened_at": "2026-02-20T14:00:00Z"
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List check deposits
Source: https://getlemma.com/docs/api-reference/list-check-deposits

GET /v0/check-deposits
Retrieve a paginated list of check deposits, optionally filtered by account.

Returns checks deposited into Lemma accounts, ordered by most recent first. Results are [paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField type="string">
  Filter check deposits to a specific bank account, prefixed with `account_`.
  You can find account IDs using the [List bank
  accounts](/docs/api-reference/list-bank-accounts) endpoint. Omit to list check
  deposits across every account you can access.
</ParamField>

<ParamField type="integer">
  The number of check deposits to return. Maximum is 100.
</ParamField>

<ParamField type="string">
  Cursor from the previous response. Omit to fetch from the beginning.
</ParamField>

## Response

<ResponseField name="data" type="object[]">
  The list of check deposit objects for the requested page.

  <Expandable title="Check deposit object">
    <ResponseField name="id" type="string">
      Unique identifier for the check deposit.
    </ResponseField>

    <ResponseField name="amount" type="integer">
      The check amount in cents.
    </ResponseField>

    <ResponseField name="status" type="string">
      The processing status of the check. One of `pending`, `submitted`, `returned`,
      or `rejected`.
    </ResponseField>

    <ResponseField name="transaction_id" type="string | null">
      The ID for the transaction created by the check deposit. Null if no
      transaction has been created yet.
    </ResponseField>

    <ResponseField name="inbound_mail_item_id" type="string | null">
      The mail item this check was found in. Null if the check was not received via
      lockbox mail.
    </ResponseField>

    <ResponseField name="hold" type="object | null">
      Fund hold details. Present when deposited funds are held before becoming
      available. Null if there is no hold.

      <Expandable title="Hold object">
        <ResponseField name="status" type="string">
          The hold status. One of `held` or `complete`.
        </ResponseField>

        <ResponseField name="automatically_releases_at" type="string">
          [ISO 8601](/docs/api-reference/timestamps) timestamp of when the hold will
          automatically release.
        </ResponseField>

        <ResponseField name="released_at" type="string | null">
          [ISO 8601](/docs/api-reference/timestamps) timestamp of when the hold was
          released. Null if the hold has not been released yet.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="return" type="object | null">
      Return details, if the check deposit was returned.

      <Expandable title="Return object">
        <ResponseField name="returned_at" type="string">
          [ISO 8601](/docs/api-reference/timestamps) timestamp of when the check deposit
          was returned.
        </ResponseField>

        <ResponseField name="reason" type="string | null">
          Why the check deposit was returned.
        </ResponseField>

        <ResponseField name="return_transaction_id" type="string | null">
          The transaction created when the check deposit was returned.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="micr" type="object | null">
      Fields read from the check's [MICR
      line](https://en.wikipedia.org/wiki/Magnetic_ink_character_recognition). Null
      when we have not submitted the check for deposit.

      <Expandable title="MICR object">
        <ResponseField name="routing_number" type="string">
          The routing number printed on the check.
        </ResponseField>

        <ResponseField name="account_number" type="string">
          The account number printed on the check.
        </ResponseField>

        <ResponseField name="auxiliary_on_us" type="string | null">
          An additional identifier from the MICR line. Business checks typically
          encode the check number here rather than in `serial_number`.
        </ResponseField>

        <ResponseField name="serial_number" type="string | null">
          The check number. For business checks, this may be null — look at
          `auxiliary_on_us` instead.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="has_next" type="boolean">
  Whether more check deposits exist after this page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Pass this value as `cursor` on the next request to fetch the following page.
  `null` when this is the last page.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "check_deposit_Tm6bXn9hRw3pFk7c",
        "amount": 100000,
        "status": "submitted",
        "transaction_id": "transaction_Ab5cDx3nKv8bTh2d",
        "inbound_mail_item_id": "inbound_mail_item_Kv7nWp3hTx9cBd5m",
        "hold": {
          "status": "held",
          "automatically_releases_at": "2026-03-19T14:00:00Z",
          "released_at": null
        },
        "return": null,
        "micr": {
          "routing_number": "021000021",
          "account_number": "9876543210",
          "auxiliary_on_us": null,
          "serial_number": "00012345"
        }
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List entities
Source: https://getlemma.com/docs/api-reference/list-entities

GET /v0/entities
Retrieve a list of entities available to your API key.

Retrieve a paginated list of entities associated with your organization. Use the
entity ID to access detailed information via the [Get entity](/docs/api-reference/get-entity),
[accounts](/docs/api-reference/list-bank-accounts), and [mail](/docs/api-reference/list-entity-mail)
endpoints. Results are [paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField type="integer">
  Maximum number of entities to return per page. Maximum is 100.
</ParamField>

<ParamField type="string">
  Pagination cursor for retrieving the next page of results. Returned as
  `cursor` in the response. See [pagination](/docs/api-reference/pagination) for
  details.
</ParamField>

## Response

<ResponseField name="has_next" type="boolean">
  Whether more entities exist beyond this page. Use the `cursor` field to
  retrieve the next page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Cursor to retrieve the next page of results. Null if this is the last page.
  Pass this value as the `cursor` query parameter in a subsequent request. See
  [pagination](/docs/api-reference/pagination) for details.
</ResponseField>

<ResponseField name="data" type="object[]">
  The list of entity objects. Each object carries the same fields as the [Get
  entity](/docs/api-reference/get-entity) response.

  <Expandable title="Entity object">
    <ResponseField name="id" type="string">
      Unique identifier for the entity, prefixed with `entity_`.
    </ResponseField>

    <ResponseField name="created_at" type="string">
      ISO 8601 timestamp of when the entity was created.
    </ResponseField>

    <ResponseField name="name" type="string">
      The name of the entity or practice.
    </ResponseField>

    <ResponseField name="structure" type="string">
      The entity's legal structure. One of `fqhc`, `govt`,
      `professional_corporation`, `professional_llc`, `professional_association`,
      `llc`, `corporation`, `partnership`, `sole_prop`, or `nonprofit`.
    </ResponseField>

    <ResponseField name="npi" type="string | null">
      The entity's 10-digit National Provider Identifier.
    </ResponseField>

    <ResponseField name="address" type="object">
      The entity's business address.

      <Expandable title="address">
        <ResponseField name="line1" type="string">
          Street address line 1.
        </ResponseField>

        <ResponseField name="line2" type="string">
          Street address line 2, or an empty string if not set.
        </ResponseField>

        <ResponseField name="city" type="string">
          City.
        </ResponseField>

        <ResponseField name="state" type="string">
          Two-letter state code.
        </ResponseField>

        <ResponseField name="postalCode" type="string">
          ZIP code.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "entity_k7mXp2vR9nTfBw4s",
        "created_at": "2026-07-01T09:30:00Z",
        "name": "Riverside Family Medicine",
        "structure": "professional_llc",
        "npi": "1234567890",
        "address": {
          "line1": "2261 Market St",
          "line2": "Ste 1234",
          "city": "San Francisco",
          "state": "CA",
          "postalCode": "94114"
        }
      },
      {
        "id": "entity_Yd3hNx8cWqJ5Fp7m",
        "created_at": "2026-07-01T14:12:00Z",
        "name": "Summit Orthopedics",
        "structure": "sole_prop",
        "npi": null,
        "address": {
          "line1": "500 Alpine Way",
          "line2": "",
          "city": "Denver",
          "state": "CO",
          "postalCode": "80202"
        }
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List entity mail
Source: https://getlemma.com/docs/api-reference/list-entity-mail

GET /v0/entities/{entity_id}/mail
Retrieve all lockbox mail for an entity.

Returns a list of all mail items received at the entity's lockbox. Each item includes a `file_id` for the scanned PDF and an `amount` representing the total value of any checks found in that piece of mail. If the mail contained checks, they are listed in the `checks` array.

## Path parameters

<ParamField type="string">
  The ID of the entity. You can find entity IDs using the [List
  entities](/docs/api-reference/list-entities) endpoint.
</ParamField>

## Query parameters

<ParamField type="integer">
  Maximum number of mail items to return per page. Default is 10, maximum is
  100\.
</ParamField>

<ParamField type="string">
  Pagination cursor for retrieving the next page of results. Returned as
  `cursor` in the response. See [pagination](/docs/api-reference/pagination) for
  details.
</ParamField>

<ParamField type="string">
  Return only mail received on or after this time. Accepts an [ISO
  8601](/docs/api-reference/timestamps) timestamp (`2026-09-01T12:00:00Z`) or a [bare
  date](/docs/api-reference/timestamps#date-only-values) (`2026-09-01`), which covers
  that whole UTC day. The bound is inclusive.
</ParamField>

<ParamField type="string">
  Return only mail received on or before this time. Same format and inclusivity
  as `received_on_or_after`.
</ParamField>

## Response

<ResponseField name="has_next" type="boolean">
  Whether more mail items exist beyond this page. Use the `cursor` field to
  retrieve the next page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Cursor to retrieve the next page of results. Null if this is the last page.
  Pass this value as the `cursor` query parameter in a subsequent request. See
  [pagination](/docs/api-reference/pagination) for details.
</ResponseField>

<ResponseField name="data" type="object[]">
  The list of mail objects.

  <Expandable title="Mail object">
    <ResponseField name="id" type="string">
      Unique identifier for the lockbox mail item.
    </ResponseField>

    <ResponseField name="entity_id" type="string">
      The ID of the entity whose lockbox received this mail.
    </ResponseField>

    <ResponseField name="file_id" type="string | null">
      The ID of the scanned PDF, prefixed with `file_`. Use the [Get
      PDF](/docs/api-reference/get-pdf) endpoint to download it. Null if the mail
      item has not been scanned yet.
    </ResponseField>

    <ResponseField name="amount" type="integer">
      The total value of all checks in this piece of mail, in cents. Zero if no
      checks were found.
    </ResponseField>

    <ResponseField name="checks" type="object[]">
      The checks found in this piece of mail. Empty array if no checks were
      found.

      <Expandable title="Check object">
        <ResponseField name="id" type="string">
          Unique identifier for the check, prefixed with `check_deposit_`.
        </ResponseField>

        <ResponseField name="amount" type="integer">
          The amount of the check in cents.
        </ResponseField>

        <ResponseField name="transaction_id" type="string | null">
          The ID for the transaction created by the check deposit. Null if the
          check is pending manual intervention.
        </ResponseField>

        <ResponseField name="status" type="string">
          The processing status of the check. One of `pending`, `submitted`, `returned`, or `rejected`.

          **Pending** means Lemma has not attempted to deposit the check yet.

          **Submitted** means the check has been submitted for deposit. There will be a hold on the funds for a few days.

          **Returned** checks are unlikely to happen to healthcare practices receiving funds from payers. Nevertheless, here are a few common reasons checks are returned:

          * Insufficient funds
          * Stop payment instructions
          * The check was drawn from a closed bank account
          * The check was not authorized

          We'll reach out if a check is returned to share additional details.

          **Rejected** checks are rare. We reject checks if it's impossible to deposit the check after a manual review. For example, a payer could've sent you another entity's check. You can use the [Get PDF](/docs/api-reference/get-pdf) endpoint to see for yourself why the check was unrelated to your account.
        </ResponseField>

        <ResponseField name="hold" type="object | null">
          Fund hold details. Present when deposited funds are held before becoming available. Null if there is no hold.

          <Expandable title="Hold object">
            <ResponseField name="status" type="string">
              The hold status. One of `held` or `complete`.
            </ResponseField>

            <ResponseField name="automatically_releases_at" type="string">
              [ISO 8601](/docs/api-reference/timestamps) timestamp of when the hold will automatically release.
            </ResponseField>

            <ResponseField name="released_at" type="string | null">
              [ISO 8601](/docs/api-reference/timestamps) timestamp of when the hold was released. Null if the hold has not been released yet.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="micr" type="object | null">
          Fields read from the check's [MICR line](https://en.wikipedia.org/wiki/Magnetic_ink_character_recognition). Null when we have not submitted the check for deposit.

          <Expandable title="MICR object">
            <ResponseField name="routing_number" type="string">
              The routing number printed on the check.
            </ResponseField>

            <ResponseField name="account_number" type="string">
              The account number printed on the check.
            </ResponseField>

            <ResponseField name="auxiliary_on_us" type="string | null">
              An additional identifier from the MICR line. Business checks typically encode the check number here rather than in `serial_number`.
            </ResponseField>

            <ResponseField name="serial_number" type="string | null">
              The check number. For business checks, this may be null — look at `auxiliary_on_us` instead.
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="received_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the mail was
      received at the lockbox.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "inbound_mail_item_Kv7nWp3hTx9cBd5m",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "file_id": "file_Xt7nRv3hBw9pKm4s",
        "amount": 372500,
        "checks": [
          {
            "id": "check_deposit_Tm6bXn9hRw3pFk7c",
            "amount": 100000,
            "transaction_id": "transaction_Ab5cDx3nKv8bTh2d",
            "status": "submitted",
            "hold": {
              "status": "held",
              "automatically_releases_at": "2026-03-19T14:00:00Z",
              "released_at": null
            },
            "micr": {
              "routing_number": "021000021",
              "account_number": "9876543210",
              "auxiliary_on_us": null,
              "serial_number": "00012345"
            }
          },
          {
            "id": "check_deposit_Jd4xVs8mBn2wYh5t",
            "amount": 2000,
            "transaction_id": null,
            "status": "rejected",
            "hold": null,
            "micr": null
          }
        ],
        "received_at": "2026-03-14T14:00:00Z"
      },
      {
        "id": "inbound_mail_item_Rs4bFj8wNm2yHt6x",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "file_id": "file_Hd5cWm8nTx2vFk7b",
        "amount": 0,
        "checks": [],
        "received_at": "2026-03-13T10:45:00Z"
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List external accounts
Source: https://getlemma.com/docs/api-reference/list-external-accounts

GET /v0/external-accounts
Retrieve saved external accounts for an entity.

Returns a paginated list of saved external accounts for an entity, ordered by
most recent first. Results are [paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField type="string">
  The ID of the entity whose external accounts to list. You can find entity IDs
  using the [List entities](/docs/api-reference/list-entities) endpoint.
</ParamField>

<ParamField type="integer">
  Maximum number of external accounts to return per page. Maximum is 100.
</ParamField>

<ParamField type="string">
  Pagination cursor for retrieving the next page of results. Returned as
  `cursor` in the response. See [pagination](/docs/api-reference/pagination) for
  details.
</ParamField>

## Response

<ResponseField name="has_next" type="boolean">
  Whether more external accounts exist beyond this page. Use the `cursor` field
  to retrieve the next page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Cursor to retrieve the next page of results. Null if this is the last page.
  Pass this value as the `cursor` query parameter in a subsequent request. See
  [pagination](/docs/api-reference/pagination) for details.
</ResponseField>

<ResponseField name="data" type="object[]">
  The list of external account objects.

  <Expandable title="External account object">
    <ResponseField name="id" type="string">
      Unique identifier for the external account, prefixed with
      `external_account_`.
    </ResponseField>

    <ResponseField name="entity_id" type="string">
      The ID of the entity that owns this external account.
    </ResponseField>

    <ResponseField name="nickname" type="string">
      The human-readable label for this external account.
    </ResponseField>

    <ResponseField name="created_at" type="string">
      The timestamp when the external account was created, in ISO 8601 format.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "external_account_Hd9vWs4mFn7xYk2t",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "created_at": "2026-03-20T18:45:00Z",
        "nickname": "Owner's Account"
      },
      {
        "id": "external_account_Bx5nTm8hKw3pVd7c",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "created_at": "2026-03-19T18:45:00Z",
        "nickname": "Payroll"
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List inbound ACH transfers
Source: https://getlemma.com/docs/api-reference/list-inbound-ach-transfers

GET /v0/inbound-ach-transfers
Retrieve a paginated list of inbound ACH transfers, optionally filtered by account.

Returns inbound ACH transfers ordered by most recent first. Results are [paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField type="string">
  Filter inbound ACH transfers to a specific bank account, prefixed with
  `account_`. You can find account IDs using the [List bank
  accounts](/docs/api-reference/list-bank-accounts) endpoint. Omit to list inbound
  ACH transfers across every account you can access.
</ParamField>

<ParamField type="integer">
  The number of inbound ACH transfers to return. Maximum is 100.
</ParamField>

<ParamField type="string">
  Cursor from the previous response. Omit to fetch from the beginning.
</ParamField>

## Response

<ResponseField name="data" type="object[]">
  The list of inbound ACH transfer objects for the requested page.

  <Expandable title="Inbound ACH transfer object">
    <ResponseField name="id" type="string">
      Unique identifier for the inbound ACH transfer.
    </ResponseField>

    <ResponseField name="account_id" type="string">
      The Lemma account the transfer moves money into or out of.
    </ResponseField>

    <ResponseField name="amount" type="integer">
      The transfer amount in cents. A positive amount indicates a credit pushed
      into the account. A negative amount indicates a debit pulled from the
      account.
    </ResponseField>

    <ResponseField name="status" type="string">
      Current status of the inbound ACH transfer.

      <Expandable title="possible values">
        * `pending` — awaiting action, will resolve automatically if none is taken.

        * `declined` — we declined the transfer.

        * `accepted` — the transfer was accepted.

        * `returned` — the transfer was returned.
      </Expandable>
    </ResponseField>

    <ResponseField name="standard_entry_class_code" type="string">
      The Standard Entry Class code for the transfer.
    </ResponseField>

    <ResponseField name="effective_date" type="string">
      The date the transfer is effective.
    </ResponseField>

    <ResponseField name="automatically_resolves_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer
      automatically resolves if we take no action.
    </ResponseField>

    <ResponseField name="originator_company_name" type="string">
      The name of the company or person that sent the transfer.
    </ResponseField>

    <ResponseField name="originator_company_entry_description" type="string">
      A description of the transfer set by the originator.
    </ResponseField>

    <ResponseField name="trace_number" type="string">
      A 15 digit number set by the sending bank; used with the amount and date to
      identify the transfer.
    </ResponseField>

    <ResponseField name="transaction_id" type="string | null">
      The settled transaction, once the transfer posts.
    </ResponseField>

    <ResponseField name="settled_at" type="string | null">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer
      settled.
    </ResponseField>

    <ResponseField name="accepted_at" type="string | null">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when we accepted the
      transfer.
    </ResponseField>

    <ResponseField name="declined" type="object | null">
      Decline details, if we declined the transfer.

      <Expandable title="Decline object">
        <ResponseField name="declined_at" type="string">
          [ISO 8601](/docs/api-reference/timestamps) timestamp of when we declined the
          transfer.
        </ResponseField>

        <ResponseField name="reason" type="string | null">
          Why the transfer was declined.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="returned" type="object | null">
      Return details, if the transfer was returned.

      <Expandable title="Return object">
        <ResponseField name="returned_at" type="string">
          [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer was
          returned.
        </ResponseField>

        <ResponseField name="reason" type="string | null">
          Why the transfer was returned.
        </ResponseField>

        <ResponseField name="return_transaction_id" type="string | null">
          The transaction created when the transfer was returned.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="addenda" type="string[]">
      The raw freeform addenda lines carried by the transfer (for example the
      835/837 `TRN` and `REF` claim-payment segments), in the order the payer sent
      them. To reconcile a healthcare claim payment, match the TRN carried here
      against the TRN in your 835 ERA. Present only when the transfer includes
      addenda.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="has_next" type="boolean">
  Whether more inbound ACH transfers exist after this page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Pass this value as `cursor` on the next request to fetch the following page.
  `null` when this is the last page.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "inbound_ach_transfer_Wp5mRx3nKv8bTh2d",
        "account_id": "account_Rv4nBt8xKw2pMh6s",
        "amount": 12500,
        "status": "accepted",
        "standard_entry_class_code": "corporate_credit_or_debit",
        "effective_date": "2026-05-01",
        "automatically_resolves_at": "2026-05-02T00:00:00Z",
        "originator_company_name": "Acme Insurance",
        "originator_company_entry_description": "HCCLAIMPMT",
        "trace_number": "021000021000001",
        "transaction_id": "transaction_Ab5cDx3nKv8bTh2d",
        "settled_at": null,
        "accepted_at": "2026-05-01T12:00:00Z",
        "declined": null,
        "returned": null
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List remittances
Source: https://getlemma.com/docs/api-reference/list-remittances

GET /v0/remittances
Retrieve an entity's remittances and whether an 835 is available for each.

Returns a paginated list of an entity's remittances, ordered by most recently
updated first. Only remittances derived from an electronic remittance advice —
those an 835 can be generated from — are returned. Results are
[paginated](/docs/api-reference/pagination).

Each remittance exposes whether its 835 is currently available. Fetch the 835
itself with [Fetch a remittance's 835](/docs/api-reference/get-remittance-era).

## Query parameters

<ParamField type="string">
  The ID of the entity whose remittances to list. You can find entity IDs using
  the [List entities](/docs/api-reference/list-entities) endpoint.
</ParamField>

<ParamField type="string">
  Return only remittances updated at or after this timestamp (ISO 8601). Pass
  the largest `updated_at` you have already seen to poll for changes
  incrementally.
</ParamField>

<ParamField type="string">
  Return only remittances with a remittance date on or after this date
  (YYYY-MM-DD).
</ParamField>

<ParamField type="string">
  Return only remittances with a remittance date on or before this date
  (YYYY-MM-DD).
</ParamField>

<ParamField type="string">
  Return only remittances whose payer name contains this text.
</ParamField>

<ParamField type="integer">
  Maximum number of remittances to return per page. Maximum is 100.
</ParamField>

<ParamField type="string">
  Pagination cursor for retrieving the next page of results. Returned as
  `cursor` in the response. See [pagination](/docs/api-reference/pagination) for
  details.
</ParamField>

## Response

<ResponseField name="data" type="object[]">
  The list of remittance objects.

  <Expandable title="Remittance object">
    <ResponseField name="id" type="string">
      Stable remittance identifier. Pass it to [Fetch a remittance's
      835](/docs/api-reference/get-remittance-era) to retrieve the 835.
    </ResponseField>

    <ResponseField name="entity_id" type="string">
      The ID of the entity the remittance belongs to.
    </ResponseField>

    <ResponseField name="payer_name" type="string | null">
      Payer name as it appears on the remittance.
    </ResponseField>

    <ResponseField name="payment" type="object">
      Payment-level details for the remittance.

      <Expandable title="payment">
        <ResponseField name="amount" type="integer | null">
          Total paid amount, in cents.
        </ResponseField>

        <ResponseField name="trace_number" type="string | null">
          Check or EFT trace number.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="remittance_date" type="string | null">
      Date the remittance was received, as a calendar date (YYYY-MM-DD).
    </ResponseField>
  </Expandable>
</ResponseField>

<Info>
  Only remittances whose 835 is ready to serve are listed, so every `id` here
  resolves on [Fetch a remittance's 835](/docs/api-reference/get-remittance-era).
</Info>

<ResponseField name="has_next" type="boolean">
  Whether more remittances exist beyond this page. Use the `cursor` field to
  retrieve the next page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Cursor to retrieve the next page of results. Null if this is the last page.
  Pass this value as the `cursor` query parameter in a subsequent request. See
  [pagination](/docs/api-reference/pagination) for details.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "remittance_DrE8uykrS8bg",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "payer_name": "Cigna",
        "payment": { "amount": 172800, "trace_number": "EFT202603200042" },
        "remittance_date": "2026-03-20"
      },
      {
        "id": "remittance_Qw3Zmn7Ht2Lp",
        "entity_id": "entity_k7mXp2vR9nTfBw4s",
        "payer_name": "United Health",
        "payment": { "amount": 45200, "trace_number": null },
        "remittance_date": "2026-03-18"
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


# List transactions
Source: https://getlemma.com/docs/api-reference/list-transactions

GET /v0/transactions
Retrieve a paginated list of transactions for a bank account.

Returns transactions ordered by most recent first. Results are [paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField type="string">
  Filter transactions to a specific bank account, prefixed with `account_`. You
  can find account IDs using the [List bank
  accounts](/docs/api-reference/list-bank-accounts) endpoint.
</ParamField>

<ParamField type="string">
  Return only transactions whose `occurred_at` is on or after this time. Accepts
  an [ISO 8601](/docs/api-reference/timestamps) timestamp (`2026-09-01T12:00:00Z`) or
  a [bare date](/docs/api-reference/timestamps#date-only-values) (`2026-09-01`),
  which covers that whole UTC day. The bound is inclusive.
</ParamField>

<ParamField type="string">
  Return only transactions whose `occurred_at` is on or before this time. Same
  format and inclusivity as `occurred_on_or_after`.
</ParamField>

<ParamField type="integer">
  The number of transactions to return. Maximum is 100.
</ParamField>

<ParamField type="string">
  Cursor from the previous response. Omit to fetch from the beginning.
</ParamField>

## Response

<ResponseField name="data" type="object[]">
  The list of transaction objects for the requested page.

  <Expandable title="Transaction object">
    <ResponseField name="id" type="string">
      Unique identifier for the transaction.
    </ResponseField>

    <ResponseField name="account_id" type="string">
      The ID of the bank account this transaction belongs to.
    </ResponseField>

    <ResponseField name="amount" type="integer">
      The transaction amount in cents. Positive for credits (money in), negative
      for debits (money out).
    </ResponseField>

    <ResponseField name="card_id" type="string | null">
      The ID of the card that produced this transaction. `null` for transactions
      that did not originate from a card.
    </ResponseField>

    <ResponseField name="occurred_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transaction
      occurred.
    </ResponseField>

    <ResponseField name="source" type="object">
      Information about the origin of the transaction.

      <Expandable title="Source object">
        <ResponseField name="category" type="string">
          The type of transaction source. We will add additional values for this
          enum over time; your application should be able to handle such additions
          gracefully. Not every transaction source will have additional details.
        </ResponseField>

        <ResponseField name="account_transfer_intention" type="object">
          <Expandable title="Account Transfer Intention object">
            <ResponseField name="description" type="string">
              The description given to this internal transfer between accounts.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="ach_transfer_intention" type="object">
          <Expandable title="ACH Transfer Intention object">
            <ResponseField name="statement_descriptor" type="string">
              The statement descriptor for this ACH transfer.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="ach_transfer_return" type="object">
          <Expandable title="ACH Transfer Return object">
            <ResponseField name="trace_number" type="string">
              The ACH trace number.
            </ResponseField>

            <ResponseField name="raw_return_reason_code" type="string">
              The raw return reason code.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="acquiring_card_payment" type="object">
          A payment received from a patient or payer via credit card.
        </ResponseField>

        <ResponseField name="acquiring_card_payment_fee" type="object">
          A fee charged for processing a card payment.
        </ResponseField>

        <ResponseField name="acquiring_chargeback" type="object">
          A chargeback dispute initiated by the cardholder.
        </ResponseField>

        <ResponseField name="acquiring_chargeback_fee" type="object">
          A fee charged by the card processor for handling a chargeback dispute.
        </ResponseField>

        <ResponseField name="acquiring_chargeback_reversal" type="object">
          A reversal of a chargeback that was previously filed by the cardholder.
        </ResponseField>

        <ResponseField name="acquiring_refund" type="object">
          A refund issued to a patient or payer who paid via credit card.
        </ResponseField>

        <ResponseField name="acquiring_refund_fee" type="object">
          A fee charged by the card processor for handling a refund.
        </ResponseField>

        <ResponseField name="card_authorization" type="object">
          <Expandable title="Card Authorization object">
            <ResponseField name="merchant_category_code" type="string">
              The merchant category code (MCC).
            </ResponseField>

            <ResponseField name="merchant_country" type="string">
              The merchant's country.
            </ResponseField>

            <ResponseField name="presentment_amount" type="string">
              The amount in the presentment currency.
            </ResponseField>

            <ResponseField name="presentment_currency" type="string">
              The presentment currency.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="card_financial" type="object">
          <Expandable title="Card Financial object">
            <ResponseField name="merchant_category_code" type="string">
              The merchant category code (MCC).
            </ResponseField>

            <ResponseField name="merchant_country" type="string">
              The merchant's country.
            </ResponseField>

            <ResponseField name="presentment_amount" type="string">
              The amount in the presentment currency.
            </ResponseField>

            <ResponseField name="presentment_currency" type="string">
              The presentment currency.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="card_refund" type="object">
          <Expandable title="Card Refund object">
            <ResponseField name="merchant_category_code" type="string">
              The merchant category code (MCC).
            </ResponseField>

            <ResponseField name="merchant_country" type="string">
              The merchant's country.
            </ResponseField>

            <ResponseField name="presentment_amount" type="string">
              The amount in the presentment currency.
            </ResponseField>

            <ResponseField name="presentment_currency" type="string">
              The presentment currency.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="card_settlement" type="object">
          <Expandable title="Card Settlement object">
            <ResponseField name="merchant_category_code" type="string">
              The merchant category code (MCC).
            </ResponseField>

            <ResponseField name="merchant_country" type="string">
              The merchant's country.
            </ResponseField>

            <ResponseField name="presentment_amount" type="string">
              The amount in the presentment currency.
            </ResponseField>

            <ResponseField name="presentment_currency" type="string">
              The presentment currency.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="check_deposit_acceptance" type="object">
          <Expandable title="Check Deposit Acceptance object">
            <ResponseField name="account_number" type="string">
              The check issuer's account number.
            </ResponseField>

            <ResponseField name="routing_number" type="string">
              The check issuer's routing number.
            </ResponseField>

            <ResponseField name="serial_number" type="string | null">
              The check number.
            </ResponseField>

            <ResponseField name="auxiliary_on_us" type="string | null">
              The auxiliary on-us field from the check.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="check_deposit_return" type="object">
          <Expandable title="Check Deposit Return object">
            <ResponseField name="return_reason" type="string">
              The reason the check deposit was returned.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="inbound_ach_transfer" type="object">
          <Expandable title="Inbound ACH Transfer object">
            <ResponseField name="trace_number" type="string">
              The ACH network trace number, assigned by the ACH network. To
              reconcile a healthcare claim payment, match on the TRN carried in
              `addenda` instead — the network trace is not known until after the
              payment is sent.
            </ResponseField>

            <ResponseField name="originator_company_name" type="string">
              The name of the originating company.
            </ResponseField>

            <ResponseField name="originator_company_id" type="string">
              The ID of the originating company.
            </ResponseField>

            <ResponseField name="originator_company_entry_description" type="string">
              The entry description set by the originator.
            </ResponseField>

            <ResponseField name="originator_company_descriptive_date" type="string | null">
              The descriptive date set by the originator.
            </ResponseField>

            <ResponseField name="originator_company_discretionary_data" type="string | null">
              Discretionary data set by the originator.
            </ResponseField>

            <ResponseField name="addenda" type="string[]">
              The raw freeform addenda lines carried by the transfer (for example
              the 835/837 `TRN` and `REF` claim-payment segments), in the order the
              payer sent them. To reconcile a healthcare claim payment, match the
              TRN carried here against the TRN in your 835 ERA. Present only when
              the transfer includes addenda.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="inbound_check_adjustment" type="object">
          <Expandable title="Inbound Check Adjustment object">
            <ResponseField name="reason" type="string">
              The reason for the check adjustment.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="inbound_real_time_payments_transfer_confirmation" type="object">
          <Expandable title="Inbound Real-Time Payments Transfer Confirmation object">
            <ResponseField name="debtor_name" type="string">
              The name of the sender.
            </ResponseField>

            <ResponseField name="creditor_name" type="string">
              The name of the creditor.
            </ResponseField>

            <ResponseField name="transaction_identification" type="string">
              The RTP transaction ID.
            </ResponseField>

            <ResponseField name="unstructured_remittance_information" type="string | null">
              Free-form remittance information.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="inbound_wire_reversal" type="object">
          <Expandable title="Inbound Wire Reversal object">
            <ResponseField name="input_message_accountability_data" type="string">
              The Fedwire input message accountability data (IMAD).
            </ResponseField>

            <ResponseField name="return_reason_code" type="string | null">
              The return reason code.
            </ResponseField>

            <ResponseField name="return_reason_additional_information" type="string | null">
              Additional information about the return reason.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="inbound_wire_transfer" type="object">
          <Expandable title="Inbound Wire Transfer object">
            <ResponseField name="input_message_accountability_data" type="string | null">
              The Fedwire input message accountability data (IMAD).
            </ResponseField>

            <ResponseField name="debtor_name" type="string | null">
              The name of the sender.
            </ResponseField>

            <ResponseField name="debtor_address_line1" type="string | null">
              The sender's address.
            </ResponseField>

            <ResponseField name="creditor_name" type="string | null">
              The name of the creditor.
            </ResponseField>

            <ResponseField name="unstructured_remittance_information" type="string | null">
              Free-form remittance information.
            </ResponseField>

            <ResponseField name="end_to_end_identification" type="string | null">
              The end-to-end ID.
            </ResponseField>

            <ResponseField name="unique_end_to_end_transaction_reference" type="string | null">
              The unique end-to-end transaction reference (UETR).
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="invoice_payment" type="object">
          A payment of an invoice between Lemma accounts.
        </ResponseField>

        <ResponseField name="lemma_adjustment" type="object">
          A manually initiated adjustment, including a fee charged or funds credited
          by Lemma.
        </ResponseField>

        <ResponseField name="lemma_customer_deposit_bonus" type="object">
          A deposit bonus credited by Lemma.
        </ResponseField>

        <ResponseField name="lemma_customer_fee" type="object">
          A fee charged by Lemma.
        </ResponseField>

        <ResponseField name="lemma_customer_spot_bonus" type="object">
          A one-off bonus credited by Lemma.
        </ResponseField>

        <ResponseField name="lemma_customer_subscription_fee" type="object">
          A recurring subscription fee charged by Lemma.
        </ResponseField>

        <ResponseField name="lemma_loan" type="object">
          A loan draw from or a payment toward a Lemma loan.
        </ResponseField>

        <ResponseField name="real_time_payments_transfer_acknowledgement" type="object">
          <Expandable title="Real-Time Payments Transfer Acknowledgement object">
            <ResponseField name="unstructured_remittance_information" type="string | null">
              Free-form remittance information.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="wire_transfer_intention" type="object">
          <Expandable title="Wire Transfer Intention object">
            <ResponseField name="message_to_recipient" type="string">
              The message to the recipient.
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="counterparty" type="object | null">
      The other party in the transaction, if known.

      <Expandable title="Counterparty object">
        <ResponseField name="type" type="string">
          The kind of account the counterparty is. One of `bank_account`,
          `external_account`, or `fixed_fee_loan`.
        </ResponseField>

        <ResponseField name="bank_account" type="object | null">
          <Expandable title="Bank account object">
            <ResponseField name="id" type="string">
              The Lemma bank account ID of the other account in the transfer.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="external_account" type="object | null">
          <Expandable title="External account object">
            <ResponseField name="id" type="string">
              The [saved recipient](/docs/api-reference/saved-recipients) ID the
              money was sent to.
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="fixed_fee_loan" type="object | null">
          <Expandable title="Fixed fee loan object">
            <ResponseField name="id" type="string">
              The Lemma fixed fee loan ID of the other account in the transfer.
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="has_next" type="boolean">
  Whether more transactions exist after this page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Pass this value as `cursor` on the next request to fetch the following page.
  `null` when this is the last page.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "transaction_Wp5mRx3nKv8bTh2d",
        "account_id": "account_Rv4nBt8xKw2pMh6s",
        "amount": 325000,
        "card_id": null,
        "occurred_at": "2026-03-12T16:45:00Z",
        "source": {
          "category": "lemma_customer_deposit_bonus"
        },
        "counterparty": null
      },
      {
        "id": "transaction_Fy7cNw4hBk9tXj6s",
        "account_id": "account_Rv4nBt8xKw2pMh6s",
        "amount": -150000,
        "card_id": null,
        "occurred_at": "2026-03-11T10:20:00Z",
        "source": {
          "category": "ach_transfer_intention"
        },
        "counterparty": {
          "type": "external_account",
          "external_account": {
            "id": "external_account_Bx5nTm8hKw3pVd7c"
          }
        }
      },
      {
        "id": "transaction_Km2vRt6qCd9wLp4x",
        "account_id": "account_Rv4nBt8xKw2pMh6s",
        "amount": -8750,
        "card_id": "card_Nx8jQw2mVt5hRb3k",
        "occurred_at": "2026-03-10T09:15:00Z",
        "source": {
          "category": "card_settlement",
          "card_settlement": {
            "merchant_category_code": "5812",
            "merchant_country": "US",
            "presentment_amount": -8750,
            "presentment_currency": "USD"
          }
        },
        "counterparty": null
      }
    ],
    "has_next": true,
    "cursor": "eyJvY2N1cmVkX2F0IjoiMjAyNi0wMy0xMVQxMDoyMDowMFoiLCJpZCI6InRyYW5zYWN0aW9uX0Z5N2NOdzRoQms5dFhqNnMifQ"
  }
  ```
</ResponseExample>


# Move money externally
Source: https://getlemma.com/docs/api-reference/move-money-externally

POST /v0/ach-transfer
Send money to a saved external account.

Creates a transfer from a Lemma account to a [saved recipient](/docs/api-reference/saved-recipients) — an external bank account registered in Lemma. External transfers are sent via ACH and typically settle within 1-2 business days.

<Info>
  Transfers over \$100,000 are held for manual review by the Lemma team as a
  security measure to protect your accounts in the event of a compromised API
  key. Need higher limits? [Contact us](mailto:contact@getlemma.com).
</Info>

## Headers

<ParamField type="string">
  A key that lets you safely retry the request without sending the same ACH
  transfer more than once. See [Idempotency](/docs/api-reference/idempotency).
</ParamField>

## Request body

<ParamField type="string">
  The ID of the Lemma account to send money from.
</ParamField>

<ParamField type="string">
  The ID of a [saved recipient](/docs/api-reference/saved-recipients). You cannot
  send money to an arbitrary bank account — it must be a pre-registered
  recipient belonging to your entity.
</ParamField>

<ParamField type="integer">
  The amount to transfer in cents. Must be greater than zero.
</ParamField>

<ParamField type="string">
  A description for the transfer. Appears on the sender's transaction history.
</ParamField>

## Response

Returns the created ACH transfer object.

<ResponseField name="id" type="string">
  Unique identifier for the ACH transfer.
</ResponseField>

<ResponseField name="account_id" type="string">
  The Lemma account the transfer moves money from or to.
</ResponseField>

<ResponseField name="external_account_id" type="string | null">
  The [external account](/docs/api-reference/saved-recipients) on the other side of
  the transfer.
</ResponseField>

<ResponseField name="amount" type="integer">
  The transfer amount in cents. A positive amount indicates a credit transfer
  pushing funds to the receiving account. A negative amount indicates a debit
  transfer pulling funds from the receiving account (an ACH pull).
</ResponseField>

<ResponseField name="status" type="string">
  Current status of the ACH transfer.

  <Expandable title="possible values">
    * `pending` — in flight.

    * `submitted` — sent to the ACH network. When the Federal Reserve settles the transfer, the status stays `submitted` and `settled_at` is populated.

    * `canceled` — we canceled the transfer after holding it for manual review.

    * `rejected` — the ACH network rejected the transfer.

    * `returned` — the transfer was returned.
  </Expandable>
</ResponseField>

<ResponseField name="statement_descriptor" type="string">
  The statement descriptor shown to the counterparty.
</ResponseField>

<ResponseField name="transaction_id" type="string | null">
  The settled transaction, once the transfer posts.
</ResponseField>

<ResponseField name="settled_at" type="string | null">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer settled.
</ResponseField>

<ResponseField name="submission" type="object | null">
  Submission details, once the transfer reaches the ACH network.

  <Expandable title="Submission object">
    <ResponseField name="submitted_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the transfer was
      submitted to the ACH network.
    </ResponseField>

    <ResponseField name="expected_funds_settlement_at" type="string | null">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the funds are
      expected to settle.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="return" type="object | null">
  Return details, if the transfer was returned.

  <Expandable title="Return object">
    <ResponseField name="raw_return_reason_code" type="string">
      The raw ACH return reason code.
    </ResponseField>

    <ResponseField name="return_transaction_id" type="string | null">
      The transaction created when the transfer was returned.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "ach_transfer_Lk7nQx4mVp9bRt3d",
    "account_id": "account_Rv4nBt8xKw2pMh6s",
    "external_account_id": "external_account_Bx5nTm8hKw3pVd7c",
    "amount": 150000,
    "status": "submitted",
    "statement_descriptor": "Acme payroll",
    "transaction_id": null,
    "settled_at": null,
    "submission": {
      "submitted_at": "2026-03-15T14:30:00Z",
      "expected_funds_settlement_at": "2026-03-17T14:30:00Z"
    },
    "return": null
  }
  ```
</ResponseExample>


# Move money internally
Source: https://getlemma.com/docs/api-reference/move-money-internally

POST /v0/book-transfer
Transfer funds instantly between Lemma accounts.

Creates a transfer between two Lemma accounts. Book transfers settle instantly, are free, and are available 24/7.

<Info>
  Transfers over \$100,000 are held for manual review by the Lemma team as a
  security measure to protect your accounts in the event of a compromised API
  key. Need higher limits? [Contact us](mailto:contact@getlemma.com).
</Info>

## Request body

<ParamField type="string">
  The ID of the Lemma account to send money from.
</ParamField>

<ParamField type="string">
  The ID of the Lemma account to send money to.
</ParamField>

<ParamField type="integer">
  The amount to transfer in cents. Must be greater than zero.
</ParamField>

<ParamField type="string">
  A memo or description for the transfer. Appears on both the sender and
  recipient's transaction history.
</ParamField>

## Response

Returns the created book transfer object.

<ResponseField name="id" type="string">
  Unique identifier for the book transfer.
</ResponseField>

<ResponseField name="created_at" type="string">
  [ISO 8601](/docs/api-reference/timestamps) timestamp of when the book transfer was
  created.
</ResponseField>

<ResponseField name="source_account_id" type="string">
  The Lemma account money moves from.
</ResponseField>

<ResponseField name="destination_account_id" type="string">
  The Lemma account money moves to.
</ResponseField>

<ResponseField name="amount" type="integer">
  The transfer amount in cents.
</ResponseField>

<ResponseField name="status" type="string">
  Current status of the book transfer.

  <Expandable title="possible values">
    * `complete` — settled. Most book transfers are complete the moment they're created.

    * `pending_approval` — held for manual review by our team for fraud prevention.

    * `canceled` — blocked after that manual review.
  </Expandable>
</ResponseField>

<ResponseField name="description" type="string">
  Description of the transfer.
</ResponseField>

<ResponseField name="source_transaction_id" type="string | null">
  The settled transaction on the source account, once the transfer posts.
</ResponseField>

<ResponseField name="destination_transaction_id" type="string | null">
  The settled transaction on the destination account, once the transfer posts.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "book_transfer_Hm3pWx9nKv4bQt7d",
    "created_at": "2026-03-15T14:30:00Z",
    "source_account_id": "account_Rv4nBt8xKw2pMh6s",
    "destination_account_id": "account_Hn9wFj3cTd7yXk5v",
    "amount": 500000,
    "status": "complete",
    "description": "Quarterly intercompany settlement",
    "source_transaction_id": "transaction_Wp5mRx3nKv8bTh2d",
    "destination_transaction_id": "transaction_Qk2nJx7mLv9bRt4c"
  }
  ```
</ResponseExample>


# Pagination
Source: https://getlemma.com/docs/api-reference/pagination

How to page through large result sets using the Lemma API.

List endpoints return results one page at a time using cursor-based pagination. Each response includes a `data` array for the current page, a `has_next` boolean, and a `cursor` string to fetch the next page.

Cursor pagination is stable within a single pass: inserting or deleting records while you page will not cause items to be skipped or duplicated.

## Query parameters

All paginated endpoints accept these parameters:

| Parameter | Type    | Default | Maximum | Description                                             |
| --------- | ------- | ------- | ------- | ------------------------------------------------------- |
| `limit`   | integer | `10`    | `100`   | Items per page                                          |
| `cursor`  | string  | —       | —       | Cursor from the previous response. Omit for first page. |

A `limit` that is not a whole number between 1 and 100 is rejected with a 400 error.

## Response structure

```json theme={null}
{
  "data": [...],
  "has_next": true,
  "cursor": "eyJvcGVuZWRfYXQiOiIyMDI2LTAzLTEyVDE2OjQ1OjAwWiIsImlkIjoiYWNjb3VudF9XcDVtUngzbkt2OGJUaDJkIn0"
}
```

`cursor` is `null` when this is the last page. Pass it as the `cursor` query parameter on the next request to fetch the following page.

## Fetching all pages

To retrieve every item, keep requesting until `has_next` is `false`:

```typescript theme={null}
async function fetchAllTransactions(accountId: string) {
  const results = [];
  let cursor: string | null = null;

  do {
    const params = new URLSearchParams({ account_id: accountId, limit: "100" });
    if (cursor) {
      params.set("cursor", cursor);
    }

    const response = await fetch(
      `https://api.getlemma.com/v0/transactions?${params}`,
      { headers: { Authorization: `Bearer ${API_KEY}` } },
    );
    const page = await response.json();

    results.push(...page.data);
    cursor = page.has_next ? page.cursor : null;
  } while (cursor);

  return results;
}
```

## Keeping a local copy in sync

Do not save a `cursor` and reuse it on a later run. Cursors page from newest to
oldest, so resuming from a stored cursor returns records *older* than your
bookmark and never the new ones that arrived above it. There is also no cursor
to save at the end of a pass: `cursor` is `null` on the last page.


# Saved recipients
Source: https://getlemma.com/docs/api-reference/saved-recipients

External bank accounts saved for outbound transfers.

Saved recipients (also called external accounts) are external bank accounts that you save in Lemma for outbound transfers. They represent accounts outside of Lemma — such as a vendor, payroll provider, or another financial institution — that your organization sends money to.

**Saved recipients are the only way to transfer funds outside of Lemma.** This is by design: requiring a pre-registered recipient prevents accidentally moving money to an account not associated with your entity's funds. Every outbound transfer must target a saved recipient that belongs to your entity.

## Creating recipients

Lemma users can create an external account through the Lemma dashboard. Platforms create external accounts via the [Create external account](/docs/api-reference/create-external-account) endpoint. Every recipient requires a `nickname`, a non-nullable text field that serves as a human-readable label in the dashboard. Choose something your team will recognize at a glance (e.g., "Owner's personal account" rather than "Acct 4821").

## Immutability

External accounts cannot be edited after creation. This is necessary for reconciliation and audit purposes. If account details could change, it would be impossible to reliably trace which bank account a historical transfer was sent to. If you need to correct a mistake, archive the existing recipient and create a new one.

## Archiving vs. deleting

External accounts are never deleted, only archived. When you archive a recipient, Lemma:

* Sets the recipient's status to `archived`
* Rejects any new transfers targeting that recipient
* Keeps the record in the database for reconciliation and audit trail

Archived recipients are excluded from the [list endpoint](/docs/api-reference/list-external-accounts) but can still be fetched directly with the [get endpoint](/docs/api-reference/get-external-account). They also remain visible in transaction history so you can always trace past payments.

As of now, you can only archive an external account by emailing our team.

## Ownership and access control

Every external account belongs to a specific entity. Lemma enforces this at the transfer level. You cannot send money to an external account owned by a different entity. This ensures each practice's funds can only be sent to accounts they have explicitly registered.

## Using recipients in transfers

Pass an external account ID as the `destination_account_id` when calling [Move money externally](/docs/api-reference/move-money-externally). Transfers to saved recipients are sent via ACH and typically settle within 1-2 business days.

## Related endpoints

* [Create external account](/docs/api-reference/create-external-account) — save a new external bank account
* [Get external account](/docs/api-reference/get-external-account) — retrieve a single external account by ID
* [List external accounts](/docs/api-reference/list-external-accounts) — retrieve active external accounts for an entity


# Timestamps
Source: https://getlemma.com/docs/api-reference/timestamps

How the Lemma API formats and accepts timestamps.

The Lemma API uses **ISO 8601** timestamps for all date and time values. This is the most widely supported timestamp format across programming languages and tools.

## Format

An ISO 8601 timestamp looks like this:

```
2026-03-15T14:30:00Z
```

| Part         | Meaning                                        |
| ------------ | ---------------------------------------------- |
| `2026-03-15` | Date in year-month-day order                   |
| `T`          | Separator between date and time                |
| `14:30:00`   | Time in 24-hour format (hours:minutes:seconds) |
| `Z`          | UTC timezone (also called "Zulu")              |

## Timezone offsets

Instead of `Z`, you can specify a UTC offset:

```
2026-03-15T09:30:00-05:00
```

This represents 9:30 AM Eastern Standard Time (UTC-5). The API converts all timestamps to UTC internally.

## Using timestamps in query parameters

When filtering by timestamp, pass the full ISO 8601 string as the parameter value:

```bash theme={null}
curl "https://api.getlemma.com/v0/transactions?account_id=account_123&occurred_on_or_after=2026-03-01T00:00:00Z&occurred_on_or_before=2026-03-31T18:00:00Z" \
  -H "Authorization: Bearer your_api_key"
```

A value that isn't valid ISO 8601 is rejected with a 400 error.

## Date-only values

Filters also accepts a bare calendar date like `2026-03-15`.

```bash All of March, including March 1 and March 31 theme={null}
curl "https://api.getlemma.com/v0/transactions?account_id=account_123&occurred_on_or_after=2026-03-01&occurred_on_or_before=2026-03-31" \
  -H "Authorization: Bearer your_api_key"
```

Bare dates are always UTC. To report on a period anchored to another timezone, pass explicit timestamps instead.

A date that doesn't exist, such as `2026-02-31`, is rejected with a 400 error.

## Generating timestamps

<Tabs>
  <Tab title="JavaScript">
    ```javascript theme={null}
    new Date().toISOString()
    // "2026-03-15T14:30:00.000Z"
    ```
  </Tab>

  <Tab title="Python">
    ```python theme={null}
    from datetime import datetime, timezone

    datetime.now(timezone.utc).isoformat()
    # "2026-03-15T14:30:00+00:00"
    ```
  </Tab>

  <Tab title="Ruby">
    ```ruby theme={null}
    Time.now.utc.iso8601
    # "2026-03-15T14:30:00Z"
    ```
  </Tab>

  <Tab title="cURL">
    ```bash theme={null}
    date -u +"%Y-%m-%dT%H:%M:%SZ"
    # 2026-03-15T14:30:00Z
    ```
  </Tab>
</Tabs>


# Webhooks
Source: https://getlemma.com/docs/api-reference/webhooks

Receive real-time notifications when events happen on Lemma.

Webhooks let your platform receive HTTP callbacks when events occur in Lemma. Instead of polling our API, you register a URL and we send a `POST` request to it whenever a relevant event fires.

To configure a webhook endpoint, [contact the Lemma team](mailto:contact@getlemma.com) with the URL you'd like to receive events at. We'll share a signing secret for that endpoint at the same time. We're planning to build a self-serve UI in the near future to manage endpoint URLs directly from the dashboard.

## Events

### `permissions.updated`

Fired whenever an entity's permissions for your platform change. Use this to know when an entity connects with you and when they revoke access.

The payload contains the entity ID and the **complete** current set of permissions your API key holds for that entity. Each permission is an object with a `resource_group`, an `operation`, and a `resource_id`. The grant allows access to the whole resource group when `resource_id` is null. When `resource_id` is present, the grant is scoped to exactly that resource. It is not a delta: every event carries the full list, so you can replace any cached permissions wholesale.

An empty `permissions` array means access has been fully revoked.

```json theme={null}
{
  "entityId": "entity_k7mXp2vR9nTfBw4s",
  "permissions": [
    { "resource_group": "entities", "operation": "read", "resource_id": null },
    {
      "resource_group": "bank_accounts",
      "operation": "read",
      "resource_id": null
    },
    {
      "resource_group": "bank_accounts",
      "operation": "send_external_transfer",
      "resource_id": "account_Rv4nBt8xKw2pMh6s"
    },
    {
      "resource_group": "bank_accounts",
      "operation": "send_external_transfer",
      "resource_id": "account_Lp7mKx3nWv9bTh4d"
    },
    {
      "resource_group": "external_accounts",
      "operation": "read",
      "resource_id": null
    },
    {
      "resource_group": "external_accounts",
      "operation": "initiate_ach_pull",
      "resource_id": "external_account_Bx5nTm8hKw3pVd7c"
    }
  ]
}
```

Every permission is one of the `resource_group` / `operation` pairs below. When a permission can have a `resource_id`, that ID narrows the grant to a single resource in the group. For example, to only allow you to read transactions for a specific bank account. Some resource groups will never have `resource_id` as shown in the table below.

| `resource_group`    | `operation`              | Can have `resource_id` | Grants the ability to                                                |
| ------------------- | ------------------------ | ---------------------- | -------------------------------------------------------------------- |
| `entities`          | `read`                   | No                     | Read the entity's identifying information, such as its company name. |
| `bank_accounts`     | `read`                   | Yes                    | Read the entity's Lemma bank account details.                        |
| `bank_accounts`     | `send_external_transfer` | Yes                    | Send money from the entity's accounts to external accounts.          |
| `bank_accounts`     | `same_entity_transfer`   | Yes                    | Move money between the entity's own Lemma bank accounts.             |
| `bank_accounts`     | `cross_entity_transfer`  | Yes                    | Move money between the entity's Lemma accounts and another entity.   |
| `external_accounts` | `read`                   | Yes                    | Read the external accounts saved on the entity's account.            |
| `external_accounts` | `write`                  | No                     | Add new external accounts to the entity's account.                   |
| `external_accounts` | `archive`                | Yes                    | Remove external accounts from the entity's account.                  |
| `external_accounts` | `initiate_ach_pull`      | Yes                    | Pull funds from the entity's external accounts via ACH.              |
| `inbound_mail`      | `read`                   | No                     | Read lockbox mail sent to the entity's Lemma account.                |

## Verifying webhooks

Lemma signs every webhook using the [Standard Webhooks](https://www.standardwebhooks.com/) specification. Each request carries three headers:

* `webhook-id` — unique message identifier
* `webhook-timestamp` — Unix timestamp (in seconds) of when we sent it
* `webhook-signature` — the signature over the payload

Always verify the signature with the signing secret we shared for your endpoint before trusting a payload. The official [standardwebhooks](https://www.npmjs.com/package/standardwebhooks) TypeScript library handles this for you:

```ts theme={null}
import { Webhook } from "standardwebhooks";

const webhook = new Webhook(process.env.LEMMA_WEBHOOK_SECRET); // "whsec_..."

// `body` must be the raw, unparsed request body string.
const payload = webhook.verify(body, {
  "webhook-id": headers["webhook-id"],
  "webhook-timestamp": headers["webhook-timestamp"],
  "webhook-signature": headers["webhook-signature"],
}) as {
  entityId: string;
  permissions: {
    resource_group: string;
    operation: string;
    resource_id: string | null;
  }[];
};

// Verified and parsed:
// {
//   entityId: "entity_...",
//   permissions: [{ resource_group: "bank_accounts", operation: "read", resource_id: null }, ...]
// }
```

`verify` throws if the signature is invalid or the timestamp is outside the allowed tolerance.


# What is inbound?
Source: https://getlemma.com/docs/api-reference/what-is-inbound

How Lemma distinguishes transfers initiated outside Lemma from transfers initiated inside Lemma.

"Inbound" refers to a transfer initiated outside Lemma, by a bank, network, or counterparty that isn't you. An "outbound" transfer, by contrast, is one initiated inside Lemma — either by your application through the API, or by a user acting manually in the Lemma dashboard.

This distinction is about who started the transfer, not which direction money moves. Both inbound and outbound transfers can move money in either direction.

For example, an [ACH transfer](/docs/api-reference/get-ach-transfer) is outbound: it was requested through the API or the dashboard, whether it sends money to an external account or pulls money from one (an ACH pull). An [inbound ACH transfer](/docs/api-reference/get-inbound-ach-transfer) is the opposite: the entry originated at another bank, whether it's a credit sending an entity money or a debit pulling money out of a Lemma account.

|             | Initiated inside Lemma (outbound)                                                         | Initiated outside Lemma (inbound)                                                                            |
| ----------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Sends money | [ACH transfer](/docs/api-reference/get-ach-transfer) with a positive amount               | [Inbound ACH](/docs/api-reference/get-inbound-ach-transfer) credit, e.g. a payment from an insurance company |
| Pulls money | [ACH transfer](/docs/api-reference/get-ach-transfer) with a negative amount (an ACH pull) | [Inbound ACH](/docs/api-reference/get-inbound-ach-transfer) debit, e.g. a vendor pulling a payroll payment   |

If you want to find deposits from payers, you want to use the [list inbound ACHs endpoint](/docs/api-reference/list-inbound-ach-transfers).


# EOB processing
Source: https://getlemma.com/docs/billing/eob-processing

Automatically parse explanation of benefits documents and reconcile insurance payments.

Lemma helps billing teams track insurance payments by parsing explanation of benefits (EOB) documents and matching them to deposited funds. Instead of manually reading EOBs and cross-referencing bank statements, Lemma extracts the data and surfaces matching transactions for you.

## Two ways to get EOBs into Lemma

<Columns>
  <Card title="Lockbox auto-parsing" icon="mailbox" href="/docs/billing/lockbox-eob-parsing">
    Insurance companies mail EOBs to your Lemma lockbox address. Lemma scans and
    parses them automatically.
  </Card>

  <Card title="Manual upload" icon="upload" href="/docs/billing/manual-eob-upload">
    Upload EOB PDFs directly from your computer. Upload in bulk to process large
    batches at once.
  </Card>
</Columns>

## What Lemma extracts

For each EOB, Lemma extracts:

* **Payer** — the insurance company name, address, phone number, and tax ID
* **Payee** — your practice's information as listed on the EOB
* **Patient details** — patient name and member ID
* **Claim line items** — CPT codes, service dates, charged amounts, allowed amounts, paid amounts, and patient responsibility
* **Payment totals** — the total amount the payer is remitting

## Reconciliation

Once an EOB is parsed, Lemma automatically looks for transactions with matching amounts in your account. This lets you confirm which deposits correspond to which insurance payments without manually comparing statements.

## Downloading 835 files

For every parsed EOB, Lemma can reconstruct the equivalent 835 EDI file. Open a payment in the **Insurance payments** table and select **Download 835** to feed the remittance into an EHR or clearinghouse that expects 835 files. See [payment reconciliation](/docs/billing/reconciliation#downloading-an-835) for details.

<Card title="Reconcile payments" icon="check-double" href="/docs/billing/reconciliation">
  Learn how to match parsed EOBs to deposited funds.
</Card>


# Fees and receipts
Source: https://getlemma.com/docs/billing/fee-receipts

Find receipts and choose which account fees are charged to.

Lemma charges fees for some services like our lockbox mail processing — see the [pricing page](/docs/billing/pricing) for what each service costs. You can find a receipt for every fee, and choose which bank account those charges come out of, on the [Fees settings page](https://app.getlemma.com/_/settings/fees).

## Change the account fees are charged to

On the [Fees settings page](https://app.getlemma.com/_/settings/fees), the **Bank account to pay fees** dropdown controls which account monthly bills are debited from. Pick a different account from the dropdown to change it and the change will apply to future invoices.

Only users with [banking owner permissions](/docs/guides/team-management#banking-permissions) can change the billing account. Other team members can
see the receipts but cannot change where charges are deducted from.


# Lockbox auto-parsing
Source: https://getlemma.com/docs/billing/lockbox-eob-parsing

Receive EOBs at your lockbox address and have them parsed automatically.

When insurance companies mail explanation of benefits documents to your Lemma [lockbox](/docs/guides/lockbox) address, Lemma scans the mail, deposits any enclosed checks, and automatically parses the EOB data.

## How it works

<Steps>
  <Step title="Payer mails the EOB">
    The insurance company sends an EOB (often with an enclosed check) to your
    lockbox mailing address.
  </Step>

  <Step title="Lemma receives and scans the mail">
    When mail arrives at your lockbox, it is opened and scanned. Checks are
    deposited into your linked bank account. The scanned documents appear in the
    **Lockbox** section of your dashboard.
  </Step>

  <Step title="EOB is parsed automatically">
    Lemma detects EOB documents in your incoming mail and extracts the payment details — payer, patient, claim line items, and amounts. A processing job appears in the **EOB > Active jobs** table.
  </Step>

  <Step title="Review the parsed data">
    Once processing completes, the extracted payment appears in the **EOB > Payer Remittances** table. Select it to review the full breakdown of claims, CPT codes, and amounts.
  </Step>
</Steps>

## Setting up your lockbox for EOBs

No additional setup is needed. If your organization has a lockbox, any EOB documents that arrive are parsed automatically. To start receiving EOBs at your lockbox:

1. Note your lockbox mailing address from the **Lockbox** page in your dashboard
2. Update payer records with your insurance companies to use this address for remittance
3. EOBs will begin appearing in the **EOB** section as they arrive

<Tip>
  It can take a few weeks for insurance companies to update their mailing
  addresses. In the meantime, you can [upload EOBs
  manually](/docs/billing/manual-eob-upload) to start using the parsing and
  reconciliation features right away.
</Tip>

## Automatic reconciliation

Lemma is actively expanding the list of insurance payers that support fully automatic reconciliation — matching parsed EOB line items directly to your outstanding claims with no manual review required. As the only banking platform built exclusively for healthcare, Lemma understands the nuances of medical billing and invests heavily in payer-specific parsing so you can get back to focusing on patient care.

<Info>
  We add support for new payer formats on a regular basis. If you work with a
  payer whose EOBs are not yet auto-reconciled, [let us
  know](mailto:contact@getlemma.com) and we will prioritize it.
</Info>


# Manual EOB upload
Source: https://getlemma.com/docs/billing/manual-eob-upload

Upload EOB documents in bulk for Lemma to parse and extract payment data.

If you receive EOBs outside of your lockbox — via email, a payer portal, or on paper that you scan yourself — you can upload them directly to Lemma for parsing.

## Uploading EOBs

1. Go to the **EOB** section in your dashboard
2. Select **Upload**
3. Choose one or more PDF files from your computer
4. Lemma begins processing each file

You can upload multiple files at once to process a batch of EOBs in a single step. Each file creates a separate processing job.

<Tip>
  This is a good way to get started with Lemma's EOB features before your
  insurance companies update their mailing addresses to your lockbox.
</Tip>

## What to upload

Upload the EOB documents you receive from insurance companies. These are the remittance advice documents that detail how claims were adjudicated — which claims were paid, denied, or adjusted, along with the amounts.

Supported format:

* **PDF** — standard EOB documents from major insurance payers

<Note>
  Lemma works best with machine-readable PDFs (not scanned images of printed
  documents). If you are scanning paper EOBs, use your scanner's OCR setting to
  produce searchable PDFs.
</Note>

## Tracking processing status

Each uploaded file appears in the **Active jobs** table on the EOB page. You can monitor the status of each file:

| Status         | Meaning                                                                       |
| -------------- | ----------------------------------------------------------------------------- |
| **Uploaded**   | File received, queued for processing                                          |
| **Extracting** | Parsing the document                                                          |
| **Completed**  | Data extracted — select the payment in the Insurance payments table to review |
| **Failed**     | Extraction failed — check the file format and try again                       |

## After processing

Once an EOB is processed, the extracted payment data appears in the **Insurance payments** table. From there, you can:

* Review the full breakdown of claims, CPT codes, and amounts
* See payer and payee details
* [Reconcile the payment](/docs/billing/reconciliation) against your deposited funds


# Medicaid payment cycles
Source: https://getlemma.com/docs/billing/medicaid-payment-cycles

Medicaid batches adjudicated claims and releases payment on a weekly cycle.

Medicaid does not pay claims as it adjudicates them. Each program accumulates adjudicated claims and releases payment on a fixed weekly cycle, called a checkwrite, so the day your money moves is set by that calendar rather than by the day the claim finished adjudication.

The 835 is generated when the batch is released, and the EFT settles one or two banking days after that. That is why a remittance advice shows up in your practice management system days before the matching deposit shows up in your account.

## Weekly checkwrites

State Medicaid programs publish their cycles, which makes them the clearest illustration. North Carolina's NCTracks runs one checkwrite per week: claims adjudicated by Friday midnight are approved on Tuesday (the date printed on the remittance), remittance advices and 835s are available by 8:00 a.m. Wednesday, and EFTs are initiated Wednesday and typically post Thursday afternoon.

Most states follow the same weekly shape, a handful pay every other week, and several skip a cycle at their fiscal year end. The MSO-PC Wiki maintains the full [payment cycle for every state](https://mso.getlemma.com/reference/payers/profiles/medicaid#payment-cycles), with cutoff days, remittance timing, and a link to each program's published schedule; the [DSO-PC Wiki](https://dso.getlemma.com/reference/payers/profiles/medicaid-dental#payment-cycles) covers the dental programs, where a dental benefit manager often pays on a different calendar than the state.

Because the cycle is weekly, a claim that finishes adjudication just after the cutoff does not slip by a day — it waits for the next checkwrite.


# How to update your bank account with insurance payers (EFT re-enrollment)
Source: https://getlemma.com/docs/billing/migrate-payers

Step-by-step instructions for re-enrolling your EFT with insurance payers after switching bank accounts.

When you switch banks, you need to re-enroll your EFT with each insurance payer that sends payments to you. Payers route reimbursements to the account on file — if that account changes, payments will route to the wrong place until you update your payer portal enrollment.

This page lists step-by-step instructions for each payer's enrollment portal so your billing team can update your bank account information one payer at a time.

## Allow time for processing

Some payers take up to four weeks to process an EFT change. Submit updates as soon as possible after switching banks to avoid delayed or misdirected payments.

## Payer directory

<AccordionGroup>
  <Accordion title="Amerigroup (NM)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Amerigroup (NM)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Amerigroup RealSolutions in Healthcare (GA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Amerigroup RealSolutions in Healthcare (GA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross (CA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross (CA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross (NY)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross (NY)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross Life and Health Insurance Company (CA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross Life and Health Insurance Company (CA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (CO)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (CO)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (CT)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (CT)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (GA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (GA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (IN)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (IN)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (KY)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (KY)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (ME)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (ME)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (MO)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (MO)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (NH)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (NH)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (NV)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (NV)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (NY)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (NY)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (OH)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (OH)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (VA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (VA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield (WI)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield (WI)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield HealthKeepers (VA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield HealthKeepers (VA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield MaineHealth" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield MaineHealth" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem Blue Cross and Blue Shield Medicaid (KY)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem Blue Cross and Blue Shield Medicaid (KY)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Anthem HealthKeepers (VA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Anthem HealthKeepers (VA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Blue Cross Blue Shield FEP Dental" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Blue Cross Blue Shield FEP Dental" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Blue Cross Blue Shield Healthy Blue (LA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Blue Cross Blue Shield Healthy Blue (LA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Blue Cross Blue Shield Healthy Blue (MO)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Blue Cross Blue Shield Healthy Blue (MO)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Blue Cross Blue Shield Healthy Blue Heritage Health (NE)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Blue Cross Blue Shield Healthy Blue Heritage Health (NE)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Blue Cross Blue Shield of North Carolina Healthy Blue" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Blue Cross Blue Shield of North Carolina Healthy Blue" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Blue Medicare Advantage Blue Cross (PA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Blue Medicare Advantage Blue Cross (PA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Clear Health Alliance" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Clear Health Alliance" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Colorado Community Health Alliance" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Colorado Community Health Alliance" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="HIGHMARK WNY BCBS MEDICAID CHP" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/highmark.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=aeb797f5893e900690077ecd43b5a690">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "HIGHMARK WNY BCBS MEDICAID CHP" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="HealthSun Health Plans" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "HealthSun Health Plans" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Healthy Blue + Medicare (NC)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Healthy Blue + Medicare (NC)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Healthy Blue Kansas (KS)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Healthy Blue Kansas (KS)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Healthy Blue - Blue Choice HealthPlan of SC - Healthy Connections" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Healthy Blue - Blue Choice HealthPlan of SC - Healthy Connections" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Horizon BCBS NJ Dental Programs" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/horizon-bcbs.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=4e47692fa914ebb089b185df8297e026">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Horizon BCBS NJ Dental Programs" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Medicare (PECOS)" icon="building-columns">
    **Portal:** [PECOS](https://pecos.cms.hhs.gov)

    Original Medicare doesn't route EFT changes through a payer portal like the plans below — it's handled through CMS's Provider Enrollment, Chain, and Ownership System (PECOS) as part of your provider enrollment record.

    <Card title="Download our PECOS Organizational Structure template" icon="download" href="/docs/download/PECOS_Organizational_Structure.docx">
      Fillable template for the ownership, managing-employee, and chain-of-ownership disclosure PECOS requires with your enrollment change.
    </Card>
  </Accordion>

  <Accordion title="Simply Healthcare" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Simply Healthcare" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Summit Community Care" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Summit Community Care" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UFCW Local 1262 Welfare Dental Program" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/ufcw.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=ec1f3d0f134e74cb34a54650e8a618e2">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "UFCW Local 1262 Welfare Dental Program" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UniCare" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "UniCare" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellmark Blue Dental" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/wellmark.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=c7758e9c2ef536824c189a2f9846e660">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellmark Blue Dental" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (AZ)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (AZ)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (DC)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (DC)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (FL)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (FL)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (IA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (IA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (MD)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (MD)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (NJ)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (NJ)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (NY)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (NY)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (SC)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (SC)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (TN)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (TN)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (TX)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (TX)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (WA)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (WA)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint (WV)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint (WV)" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Wellpoint Commonwealth of Massachusetts" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/anthem.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=d134d160de6a135db99ceb2eb33b31d8">
    **Portal:** [EnrollSafe / PayeeHub](https://enrollsafe.payeehub.org)

    <Steps>
      <Step>
        Go to [https://enrollsafe.payeehub.org/](https://enrollsafe.payeehub.org/) and log in with your provider credentials.
      </Step>

      <Step>
        Locate "Wellpoint Commonwealth of Massachusetts" in the Participating Plans list.
      </Step>

      <Step>
        Click the payer link to view or update your EFT enrollment and payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Aetna" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/aetna.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=b9dc05dd6332c5ed5bbf1dba9e112664">
    **Portal:** [Payer Enrollment Services](https://payerenrollservices.com/)

    <Steps>
      <Step>
        Go to [https://payerenrollservices.com/](https://payerenrollservices.com/) and log in with your provider credentials.
      </Step>

      <Step>
        Click the "PAYER LIST" tab at the top of the page.
      </Step>

      <Step>
        Locate "Aetna" in the Payer List.
      </Step>

      <Step>
        Click on the payer to view or update your enrollment details.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="BlueCross BlueShield of Tennessee" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [Payer Enrollment Services](https://payerenrollservices.com/)

    <Steps>
      <Step>
        Go to [https://payerenrollservices.com/](https://payerenrollservices.com/) and log in with your provider credentials.
      </Step>

      <Step>
        Click the "PAYER LIST" tab at the top of the page.
      </Step>

      <Step>
        Locate "BlueCross BlueShield of Tennessee" in the Payer List.
      </Step>

      <Step>
        Click on the payer to view or update your enrollment details.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Healthfirst NY" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/healthfirst.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=0d97d6763cf44a310ca5df766f5d28d7">
    **Portal:** [Payer Enrollment Services](https://payerenrollservices.com/)

    <Steps>
      <Step>
        Go to [https://payerenrollservices.com/](https://payerenrollservices.com/) and log in with your provider credentials.
      </Step>

      <Step>
        Click the "PAYER LIST" tab at the top of the page.
      </Step>

      <Step>
        Locate "Healthfirst NY" in the Payer List.
      </Step>

      <Step>
        Click on the payer to view or update your enrollment details.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Shared Health" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/bcbs.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=3727c29d574585a16f2195fa021b7383">
    **Portal:** [Payer Enrollment Services](https://payerenrollservices.com/)

    <Steps>
      <Step>
        Go to [https://payerenrollservices.com/](https://payerenrollservices.com/) and log in with your provider credentials.
      </Step>

      <Step>
        Click the "PAYER LIST" tab at the top of the page.
      </Step>

      <Step>
        Locate "Shared Health" in the Payer List.
      </Step>

      <Step>
        Click on the payer to view or update your enrollment details.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="TRICARE For Life" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/tricare.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=82eccba1b5cdd8d77cf28e4f339efb15">
    **Portal:** [Payer Enrollment Services](https://payerenrollservices.com/)

    <Steps>
      <Step>
        Go to [https://payerenrollservices.com/](https://payerenrollservices.com/) and log in with your provider credentials.
      </Step>

      <Step>
        Click the "PAYER LIST" tab at the top of the page.
      </Step>

      <Step>
        Locate "TRICARE For Life" in the Payer List.
      </Step>

      <Step>
        Click on the payer to view or update your enrollment details.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="WPS – Family Care (FAMC)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/wps.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=4adb4cf32ab175f0720ce0cecf08ba11">
    **Portal:** [Payer Enrollment Services](https://payerenrollservices.com/)

    <Steps>
      <Step>
        Go to [https://payerenrollservices.com/](https://payerenrollservices.com/) and log in with your provider credentials.
      </Step>

      <Step>
        Click the "PAYER LIST" tab at the top of the page.
      </Step>

      <Step>
        Locate "WPS – Family Care (FAMC)" in the Payer List.
      </Step>

      <Step>
        Click on the payer to view or update your enrollment details.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Cigna" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/cigna.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=336387ef269aaf5a70600a85cb6c5868">
    **Portal:** [Cigna for Health Care Professionals](https://cignaforhcp.cigna.com/app/login)

    <Steps>
      <Step>
        Go to [https://cignaforhcp.cigna.com/app/login](https://cignaforhcp.cigna.com/app/login) and log in with your provider credentials.
      </Step>

      <Step>
        Navigate to the relevant section to update your payer portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="AARP Supplemental from UnitedHealthcare" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/uhc.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=eab548760f7d33878a041930de0ba408">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "AARP Supplemental from UnitedHealthcare" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Government Employees Health Association" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/geha.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=163e7d33ee2eb3986265004640030de6">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "Government Employees Health Association" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UnitedHealthcare" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/uhc.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=eab548760f7d33878a041930de0ba408">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "UnitedHealthcare" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UHC Community Plan MI Dual" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/uhc.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=eab548760f7d33878a041930de0ba408">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "UHC Community Plan MI Dual" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UHC Community Plan Michigan" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/uhc.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=eab548760f7d33878a041930de0ba408">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "UHC Community Plan Michigan" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UHC Community Plan" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/uhc.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=eab548760f7d33878a041930de0ba408">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "UHC Community Plan" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Optum VA CCN Region 2" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/optum.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=4bd4e114b13e6ebd25cd5572281397e0">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "Optum VA CCN Region 2" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Optum VA CCN Region 3" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/optum.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=4bd4e114b13e6ebd25cd5572281397e0">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "Optum VA CCN Region 3" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Optum VA CCN Region 5" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/optum.svg?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=4bd4e114b13e6ebd25cd5572281397e0">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "Optum VA CCN Region 5" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="UMR" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/uhc.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=eab548760f7d33878a041930de0ba408">
    **Portal:** [Optum Health Payment Services](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do)

    <Steps>
      <Step>
        Go to [https://myservices.optumhealthpaymentservices.com/registrationSignIn.do](https://myservices.optumhealthpaymentservices.com/registrationSignIn.do) and sign in with your provider credentials.
      </Step>

      <Step>
        Locate "UMR" in your payer list.
      </Step>

      <Step>
        Click on the payer to view or update your payment and portal settings.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="HAP (Health Alliance Plan)" icon="https://mintcdn.com/tobiasgetlemmacom/KwzPZhF6OmPiRqMI/images/payers/hap.png?fit=max&auto=format&n=KwzPZhF6OmPiRqMI&q=85&s=9c832b6399f48119f8dbd49d68c3a880">
    **Portal:** [HAP Provider Portal](https://www.hap.org/providers)

    <Note>Allow up to 4 weeks for enrollment. HAP sends a 1-cent test deposit to verify your account before live payments begin. Questions? Contact [accountspayable@hap.org](mailto:accountspayable@hap.org).</Note>

    <Steps>
      <Step>
        Go to [https://www.hap.org/providers](https://www.hap.org/providers) for general provider information.
      </Step>

      <Step>
        Download the HAP Direct Deposit (EFT) Application using the button below.
      </Step>

      <Step>
        Fill in: Provider/Vendor Tax ID (TIN/EIN), Provider Name, Address, EFT Contact Name, Phone, and Email.
      </Step>

      <Step>
        Fill in your bank details: Financial Institution Name, City/State, 9-digit Routing Number, and Account Number.
      </Step>

      <Step>
        Select enrollment type: New Enrollment, Change Enrollment, or Cancel Enrollment.
      </Step>

      <Step>
        Have an authorized signer sign and date the completed form.
      </Step>

      <Step>
        Attach a voided check (or bank letter on letterhead) to the PDF.
      </Step>

      <Step>
        Email the completed form + voided check to [accountspayable@hap.org](mailto:accountspayable@hap.org).
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

***

Company names, logos, and trademarks are the property of their respective owners and are used solely for identification purposes. Lemma is not affiliated with, endorsed by, or sponsored by any of the companies listed.


# Patient refunds
Source: https://getlemma.com/docs/billing/patient-refunds

Mail a refund check to a patient with a printed explanation enclosed.

When a patient is owed a refund, you can mail them a physical check directly from Lemma. You can also include a PDF document, such as an explanation of benefits or itemized statement, that will be printed and enclosed with the check.

## Sending a refund

Go to [Move money > Mail a check](https://app.getlemma.com/_/move-money/mail-a-check) and complete the following steps:

<Steps>
  <Step title="Enter the patient's address">
    Provide the patient's full mailing address. This is where the check will be
    delivered.
  </Step>

  <Step title="Enter the refund amount">
    Enter the amount to refund the patient.
  </Step>

  <Step title="Choose a shipping method">
    | Method               | Speed             | Delivers to PO boxes |
    | -------------------- | ----------------- | -------------------- |
    | **USPS First Class** | 5-7 business days | Yes                  |
    | **FedEx Overnight**  | Next business day | No                   |

    FedEx Overnight checks submitted before 2 PM ET are printed and mailed the
    same day, so they can be delivered by the next morning. USPS First Class
    checks are printed by the end of the next business day.

    USPS delivers to any address in the United States, including PO boxes. FedEx
    Overnight requires a street address and cannot deliver to PO boxes.
  </Step>

  <Step title="Upload an attachment (optional)">
    You can upload a PDF to include with the check. The document will be printed
    in black and white and mailed in the same envelope.

    Requirements:

    * **Format:** PDF
    * **Page size:** US Letter (8.5" × 11") on every page
    * **Page limit:** up to 5 pages

    Skip this step if you do not need to include a document.
  </Step>

  <Step title="Review and confirm">
    Review the details and confirm. The [mailing fee](/docs/billing/pricing) is deducted from your account
    automatically.
  </Step>
</Steps>


# Pricing
Source: https://getlemma.com/docs/billing/pricing

Compare Lemma plans and see what's included at each tier.

Your first month is free on every plan.

<Columns>
  <Card icon="building-columns" href="https://app.getlemma.com/sign-up">
    <div>
      Lemma<br />Single-Entity
    </div>

    <div>
      <span> / entity / month</span>
    </div>

    <div>Get started free</div>

    <div>
      Healthcare banking essentials included with every account.
    </div>
  </Card>

  <Card icon="sitemap" href="https://calendly.com/d/ct72-djp-r7w">
    <div>
      Lemma<br />Multi-Entity
    </div>

    <div>
      <span> / entity / month</span>
    </div>

    <div>Book a demo</div>

    <div>
      For organizations that need multi-entity money movement and compliance.
    </div>
  </Card>

  <Card icon="hospital" href="https://calendly.com/d/ct72-djp-r7w">
    <div>
      Lemma<br />Healthcare Systems
    </div>

    <div>
      <span>Talk to Sales</span>
    </div>

    <div>Book a demo</div>

    <div>
      For organizations that need a relationship manager and custom reporting.
    </div>
  </Card>
</Columns>

## Plan comparison

| Feature                                         | Single-Entity | Multi-Entity |   Healthcare Systems  |
| ----------------------------------------------- | :-----------: | :----------: | :-------------------: |
| Bank accounts                                   |   One entity  | Every entity |      Every entity     |
| Free physical and virtual debit cards           |       ✓       |       ✓      |           ✓           |
| Free ACH, RTP, and FedNow transfers             |       ✓       |       ✓      |           ✓           |
| Free cash sweeps                                |       ✓       |       ✓      |           ✓           |
| Earn APY on all balances                        |     1.05%     |     1.75%    |      Custom rate      |
| Free EOB-to-835 conversion                      |       ✓       |       ✓      |           ✓           |
| Guardrails and permissions from your agreements |       —       |       ✓      |           ✓           |
| Cross-entity invoicing and attachments          |       —       |       ✓      |           ✓           |
| Onboarding support                              |       —       |       ✓      | White-glove concierge |
| API access                                      |       —       |       ✓      |           ✓           |
| Custom API rate limits                          |       —       |       —      |           ✓           |
| Dedicated relationship manager                  |       —       |       —      |           ✓           |
| Custom reporting                                |       —       |       —      |           ✓           |
| Priority support                                |       —       |       —      |           ✓           |

## Fee schedule

| Fee                            |   Single-Entity   |    Multi-Entity   | Healthcare Systems |
| ------------------------------ | :---------------: | :---------------: | :----------------: |
| Domestic wire transfer         |        \$15       |        \$15       |       Custom       |
| Mail a check, USPS First Class |        \$2        |        \$2        |       Custom       |
| Mail a check, FedEx Overnight  |        \$25       |        \$25       |       Custom       |
| Mail patient refund check      |        \$4        |        \$4        |       Custom       |
| Lockbox                        | \$2.50 / envelope | \$2.00 / envelope |       Custom       |
| EOB/ERA reconciliation         |   \$1.00 / match  |   \$0.80 / match  |       Custom       |

Standard rates shown. Your company may have a negotiated contract with Lemma. Get in touch with our team for custom pricing and plan options at [contact@getlemma.com](mailto:contact@getlemma.com).


# Payment reconciliation
Source: https://getlemma.com/docs/billing/reconciliation

Match parsed EOB payments to bank transactions to confirm which deposits correspond to which insurance payments.

After Lemma parses an EOB, you need to confirm which bank deposit corresponds to that insurance payment. Lemma helps by automatically surfacing transactions with matching amounts.

## How reconciliation works

When you view a parsed EOB in the **Payer Remittances** table, Lemma searches your recent transactions for deposits that match the EOB's total payment amount. Matching transactions are displayed alongside the EOB details so you can confirm the connection in one place.

This replaces the manual process of:

1. Reading the total payment amount from an EOB
2. Opening your bank statement
3. Searching for a deposit with that amount
4. Cross-referencing dates and payer names to confirm it is the right one

## Reconciling a payment

<Steps>
  <Step title="Go to the EOB section">
    Navigate to the **EOB** page and select the **Insurance payments** tab.
  </Step>

  <Step title="Select a payment">
    Choose a parsed EOB from the list. The detail panel shows the full breakdown —
    payer, claims, and total amount.
  </Step>

  <Step title="Review matching transactions">
    Lemma displays transactions with amounts that match the EOB's payment total.
    Review the transaction details (date, counterparty, amount) to confirm it is
    the correct deposit.
  </Step>

  <Step title="Confirm the match">
    Once you identify the matching transaction, confirm the reconciliation. The
    EOB and transaction are linked together for your records.
  </Step>
</Steps>

## Downloading an 835

Once Lemma has parsed a lockbox or uploaded EOB, you can download the equivalent 835 EDI file from the remittance detail view. Use this when your EHR or clearinghouse accepts 835 files but the payer sent you a paper EOB instead.

1. Open the **EOB** page and select the **Insurance payments** tab.
2. Choose a parsed remittance.
3. Click **Download 835**.

## Provider-level adjustments

For remittances sourced from an ERA or 835 file, the check total may not equal the sum of claim payments. Provider-level balance (PLB) adjustments account for the difference. These include:

* **Recoupments**: the payer clawing back a prior overpayment
* **Forwarding balance**: a balance carried into or out of this check
* **Interest**: interest the payer owes on late payments
* **Capitation**: periodic capitated payments outside any single claim
* **Withholding**: funds withheld against a future obligation

When a parsed remittance contains any of these, the detail page shows a **Provider-Level Adjustments** section listing each entry with its reason code, reference, fiscal period, and signed effect on the check. A positive amount reduces the check; a negative amount adds to it. Use this section to explain why the deposit does not match the total of the claim lines.

## Lockbox payments

When an insurance company mails both a check and an EOB to your [lockbox](/docs/billing/lockbox-eob-parsing), the process is even simpler. The check is deposited automatically and the EOB is parsed automatically. Lemma links the check deposit to the parsed EOB, so many lockbox payments arrive pre-reconciled.

## Tips for reconciliation

* **Check amounts first**: the total payment amount is the primary matching criterion
* **Verify the payer**: confirm the transaction counterparty matches the insurance company on the EOB
* **Allow for timing differences**: a check deposit may settle a few days after the EOB is dated, so the transaction date and EOB payment date may not match exactly
* **Bulk payments**: some payers send a single check covering multiple EOBs. In this case, the deposit amount will be the sum of several EOB payment totals
* **Check totals that don't match the claims**: for ERA-sourced remittances, look at the [Provider-Level Adjustments](#provider-level-adjustments) section on the detail page. Recoupments, forwarding balances, and interest are applied outside any single claim


# Changelog
Source: https://getlemma.com/docs/changelog

Lemma launches new features every week.

<Update label="August 28, 2026">
  ### Connect Candid Health as a remittance source

  You can now connect [Candid Health](https://app.getlemma.com/_/settings/integrations/candid). Paste the API client ID and client secret from your Candid org-admin, and Lemma pulls your remittances into your Payer Remittances feed and reconciles them against your claims.
</Update>

<Update label="August 26, 2026">
  ### Get an email when money moves

  You can now get an email each time money moves on one of your accounts. Select the payment types and direction, and set an optional minimum amount so only larger payments reach your inbox. See [Email notifications](/docs/email-notifications) for how these work.
</Update>

<Update label="August 26, 2026">
  ### Watch each check in a bulk deposit land

  When you deposit a stack of checks through [check deposit](https://app.getlemma.com/_/move-money/check-deposit) or the [desktop check scanner](https://app.getlemma.com/_/move-money/scanner-check-deposit), the final screen now shows a live status for every check as it deposits. Each check is submitted on its own, so one slow or failed check no longer holds up or fails the rest of the batch. If a check fails, use **Retry** to resubmit only the failed checks. Retrying is safe: a check that already went through is never deposited twice. Refreshing or leaving the page mid-deposit is fine too; the remaining checks finish automatically when you come back.
</Update>

<Update label="August 26, 2026">
  ### Monthly cash sweeps

  [Cash sweeps](/docs/guides/cash-sweeps) can now run **monthly** instead of only weekly. Choose **Monthly** when you set the schedule and the rule runs on the first day of each month. Use monthly sweeps to schedule recurring payments between your entities like MSO management fees.
</Update>

<Update label="August 25, 2026">
  ### Charge a virtual card yourself

  When a payer gives you a virtual card directly, in a payer portal, by fax, or over the phone, you can now charge it yourself from [Move money > Charge a card](https://app.getlemma.com/_/move-money/charge-card). Enter the amount and the card details, and the funds land in your account in 24 to 36 hours. The charge appears on your [Card Processing](https://app.getlemma.com/_/acquiring) page alongside the cards Lemma charges from your lockbox. Reach out to Lemma to get self-serve charging enabled, then see the [guide](/docs/acquiring/charge-a-card).
</Update>

<Update label="August 25, 2026">
  ### Cancel a card from the API

  Platform partners can now [cancel a card](/docs/api-reference/delete-card) they issued through our API. Cancelling takes effect immediately and can't be undone, so freeze the card instead if the entity only needs to pause spending.
</Update>

<Update label="August 24, 2026">
  ### Manage a card after issuing it

  Open any card from the [cards page](https://app.getlemma.com/_/cards) and use the `...` menu at the top-right to manage it:

  * **Update limits.** Change the max purchase amount or max total spend, switch a limit off, or add one you skipped.
  * **Freeze.** Instantly block new transactions while preserving the card's limits and history. Unfreeze any time to resume using the card.
  * **Cancel.** Permanently stop the card. This can't be undone, so freeze it instead if you only need to pause it temporarily.

  New transactions are checked against the new state as soon as you save.
</Update>

<Update label="August 22, 2026">
  ### See why a payer's check doesn't match its claims

  Payer remittances sourced from an ERA now show a **Provider-Level Adjustments** section on the detail page. Recoupments, forwarding balances, interest, and capitation each appear with their signed effect on the check, so you can explain a deposit that doesn't equal the sum of the claim payments. See the [reconciliation guide](/docs/billing/reconciliation#provider-level-adjustments).
</Update>

<Update label="August 21, 2026">
  ### Track every card payment in one place

  Card acquiring now has its own [Card Processing](https://app.getlemma.com/_/acquiring) page. Every charge attempt against a payer's virtual card appears in a single ledger, with a status filter, sortable columns, and a detail drawer that walks the payment from the document it came out of through to settlement or chargeback.
</Update>

<Update label="August 21, 2026">
  ### Archive an application you no longer need

  Draft onboarding applications now have an **Archive** button in the Application Structure dialog. Archive removes the application from the onboarding dashboard and closes it for every collaborator, with a toast letting them know who archived it. Submitted applications are unaffected.
</Update>

<Update label="August 20, 2026">
  ### Answer "where is my check deposit?" from the drawer

  The [check deposits page](https://app.getlemma.com/_/check-deposits) now shows a processing timeline when you click on a check. The check deposits page also gained a status filter and pagination, so you can page through history and pull up only the deposits in a given state.
</Update>

<Update label="August 17, 2026">
  ### Connect Stedi as a remittance source

  You can now connect [Stedi](https://app.getlemma.com/_/settings/integrations/stedi). Enter your credentials, run the built-in connection test, and Lemma will pull your 835 remittances into your Payer Remittances feed. Each remittance now shows its source with the vendor's logo, so you can tell at a glance where it came from.
</Update>

<Update label="August 19, 2026">
  ### Invite licensed professional owners at application submit

  The review step of a PC, PLLC, or PA application now offers to invite any licensed professional owner who isn't already a collaborator. Each owner appears with a Yes/No toggle, defaulted to **Yes**. Leaving it on **Yes** sends the invite when you submit, and the invite carries over to the entity once the application is approved. See [Collaborate opening an account](/docs/guides/collaboration) for the full collaboration flow.
</Update>

<Update label="August 13, 2026">
  ### Add an owner without contacting Lemma

  Owners can now add another beneficial owner directly from **Settings > Profile**. The form collects the same details as the onboarding application, so you can add a new principal to your entity without reaching out to us.
</Update>

<Update label="August 11, 2026">
  ### NPI is optional during onboarding + edit your NPI from settings

  NPI is now optional during onboarding. New professional entities can sign up without an NPI and submit the NPI later from [Settings > Profile](https://app.getlemma.com/_/settings/profile) when they get one.
</Update>

<Update label="August 6, 2026">
  ### Onboard a Professional Association

  Professional Associations (PAs) can now sign up for Lemma alongside PCs and PLLCs. The application asks for the licensed physician who owns the practice and the entity's NPI, and PAs are covered by the same [licensed professional owner protections](/docs/guides/mso-pc-compliance) as other professional entities.
</Update>

<Update label="August 4, 2026">
  ### See when a mailed check's funds become available

  Check deposits into your [lockbox](/docs/guides/lockbox) now show a **Settlement date** in the mail detail drawer, so you can tell at a glance when a payer's check will be spendable.
</Update>

<Update label="August 4, 2026">
  ### Reconcile inbound ACH payments with the raw addenda

  Inbound ACH transfers now expose an `addenda` field across the [get transaction](/docs/api-reference/get-transaction), [list transactions](/docs/api-reference/list-transactions), [get inbound ACH transfer](/docs/api-reference/get-inbound-ach-transfer), and [list inbound ACH transfers](/docs/api-reference/list-inbound-ach-transfers) endpoints.

  `addenda` returns the raw freeform addenda lines the payer sent, in transmission order (for example the 835/837 `TRN` and `REF` claim-payment segments). To reconcile a healthcare claim payment, match the TRN carried in the addenda against the TRN in your 835 ERA.
</Update>

<Update label="August 3, 2026">
  ### Filter out zero-payment payer remittances

  The Payer Remittances page now marks fully written-off remittances (a \$0.00 payment) with their own **NON** state, so they no longer sit in the [reconciliation queue](/docs/billing/reconciliation) as unmatched. Filter by match state to hide them, or pull them up on their own when you need to review write-offs.
</Update>

<Update label="July 31, 2026">
  ### Issue debit cards from the API

  Platform partners can now [issue a virtual debit card](/docs/api-reference/create-card) with their own spending limits and [read it back](/docs/api-reference/get-card) through our API. Set caps per transaction, per day, per week, per month, or over the card's lifetime — the most restrictive limit applies.
</Update>

<Update label="July 31, 2026">
  ### Display card details in your own app

  Fetch a short-lived [iframe URL](/docs/api-reference/get-card-iframe) to display a partner-issued card's number, CVV, and expiration date directly to the account holder. The sensitive values render inside the iframe and never touch your servers, so you can surface a card in your product without taking on PCI scope.
</Update>

<Update label="July 31, 2026">
  ### Download settlement instructions from the API

  Platform partners can now [download a bank account's settlement instructions](/docs/api-reference/get-account-settlement-instructions) as a PDF through our API. Share the file with a payer who needs to send funds to the account by wire or ACH credit. The PDF includes the account and routing numbers, beneficiary name and address, and the receiving bank's details.
</Update>

<Update label="July 30, 2026">
  ### Checkbooks

  You can now order a checkbook for any Lemma account from [order checkbooks](https://app.getlemma.com/_/order-checkbooks). Each checkbook includes 150 checks and is mailed directly to you.
</Update>

<Update label="July 30, 2026">
  ### Card acquiring is live

  When a payer reimburses you by virtual card, Lemma now detects the card in your [lockbox](/docs/guides/lockbox) mail and charges it for you — no terminal to key the number into, no portal to log into. The money is deposited into your account, with every payment and fee landing on your [Transactions page](https://app.getlemma.com/_/transactions) as its own labeled line item: payments as **Acquiring**, fees as **Fee**.

  Read [How card payments show up](/docs/acquiring) and [Chargebacks](/docs/acquiring/chargebacks) to get started. Reach out to Lemma to get card acquiring enabled.
</Update>

<Update label="July 30, 2026">
  ### Attach documents to transfers and invoices

  You can now attach the paperwork behind a payment to the payment itself. Upload an invoice, loan agreement, or management services agreement when you [send a transfer](/docs/guides/move-money) or [raise an invoice](/docs/guides/invoicing), and it stays on the transaction — so months later the record explains itself instead of prompting a question.

  * **Both sides hold the same document.** Attach a file to a transfer between two entities, or to an invoice, and the other entity sees it on their side of the transaction. For MSO-PC groups, that turns an intercompany fee into a documented, arm's-length record rather than an unexplained transfer.
  * **Readable before approval.** Whoever signs off on a transfer, and whoever decides whether to pay an invoice, can open the attachment while deciding — so the approval is made against the contract, not against a note saying one exists.
  * **It stays with the money.** If a payment is later returned or reversed, the attachment shows on that transaction too, with nothing to re-attach.
  * **External payments stay private.** A document attached to an external transfer is for your records only and is never sent to the recipient.

  PDF, PNG, and JPEG files up to 10 MB each — one per transfer, up to ten per invoice. See [Attachments](/docs/guides/attachments) for who can see what.
</Update>

<Update label="July 28, 2026">
  ### Invoicing is live

  [Invoicing](/docs/guides/invoicing) is now available on Lemma. Bill another entity for a payment without giving them access to your accounts, or needing access to theirs. Each invoice carries line items that lock once it's sent, so both sides keep an auditable record of what the payment covers.

  Today you can send invoices to other entities on Lemma, which is useful if you run an MSO-PC structure: management fees move between the two entities on a documented, arm's-length record, and the PC's owner still decides whether to pay.

  We're also working on external invoices, so you'll be able to bill clients who aren't on Lemma.
</Update>

<Update label="July 21, 2026">
  ### Transaction categories overhaul

  We shipped several new [transaction category](/docs/guides/transaction-categories) features to streamline your bookkeeping easier:

  * **Categorize any transfer as you send it.** ACH, wire, RTP, FedNow, and mailed checks join book transfers with an optional category step, so the transaction arrives already filed.
  * **Categorize pending transactions.** No need to wait for settlement, tag a transaction while it's still pending.
  * **Lemma transactions categorize themselves.** Bank fees, loan disbursements, and deposit bonuses are filed for you, cutting down the bookkeeping you do by hand.
</Update>

<Update label="July 20, 2026">
  ### Retrieve payer remittances and their 835s from the API

  Platform partners can now pull a paginated list of an entity's [remittances](/docs/api-reference/list-remittances) and retrieve each one's [835 electronic remittance advice (ERA)](/docs/api-reference/get-remittance-era) through our API.

  Each remittance includes the payer, trace number, paid amount, and remittance date. Fetch any remittance's 835 as raw X12 to post it straight into your billing or EHR system.
</Update>

<Update label="July 20, 2026">
  ### New transactions table on card pages

  Card pages now show all of the card's transactions. Sort by date or amount to find what you're looking for.
</Update>

<Update label="July 19, 2026">
  ### Custom spending limits for debit cards

  When issuing a new card, you can now set a max purchase amount and a max total spend limit that resets daily, weekly, or monthly.
</Update>

<Update label="July 16, 2026">
  ### Set a category when sending a book transfer

  You can now choose a [transaction category](https://app.getlemma.com/_/settings/transaction-categories) while sending a book transfer — it's applied to the created transaction automatically, so you don't need to open the transactions page later to categorize it.
</Update>

<Update label="July 15, 2026">
  ### Licensed professional owner protections

  When you onboard a PC or PLLC, you now identify the licensed physician who owns the practice as part of your application. Once recorded, that person keeps guaranteed control of the entity's money, which helps your practice meet corporate practice of medicine laws:

  * They can approve their own transfers and cash sweep changes, even when your [approval rules](https://app.getlemma.com/_/requests/configure-rules) would otherwise require another team member to sign off.
  * No one can remove them or reduce their access, not even the physician themselves.
</Update>

<Update label="July 15, 2026">
  ### Create your own transaction categories

  You can now add custom transaction categories from [Transaction Category settings](https://app.getlemma.com/_/settings/transaction-categories). Rename a custom category any time, and archive it once you're done with it. Archived categories stay attached to transactions they already tagged, but are hidden from the list when categorizing new ones.
</Update>

<Update label="July 9, 2026">
  ### List inbound ACH transfers and check deposits from the API

  Platform partners can now pull paginated lists of [inbound ACH transfers](/docs/api-reference/list-inbound-ach-transfers) and [check deposits](/docs/api-reference/list-check-deposits) through our API.

  Both endpoints return newest results first and accept an optional account filter, so you can reconcile a single account or sweep across every account you can access. Listing inbound ACH transfers is the fastest way to find deposits from payers, such as payments from an insurance company.
</Update>

<Update label="June 29, 2026">
  ### Customize your notification emails

  Each person can now choose which notification emails they receive, including transfer approval requests and microdeposit alerts. Previously these always sent; now you decide what lands in your inbox from your [notification settings](https://app.getlemma.com/_/settings/profile/notifications).
</Update>

<Update label="June 25, 2026">
  ### Fetch transfer details from the API

  Platform partners can now retrieve the details of a [book transfer](/docs/api-reference/get-book-transfer) or an [ACH transfer](/docs/api-reference/get-ach-transfer) through our API. This is particularly useful for ACH transfers, which can take several hours to process, so you can see when one transitions from a pending to a submitted state.
</Update>

<Update label="June 24, 2026">
  ### Per-rail approval rules

  You can now tailor approval rules to each payment rail. Set different requirements for ACH, wires, check mailing, and more. For example, require owner approval for small patient refunds you are sending as a check, but allow larger ACHs to go through without review.
</Update>

<Update label="June 10, 2026">
  ### Approval rules for transfers

  Add a layer of oversight to outgoing money. With [approval rules](https://app.getlemma.com/_/requests/configure-rules) turned on, a transfer must be approved by an owner before it's sent.
</Update>

<Update label="June 2, 2026">
  ### Attach a document when mailing a check

  You can now upload a PDF to include with any check you mail — useful for sending an itemized statement alongside a [patient refund](/docs/billing/patient-refunds). The document is printed in black and white and mailed in the same envelope as the check.
</Update>

<Update label="May 29, 2026">
  ### Balance history

  View your account balance over time with the new balance history chart on the home page and dedicated account pages. Choose from four lookback periods — **1 month**, **3 months**, **1 year**, or **year-to-date** — to zoom in on the time range that matters.
</Update>

<Update label="May 14, 2026">
  ### Transaction categories

  Categorize any transaction directly from the detail panel. A category column is included in every [CSV export](/docs/guides/export-transactions).

  For MSOs, categories like **MSO Fees** and **MSO Loan Repayment** create an audit trail that keeps fee and loan flows legally distinct. [See the full list of categories.](/docs/guides/transaction-categories)
</Update>

<Update label="May 8, 2026">
  ### Email when microdeposits arrive

  Payroll companies often send small deposits when you're linking a new bank account and asks you to confirm the amounts to prove account ownership.

  You'll now receive an email the moment those deposits land, so you can finish verification without constantly checking your Lemma transactions.
</Update>

<Update label="May 8, 2026">
  ### Filter, sort, and export on Payer Remittances

  The Payer Remittances now supports filtering and sorting your data. Filters are saved to your URL so you can bookmark the page or share a link with a coworker.
</Update>

<Update label="May 8, 2026">
  ### Click-to-copy on transaction details

  Clicking transaction metadata will automatically copy it — useful for billing teams who regularly copy trace numbers.
</Update>

<Update label="May 8, 2026">
  ### ACH addenda surfaced

  The free-text addenda field that payers and senders include with an ACH transfer is now shown in the transaction details. The addenda is useful for billing teams to match payments to invoices.
</Update>

<Update label="May 7, 2026">
  ### Type dates directly into calendar pickers

  Every date input in the dashboard now lets you type in case you want to skip using a mouse to select a date on the calendar.
</Update>

<Update label="May 6, 2026">
  ### Inline notes on lockbox items

  Leave a note on any item in your lockbox feed without leaving the page. Notes are useful for flagging items that need follow-up ("call payer"), recording which payments were posted to your EHR, and any other billing team workflow.
</Update>

<Update label="May 5, 2026">
  ### Unified entity switcher

  The entity switcher in the top-left now shows everything that's relevant to your account in one place:

  * **Active entities** you already manage
  * **Pending applications** that haven't finished onboarding
  * **Invitations** from practices that have added you as a collaborator

  Each row shows the entity's full legal name on hover, which helps MSO operators tell apart similarly-named PCs at a glance. [Learn more about managing multiple entities.](/docs/guides/own-multiple-entities)
</Update>

<Update label="May 3, 2026">
  ### Export transactions to QuickBooks

  Export your Lemma transactions as a `.qbo` file and import them straight into QuickBooks. Exports respect any active filters on the [transactions page](https://app.getlemma.com/_/transactions), so you can pull a single account, date range, or category.
</Update>

<Update label="April 29, 2026">
  ### Collaborative application

  Fill out your Lemma account application alongside coworkers in real time. Each person can enter the sections they're responsible for — like beneficial owner details — without sharing sensitive personal information. Sensitive fields like Social Security numbers open in a private popup and are encrypted immediately, invisible to other collaborators. [Learn more about collaborating on an application.](/docs/guides/collaboration)
</Update>

<Update label="April 25, 2026">
  ### Hide account and routing numbers by default

  Account and routing numbers on the [accounts page](/docs/guides/accounts) are now redacted by default and only shown when you click to reveal them. This reduces incidental exposure during screen shares and demos.
</Update>

<Update label="April 24, 2026">
  ### Mail checks for vendor payments

  Our dashboard lets you mail checks to vendors directly, eliminating trips to the post office and making it easy to handle payments like government fees.
</Update>

<Update label="April 21, 2026">
  ### Disable sweeps to keep them as drafts

  Collaborate on cash sweeps by disabling them and continuing to edit them until you're ready to turn them on. All cash sweeps are active by default when published but you can disable them from the [cash sweeps page](https://app.getlemma.com/_/sweeps) to stop them from running until you're ready.
</Update>

<Update label="April 19, 2026">
  ### Recent transactions in the accounts and card detail pages

  The card and bank account pages now list recent transactions right alongside the account info, so you can quickly find what you need without jumping over to the main [transactions page](https://app.getlemma.com/_/transactions).
</Update>

<Update label="April 17, 2026">
  ### Mobile check deposits

  Deposit paper checks from your phone on the [move money page](https://app.getlemma.com/_/move-money) of the dashboard. Snap a photo of the front and back and funds are credited to your account once the check clears. A live viewfinder with edge detection helps you capture a clean image on the first try. Depositing from a desktop works too — upload a photo of the front and back of the check instead of capturing one with the camera.
</Update>

<Update label="April 14, 2026">
  ### Cash sweeps

  Set up automated transfers that run on a recurring schedule. Define rules for each sweep — including the amount, destination, days of the week, and time of day — so money is always where it needs to be without manual intervention.
</Update>

<Update label="April 8, 2026">
  ### Dedicated entity links

  Each entity now has its own URL so you can keep a tab open for each one you control. The URLs look like `app.getlemma.com/entity_123` and `app.getlemma.com/entity_456`. This is important for MSO-PC structures where one individual may own multiple entities and wants to bookmark direct links to specific dashboards. [Read our docs to learn how to link different entities.](/docs/guides/own-multiple-entities)
</Update>

<Update label="April 5, 2026">
  ### Hold release dates

  Check deposits now show when the hold is expected to release. This is visible on the transaction detail panel in the dashboard and in [the API available to our partners](/docs/api-reference/get-check-deposit).
</Update>

<Update label="April 4, 2026">
  ### Payer update concierge

  Our concierge team will update your banking information with payers. Visit the [accounts page](https://app.getlemma.com/_/accounts) to request a call.
</Update>

<Update label="April 3, 2026">
  ### Digital wallets

  Every debit card is now compatible with Apple Pay and Google Pay.
</Update>

<Update label="March 28, 2026">
  ### Instant payments

  Send money instantly with two new payment rails: **Real-Time Payments (RTP)** and **FedNow**. Both are free, settle in seconds, and are available from the [move money](/docs/guides/move-money) page. Each transfer validates the recipient's routing number to confirm the bank supports instant payments before you send.
</Update>

<Update label="March 27, 2026">
  ### Plaid integration

  Your Lemma accounts are now available through Plaid. Connect Plaid-powered apps like Venmo, QuickBooks, and other accounting software to see your Lemma balances and transactions alongside your other financial accounts.
</Update>

<Update label="March 25, 2026">
  ### Self-serve debit cards

  Issue virtual and physical debit cards on your own — no need to contact our team. Create as many virtual cards as you need. Physical cards are limited to one per person, per entity.
</Update>

<Update label="March 23, 2026">
  ### CSV transaction export

  Export transactions to CSV directly from the [transactions page](https://app.getlemma.com/_/transactions). Exports respect any active filters, so you can pull exactly the transactions you need for reconciliation or accounting.
</Update>

<Update label="March 23, 2026">
  ### Referral program

  Refer another entity to Lemma and you'll each receive \$250 when they get their first patient or insurance payment!
</Update>

<Update label="March 21, 2026">
  ### Foreign currency

  Card transactions made in a foreign currency now show the original presentment amount alongside the settled total.
</Update>

<Update label="March 19, 2026">
  ### Multi-factor authentication

  Secure your account with authenticator apps or SMS verification. Setup takes under a minute.
</Update>

<Update label="March 16, 2026">
  ### Card spending controls

  Set per-transaction spending limits on card transactions. Transactions that exceed your policy are declined at the point of sale.
</Update>

<Update label="March 13, 2026">
  ### Check mailing

  Send physical checks directly from Lemma. Enter a recipient, amount, and mailing address. Lemma prints and mails the check with your practice's name and address as the payer. Useful for vendors that don't accept electronic payments.
</Update>

<Update label="March 9, 2026">
  ### Account verification letters

  Generate and download official account verification letters issued by our banking partners. Useful for credentialing, payer enrollment, or proving account ownership to third parties.

  ### Void check downloads

  Download a void check PDF for any account. Helpful when a payer or payroll provider requires a voided check to set up ACH deposits.
</Update>

<Update label="March 9, 2026">
  ### Real-time transactions

  Posted transactions now appear within 5 seconds, down from an average of 30 seconds.
</Update>

<Update label="March 7, 2026">
  ### Settlement instruction PDFs

  Download settlement instruction documents for any account. Settlement instructions include your account's routing number, account number, and payee details. Hand these to payers or billing companies to route payments correctly.
</Update>

<Update label="March 5, 2026">
  ### Cross-entity internal transfers

  Move funds between any of your Lemma accounts instantly, including across different legal entities. Ideal for MSO structures where a management company needs to allocate funds to individual entity accounts. The transfer form shows full entity context on the review step so you always know where money is going.
</Update>

<Update label="March 4, 2026">
  ### Team management and role-based access

  Invite team members via email link with role-based permissions. Owners can create recipients, open accounts, and send money. Read-only users get full visibility without the ability to initiate transfers, ideal for billing staff or accountants who need to monitor activity.
</Update>

<Update label="February 26, 2026">
  ### Sole proprietor onboarding

  Solo practitioners can now onboard with a streamlined application flow tailored to sole proprietorships.
</Update>


# Email notifications
Source: https://getlemma.com/docs/email-notifications

Choose which Lemma emails you receive, for each entity you belong to.

Lemma emails you when something happens that you may need to act on, like a transfer waiting on your approval. Each person chooses which of these emails they receive from the [notification settings page](https://app.getlemma.com/_/settings/profile/notifications).

## Notifications you can turn off

### Microdeposit emails

Sent when microdeposits — verification deposits of a dollar or less, sent by another service you're linking your Lemma account to — arrive in one of your entity's bank accounts. Lemma checks once a day and includes any microdeposit that arrived in the last three days, so a deposit that lands overnight reaches you the following morning. Every member of the entity can receive these.

### Transfer approval emails

Sent when a transfer is held by an [approval rule](/docs/guides/approval-rules) and needs your decision. This also covers [invoices](/docs/guides/invoices-paid) whose payment is waiting on an approval.

### Cash sweep approval emails

Sent when someone creates, edits, or turns off a [cash sweep](/docs/guides/cash-sweeps) and the change needs your approval. The sweep's status doesn't change until an owner approves it.

<Info>
  Only owners can decide approval requests, so only owners receive the two
  approval notifications. You are never emailed about a request you raised
  yourself, even when you're the one who has to approve it.
</Info>

## Money in and out

Get an email each time money moves on one of your open accounts. These are off until you turn them on. Pick the payment types you want to hear about, set separately for money coming in and money going out:

* **Money in**: ACH transfers, wire transfers, check deposits, and card processing.
* **Money out**: ACH transfers, wire transfers, checks you send, and card processing refunds and chargebacks.

Each email shows the amount, who the money was from or to, and the account it moved through, with a link to the transaction.

To hear about only larger payments, set an amount under **Money in** or **Money out** and Lemma emails you only for payments at or above it. Leave it blank to be notified for any amount.

Internal transfers between your own accounts, Lemma fees, and loan activity don't trigger these emails.

## Settings apply to one entity at a time

Your choices are stored per person and per entity, so turning off transfer approval emails for one entity leaves your other entities untouched, and your teammates' settings are unaffected either way. If you [manage several entities](/docs/guides/own-multiple-entities) and want the same choices everywhere, turn on **Share these settings across all my entities** at the top of the page. While it's on, every change you make applies to all of them.

## Emails you can't turn off

Emails such as "You've been invited to \[your entity] on Lemma" can't be turned off, because they're necessary for your account to function.


# Entity settings
Source: https://getlemma.com/docs/entity-settings

Manage your entity profile, team, security, fees, integrations, and documents.

Open [Settings](https://app.getlemma.com/_/settings/profile) from the entity you want to manage. Use the entity dropdown in the sidebar to switch to a different entity before making a change.

An entity is the legal business that holds your Lemma bank accounts, cards, transactions, and team membership. An entity can be a professional corporation, medical practice, or management company. One entity can have multiple bank accounts, cards, transactions, and team members.

## Access at a glance

If you can't see something in a settings page, you might not have permission to access it. Your (team role)\[/guides/team-management] controls what you can see.

<Badge>Owners only</Badge> Owner-only controls include entity address, NPI, EIN reveal, controllers and beneficial owners, user management, integrations, and more.

<Badge>Accounting and owners</Badge> Accounting members and owners can manage custom transaction categories but not most of the core entity settings.

## Settings pages

<CardGroup>
  <Card title="Profile" icon="user" href="/docs/entity-settings/profile">
    View business information, edit the entity address, manage NPI and beneficial-owner information, and update your personal notification, email, and password settings.
  </Card>

  <Card title="Users" icon="users" href="/docs/entity-settings/users">
    Invite colleagues to your team and control their account access.
  </Card>

  <Card title="Security" icon="shield-check" href="/docs/entity-settings/security">
    Configure multi-factor authentication for your Lemma login.
  </Card>

  <Card title="Fees" icon="receipt" href="/docs/entity-settings/fees">
    Choose the account Lemma uses for monthly fees and review fee invoices.
  </Card>

  <Card title="Integrations" icon="plug" href="/docs/entity-settings/integrations">
    Connect enabled EHR, remittance, banking, and accounting integrations.
  </Card>

  <Card title="Share documents with Lemma" icon="file-text" href="/docs/entity-settings/documents">
    Securely upload and review requested documents when Lemma enables document collection for your entity.
  </Card>

  <Card title="Transaction categories" icon="tags" href="/docs/entity-settings/transaction-categories">
    Create, rename, and archive custom transaction categories.
  </Card>
</CardGroup>


# Share documents with Lemma
Source: https://getlemma.com/docs/entity-settings/documents

Securely share requested documents with Lemma.

[Share documents with Lemma](https://app.getlemma.com/_/settings/documents) is an on-demand secure upload area. Lemma toggles this page on only if it needs documents from you. Use this page instead of sending sensitive business documents by email.

This page is for sharing requested business documents. EOB processing and EOB-to-835 conversion are separate workflows. Read the [EOB processing guide](/docs/billing/eob-processing) to learn how Lemma parses EOBs, reconciles payments, and creates 835 files.

<Badge>Owners only</Badge> Owners can upload documents and download previously uploaded files. Other members may see the document list when the page is enabled, but download controls are blocked for them.

## Share a requested document

1. Open [Settings → Your documents](https://app.getlemma.com/_/settings/documents).
2. Select a **Document type** that matches Lemma's request.
3. Click or drag a file into the upload area.
4. Wait for the success confirmation.

You must select a document type before the file area becomes active. The accepted file types and maximum size are shown beneath the upload area.

## Review shared documents

The **Uploaded documents** section lists the document name, type, and upload date. Owners can click on a document to download it.


# Fees settings
Source: https://getlemma.com/docs/entity-settings/fees

Choose the entity account used for monthly Lemma fees and review fee invoices.

[Fees settings](https://app.getlemma.com/_/settings/fees) has two parts: the account Lemma uses to debit monthly fees and the invoices for fees charged to the entity.

## Bank account to pay fees

The selected account is used for monthly fee billing. Lemma debits monthly bills on the first day of the month.

<Badge>Owners only</Badge> Owners can open the account selector and choose a different entity bank account. Other roles can see the current selection but cannot change it.

If the expected account is not available, confirm that the account belongs to the selected entity and is visible to your role. Contact Lemma if the account still cannot be selected.

## Fee invoices

The invoice list shows fee invoices for the entity. Open an invoice to review its details. The list is read-only from Settings; changing the fee account does not rewrite past invoices.

## Changing the default account

1. Confirm that you are viewing the correct entity. Use the entity dropdown in the sidebar to switch entities if needed.
2. Open [Settings → Fees](https://app.getlemma.com/_/settings/fees).
3. Select the account dropdown under **Bank account to pay fees**.
4. Choose the account to use for future monthly debits.

The new default applies to future fee billing. It does not move money immediately or change any other account setting.


# Integrations settings
Source: https://getlemma.com/docs/entity-settings/integrations

Connect supported banking, accounting, EHR, and remittance tools to your entity.

[Integrations settings](https://app.getlemma.com/_/settings/integrations) lists connections enabled for your entity. The page appears only when at least one integration is enabled for the entity.

<Badge>Owners only</Badge> Owners connect, disconnect, and manage integration credentials. Integration availability is controlled by Lemma, so an integration that exists for another entity may not be available here.

## Plaid

Plaid securely connects external bank accounts to Lemma so transactions can sync. Select **Connect Plaid**, complete Plaid Link, and choose the accounts to connect. The page shows whether Plaid is connected and lists connected external accounts. You can remove a connected account from the Plaid detail page.

## QuickBooks Online

QuickBooks Online receives Lemma account transactions through a native bank feed. Start the connection in QuickBooks Online:

1. Open **Accounting → Bank transactions**.
2. Select **Link account** and search for **Lemma**.
3. Sign in with your Lemma credentials when QuickBooks redirects you.
4. Confirm the connection after QuickBooks returns you to Lemma.

After connection, the page groups accounts by connected status and shows that transactions sync in real time as they clear.

## Canvas Medical

Canvas Medical connects to Lemma so reconciled remittances can be posted to matching claims. You need your Canvas instance URL and the API key for the Lemma plugin installed on that instance.

## Candid Health

Candid Health lets Lemma pull remittances and reconcile them against claims. An organization administrator must create an API `client_id` and `client_secret` in Candid under **Users & Credentials → API credentials**.

## Healthie

Healthie lets Lemma read billing data. When enabled for your connection, Lemma can also post lockbox EOBs and sync deposit status back to Healthie. The connected page shows the capabilities granted to Lemma so you can review them.

## Stedi

Stedi lets Lemma pull 835 remittance advices (ERAs) read-only and reconcile them against claims. Stedi does not provide read-only API keys, so the key must be created by a member with the Operator role in Stedi.

## EHR and accounting integrations

Lemma supports both EHR and accounting integrations. Examples of EHR and remittance connections include Canvas Medical, Candid Health, Healthie, and Stedi. Examples of accounting connections include QuickBooks Online, Xero, and NetSuite. The connections shown in your settings depend on what Lemma has enabled for your entity.

For the complete list of supported accounting platforms and accounting connection guidance, read the [accounting integrations guide](/docs/accounting-integrations). That guide covers accounting platforms; it is not a complete list of EHR integrations.

If the integration you need is not shown, contact Lemma. Do not paste API keys or secrets into a support message.


# Notification settings
Source: https://getlemma.com/docs/entity-settings/notifications

Customize the notification emails Lemma sends to you.

[Manage notification settings](https://app.getlemma.com/_/settings/profile/notifications) is where you customize the notification emails Lemma sends to you.

These preferences belong to your Lemma user account. You can keep separate preferences for each entity or turn on **Share these settings across all my entities** to use one set everywhere.

## Approvals and alerts

Choose the alerts you want to receive:

* **Microdeposit emails** when microdeposits arrive in your bank accounts
* **Transfer approval emails** when a transfer requires your approval
* **Cash sweep approval emails** when editing a cash sweep requires your approval

## Money in and out

Choose which transaction types should send an email when money moves. You can set preferences separately for money in and money out.

### Money in

* ACH transfers
* Wire transfers
* Check deposits
* Card processing

### Money out

* ACH transfers
* Wire transfers
* Checks sent
* Card processing refunds and chargebacks

For each direction, you can set a minimum amount. Leave the minimum amount empty to receive notifications for every matching transaction, or enter an amount to receive notifications only when the transaction meets that threshold.

## Update your preferences

1. Open [Manage notification settings](https://app.getlemma.com/_/settings/profile/notifications).
2. Turn on **Share these settings across all my entities** if you want one set of preferences everywhere.
3. Select the approval, alert, and transaction notifications you want.
4. Set thresholds for money-in and money-out notifications when needed.

Changes save as you make them.


# Profile settings
Source: https://getlemma.com/docs/entity-settings/profile

View entity information and manage your personal profile settings.

[Profile settings](https://app.getlemma.com/_/settings/profile) has two sections: **Business Information** for the selected entity and **Your Information** for your Lemma user account.

<Frame>
  <img alt="Lemma profile settings page showing business information and personal information links." />
</Frame>

## Business Information

### Entity name

The entity name is shown for reference. It identifies the business whose settings you are viewing.

### Address

<Badge>Owners only</Badge>

The address shown here is the entity's business address. Click the green **Edit** link next to **Address**, update the required address fields, and select **Save**. Select **Cancel** to discard an edit in progress.

You can edit your entity's address directly from this page. Updating the address does not change the address of another entity in your account.

### NPI

<Badge>Owners only</Badge>

The NPI is the entity's 10-digit National Provider Identifier. Select **Edit**, enter a valid NPI, and choose **Save**. Lemma validates the check digit before saving. An invalid value stays in the dialog so you can correct it.

### EIN

<Badge>Owners only</Badge>

Owners can reveal the entity EIN using the eye control. The EIN is masked until you choose to reveal it. Other roles do not receive the reveal control.

### Controllers and beneficial owners

<Badge>Owners only</Badge>

This section shows how many controllers and beneficial owners are on file. Select **Add** to open the owner information flow and add another person to the entity's records. If you need to change the licensed professional owner on file, contact Lemma.

### Transaction categories

The Profile page links to transaction category settings. All members who can work with transactions can apply an existing category. <Badge>Accounting and owners</Badge> Accounting members and owners can create, rename, and archive custom categories. Default categories cannot be renamed or archived.

See [Transaction categories](/docs/entity-settings/transaction-categories) for the full workflow.

## Your Information

### Your name

Your name comes from your Lemma user profile and is shown at the top of this section.

### Notification settings

Select [Manage notification settings](/docs/entity-settings/notifications) to customize the notifications Lemma sends you. You can configure approval, alert, and transaction notifications. You can also choose whether to share these preferences across all entities you access.

### Email address

Select **Update email** to change the email address used for your Lemma account. For security, you will need to click a link in *both* your old and your new email addresses before your email changes.

### Password

Select **Update password** to change your password. Use a strong, unique password and never share it with another team member.

## What can I edit?

The Profile page is intentionally mixed-access. Everyone with access to the entity can see the business and personal information that applies to them, while entity-level changes are protected by the owner permission. If a green edit link is missing, another owner must make that change.


# Security settings
Source: https://getlemma.com/docs/entity-settings/security

Protect your Lemma sign-in with an authenticator app or text message.

[Security settings](https://app.getlemma.com/_/settings/security) manages multi-factor authentication (MFA) for your Lemma user account. MFA protects your sign-in even if someone learns your password.

MFA is configured per user, not per entity. If you access multiple entities, the same factors protect your Lemma account across them.

## Available methods

### Authenticator app

Use an app such as Google Authenticator, Authy, or Duo to generate verification codes.

To enable it:

1. Select **Enable** next to **Authenticator app**.
2. Scan the QR code with your authenticator app. If you cannot scan it, enter the displayed secret manually.
3. Enter the six-digit verification code.
4. Select **Verify and enable**.

### Text message (SMS)

SMS sends a one-time verification code to a mobile phone each time you sign in. Landline numbers cannot receive SMS codes.

To enable it:

1. Select **Enable** next to **Text message (SMS)**.
2. Enter a mobile phone number.
3. Select **Send code**.
4. Enter the six-digit code sent by text.
5. Select **Verify and enable**.

## Disable a method

Select **Disable** next to the method you want to remove and complete the verification step. If another factor is enrolled, Lemma may ask you to verify with it before disabling the selected factor. This protects the session while you change security settings.

Keep at least one secure factor enabled whenever possible. If your phone or authenticator is unavailable, contact Lemma support rather than sending a verification code through an untrusted channel.


# Transaction category settings
Source: https://getlemma.com/docs/entity-settings/transaction-categories

Create, rename, and archive custom categories for your entity.

[Transaction category settings](https://app.getlemma.com/_/settings/transaction-categories) helps your team organize and report on transactions. Default categories are available to every entity. Custom categories are specific to the selected entity.

<Badge>Accounting and owners</Badge> Accounting members and owners can manage custom categories. Any member who can access a transaction can apply an existing category from transaction details or when sending a transfer.

## Custom categories

### Create a category

Select **Add category**, enter a name, and save it. Use a name that makes the bookkeeping purpose clear. Lemma limits custom category names to 30 characters.

### Rename a category

Open the action controls for a custom category, select **Edit**, enter the new name, and save. Renaming changes the label available for future use; it does not rewrite the transaction history or alter the underlying transaction.

### Archive a category

Choose the archive action and confirm. An archived custom category is removed from the category picker for new transactions, but transactions already tagged with it keep their existing label. Archiving is not the same as deleting historical categorization.

## Default categories

Default categories appear in their own list. They are provided by Lemma and cannot be renamed or archived from this page.

## Applying a category

You do not need to open Settings to categorize a transaction:

* Open a transaction and choose a value from **Category**.
* When sending money, choose the optional **Category** before submitting the transfer. If the transfer requires approval, the category is applied when the transfer is approved and sent.

See the [Transaction categories guide](/docs/guides/transaction-categories) for the full category list and reporting guidance.


# Users settings
Source: https://getlemma.com/docs/entity-settings/users

Invite team members, assign roles, manage account visibility, and remove access.

[Users settings](https://app.getlemma.com/_/settings/users) lists every member of the selected entity and any pending invitations. Each member can have a **banking permission** and a separate **practice permission**.

<Badge>Owners only</Badge> Owners can invite users, edit member access, resend or cancel invitations, and remove members. Other roles can review the list and the permissions shown there.

## Invite a user

1. Select **Invite User**.
2. Enter the person's email address.
3. Choose a banking permission.
4. Choose the optional practice permission.
5. If account-level visibility is enabled, choose the bank accounts the member can see.
6. Send the invitation.

Pending invitations appear in the Users table with the invited date. Owners can resend an invitation or cancel it from the row actions.

## Banking permissions

Banking permissions control access to Lemma's financial features. They are hierarchical: Accounting includes Read Only, and Owner includes Accounting.

### Read Only

Read Only members can view balances and transactions, export statements and reports, categorize transactions, deposit checks, and charge payer virtual cards. They cannot move money, issue debit cards, manage users, or change entity settings.

### Accounting

Accounting members can do everything in Read Only, plus move money, open bank accounts, issue debit cards, create cash sweeps, manage external recipients, send invoices, and create or rename transaction categories. Accounting members cannot manage users or owner-only entity settings.

### Owner

Owners have the full banking permission set. In addition to Accounting capabilities, they can accept loans, approve requests and set approval rules, invite and remove users, order checkbooks, upload requested documents, and manage entity settings.

## External accounts

<Badge>Accounting and owners</Badge>

To manage saved external accounts for future transfers, open [External accounts](https://app.getlemma.com/_/external-recipients) to see all saved recipients. Select [New External Recipient](https://app.getlemma.com/_/external-recipients/new) to add another destination. The [External accounts guide](/docs/guides/external-accounts) explains how saved recipients work.

## Practice permissions

Practice permission is independent of banking permission. The **Billing Team** option provides access to:

* Lockbox mail and note editing
* Health data imported from your EHR
* EOB and ERA approval workflows
* Direct EOB uploads

Removing practice permission does not automatically remove banking permission, and changing banking permission does not automatically remove practice permission.

## Edit member access

Depending on your entity's configuration, selecting **Edit access** opens controls for:

* Banking permission
* Practice permission
* The bank accounts visible to that member

When a member is an Owner, account selections are retained but do not limit the Owner: owners can always see every account. If the member later leaves the Owner role, the saved selection applies again.

Changing banking permission to **No access** removes access to banking balances, transactions, payments, cards, and statements. It does not remove practice access. To remove all membership access, use **Remove from entity** instead.

## Safe role changes

Lemma protects the last owner. You can lower your own role only when another owner already has access to the entity. This prevents you from locking the entity out of owner controls.

After a self-downgrade, you lose the ability to change roles. You cannot promote yourself again, including from Read Only to Owner. Another owner must restore your role.

A downgrade does not cancel the member's card. Removing the member cancels their card.

The licensed professional owner on file may be protected from role changes and removal. If an action is disabled, hover over it for the reason shown by Lemma.

## Remove a member

Select the row actions menu, choose **Remove from entity**, and confirm. Removal cannot be undone from the Users page. The removed member loses access to the entity; if they need access again, an owner must invite them again.

Removing yourself affects the selected entity only. If you belong to other entities, those memberships remain available.


# Accounts
Source: https://getlemma.com/docs/guides/accounts

View and manage your Lemma bank accounts.

The [Accounts page](https://app.getlemma.com/_/accounts) lists all bank accounts associated with your organization. Each account has its own account number, routing number, and balance.

## Viewing account details

Select an account to see:

* **Account number** and **routing number** for receiving payments
* **Current balance** — the amount available for transactions
* **Held balance** — funds that are pending (e.g., outbound transfers that haven't settled)

<Note>
  For security, account and routing numbers are hidden by default. Click the redacted value to reveal it. This reduces incidental exposure during screen shares.
</Note>

## Downloading account documents

From the account's detail view, the **Account Information** card lets you download:

* **Settlement Instructions** — your account and routing numbers, beneficiary name and address, and the receiving bank's details. Hand this to a payer or billing company that needs to send a wire or ACH credit to the account.
* **Void Check** — a voided check PDF. Useful when a payer or payroll provider requires one to set up ACH deposits.
* **Account Verification Letter** — an official letter issued by our banking partner, confirming account ownership. Useful for credentialing or payer enrollment.
* **Bank Statements** — monthly statements for your bank account.

<Frame>
  <img alt="Settlement Instructions, Void Check, and Account Verification Letter download buttons on an account's detail page" />
</Frame>

## Multiple accounts

Your organization can have multiple bank accounts. This is useful for separating funds by purpose, such as keeping operating expenses separate from patient collections.

## Renaming an account

Owners can rename a bank account by clicking the pencil icon beside the account name in the detail view. Account names must be unique within your entity.

## Cards

Every account comes with free debit cards, including virtual cards, physical cards, and custom spending limits. See the [Cards guide](/docs/guides/cards) for details.

## Balance History

The Balance History chart shows how your account balance has changed over time.

Choose a lookback period to filter the chart:

* **1 month** — the last 30 days
* **3 months** — the last 90 days
* **1 year** — the last 365 days
* **Month-to-date** — from the 1st of the current month through today
* **Quarter-to-date** — from the 1st of the current quarter through today
* **Year-to-date** — from January 1st of the current year through today

<Frame>
  <img alt="Balance history chart with time period selector" />
</Frame>

## Ordering checkbooks

Every bank account's page includes a button for ordering checks. Checkbooks are subject to a \$45 fee. Read the [checkbooks guide](/docs/guides/order-checkbooks) for more details.


# Approval rules
Source: https://getlemma.com/docs/guides/approval-rules

Require an owner to sign off on a transfer before any money leaves your account.

Approval rules add a layer of oversight to outgoing money. When a rule is in place, a transfer above the amount you set is held until an owner reviews and approves it. Use this to catch mistakes before funds move, while letting smaller, routine payments go through without friction.

This applies to every way money leaves your account: ACH, wires, and other external transfers, transfers between your own Lemma accounts, and mailed checks such as [patient refunds](/docs/billing/patient-refunds).

## Setting up a rule

Only owners can configuring approval rules.

<Steps>
  <Step title="Open approval rules">
    Go to [Move Money > Requests > Configure rules](https://app.getlemma.com/_/requests/configure-rules).
  </Step>

  <Step title="Set a threshold">
    Enter the amount above which a transfer must be approved. Rules apply per
    payment rail, so you can choose which kinds of transfers are subject to review
    — for example, you can auto-approve transfers between accounts in the same
    legal entity.
  </Step>

  <Step title="Save">
    Save your changes. The new rule takes effect immediately and applies to every
    transfer requested from then on.
  </Step>
</Steps>

## Approving transfers

Only **owners** can approve transfers. A team member with a different role can
request a transfer, but it cannot be sent until an owner approves it.

An owner can approve a transfer they requested themselves. Owners are the
entity's final authority over its money, so a rule set above an owner's own
transfers slows them down rather than controlling them — and a single-owner
entity would otherwise be waiting on a second person who doesn't exist. Every
approval is recorded with who gave it, self-approvals included, so if you want a
second person to sign off on your own transfers, keep the threshold at a level
your day-to-day transfers stay under and have another owner review the rest.

When a transfer needs approval, it appears on the [requests page](https://app.getlemma.com/_/requests), and the owners on the account are notified by email. Owners can disable notification emails from the [notification settings page](https://app.getlemma.com/_/settings/profile/notifications).

<Steps>
  <Step title="Open the request">
    Go to [Move Money > Requests](https://app.getlemma.com/_/requests) and select the pending
    transfer. You'll see who requested it, the amount, and where the money is
    going.
  </Step>

  <Step title="Approve or reject">
    As an owner, approve the request to send the transfer, or reject it to cancel
    it. The funds are held while the request is pending and are released back to
    your available balance if it is rejected.
  </Step>
</Steps>

## Cash sweeps

A [cash sweep](/docs/guides/cash-sweeps) moves money automatically on a schedule. Whenever any approval rule is active, creating or editing a sweep will require an owner's approval before the sweep takes effect. Once a sweep is approved, it runs on its schedule without opening a new request each time it moves money.


# Attachments
Source: https://getlemma.com/docs/guides/attachments

Attach the agreement or invoice behind a payment so the record explains itself later.

A bank statement tells you a payment happened. It does not tell you why. Attachments close that gap: upload the invoice, loan agreement, or management services agreement that justifies a payment, and it stays on the transaction for anyone who can see it.

This matters most when the two sides of a payment are related entities. An intercompany transfer with a service agreement attached to it is a documented, arm's-length record. The same transfer with nothing attached is a number an auditor has to ask about.

## Where you can attach a file

| Where                                                                       | How many  | Shared with the other side              |
| --------------------------------------------------------------------------- | --------- | --------------------------------------- |
| [Transfer within Lemma](https://app.getlemma.com/_/move-money/within-lemma) | one       | Yes, when the transfer crosses entities |
| [Send externally](https://app.getlemma.com/_/move-money/externally)         | one       | No                                      |
| [Invoicing](https://app.getlemma.com/_/invoicing)                           | up to ten | Yes                                     |

Attachments are optional everywhere. Accepted files are PDF, PNG, and JPEG, up to 10 MB each — a photographed or scanned agreement works as well as a PDF.

## Who can see an attachment

This is the part worth reading carefully, because it differs by the kind of payment.

An attachment on an external transfer is **never** sent to the recipient. It
is bookkeeping evidence for your own records. If you need to send a document
to someone you are paying, mail it with a check instead — see [Move
money](/docs/guides/move-money).

* **Transfer within Lemma, between two entities.** The receiving entity sees the attachment on its side of the transaction. The upload step names the entity that will receive it, so you know before you send.
* **Transfer within Lemma, between your own accounts.** There is no counterparty, so the attachment is only for your records.
* **Invoice.** The entity you bill sees the attachment, and can read it before deciding whether to pay. That is the point: an invoice for a management fee is easier to approve when the agreement setting that fee is attached to it.
* **Send externally.** Only your team. See the warning above.

Every screen that shows an attachment repeats which of these applies, so you never have to remember.

## Finding attachments later

Open any transaction from [Transactions](https://app.getlemma.com/_/transactions) and its documents appear in the drawer. Where a transaction has more than one, numbered buttons switch between them.

A paid invoice is the common case for several: the receipt is the first document, and anything the sender attached follows it. You can read every one of them from either side of the payment, and download each individually.

## Attachments and approvals

If a transfer needs an owner's sign-off under your [approval rules](/docs/guides/approval-rules), the attachment travels with the request, and the reviewer can open it while they decide. An agreement is only useful to an approver who can read it before approving.

Once the transfer sends, the attachment follows the money rather than the request: anyone on your team who can see the transaction can open it.

If a payment is later returned or reversed, the attachment appears on that
transaction too. You do not need to attach anything again. The justification
stays with the money for the life of the payment, including the parts you did
not plan for.

## MSO-PC structures

For groups running a management services organization alongside a physician-owned practice, attachments are where the paper trail lives. Attach the management services agreement to the fee transfer, or the loan agreement to a capital contribution, and the justification sits on the transaction instead of in someone's inbox.

Because a cross-entity attachment is visible to both entities, the practice and the MSO are looking at the same document — neither side has a private version of the record. See [MSO-PC compliance](/docs/guides/mso-pc-compliance) for the other controls we configure around this structure.

## Next steps

<CardGroup>
  <Card title="Move money" icon="arrow-right-arrow-left" href="/docs/guides/move-money">
    Send externally or transfer between your Lemma accounts.
  </Card>

  <Card title="Invoices" icon="file-invoice" href="/docs/guides/invoicing">
    Bill another entity without sharing account access.
  </Card>
</CardGroup>


# Cards
Source: https://getlemma.com/docs/guides/cards

Issue and manage debit cards for your organization.

Every account comes with free debit cards. [Issue a new card](https://app.getlemma.com/_/cards/new) as virtual or physical, with optional custom spending limits. Debit cards give you an extra layer of payment protection: paying a vendor by card or making an online purchase is disputable through the card networks, and Lemma automatically blocks high-risk transactions. Wires and ACH transfers don't come with those protections once the money leaves your account.

## Who can do what

Card management is limited to Owner and Accounting [banking roles](/docs/guides/team-management#banking-permissions). Read-only members can hold a card and see their own transactions, but cannot issue, change, freeze, rename, or activate a card, including their own.

| Action                             | Owner | Accounting | Read only |
| ---------------------------------- | :---: | :--------: | :-------: |
| Issue a new card                   |   ✓   |      ✓     |     —     |
| Change spending limits             |   ✓   |      ✓     |     —     |
| Freeze or unfreeze a card          |   ✓   |      ✓     |     —     |
| Cancel a card                      |   ✓   |      ✓     |     —     |
| Rename a card                      |   ✓   |      ✓     |     —     |
| Activate a delivered physical card |   ✓   |      ✓     |     —     |
| Hold a card and see its activity   |   ✓   |      ✓     |     ✓     |

Because limit changes, freezes, and activation are Owner or Accounting only, a cardholder cannot raise their own limit, unfreeze their own card, or activate a physical card that arrived in their own mail.

## Why pay with a debit card

Use a Lemma debit card for vendor payments and online purchases whenever the option exists:

* **Payment protection.** Card payments can be disputed through the card networks, so a bad charge or a vendor that doesn't deliver is recoverable in a way a completed wire or ACH usually isn't.
* **Fraud protection.** Lemma automatically declines high-risk transactions, and you can freeze the card instantly if anything looks off.
* **Bounded exposure.** A card only spends the cash in its funding account, and per-transaction and total-spend limits cap how much a single charge or a bad week can cost you.
* **Instant issuance.** Virtual card numbers are usable the moment they're created, so you can pay a new vendor or place an online order without waiting for a physical card.

## Virtual and physical cards

* **Virtual cards** — available instantly after creation. Use them for online purchases or anywhere a physical card isn't required.
* **Physical cards** — a branded card mailed to your address, arriving in an estimated 5-7 business days. The card number is visible as soon as you issue it, so online purchases work right away. In-person purchases stay blocked until you [activate the card](#tracking-and-activating-a-physical-card) after it arrives.

<Columns>
  <Frame>
    <img alt="Order Card button on an account page" />
  </Frame>

  <Frame>
    <img alt="Card list with Issue new card button" />
  </Frame>
</Columns>

## Issuing a card

Open [Issue new card](https://app.getlemma.com/_/cards/new) and fill in:

* **Cardholder** — any team member with a banking role. Read-only members can be cardholders, which lets you manage their spending without granting them access to the account.
* **Card nickname** — how you'll recognize the card in the cards list and on transactions.
* **Card type** — virtual or physical. Each cardholder can hold one physical card per entity, so the physical option is unavailable when the selected cardholder already has one. Virtual cards are unlimited.
* **Funding account** — the account the card spends from. Preselected to the account with the most available cash.
* **Spending limits** — optional per-transaction and total-spend caps (see below).

For a physical card, you'll also confirm the name printed on the card, the delivery address, and a delivery phone number.

## Tracking and activating a physical card

A physical card ships USPS and arrives in an estimated 5-7 business days. Its number works for online purchases from the moment you issue it, but the card declines in-person purchases until someone activates it, so activate the card as soon as it arrives.

Open the card from the [cards page](https://app.getlemma.com/_/cards) to follow the shipment.

| Stage      | What it means                                                |
| ---------- | ------------------------------------------------------------ |
| Printing   | The order is with the card printer. Nothing has shipped yet. |
| In transit | The card is printed and on its way to the delivery address.  |
| Delivered  | The card reached the address. It's ready to activate.        |

### Activating the card

<Steps>
  <Step title="Open the card">
    Go to the [cards page](https://app.getlemma.com/_/cards) and select the card
    that arrived.
  </Step>

  <Step title="Check that the delivery status reads Delivered">
    **Activate card** stays disabled until the card is delivered. If the card is
    in your hands but the status hasn't caught up, give the shipment a day to
    update.
  </Step>

  <Step title="Press Activate card">
    The card starts approving in-person purchases immediately, within whatever
    spending limits it already has. The delivery panel disappears once the card
    is activated.
  </Step>
</Steps>

<Info>
  Only Owner and Accounting members can activate a card. A read-only cardholder
  who receives their own card in the mail needs an Owner or Accounting teammate
  to activate it for them.
</Info>

### If the card doesn't arrive

Don't activate a card you haven't physically received. If a card is lost in transit, [cancel it](#cancelling-cards) and issue a new one.

## Spending limits

Lemma automatically blocks high-risk transactions. Card spending is always capped at the available cash in the linked account. On top of that, you can set two optional limits when issuing a card:

* **Max purchase amount** — declines any single purchase above a set dollar amount.
* **Max total spend** — caps total spend across a day, week, or month. Limits reset at UTC midnight. If you live on the east coast, that means your daily card limit resets at 7PM EST.

If both limits are on, a purchase must fit within both, or it's declined.

<Frame>
  <img alt="Spending limits controls in the card issuance flow" />
</Frame>

## Managing your cards

### Changing limits on a card you already have

You do not have to get the limits right when you issue the card. Open the card, click the `...` button at the top-right, and select **Update limits** to change either limit, switch one off, or add one you skipped. New transactions are checked against the new limits as soon as you save.

If you switch both limits off, the debit card approves any purchase up to the cash available in its bank account.

### Freezing cards

Freeze a card to instantly block new transactions. Freezing preserves its spending limits and transaction history, so unfreezing puts the card back exactly as it was.

<Steps>
  <Step title="Open the card">
    Go to the [cards page](https://app.getlemma.com/_/cards) and select the card
    you want to freeze.
  </Step>

  <Step title="Open the card menu">
    Click the `...` button at the top-right of the card's page.
  </Step>

  <Step title="Select Freeze card">
    Confirm in the dialog that follows. The card is frozen immediately.
  </Step>
</Steps>

To unfreeze, follow the same steps and select **Unfreeze card**. The card resumes approving transactions within its existing spending limits.

Only Owner or Accounting members can freeze or unfreeze a card, including their own. If a cardholder loses a card and doesn't have those permissions, they need an Owner or Accounting teammate to freeze it for them.

### Renaming a card

The nickname is how you'll recognize a card on the cards page and against its transactions. To change the nickname, open the card's page and click the pencil beside its name. The new name shows up everywhere the old one did, including on transactions that already happened.

### Cancelling cards

Cancel a card when you want to permanently stop it, for example when an employee leaves or a physical card is lost. Cancelling cannot be undone. If you only need to pause spending temporarily, freeze the card instead.

Cancelling covers the physical card too, so a card cancelled while in the mail can never be activated, even after it lands. Delivery tracking and the **Activate card** button both disappear from a cancelled card's page.

<Steps>
  <Step title="Open the card">
    Go to the [cards page](https://app.getlemma.com/_/cards) and select the card
    you want to cancel.
  </Step>

  <Step title="Open the card menu">
    Click the `...` button at the top-right of the card's page.
  </Step>

  <Step title="Select Cancel card">
    Confirm in the dialog that follows. The card is cancelled immediately and
    can no longer approve transactions.
  </Step>
</Steps>

Only users with Owner or Accounting [banking permissions](/docs/guides/team-management#banking-permissions) can cancel a card.

### Review all of your entity's cards

The [cards page](https://app.getlemma.com/_/cards) shows every card issued in your legal entity. The table gives you an overview of all cardholders, their card nicknames, and whether each card is virtual or physical.

## Cards for software and AI agents

### Cards issued by connected software

If you've linked software to Lemma which is authorized to issue virtual cards on your behalf, those cards show up alongside your own, with cardholder names reading "Managed by Platform Name".

Such a card belongs to the software that issued it, so it keeps the name and spending limits that software gave it — the pencil and the **Update limits** menu item aren't offered on its page. Everything else works the same: you can review its transactions and freeze it like any other card.

### Virtual cards for AI agents

Issue a virtual card with spending limits to safely share payment credentials with an AI agent. You can cancel the card at any time if something looks off.

Do you have multiple AI agents? Since Lemma debit cards only spend the cash in the linked account, they never borrow funds like a credit card. That makes it easy to cap your total exposure by opening a dedicated bank account for AI agent spending.

For example, let's say you have three AI agents. Open an "AI spending" account and fund it with \$10,000 — the most you're willing to spend across all your agents. Then issue three separate cards for each agent, each with its own \$5,000 limit. Any one agent can spend up to \$5,000, and your total exposure across all agents is still only \$10,000 instead of \$15,000.


# Cash sweeps
Source: https://getlemma.com/docs/guides/cash-sweeps

Automate fund movement between accounts so passthrough and MSO collections land where they belong, without daily manual transfers.

In healthcare billing, money often arrives in one account but needs to end up in another. Insurance payments land in a passthrough account that feeds the operating account. An MSO collects on behalf of its PCs and needs to distribute funds daily. A practice keeps a reserve threshold and sweeps the rest to a higher-yield account overnight. A PC owes its MSO the same management fee on the first of every month.

Cash sweeps handle all of this automatically. You define a rule once (which account to watch, how much to keep, where to send the excess, and when to check) and Lemma runs it on schedule.

Sweeps can move funds **between your Lemma accounts** or **out of Lemma to accounts you hold at another bank**. Many customers pair Lemma's lockbox, MSO-PC compliance, and other products with existing accounts elsewhere by sweeping over RTP, which settles in seconds. That lets critical money movement, like funding payroll at your primary bank, keep running on schedule while the rest of your treasury runs on Lemma.

<img alt="Cash Sweeps page showing a configured sweep rule that moves excess funds from Business Checking to a Cigna account" />

## Creating a sweep rule

<Steps>
  <Step title="Pick an account">
    Select the source account to sweep from and name your rule.
  </Step>

  <Step title="Configure the rule">
    Lemma supports two sweep methods: keep a minimum balance and sweep the
    excess, or send a fixed amount each run.
  </Step>

  <Step title="Choose the destination">
    Choose whether funds go to another Lemma account or an external recipient.
  </Step>

  <Step title="Set the schedule">
    Choose whether the rule runs weekly or monthly, then pick what times of day
    to check the balance.
  </Step>

  <Step title="Review and create">
    Click Create Sweep Rule. You can always edit your rule later if you made a
    mistake.
  </Step>
</Steps>

## When to use sweeps

* **MSO-PC fund distribution**: an MSO collects insurance payments centrally, then sweeps each PC's share to their dedicated account at the end of each day
* **Passthrough accounts**: a lockbox account receives all inbound checks, then sweeps the balance to your operating account after keeping a small reserve
* **Cash concentration**: multiple practice locations each maintain a local account, and excess funds are swept nightly to a single treasury account
* **Recurring monthly fees**: a PC sends its MSO the same management fee on the first of every month, so the payment moves on a documented schedule instead of being invoiced and chased

## Sweep methods

### Target balance

The default method keeps your source account at a set floor. Whenever the sweep runs, Lemma checks the current balance and sends everything above your threshold to the destination. If the balance is already at or below the target, the sweep is skipped.

<Frame>
  <img
    alt="Sweep rule configured to keep a target balance and send excess funds to
another Lemma account."
  />
</Frame>

### Fixed amount

You can send a specific dollar amount each time the rule runs. This is useful when you need to fund an account by a predictable amount. For example, top up a PC's operating account with a fixed daily allocation from the MSO.

Paired with a monthly schedule, it also covers a payment that is identical every month, like an MSO management fee or a loan repayment.

The sweep is skipped entirely when the source account has less than the fixed amount.

<Frame>
  <img
    alt="Sweep rule configured to send a fixed amount to another Lemma
account."
  />
</Frame>

## Sweeping to another Lemma account

When both accounts are on Lemma, transfers settle instantly at no cost. This is ideal for MSO-PC structures where the MSO and each PC both bank with Lemma.

Select **Another Lemma account**, then pick the destination entity and account. If your organization only has one entity, the entity dropdown is skipped.

## Sweeping to an external account

You can also sweep funds to a bank account outside Lemma. Choose your transfer method based on urgency and cost:

| Method | Speed             | Best for                      |
| ------ | ----------------- | ----------------------------- |
| ACH    | 1-2 business days | Routine, low-cost transfers   |
| RTP    | Seconds           | Urgent transfers up to \$1M   |
| FedNow | Seconds           | Urgent transfers up to \$500K |

<Frame>
  <img
    alt="Sweep rule configured to send excess funds to an external account. Shows the
transfer method options: ACH, RTP, and FedNow."
  />
</Frame>

<Tip>
  External recipients must be added before they can be used as a sweep
  destination. See [external accounts](/docs/guides/external-accounts).
</Tip>

## Setting the schedule

Each rule runs either weekly or monthly.

**Weekly** rules run on the days of the week you pick. Select every weekday, just Fridays, or any other combination.

**Monthly** rules run on the first day of every month. Use this when the payment is the same each month rather than tied to a balance.

Either way, you choose what times of day to check the balance. You can add multiple check times — for example, 9:00 AM and 5:00 PM — so excess funds are swept both when the business day opens and after the last deposits settle.

ACH transfers only process during banking hours on business days. A sweep that triggers on a weekend or holiday will queue the ACH, but it won't settle until the next business day. This catches monthly rules a few times a year, whenever the 1st lands on a weekend. If you need funds to move over weekends, use RTP or FedNow instead. Both RTP and FedNow settle in seconds, any day of the week. Lemma remembers your timezone when you create a rule, so a 5:00 PM sweep always runs at 5:00 PM in your timezone. Team members who edit an existing sweep will not be able to change the timezone.

## Limits

Each sweep run can transfer up to **\$100,000**. If the excess balance is larger than that, the remaining amount will be swept on the next scheduled run. Contact us at [contact@getlemma.com](mailto:contact@getlemma.com) if your practice needs higher per-run limits.

## Editing a rule

Click any row in the sweep rules table to open the editor. The form is pre-filled with the current configuration. **Save Changes** only activates when you have actually changed something, so you cannot accidentally save a no-op update.

## Who can manage sweeps

Team members with the **Accounting** or **Owner** banking role can view the Cash Sweeps page and create and edit sweep rules. Read Only members do not see the page. See [team management](/docs/guides/team-management) for what each role can do. To require an owner's sign-off when an Accounting member creates or edits a sweep rule, set up an [approval rule](/docs/guides/approval-rules). While any approval rule is active, sweep changes take effect only after an owner approves them.


# Collaborate opening an account
Source: https://getlemma.com/docs/guides/collaboration

Ask your coworkers to fill out account information while keeping sensitive details private.

Opening a Lemma account requires information about your business's ownership structure. Federal regulations require you to identify a **controller** (a principal officer with significant management authority) as well as every **beneficial owner** who holds 25% or more of the business. Depending on your ownership structure, this can mean collecting Social Insurance Numbers and other personal details from several different people.

Lemma's collaboration feature lets multiple people work through the application at the same time, similar to Google Docs. Each person can fill in the sections they're responsible for directly, so no one has to share sensitive personal information with a coworker.

## How collaboration works

When two or more people are in the application at the same time, you'll see an avatar on the page each coworker is viewing. Any text they type appears on your screen in real time, and anything you type appears on theirs.

This means you can divide up the form naturally: your office manager handles the business profile, one owner fills in their own personal details, and another owner fills in theirs, all at the same time without coordinating over email or phone.

## Inviting a collaborator

To invite someone to fill out the application with you:

1. Open your application
2. Click **Share** in the left sidebar
3. Enter the person's email address and click "Invite collaborator"

<Frame>
  <img alt="Invitation dialog with an email address field and a Send invite button" />
</Frame>

The collaborator receives an email with a link to the application. You can also copy the link for the page you're on and send it to them directly, for example over Slack or by text, once the invitation has been sent.

## Sensitive fields

Some fields contain information that's personal enough that even coworkers shouldn't see it. Birthdays and Social Insurance Numbers fall into this category.

When you click one of these fields, it opens in a private popup rather than directly in the form. Once you save the value:

* It is encrypted immediately and stored in our database
* It is not retained in your browser or transmitted to anyone else's browser
* Your collaborators can see that the field has been filled in, but cannot read the value

If you need to correct a sensitive field, you can overwrite it by entering a new value in the same popup. The original value is not shown.

## Accessing the Lemma dashboard

When the account is approved, all collaborators automatically get full access to the Lemma dashboard. This is intentional: since beneficial owners are required to fill out the application, they'll have access to the account without any extra setup.

If you need to invite additional team members who weren't part of the application, or remove a collaborator who shouldn't have long-term access, you can do that from the [Users](https://app.getlemma.com/_/settings/users) page.

## Managing multiple applications

If you're onboarding several entities at once, for example an MSO opening accounts for each of its professional corporations, you can start a separate application for each one. [Click here to visit our onboarding dashboard](https://app.getlemma.com/onboarding) where you can see all of your in-progress forms and onboard new entities any time.

If you started an application you no longer need, open it, click the structure badge next to the entity name at the top-left of the application page, and click **Archive**. The badge reads **PC**, **Corporation**, **LLC**, or whatever structure you selected. The application disappears from the onboarding dashboard for you and every collaborator. Anyone else with the application open sees a toast naming who archived it and is returned to the onboarding page. You can only archive draft applications; to modify a submitted application, [contact us](mailto:contact@getlemma.com).

<Frame>
  <img alt="An onboarding application page with a PC structure badge next to the entity name at the top-left" />
</Frame>

## Attestation

Every application includes an attestation step where you confirm that every individual who owns 25% or more of the company is listed.

### Attesting on behalf of the owners

If none of the listed owners has joined the application as a collaborator, the attestation step also asks you to attest that an owner authorized you to open and operate the account.

You can back this attestation with an optional supporting document, such as a Management Services Agreement, Power of Attorney, or board resolution. PNG, JPG, and PDF files up to 10 MB are accepted. If you don't have the document on hand, you can share it with Lemma later.

Inviting an owner to [collaborate on the application](#inviting-a-collaborator) removes the authorization attestation. Once a listed owner joins, their participation shows they approve of the account being opened.

### Licensed professional owners on a PC, PLLC, or PA application

On a Professional Corporation, PLLC, or Professional Association application, the attestation step also asks you to confirm that the licensed professional owner has been identified. The review step then offers to invite each licensed professional owner who isn't already a collaborator, so the owner joins the application directly instead of you attesting on their behalf. See [MSO-PC compliance](/docs/guides/mso-pc-compliance) for why this matters and how it works.


# Deposit bonuses
Source: https://getlemma.com/docs/guides/deposit-bonuses

How Lemma calculates and pays deposit bonuses on your bank account balance.

Lemma is not a bank. Banking services are provided by Core Bank, Member FDIC, our banking partner. Because Lemma is not a bank, we pay a "deposit bonus" rather than "interest".

## How the deposit bonus accrues

The deposit bonus accrues daily at an annual rate set by your plan — see the [pricing page](/docs/billing/pricing) for standard rates<sup>1</sup> — based on your account's balance at the end of each day. Daily accrual is calculated at east coast midnight (UTC-5).

## When the deposit bonus is paid

Accrued deposit bonus amounts are totaled and paid into your account on the 1st of each month, covering the prior month's accrual.

<sup>1</sup> Your entity may be subject to a different rate if you have a negotiated contract with Lemma, in which case you can see your active rate on the account page.


# Export transactions
Source: https://getlemma.com/docs/guides/export-transactions

Export your transactions as a CSV or QuickBooks (.qbo) file to import into your accounting software.

You can export your transaction history as a CSV or QuickBooks (`.qbo`) file directly from the [transactions page](https://app.getlemma.com/_/transactions). CSV works with any spreadsheet or accounting tool, while `.qbo` is intended for QuickBooks Online and QuickBooks Desktop.

If you want Lemma to sync directly with your accounting software instead, see [Accounting integrations](/docs/accounting-integrations).

<Frame>
  <img alt="Transactions page showing the Filters and Export buttons" />
</Frame>

## Export your transactions

<Steps>
  <Step title="Choose your entity">
    Transactions are automatically filtered to your current entity. If you
    manage multiple legal entities, use the entity switcher to select the right
    one before exporting.
  </Step>

  <Step title="Apply filters (optional)">
    Use the filter bar to narrow the transactions shown on the page. You can
    [filter](/docs/guides/transactions#filter-transactions) by search term, date
    range, account, type, and direction. Any filters you set will carry over to
    your export.
  </Step>

  <Step title="Click Export">
    Click the **Export** button in the top-right corner of the page, then choose
    **CSV** or **QuickBooks (.qbo)**. Your browser will download a
    `transactions.csv` or `transactions.qbo` file.
  </Step>
</Steps>

## Importing into QuickBooks

In QuickBooks Online, open **Transactions → Link account** and click **Upload from file**. Select your `.qbo` file. In QuickBooks Desktop, use **File → Utilities → Import → Web Connect Files** and select the downloaded `.qbo` file.

## What's included in the export

<Tabs>
  <Tab title="CSV">
    One row per transaction with the following columns:

    <ResponseField name="Date">
      When the transaction occurred, formatted as `YYYY-MM-DD`.
    </ResponseField>

    <ResponseField name="Description">A summary of the transaction.</ResponseField>

    <ResponseField name="Amount">
      The transaction amount in US dollars (e.g. `$1,234.56`).
    </ResponseField>

    <ResponseField name="Bank Account Name">
      The name of the account the transaction belongs to.
    </ResponseField>

    <ResponseField name="Category">
      The [category](/docs/guides/transaction-categories) assigned to the transaction,
      defaults to "Uncategorized".
    </ResponseField>
  </Tab>

  <Tab title="QuickBooks (.qbo)">
    The `.qbo` file uses the OFX 1.0 format that QuickBooks expects. It contains one statement block per account, each with:

    <ResponseField name="Transaction type">
      Classified as one of the standard OFX types (e.g. `DEP` for deposits, `DIRECTDEP` for incoming ACH, `CHECK` for outgoing checks, `POS` for card purchases). QuickBooks uses this to suggest the right account mapping.
    </ResponseField>

    <ResponseField name="Date">When the transaction posted.</ResponseField>

    <ResponseField name="Amount">Signed dollar amount (negative for money out).</ResponseField>

    <ResponseField name="Transaction ID">
      The Lemma transaction ID. QuickBooks uses this to deduplicate, so re-uploading the same file won't create duplicate entries.
    </ResponseField>

    <ResponseField name="Counterparty">
      Who you sent money to or received money from.
    </ResponseField>

    <ResponseField name="Memo">Full transaction description.</ResponseField>

    <ResponseField name="Routing number">
      The ABA routing number for the account.
    </ResponseField>

    <ResponseField name="Balance">
      The current account balance at the time of export.
    </ResponseField>

    <Note>
      Categories are not included in the `.qbo` file. If you need category data, use the CSV export.
    </Note>
  </Tab>
</Tabs>


# External accounts
Source: https://getlemma.com/docs/guides/external-accounts

Save and manage bank accounts for outbound payments.

External accounts (also known as external recipients) are saved bank accounts you can send payments to. Instead of entering routing and account numbers every time, save a recipient once and select them when you [move money](/docs/guides/move-money).

## Adding a new external recipient

1. Go to [New External Recipient](https://app.getlemma.com/_/external-recipients/new)
2. Enter the recipient's details:
   * **Name** — the account holder's name
   * **Nickname** — a label for your reference (e.g., "Lab supplier")
   * **Holder type** — business or individual
   * **Account type** — checking or savings
   * **Routing number** and **account number**
3. Save the recipient

The recipient is now available when sending external payments.

## Archiving a recipient

If you no longer need a recipient, you can archive them. Archived recipients are removed from the active list but can still be viewed in past transactions.


# FDIC insurance
Source: https://getlemma.com/docs/guides/fdic-insurance

How Lemma accounts are FDIC-insured through Core Bank and IntraFi, and how to confirm coverage.

Lemma is not a bank. Banking services are provided by [Core Bank](https://corebank.com), Member FDIC, our banking partner. Every dollar you hold in a Lemma account sits at Core Bank.

## How your deposits are insured

The standard FDIC insurance limit is \$250,000 per depositor, per insured bank, per ownership category. Lemma extends coverage well beyond that limit through the [IntraFi](https://www.intrafi.com) network:

* Up to **\$250,000** stays at Core Bank and is directly FDIC-insured.
* Balances above **\$250,000** are insured through the IntraFi network, which spreads the excess across other Member FDIC banks so each portion sits below the per-bank insurance limit.
* Every account is covered for up to **\$10M** in FDIC insurance in total.

Your money never leaves the FDIC-insured banking system, and you continue to work with a single Lemma account regardless of how balances are distributed behind the scenes.

## Confirming coverage

Two independent sources can confirm how your deposits are held.

### Core Bank

We're happy to put you in touch with Core Bank directly to confirm our practices, including how Lemma accounts are custodied and how IntraFi enrollment works. Email [contact@getlemma.com](mailto:contact@getlemma.com) and we'll make the introduction.

### IntraFi

IntraFi issues a confirmation letter directly to the depositor once an account is open and enrolled in the IntraFi network. IntraFi does not issue confirmations before that point.


# Fixed fee loans
Source: https://getlemma.com/docs/guides/fixed-fee-loans

Draw a loan against your practice's approved limit for a flat, upfront fee.

A fixed fee loan lets your practice draw funds against a preapproved limit whenever you need extra cash flow. There's no interest and no recurring payments, just a flat, upfront fee shown to you before you confirm the draw.

## Get approved for a loan

Loans loans are pre-approved and sized according to your insurance deposits flowing through Lemma, perfect for working capital. Lemma also
offers practice acquisition loans for customers expanding to new locations.

Interested in enabling loans for your entity? Email
[contact@getlemma.com](mailto:contact@getlemma.com). Getting a limit approved
doesn't obligate you to draw from it — it's there for when you need it.

## How a draw works

[Owners](/docs/guides/team-management#banking-permissions) can draw from an approved limit at any time from the **Loans** page. The draw flow walks through three steps:

1. **Amount** — enter how much you want to draw.
2. **Repayment** — review the origination fee and total repayment amount.
3. **Review** — confirm and choose the account to deposit the funds into.

Funds are deposited into your chosen account as soon as you confirm the draw.

### The fee

Each draw carries a flat origination fee: a percentage of the amount you draw, not an annualized interest rate. There's no interest and no additional fees. The fee is calculated and shown to you on the **Repayment** step, alongside a breakdown of the draw amount, origination fee, and total repayment amount, before you confirm.

### Repayment

Loans are due 30 days after you draw them. Lemma automatically debits the full repayment amount from your account on the due date — no action is needed from you.

### Early repayment discount

Repay a loan within the first 15 days and half of the origination fee is refunded.


# Insurance payments
Source: https://getlemma.com/docs/guides/insurance-payments

Upload explanation of benefits documents and track insurance claim payments.

The EOB (Explanation of Benefits) section helps you track payments from insurance companies. Upload EOB documents and Lemma extracts the payment details so you can reconcile claims without manual data entry.

## Uploading an EOB

1. Go to **EOB** and select **Upload**
2. Upload a PDF of the explanation of benefits document
3. Lemma extracts the payment information automatically

The extraction job appears in the **Active jobs** table. Processing typically takes a few moments.

| Status         | Meaning                                            |
| -------------- | -------------------------------------------------- |
| **Uploaded**   | Document received, waiting to be processed         |
| **Extracting** | Parsing the document                               |
| **Completed**  | Data extracted successfully                        |
| **Failed**     | Extraction encountered an error — try re-uploading |

## Viewing insurance payments

Once extraction completes, the parsed payments appear in the **Insurance payments** table showing:

* **Payer** — the insurance company
* **Payment date**
* **Amount paid**

Select a payment to see the full breakdown:

* Payer and payee details (addresses, phone numbers, tax IDs)
* Patient and member information
* Individual claim line items with CPT codes
* Service dates, amounts charged, amounts paid, and patient responsibility

## Automatic lockbox matching

When an insurance check arrives at your [lockbox](/docs/guides/lockbox) and matches an uploaded EOB, Lemma links the two together so you can see the complete payment lifecycle — from the EOB document to the deposited check.


# Invoice contacts
Source: https://getlemma.com/docs/guides/invoice-contacts

Who you can bill from and who you can bill to.

Every invoice has a sender entity ("bill from") and a recipient entity ("bill to"). Lemma checks your access separately for each side.

## Billing from an entity

To send an invoice from an entity, you need the **Accounting** [banking permission](/docs/guides/team-management#banking-permissions) or higher on that entity. Owners and accounting-role members can bill from an entity; read-only members cannot.

## Billing to an entity

You can bill to:

1. Any entity you have access to, including entities where you only have read-only access.
2. Any entity in your organization, if this is configured with Lemma's team — even entities you have no access to at all.

### Entities you have access to

If you're a member of the recipient entity — at any role, including read-only — you can send it an invoice. The recipient's own owner decides whether to pay it, so this works even if you personally have no ability to move money on that entity.

### Entities in your organization

MSO-PC structures often need one entity to bill another — for example, a practice paying a management fee to its MSO — without either side seeing the other's accounts. Contact us and we'll group your entities into an organization on Lemma's end. Once configured, entities in the same organization can send invoices back and forth without either side granting the other any account access. See [MSO-PC compliance](/docs/guides/mso-pc-compliance) for how Lemma supports this ownership structure more broadly.

## Self-approvals

If you're an owner of both the sending and receiving entity, you can send an invoice and then approve its own payment. We allow this because plenty of owners run multiple entities and are the only person with access to one side of the relationship — there's no one else around to approve the payment. Invoicing still gives you a clean paper trail of line items and amounts for why the money moved, even when the same person is on both ends of the transaction.


# Invoices you've paid
Source: https://getlemma.com/docs/guides/invoices-paid

Find invoices you've paid, download a receipt, and see who approved the payment.

There are two ways to find an invoice you've paid: the transaction the payment created, and the approval that authorized it. Start with the transaction if you want a receipt, and the approval if you want to know who signed off.

## Find the transaction and its receipt

Once you pay an invoice, it appears as a transaction on your [Transactions](https://app.getlemma.com/_/transactions?type=Invoice) page. Filter by type **Invoices** to see them. Click on a transaction to see its details and download a receipt.

## See who approved the payment

Paying an invoice goes through an approval, so the [approved transfers page](https://app.getlemma.com/_/requests?status=approved) lists every payment your entity has approved. Click one to see who approved it and when, which account it was paid from, and the invoice itself. Use this when you need to know who authorized a payment, not just that it went out.


# Invoices you've sent
Source: https://getlemma.com/docs/guides/invoices-sent

Review an invoice you sent, and cancel one that hasn't been paid yet.

Go to [Invoicing](https://app.getlemma.com/_/invoicing) to see every invoice sent from your entity. Click an invoice to open its details: its status, the total, who it's billed from and to, the account it deposits into, and the memo. The same panel previews the invoice itself, with the line items, and you can download that as a PDF.

## Cancel an invoice

While an invoice is still **Sent**, meaning the recipient has not approved a payment yet, you can withdraw it. Open the invoice and click **Cancel invoice**, then confirm. The recipient can no longer pay it. Canceling can't be undone. To bill the recipient again, send a new invoice.

Once the recipient approves the payment, the invoice is **Paid** and cannot be canceled. You need permission to send invoices to cancel one.

## Correct a mistake on an invoice

A sent invoice can't be edited. Its line items are locked so the record can't be altered after the fact. If you got something wrong, cancel the invoice and send a replacement with the correct details. That leaves both the withdrawn invoice and its replacement on the record, which is what you want for an auditable trail.


# Invoices
Source: https://getlemma.com/docs/guides/invoicing

Send invoices to bill another entity without sharing account access.

An invoice requests a payment from another entity on Lemma, without giving them access to your accounts and without you needing access to theirs. You can bill any entity in your organization, once your entities are grouped into one, or any entity you already have access to — read-only access counts. See [Invoice contacts](/docs/guides/invoice-contacts) for the full rules on who you can bill from and bill to. Go to [Invoicing](https://app.getlemma.com/_/invoicing) to send one.

## When to use an invoice instead of team access

If two entities transact often and it's fine for both sides to see the shared history, [add each other as team members](/docs/guides/team-management) so someone can move money directly. Use an invoice for the opposite case: two entities do business but neither should see the other's balances or transaction history.

For example, two independently owned practices refer patients to each other and periodically settle a referral fee. Neither wants the other to see their bank balance, so instead of sharing account access, one sends the other an invoice for the agreed amount.

Invoices are also useful when someone can propose a payment but shouldn't be able to move money themselves. A read-only member of one entity who is also an owner of another can send an invoice from the entity they own to the entity where they only have read access — the recipient's own owner still decides whether to pay it.

### Line items

Every invoice has one or more line items — a description and amount for each service or product being billed. Line items must sum to the invoice total, and they're locked once the invoice is sent so the record can't be altered afterward. Use them to give the recipient an auditable breakdown of exactly what a payment covers, instead of a single lump sum.

### Invoice numbers

Every invoice is assigned a unique invoice number so you can identify it in your accounting software.

### Attachments

Add up to ten [attachments](/docs/guides/attachments) to an invoice — the contract or agreement that justifies what you're billing for. The entity you bill can read them before deciding whether to pay, which is the difference between approving a management fee on trust and approving it against the agreement that sets it.

<Frame>
  <img alt="An example invoice generated on Lemma showing the invoice sender, the invoice recipient, the invoice ID, the invoice memo, the invoice line items, and the total due" />
</Frame>

## Another way to keep control: approval rules

Invoicing lets a read-only member propose a payment without ever touching the recipient's money — the owner on the other side decides whether it goes through. If you want that same kind of oversight on transfers your own team initiates, [approval rules](/docs/guides/approval-rules) are the tool for the job: set a threshold, and any transfer above it waits for an owner's sign-off before a dollar leaves the account. Pair the two and every dollar moving in or out of your entity has a second set of eyes on it.

## Next steps

<CardGroup>
  <Card title="Invoice contacts" icon="address-book" href="/docs/guides/invoice-contacts">
    Who you can bill from and bill to.
  </Card>

  <Card title="Invoices you've sent" icon="paper-plane" href="/docs/guides/invoices-sent">
    Find invoices you've sent and cancel one that hasn't been paid.
  </Card>

  <Card title="Invoices you've paid" icon="receipt" href="/docs/guides/invoices-paid">
    Find invoices you've paid and download receipts.
  </Card>
</CardGroup>


# Lockbox
Source: https://getlemma.com/docs/guides/lockbox

Receive checks and mail through a dedicated mailing address.

A lockbox is a physical mailing address managed by Lemma where your practice receives checks, EOBs, and other payer mail. Lemma scans everything that arrives, deposits any payments into your linked bank account, and ties the rest back to your claims so you have a single place for payer correspondence.

## How it works

1. Lemma assigns a unique mailing address to your business
2. Instruct payers (insurance companies, patients, etc.) to send checks and correspondence to this address
3. When mail arrives, we scan and display it in your [**Lockbox**](https://app.getlemma.com/_/lockbox) page
4. Payments are processed automatically and correspondence is parsed for claim data

## Receiving payments in your lockbox

Your lockbox captures every piece of mail a payer sends you, whether or not money is attached. Lemma scans each item, parses any EOBs it finds, and can generate 835 files to send back into your EHR, so it's worth pointing payers at your lockbox even when they're paying you some other way. That way EOBs, correspondence, and payments all land in one place and stay tied to the right claims.

### Checks

Paper checks are scanned on arrival, deposited into your linked bank account, and posted to your [transactions page](/docs/guides/transactions) so you can reconcile them alongside the rest of your activity. You don't need to endorse or deposit anything yourself.

### Virtual card payments

Some payers (like Zelis) send payment as a virtual card instead of a paper check. When one of these arrives in your lockbox, Lemma automatically charges the card on your behalf, so you don't have to key in card numbers or handle the payment manually.

Virtual card payments show up in your transactions as two separate entries:

* **Card amount** — the gross payment from the payer
* **Card processing fee** — the fee charged to accept the card (see [pricing](/docs/billing/pricing))

Splitting the payment this way makes reconciliation straightforward: the card amount matches what the payer said they were paying you, so credit card deposits line up with what your service billed for instead of arriving slightly short.

## Viewing lockbox mail

The [Lockbox page](https://app.getlemma.com/_/lockbox) shows all inbound mail items with:

* **Date received**
* **Sender's name**
* **Mail type** — check, virtual credit card, EOB, or general mail
* **Status** — whether the check or card payment has been processed

Click on any a mail item to view its scanned image and deposit details.

## EHR integration and claim reconciliation

Lemma integrates with your EHR to automatically match incoming payments against the claims you submitted. Checks, virtual card payments, and EOBs from your lockbox are reconciled against open claims so you can see exactly which visit or service each deposit covers, without manually cross-referencing remittances. Read our [insurance payments](/docs/guides/insurance-payments) page for more on how EOBs and claim matching work.

Some payers (like Zelis) send payment as a virtual card instead of a paper check. When one of these arrives in your lockbox, Lemma automatically charges the card on your behalf, so you don't have to key in card numbers or handle the payment manually.

Virtual card payments show up in your transactions as two separate entries:

* **Card amount** — the gross payment from the payer
* **Card processing fee** — the fee charged to accept the card (see [pricing](/docs/billing/pricing))

Splitting the payment this way makes reconciliation straightforward: the card amount matches what the payer said they were paying you, so credit card deposits line up with what your service billed for instead of arriving slightly short.


# Deposit a check from your phone
Source: https://getlemma.com/docs/guides/mobile-check-deposit

Use mobile check deposit to snap a photo of a paper check and credit the funds to your Lemma account.

Mobile check deposit lets you deposit a paper check straight from your phone. No
trip to the bank or lockbox mailing required. Open Lemma in your phone's browser,
visit [Move money > Mobile check deposit](https://app.getlemma.com/_/move-money/mobile-check-deposit), photograph the front and
back of the check, and the funds are credited to your account once the check
clears. There's no limit on the size of checks you can deposit at Lemma.

You need [banking permissions](/docs/guides/team-management#banking-permissions) to
deposit a check. Read-only users are allowed to deposit checks but not move
the money after it's deposited.

## Before you start

* **Payee matches account name.** The "Pay to" / "Pay to the order of" line must
  match your account entity name exactly. Reach out to us if you are depositing a check in the name of an owner or healthcare provider rather than the clinic's name.
* **Endorse the back.** Sign or write your name on the back, then write
  "For deposit only at Lemma" below it.
* Find good, even lighting and a dark, flat surface for contrast.

## Deposit a check

### Mobile

<Steps>
  <Step title="Visit the move money page">
    In your phone's browser, sign in to Lemma and go to
    [Move money > Mobile check deposit](https://app.getlemma.com/_/move-money/mobile-check-deposit).
  </Step>

  <Step title="Choose the destination account">
    Select the Lemma account you want the funds credited to. If you manage
    multiple entities, confirm you're on the right one first.
  </Step>

  <Step title="Capture the front of the check">
    Point your camera at the front of the check. A live viewfinder with edge
    detection frames the check and helps you capture a clean image on the first
    try. Hold steady until it captures, then confirm the photo is sharp and all
    four corners are visible.
  </Step>

  <Step title="Capture the back of the check">
    Flip the check over and photograph the endorsed back the same way. Make sure
    your signature and any required "for mobile deposit" note are legible.
  </Step>

  <Step title="Review and submit">
    Check the account and both images. The amount is read automatically from the
    front of the check. If anything looks off, retake the photo. When everything
    is correct, submit the deposit.
  </Step>
</Steps>

## Desktops

Prefer a bigger screen? Mobile deposit also works from a computer. On the
[Move money > Mobile check deposit](https://app.getlemma.com/_/move-money/mobile-check-deposit) page, upload a photo of
the front and back of the check instead of capturing one with the camera.

## After you deposit

Once submitted, the deposit appears in your
[transaction history](/docs/guides/transactions). The check is credited to your
account after it clears, and the funds are held for a few days before they become available to spend.

Open the transaction's detail panel to see:

* **Status**: a deposit moves through `pending`, `submitted`, and then either
  clears or is `returned` / `rejected`.
* **Hold release date**: when a hold is in place, the panel shows the date the
  funds are expected to become available.

## Tips for a clean capture

* Use a dark, flat surface so the check's edges stand out.
* Keep all four corners visible inside the frame.
* No shadows or glare. Diffuse, even light works best.
* Make sure the image is in focus before submitting.
* Keep the paper check until the deposit clears, then store or destroy it per
  your record-keeping policy.

## Related

<CardGroup>
  <Card title="Lockbox" icon="mailbox" href="/docs/guides/lockbox">
    Mail paper checks to your dedicated lockbox address for deposit.
  </Card>

  <Card title="Transactions" icon="list" href="/docs/guides/transactions">
    Track the status and hold release date of every deposit.
  </Card>
</CardGroup>


# Move money
Source: https://getlemma.com/docs/guides/move-money

Send payments externally or transfer funds between your Lemma accounts.

Lemma supports two ways to move money: sending to external bank accounts and transferring between your own Lemma accounts.

## Transfer within Lemma

Transfer funds between your own Lemma accounts or to other Lemma members. You can also transfer between separate entities on Lemma as long as you have access to both of them. Go to [Move money > Transfer within Lemma](https://app.getlemma.com/_/move-money/within-lemma).

Internal transfers are:

* **Instant** — funds arrive immediately
* **Free** — no fees
* **Available 24/7** — no business-hours restriction

Select the source and destination accounts, enter an amount, and confirm.

You can also [attach a document](/docs/guides/attachments) — an invoice or service agreement that explains what the transfer is for. When the transfer crosses two entities, the receiving entity sees the attachment too, so both sides hold the same record.

## Send externally

Send payments to bank accounts outside of Lemma. Go to [Move money > Send externally](https://app.getlemma.com/_/move-money/externally) and follow the three-step process:

<Steps>
  <Step title="Choose a recipient">
    Select a saved recipient from your [external
    recipients](/docs/guides/external-accounts) list, or add a new one.
  </Step>

  <Step title="Enter payment details">
    Enter the amount and choose a transfer method. The RTP and FedNow networks cap how much you can send in a single transfer, but you can send multiple transfers in a row to move a larger amount.

    | Method                       | Speed             | Fee  | Transfer Limit  |
    | ---------------------------- | ----------------- | ---- | --------------- |
    | **ACH**                      | 1-3 business days | Free | None            |
    | **Wire**                     | Same day          | \$15 | None            |
    | **Real-time payment (RTP)**  | Instant           | Free | \$1M per send   |
    | **FedNow**                   | Instant           | Free | \$500k per send |
    | **Check** (USPS First Class) | 5-7 business days | \$2  | None            |
    | **Check** (FedEx Overnight)  | Next business day | \$25 | None            |

    <Note>
      Fees may differ if your entity has a negotiated contract with Lemma. See the
      [pricing page](/docs/billing/pricing) for standard rates.
    </Note>

    <Note>
      All transfer methods are enabled on every Lemma account, but the recipient's
      bank may not accept some of them. Lemma checks the recipient's routing number
      and disables any method the bank does not accept.
    </Note>
  </Step>

  <Step title="Review and confirm">
    Review the transfer details and confirm. For wire transfers and check
    mailings, the fee is deducted from your account automatically.
  </Step>
</Steps>

You can [attach a document](/docs/guides/attachments) to an external payment for your own records. Unlike a document mailed with a check, it is never sent to the recipient.


# MSO-PC compliance
Source: https://getlemma.com/docs/guides/mso-pc-compliance

How Lemma supports MSO-PC structures with banking guardrails aligned with the corporate practice of medicine doctrine.

Many healthcare groups are organized as a physician-owned professional entity (a PC or, where permitted, a PLLC) supported by a management services organization (MSO). Lemma is built for this structure: each legal entity gets its own accounts, [cash sweeps](/docs/guides/cash-sweeps) automate the funds flow between an MSO and its practices, and [role-based access](/docs/guides/team-management) lets MSO staff operate day to day while the practice keeps oversight.

Beyond those defaults, send us your management services agreement and related documents, and we configure guardrails on your accounts that match how regulators expect a compliant MSO-PC relationship to operate.

*This page describes banking controls, not legal advice. Corporate practice of
medicine (CPOM) requirements vary by state and depend on your specific
agreements and conduct. We are the only ones to offer MSO-PC compliant
banking, and we configure the best we can from the documents you give us —
but we cannot guarantee compliance. Work with healthcare regulatory counsel to
confirm what your structure requires.*

## Why bank account control matters

In states that enforce the corporate practice of medicine doctrine, the licensed professional owner of the practice must keep ultimate control of the practice, including its finances. Enforcement actions have specifically targeted banking arrangements: consolidated accounts the practice owners could not access, management companies with unrestricted access to practice funds, and sweep arrangements the physician could not stop. For practices that bill Medicare or Medicaid, federal rules additionally require that government-payer receivables land in an account the provider controls.

The common thread: the physician should never have to ask the MSO for permission to access the practice's money, and should always be able to see it and turn off the tap.

## What Lemma configures

### A physician on file

We record which owner of each entity is its physician on file. That member's access is protected: no one — not the MSO, not other owners, not even the physician themselves — can lower their permissions or remove them from the entity inside the product. The team settings page explains why those controls are locked, and any attempt to change them through the API is rejected as well.

If the physician on file needs to change — a sale, retirement, license event, death, or disability — [contact us](mailto:contact@getlemma.com). We verify the successor and make the change deliberately, so the transition itself stays compliant instead of happening through a quiet settings edit.

### Inviting licensed professional owners at application submit

For the same reason, when you submit a PC, PLLC, or PA application, the review step lists every licensed professional owner who isn't already a [collaborator](/docs/guides/collaboration) and offers to invite them. Each owner has a Yes/No toggle, defaulted to **Yes**. Leave it on **Yes** to send the invite at submission, or switch to **No** to submit without inviting that owner. Either choice lets you submit the application. Invites sent this way carry over to the entity once the application is approved, so the licensed professional owner has access to the account from day one without any extra setup.

### Physician authority no rule can override

[Approval rules](/docs/guides/approval-rules) route a transfer above your threshold to an owner for approval, and when they are active, creating or editing a [cash sweep](/docs/guides/cash-sweeps) needs an owner's approval too.

No such rule can stand between the physician and the practice's money. Owners can approve requests they raised themselves, so the physician on file — whose Owner role is locked and cannot be lowered — can always move the practice's funds and stop a sweep without asking the MSO. This is what CPOM expects: the physician's authority over practice funds is ultimate, not delegated. Every approval is recorded with who gave it, self-approvals included, and that audit trail is standing evidence that the physician, not the MSO, controls the account.

### Guardrails from your agreements

Send us your management services agreement and we align your account setup with it: the funds flow (patient revenue landing in the practice's account before management fees move to the MSO) and sweep configurations the physician can always see and stop.

### A paper trail on the money itself

Guardrails control what can happen. [Attachments](/docs/guides/attachments) record why it happened: attach the management services agreement to a fee transfer, or a loan agreement to a capital contribution, and the justification sits on the transaction rather than in an inbox.

A cross-entity attachment is visible to both entities, so the practice and the MSO read the same document — neither side holds a private version of the record. Paired with an [invoice](/docs/guides/invoicing), where the practice's owner reads the agreement before approving the payment, an intercompany fee becomes a documented, arm's-length transaction on its face.

## Go deeper on the MSO-PC model

This page covers what Lemma configures on your accounts. For everything around it, Lemma maintains the [MSO-PC Wiki](https://mso.getlemma.com), a free, cited reference on the structure itself. It covers CPOM state by state, entity formation, the agreement stack, payer enrollment, and billing. Useful starting points:

<CardGroup>
  <Card title="CPOM, explained" icon="lightbulb" href="https://mso.getlemma.com/concepts/model/cpom">
    The doctrine behind the MSO-PC structure and how enforcement actually works.
  </Card>

  <Card title="CPOM state map" icon="map" href="https://mso.getlemma.com/reference/legal/cpom-state-map">
    How strictly each state enforces CPOM, with a page of cited rules per state.
  </Card>

  <Card title="Intercompany money movement" icon="arrow-right-arrow-left" href="https://mso.getlemma.com/concepts/banking/intercompany-money-movement">
    How money should flow between an MSO and its PCs, and what regulators look for.
  </Card>

  <Card title="Run a CPOM self-audit" icon="list-check" href="https://mso.getlemma.com/guides/compliance/run-a-cpom-self-audit">
    Check your own structure against the patterns enforcement actions target.
  </Card>
</CardGroup>


# Order checkbooks
Source: https://getlemma.com/docs/guides/order-checkbooks

Order a checkbook for any Lemma account so you can write checks directly.

Order a checkbook for any Lemma account from
[this page](https://app.getlemma.com/_/order-checkbooks) on your dashboard. Each checkbook
includes 150 checks printed with the entity's name, so you can write checks the same way you would from any other
bank account.

You can also order from an account itself: open the account from the
[Accounts page](https://app.getlemma.com/_/accounts) and use **Order Checks** on the
**Account Services** card. That route opens a confirmation window with the account already
chosen, so you only need to enter a mailing address.

You need [owner banking permissions](/docs/guides/team-management#banking-permissions) to
order a checkbook.

## Ordering a checkbook

<Steps>
  <Step title="Visit order checkbooks">
    Go to [this page](https://app.getlemma.com/_/order-checkbooks) on your
    dashboard.
  </Step>

  <Step title="Choose the account">
    Select the Lemma bank account account the checkbook should be linked to. If
    you manage multiple entities, confirm you're on the right entity first. You
    can change entities from the dropdown in the sidebar.
  </Step>

  <Step title="Enter your mailing address">
    You can mail checks to any address in the USA.
  </Step>

  <Step title="Submit your order">
    Review the order carefully. Submitting charges the one-time printing fee to
    the account you're printing checks from, and you cannot change the mailing
    address afterwards.
  </Step>
</Steps>

The confirmation window names the printing fee and the account it will be
charged to before you commit. If that account doesn't have enough available
balance to cover the fee, the order is blocked until it does.

## Shipping

Checkbooks ship via USPS First Class and typically arrive within 7-12 business
days.


# Own multiple entities
Source: https://getlemma.com/docs/guides/own-multiple-entities

Link multiple entities to a single login for easy access and instant transfers.

You can manage multiple entities under the same email login. To add a new entity, go to [Add New Entity](https://app.getlemma.com/onboarding/new-application) in the sidebar (no separate email required). Use the entity switcher to move between entities you've created without signing out.

<Frame>
  <img alt="The entity switcher in the sidebar showing two linked entities and a button to add a new entity." />
</Frame>

## Why link entities

Linking entities to a single login gives you:

* **Instant transfers:** [transfers between your linked entities](/docs/guides/move-money#transfer-within-lemma) are free, instant, and available 24/7
* **One login for everything:** switch between entities without managing separate credentials
* **MSO-PC friendly:** management services organizations and professional corporations can keep finances separate while maintaining easy access to both

## Inviting others to an entity

If you want other people to view or manage an entity, invite them as team members instead of sharing your login. See [Team management](/docs/guides/team-management) for details on inviting users and assigning roles.


# Personal account management
Source: https://getlemma.com/docs/guides/personal-account

Update your email and password, and secure your account with multi-factor authentication.

Manage your personal sign-in details and security methods any time you're logged in. These settings apply to your own user account, not your organization. To manage other people's access, see [team management](/docs/guides/team-management).

## Change your email

1. Open the [Update email page](https://app.getlemma.com/update-email).
2. Enter your new email address and select **Send confirmation links**.
3. Lemma sends a confirmation link to both your current and your new address. The change takes effect once you confirm from both.

Until you confirm from both inboxes, you keep signing in with your current email.

## Change your password

1. Open the [Update password page](https://app.getlemma.com/update-password).
2. Enter your new password, confirm it, and select **Save new password**.

Your password must be at least 12 characters and include an uppercase letter, a lowercase letter, and a number.

If you're signed out and can't remember your password, select **Forgot your password?** on the [login page](https://app.getlemma.com/login). Lemma emails you a link to reset it.

## Set up multi-factor authentication

Multi-factor authentication (MFA) protects your account by requiring a one-time code in addition to your password when you sign in. Lemma supports two methods:

* **Authenticator app**: an app like Google Authenticator, Authy, or Duo generates codes on your device.
* **Text message (SMS)**: Lemma texts a one-time code to your mobile phone.

### Enable an authenticator app

1. Go to [Settings > Security](https://app.getlemma.com/_/settings/security) and select **Enable** next to Authenticator app.
2. Scan the QR code with your authenticator app. If you can't scan it, enter the setup secret manually instead.
3. Enter the 6-digit code from the app and select **Verify and enable**.

### Enable SMS verification

1. Go to [Settings > Security](https://app.getlemma.com/_/settings/security) and select **Enable** next to Text message (SMS).
2. Enter your mobile phone number and select **Send code**. Landlines can't receive SMS codes.
3. Enter the 6-digit code from the text message and select **Verify and enable**.

### Switch or disable a method

You can only disable a method while the other one stays enabled, so your account always keeps at least one active method. To switch methods, enable the new method first, then disable the old one. When you disable a method, Lemma asks you to confirm with a code from the method that remains.

## Why an authenticator app is better than SMS

Both methods are far better than a password alone, but an authenticator app is the stronger choice:

* **Resistant to SIM swapping.** SMS codes go to your phone number. An attacker who convinces your carrier to transfer your number to their SIM receives your codes. Authenticator codes are generated on your device and never leave it.
* **Nothing to intercept.** SMS messages travel over carrier networks and can be intercepted or redirected. Authenticator codes are computed locally, so there is no message to steal.
* **Works without cell service.** Authenticator apps generate codes offline, so you can sign in while traveling or anywhere without reception.


# Team management
Source: https://getlemma.com/docs/guides/team-management

Invite team members and manage roles within your organization.

Lemma supports multiple users per organization with role-based access. Visit the [Users page](https://app.getlemma.com/_/settings/users) to manage your team.

## User roles

Each team member has **banking permissions** that control what they can do with money, and an optional **practice permission** that grants access to billing and clinical workflow features. More granular controls, like requiring approval on specific transactions, can be configured using [approval rules](/docs/guides/approval-rules).

<Frame>
  <img alt="The team management page showing a list of organization members with their roles." />
</Frame>

### Banking permissions

Every member has one of these banking roles:

| Role           | Permissions                                                                                                                                                                                                                                                                                     |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner**      | Full access. Everything Accounting can do, plus can accept loans, approve requests and set approval rules, upload documents, connect API platforms, manage team members, change organization settings, and order checkbooks.                                                                    |
| **Accounting** | Everything Read Only can do, plus can move money, open bank accounts, issue debit cards, create cash sweeps, manage external recipients, create and rename transaction categories, and send invoices. Cannot accept loans, order checkbooks, approve transfer requests, or manage team members. |
| **Read Only**  | Can view balances and transactions, export statements, categorize transactions, deposit checks, and charge payer virtual cards. Cannot move money, issue cards, or change settings.                                                                                                             |

### Practice permissions

In addition to their banking role, a member can have the **Billing Team** practice permission enabled or disabled.

When enabled, the member can:

* Read all Lockbox mail and edit notes
* See health data imported from your EHR
* Approve EOBs and ERAs
* Upload EOBs directly

Owners can toggle practice access for any member from the [Users page](https://app.getlemma.com/_/settings/users). Practice access is independent of the banking role.

## Inviting a team member

An owner can invite new team members with the following steps.

1. Select [Invite user](https://app.getlemma.com/_/settings/users/invite) from your settings page.
2. Enter the person's email address
3. They'll receive an email with a link to join your organization

Pending invitations are listed on the [Users page](https://app.getlemma.com/_/settings/users) until the recipient accepts.

## Removing a team member

Owners can remove members from the [Users page](https://app.getlemma.com/_/settings/users). Select the member and choose **Remove**. Their access is revoked immediately, they will no longer be able to view any data for your organization.


# Transaction categories
Source: https://getlemma.com/docs/guides/transaction-categories

Label transactions to track spending by type and simplify reconciliation and compliance reporting.

Transaction categories let you tag any transaction with a label such as "MSO Fees" or "Payroll". A category column is included in every [CSV export](/docs/guides/export-transactions).

## How to categorize a transaction

### From the transaction details

Click any transaction to see its details. Use the **Category** dropdown to assign a category.

<Frame>
  <img alt="Transaction detail panel showing the Category dropdown" />
</Frame>

Categories are saved instantly and visible to all team members with access to your entity.

Read-only team members can also set categories. Categorization is treated as an annotation, not a financial action.

### When sending a transfer

Every time you send money from the [Move Money page](/docs/guides/move-money), you will see an optional **Category** field. The category is applied to the resulting transaction the moment it's created, so there's nothing to tag afterwards. If the transfer needs [approval](/docs/guides/approval-rules) first, the category is applied when the transfer is approved and sent.

## Built-in categories

The following categories are available to every entity by default:

| Category                       | Common use                                                     |
| ------------------------------ | -------------------------------------------------------------- |
| **Revenue**                    | Practice or business income not tied to a specific payer       |
| **Payer Remittance**           | Insurance payer payments on submitted claims                   |
| **Patient Copay**              | Copays and out-of-pocket amounts collected from patients       |
| **Interest**                   | Interest earned on account balances                            |
| **Patient / Insurance Refund** | Refunds issued to patients or returned to payers               |
| **Payroll**                    | Staff wages and employer payroll taxes                         |
| **Rent & Utilities**           | Office or equipment lease payments and utilities               |
| **Supplies & Inventory**       | Medical or office consumables                                  |
| **Equipment Purchase**         | Capital purchases of clinical or office equipment              |
| **Insurance Premium**          | Malpractice, health, property, or liability insurance          |
| **Software & Subscriptions**   | SaaS subscriptions and software licenses                       |
| **Professional Services**      | Legal, accounting, or consulting fees                          |
| **Vendor Payment**             | Suppliers, contractors, or service providers                   |
| **Bank Fees**                  | Account, wire, or card-processing fees                         |
| **Taxes**                      | Federal, state, or local tax remittances                       |
| **Travel & Transportation**    | Mileage, airfare, lodging, and other travel costs              |
| **Business Meals**             | Meals with patients, staff, or partners                        |
| **Marketing**                  | Ads, promotional materials, marketing agencies                 |
| **Charitable Contribution**    | Donations to nonprofit or charitable organizations             |
| **MSO Fees**                   | Periodic management fees paid under an MSA                     |
| **MSO Loans**                  | Loans from an MSO to a PC or PLLC entity                       |
| **MSO Loan Repayment**         | Principal or interest payments on loans from the MSO to the PC |
| **Owner Distribution**         | Profit distributions to owners or shareholders                 |
| **Loan**                       | Loan proceeds received or repaid                               |
| **Intercompany Transfer**      | Transfers between related entities under common ownership      |
| **Intracompany Transfer**      | Transfers between accounts of the same entity                  |

## Why categories matter for MSOs

Management services organizations that operate under a management services agreement (MSA) must keep a clear audit trail distinguishing payments made under the MSA from loans made to the professional corporation. Misclassifying an MSO fee as a loan repayment (or vice versa) can create legal exposure during a practice acquisition, state licensing review, or tax audit.

Categories make that distinction explicit. Tagging every outbound transfer as **MSO Fees** or **MSO Loan Repayment** as it happens, rather than reconstructing intent months later, keeps your records defensible.

## Custom categories

### Creating a custom category

Owners and accounting members can add custom categories from [Transaction category settings](/docs/entity-settings/transaction-categories). You can always rename a custom category later.

<Frame>
  <img alt="Transaction Categories settings page showing the new category input." />
</Frame>

### Archiving a custom category

If a custom category no longer fits your workflow, owners and accounting members can archive it from the same settings page. On mobile, hover over a category and click the trash icon, or tap it on mobile and choose Archive.

Archiving removes the category from the category dropdown so it can't be selected for new transactions. Any transaction already tagged with that category keeps its label, archiving never changes or removes existing categorization.


# Transactions
Source: https://getlemma.com/docs/guides/transactions

View your complete transaction history and transaction details.

The [Transactions page](https://app.getlemma.com/_/transactions) shows every transaction across your accounts in reverse chronological order.

## Transaction list

Each transaction shows:

* **Description** — a summary of the transaction
* **Counterparty** — who you sent money to or received money from
* **Amount** — the transaction amount (positive for deposits, negative for withdrawals)
* **Date** — when the transaction occurred

Select any transaction to open a detail panel with the full metadata.

## Filter transactions

Use the filter bar above the transaction list to narrow the feed:

* **Search** — match transactions by company, description, or amount
* **Date** — show only transactions within a date range. Set a start date, an end date, or both. Both bounds are inclusive.
* **Account** — limit results to one or more of your bank accounts
* **Type** — limit results to specific transaction types
* **Inbound/outbound** — show only money in or money out

Active filters also apply when you [export transactions](/docs/guides/export-transactions).

## Transaction types

Transactions come from several sources:

| Type                  | Description                                                                                 |
| --------------------- | ------------------------------------------------------------------------------------------- |
| **ACH transfer**      | Automated clearing house transfers                                                          |
| **Wire transfer**     | Irreversible domestic wires                                                                 |
| **Real-time payment** | Instant and irreversible domestic transfer                                                  |
| **FedNow**            | Instant and irreversible domestic transfer                                                  |
| **Check deposit**     | Check received and deposited via your [lockbox](/docs/guides/lockbox)                       |
| **Debit card**        | Purchases using a [Lemma card](/docs/guides/cards)                                          |
| **Internal transfer** | Instant transfers between Lemma accounts, including [moving money](/docs/guides/move-money) |
| **Invoice**           | Payment of an [invoice](/docs/guides/invoicing) you sent, settled between Lemma accounts    |
| **Acquiring**         | A virtual card processed to collect money from a payer                                      |
| **Loan**              | A draw from or a payment toward a Lemma loan                                                |
| **Banking fee**       | A fee charged by Lemma                                                                      |


# Banking built for healthcare
Source: https://getlemma.com/docs/index

Lemma is a healthcare banking platform that brings bank accounts, payments, treasury workflows, and insurance payment reconciliation into one place.

Whether you run a single practice or a group of entities, each one gets its own account and a single dashboard across all of them. These guides cover how each piece works.

## Start here

<Columns>
  <Card title="Quickstart" icon="rocket" href="/docs/quickstart">
    Open your first account in about five minutes. No branch visit.
  </Card>

  <Card title="Own multiple entities" icon="sitemap" href="/docs/guides/own-multiple-entities">
    Every entity its own account, all under a single login.
  </Card>

  <Card title="Collaborate on onboarding" icon="user-group" href="/docs/guides/collaboration">
    Ask a business partner to fill in their own details, without routing sensitive information through you.
  </Card>
</Columns>

## What you can do with Lemma

<Columns>
  <Card title="Deposits that arrive reconciled" icon="file-invoice-dollar">
    Your lockbox scans and matches EOBs on arrival, so insurance payments land already tied to the claim they paid.

    <Links />
  </Card>

  <Card title="Every account in one place" icon="building-columns">
    One account per entity and one view across all of them, with balances and transactions updating in real time.

    <Links />
  </Card>

  <Card title="Money that moves on your rules" icon="money-bill-transfer">
    Free ACH, RTP, and FedNow transfers. Set a sweep threshold once and balances rebalance themselves.

    <Links />
  </Card>

  <Card title="Invoices you send and can track" icon="file-invoice">
    Bill your own customers, and see each payment land against the invoice that earned it.

    <Links />
  </Card>
</Columns>

## Built for your whole team

<Columns>
  <Card title="Owners and admins" icon="shield-halved">
    Decide who sees balances, who moves money, and how much approval a transfer needs.

    <Links />
  </Card>

  <Card title="Billing teams" icon="calculator">
    Move your payers over, let remittances parse themselves, and close the month out of one system.

    <Links />
  </Card>

  <Card title="Engineers" icon="code">
    A REST API over accounts, transactions, transfers, and remittance data, with webhooks when things change.

    <Links />
  </Card>
</Columns>

## Programs that come with your account

<Columns>
  <Card title="Deposit bonuses" icon="gift" href="/docs/guides/deposit-bonuses">
    Earn a bonus on every dollar you bring over, across every account.
  </Card>

  <Card title="Fixed-fee loans" icon="hand-holding-dollar" href="/docs/guides/fixed-fee-loans">
    Borrow against insurance receivables you have already earned, at a flat fee.
  </Card>

  <Card title="MSO-PC compliance" icon="scale-balanced" href="/docs/guides/mso-pc-compliance">
    Keep management company and professional corporation money cleanly separated.
  </Card>
</Columns>

## Keep up with Lemma

<Columns>
  <Card title="Changelog" icon="clock-rotate-left" href="/docs/changelog">
    Every product change we ship.
  </Card>

  <Card title="Roadmap" icon="map" href="/docs/roadmap">
    What we are building next.
  </Card>
</Columns>


# Quickstart
Source: https://getlemma.com/docs/quickstart

How to open an account for your entity on Lemma in less than 5 minutes.

## Onboard your entity's in 5 minutes

<Steps>
  <Step title="Sign up">
    Go to [app.getlemma.com/sign-up](https://app.getlemma.com/sign-up) and create an account with your email address.

    Open the confirmation email from Lemma and click the link inside to verify your email address. You will not be able to log in until your email is confirmed.
  </Step>

  <Step title="Fill out the onboarding form for your entity">
    Head to [app.getlemma.com/onboarding/new-application](https://app.getlemma.com/onboarding/new-application). Since you're opening a bank account, we need to know a few details about your business:

    * **Business profile**: business legal name, EIN, state of incorporation
    * **Control person**: name, title, date of birth, address, email, phone number
    * **Beneficial owners**: anyone with more than 25% ownership stake, can be the same as your control person

    This information is required for regulatory compliance (Know Your Business). Your data is encrypted and stored securely.

    <Tip>
      Need details from a business partner? [Share the onboarding application](/docs/guides/collaboration) with them. Your partner can fill out the onboarding form directly without sending sensitive information to you.
    </Tip>
  </Step>

  <Step title="Sign the platform agreement and business associate agreement">
    Review and sign the [Lemma Platform Agreement](https://getlemma.com/lemma-platform-agreement) and [Business Associate Agreement (BAA)](https://getlemma.com/business-associate-agreement). Lemma is HIPAA-compliant and includes a BAA with every signup to cover the health data we ingest on your behalf.

    The agreements are included at the end of the onboarding application. You sign electronically. We don't need a wet signature.
  </Step>

  <Step title="Submit your onboarding application">
    Most entities are approved within a few hours so you can start using your account right away! We'll email you when your entity is approved.

    In some cases, our banking partners are unable to verify your identity from your tax ID alone. If that happens, we'll reach out to request a scan of your government-issued ID.

    <Tip>
      Managing multiple entities? You can submit multiple applications while waiting for them to get approved. Once you've submitted your first one, visit [app.getlemma.com/onboarding/new-application](https://app.getlemma.com/onboarding/new-application) to start another.
    </Tip>
  </Step>
</Steps>

## Once approved

When your entity is approved, Lemma sets everything up for you automatically.

### Your checking accounts

Your checking accounts are created and ready to use as soon as you're approved. Head to your dashboard to view balances and transactions.

Your account and routing numbers are available on the [accounts page](https://app.getlemma.com/_/accounts). Click into any account and you'll find both numbers at the top of the page, ready to hand off to payers when you update your electronic payment information.

### Your lockbox

Your lockbox is provisioned instantly. See your lockbox address in [your dashboard's lockbox page](https://app.getlemma.com/_/lockbox). You can immediately start sharing your address with payers and clearing houses. Learn more in the [lockbox guide](/docs/guides/lockbox).

### Your team

Onboarding collaborates will automatically have access to the entity's dashboard. You can [invite additional team members](/docs/guides/team-management) for free. We support limiting user's access, for example, when you want a billing team to have read-only permissions.

## Next steps

**Migrate your payers to Lemma**: switching bank accounts is one of the hardest parts of running a healthcare entity. Lemma's EFT enrollment team will assign you a dedicated person to handle the migration and make sure every deposit lands in the right account. Each migration comes with its own onboarding dashboard so you can track progress in real time and see who is responsible for each payer. [Book a call to learn about the EFT migration service](https://calendly.com/tushar-getlemma/lemma-eft-enrollment-service).


# Roadmap
Source: https://getlemma.com/docs/roadmap

Features we don't support yet, and what to do in the meantime.

Lemma is always growing. This page lists notable features we don't support yet but plan to support in the near future.

## Multiple cash sweeps on one account

Each account can have one active [cash sweep](/docs/guides/cash-sweeps) rule today, sending either the balance above a target or a fixed amount to a single destination. We plan to support several sweeps on the same account, including splitting a balance by percentage so money is routed to different places in one run.

## ATM cash deposits

As a digital bank, Lemma mainly focuses on cash-less money movement. However, we recognize the need for cash deposits in healthcare. We're working on coverage through a partner and will have something live by October.

## Zelle

We currently don't support sending or receiving Zelle payments. For now, use [ACH, wire, RTP, FedNow, or checks](/docs/guides/move-money) to move money externally. RTP is a good option for Zelle users since it supports instant transfers 24/7. With Lemma, RTP is free to use.

## Credit cards with cashback

Lemma issues [debit cards](/docs/guides/cards) today. Business credit cards with entity-level controls, cashback, and underwriting based on your Lemma deposit and revenue data are on the roadmap.

## Expanded lending

[Fixed fee loans](/docs/guides/fixed-fee-loans) and revolving lines of credit are live today, backed by your AR and underwritten from reconciliation data. Planned expansion:

* Larger loan sizes, faster decisions, and broader eligibility
* Acquisition loans
* Equipment financing and term loans

## Personal banking for owners

Lemma accounts today are for business entities. We currently offer personal accounts for licensed professional owners under the same login on a case by case basis, so business and personal balances live in one view. Please get in touch with us at [contact@getlemma.com](mailto:contact@getlemma.com) if you are a current business banking client who is interested in personal banking.

## International wires

We don't support outbound international wires. For payments to offshore billing or admin teams, use a third-party provider like Wise or Airwallex. A native path with predictable USD wire and FX pricing is on the roadmap.

## Higher yield on idle cash

We pay yield on operating balances today through [deposit bonuses](/docs/guides/deposit-bonuses) at the rates shown on our [pricing page](/docs/billing/pricing). A higher-yield tier for larger idle balances, with automated sweeps on the same threshold rules used in [cash sweeps](/docs/guides/cash-sweeps), is on the roadmap.

## Invoicing entities outside of Lemma

[Invoicing](/docs/guides/invoicing) only supports billing another entity that's already on Lemma. You can't yet send an invoice to get paid by ACH from an entity outside the platform. We plan to support this so you can invoice any entity, not just other Lemma entities.