> For the complete documentation index, see [llms.txt](https://docs.nifty.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nifty.ai/analytics/bankimports.md). # Bank imports Connect your bank through Plaid to automatically import transactions into Nifty's **Expenses**. {% hint style="info" %} Bank imports are available to US users on **Crosslisting Pro** or **Bundle Pro**. Eligibility is based on the country set in your Nifty account. For help or feedback, contact . {% endhint %} ### Where to find it Go to **Settings** → [**Bank Accounts**](https://app.nifty.ai/settings/bank-accounts). ### Banks and accounts A bank connection can include several accounts, such as checking, savings, or a credit card. You choose which accounts import transactions. You can connect up to **two banks** and import from up to **two accounts total**. For example, you can import from two accounts at one bank, or one account at each of two banks. Only supported US banks and credit cards are available.

Bank Accounts settings showing Example Bank with two accounts and importing enabled for Business Checking. — One bank connection can include several accounts. Turn on importing for the accounts you want to use.

### Start importing 1. Click **Connect Bank**. If you've already connected a bank, click **Connect to a new bank**. 2. Follow the Plaid prompts to connect your bank. 3. Turn on the switch next to an account you want to import from. 4. Choose a **Start date**, then click **Import Transactions**.

Import Transactions dialog for a sample credit card, with a Start date field and Import Transactions button. — Choose how far back to import transactions for each account.

You can choose a start date up to two years ago. The amount of history available depends on your bank. Choose a date that avoids overlapping with expenses you've already entered or imported from a spreadsheet. Nifty checks for new transactions automatically. Your first import and later updates may take time to appear, depending on your bank. ### Review imported expenses Go to **Analytics** → [**Expenses**](https://app.nifty.ai/analytics/expenses). Imports follow your chosen start date and include personal purchases as well as business transactions. Review the descriptions and categories, delete expenses that don't belong in your business records, then mark the remaining expenses as reviewed. Imported expenses can affect your reports before you mark them as reviewed. Use **Filter by source** to find transactions from a particular account and **Filter by reviewed** to find expenses you haven't checked yet. Pending transactions can't be edited or marked as reviewed until they're finalized. ### Manage imports In **Settings → Bank Accounts**: * **Change the start date** — Click the date beside **Importing from**. * **Stop importing** — Turn off the account's switch, then click **Stop Importing**. * **Disconnect a bank** — Click **Delete** on the bank connection to stop imports from all its accounts. Changing the start date, stopping imports, or disconnecting a bank keeps previously imported expenses in Nifty. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nifty.ai/analytics/bankimports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.