Bank Feeds (Plaid)

Bank Feeds uses Plaid to bring bank and credit-card activity into a Wesley client book. Open the client and go to Settings > Integrations > Bank Feeds (Plaid). You can also enter the connection flow from Banking.

Before connecting

Confirm all of the following:

• you are in the correct client;
• the client has authorized access to the institution;
• the selected accounts belong in the business books;
• the intended sync start date will not overlap an existing feed or statement import;
• the chart-of-accounts mapping is appropriate for each checking, savings, credit-card, loan, investment, or other account.

Current balance and available balance are reported by the institution. They are not Wesley book balances and should not replace reconciliation.

Connect an institution

1. Choose Connect Account or the available Plaid connection action.
2. Search for the bank, card issuer, or other institution.
3. Complete the institution's Plaid authorization, including any multifactor prompt.
4. Authorize the accounts Wesley should sync. If the same login serves several client books, use one shared bank login and assign each account to its own client as described below.
5. For each selected account, create or link the Wesley ledger account and confirm the account type.
6. Choose the transaction start date and review the opening-balance setup.
7. Start the sync and wait for the selected accounts to appear in Banking.

If that institution is already connected, Wesley can send you through an update and account-selection flow instead of creating a duplicate institution connection.

Connect a separate login at the same bank

A business bank account and a credit card may use different usernames at the same bank. Each login needs its own connection, while each bank or card feed still maps to its own Wesley ledger account.

1. In Banking, choose Add account > Connect bank or card.
2. Choose Connect a different bank login. Review the existing accounts and confirm that you will use a different login. If other clients' logins are listed, review those before continuing.
3. Choose Continue to bank sign-in (or Connect a different bank login when reviewing other clients' connections).
4. Select the same bank in Plaid and sign in with the separate username for the missing account.
5. In Set up bank accounts, select the matching Existing bank/card account under Set up in Wesley if the account is already in the books.
6. Review the import start date and finish setup.

Use the existing connection's account-selection flow for accounts under the same username. Signing in again with that username can interrupt its existing feeds. A dismissed setup banner does not remove the setup options under Add account > Connect bank or card.

Use one bank login across clients

If the same bank login includes accounts for multiple companies, keep one connection and assign the individual accounts to their respective client books. Creating separate connections with the same Chase login can invalidate an earlier connection.

1. Open Settings > Integrations > Bank Feeds (Plaid) and choose Manage shared bank login. This action is also available while reviewing an existing login during Connect Account.
2. Choose the existing bank login to keep. A working connection can be reused without signing in again.
3. If an account is missing, choose Authorize more accounts. If authorization is unavailable, choose Restore bank access. Review the affected clients and confirm before continuing. In the bank window, keep every account needed by these clients selected.
4. For each unassigned account, choose its Client and Existing bank/card account. If a separate connection stopped working, select the original unavailable ledger account with matching bank, last four digits, and account type. No new ledger account is needed.
5. Review Import start date. The suggested date overlaps recent bank activity to catch delayed transactions and ignores later manual adjusting entries. When a replacement feed is linked to an account with history, backfilled activity waits in Banking > Duplicate for review before automatic posting. The existing opening balance is preserved.
6. Choose Review assignments, check the client and account pairs, and choose Save and restore feeds. Accounts that are already mapped keep their existing assignments.
7. Open each client's Banking page to review new activity. If an import needs another attempt, choose Continue setup, then Retry. Saved choices survive closing the window.

To create a new ledger account instead, choose Set up in this client later, save the assignment, and complete bank setup in that client. Other clients' accounts are kept out of its setup choices.

The person who originally connected the bank must have write access to every client using the login to change shared authorization. Paused clients stay paused. Account assignments keep transactions, journals, reconciliations, opening balances, and sync receipts in their original client books. Renewing bank authorization can also invalidate a separate connection using the same credentials; restore that client's existing account on the shared login rather than repeatedly signing in to separate connections.

Replace an unavailable connection and keep history

Use replacement when an existing single-client connection needs bank authorization and cannot be restored through its normal update flow. Only the original connector can replace it. Shared logins must be managed together.

1. Open Settings > Integrations > Bank Feeds (Plaid). In the unavailable bank's actions, choose Replace connection and keep history.
2. Choose Remove old bank access and confirm. This revokes the old bank authorization while keeping the existing Wesley accounts, transactions, journal entries, reconciliations, and sync history. It cannot restore the old authorization, and the bank may still reject the new connection.
3. Wait until removal is confirmed. If it is not confirmed, use Retry removal. After closing the screen, Continue replacement resumes the saved operation.
4. Choose Connect replacement, sign in to the same bank, and authorize every checking and card account needed for this client.
5. In the mapping screen, choose the existing Wesley account for each bank account. Review the import dates, choose Review assignments, then Save and restore feeds. If the bank connection already completed, Review mappings resumes this step without another bank sign-in.
6. Open Banking > Duplicate. Compare the backfilled imports with the existing records. Discard copies already recorded and keep new activity to move it to Uncategorized for posting or matching. Amount and nearby date suggest comparison candidates; they do not prove a duplicate, so Wesley does not automatically discard these imports.

Saved history older than the bank's new lookback window stays in Wesley. Future activity dated after the replacement's review boundary follows the normal bank-feed workflow. Late-arriving activity dated within that boundary continues to require review.

Use this replacement action instead of Disconnect Plaid Item, which follows the account and transaction deletion flow.

Account mapping

Each selected bank or card account must be linked to the matching account in Wesley's chart of accounts. Link an existing account when it already represents the same real-world account. Create a new one only when the client book does not have it. Do not map two unrelated accounts together merely because their names are similar.

Accounts created manually or imported from QuickBooks are not Plaid connections by default. They can hold uploaded or imported activity and can later be explicitly linked to Plaid. Wesley performs that provider change atomically on the same ledger account, preserving prior journals, transactions, and reconciliations. Set the Plaid start date after existing activity to avoid importing an overlapping range.

Clearing an account in Wesley's setup dialog only means it will not be configured in Wesley yet; it does not change the authorization already granted in Plaid. Use the existing institution's Manage accounts (Update Mode) action to remove the account from this client. Accounts removed there stop syncing and appear disconnected if they had already been mapped, while their accounting history remains intact. You can reconnect the live feed later or continue using statement uploads on the same ledger account.

Match an existing journal

Use Match to link imported bank activity to an existing journal line in the linked account or one of its sub-accounts in the same client book. If a receipt was allocated across several sub-accounts, match each allocation until the receipt's remaining amount is zero. Matching preserves the journal's accounts and amounts, including any existing match on the other side of a transfer.

What a sync can change

A Plaid sync can add transactions and reflect changes supplied by the institution. Review the visible sync status before working with newly imported activity.

When opening balances are enabled, Wesley can create one opening-balance entry for the account. Do not create a second manual opening entry without first confirming that one is missing.

After the sync:

1. compare the date range with the institution;
2. check the first and last imported transactions;
3. review duplicates if the same dates were uploaded from a statement or another source;
4. categorize and post from the transaction-review workflow;
5. reconcile to a statement before relying on the balance.

Connected and Needs attention

The integrations card shows Connected when the institution connection is ready. It shows Needs attention when renewed authorization or another user action is required. Open the institution to read the current message and follow the displayed action.

An individual account may also be added or removed through Manage accounts (Update Mode) without changing the health of every other account at the same institution.

Reconnect an institution

Reconnect when credentials changed, the institution changed its security flow, account consent expired, or the integration shows Needs attention.

1. Open the existing institution connection.
2. Choose its update or reconnect action.
3. Complete Plaid authorization.
4. Reconfirm the account selection and mapping.
5. Run or monitor the next sync.

Do not disconnect merely to fix expired authorization. Reconnect preserves the existing account mapping and review history.

If bank access has been revoked or Plaid reports that the connection no longer exists, Wesley automatically disconnects its feeds and retires the old login. Existing accounts, transactions, journals, reconciliations, and sync history stay in Wesley. Connect the bank again, then use Manage shared bank login to assign each new feed to its existing Wesley account.

Restore an account that appears twice

After renewed authorization, a bank may return a different Plaid account ID or name for the same account. You may see a new Not matched account alongside the old account marked Feed unavailable or Setup status unavailable. The old account's accounting history remains in Wesley.

1. If authorization is still needed, open the existing institution's Manage accounts (Update Mode) action and complete Plaid authorization. Select the bank accounts that belong to this client. If the new account already appears as Not matched, continue without signing in again.
2. Choose Create unmatched accounts to open Set up bank accounts. This dialog can also link an existing account; opening it does not create an account.
3. Select the new bank account. Under Set up in Wesley, search for the old account's name or last four digits and choose it under Existing bank/card accounts. An unavailable matching feed is labeled Reconnect · keep existing history.
4. Confirm that the bank, last four digits, and account type match. The bank's new account name can differ from the name already in Wesley.
5. Review Import start date. Wesley fills in the day after the existing account's latest activity when available. Choose a range that does not overlap transactions already imported or uploaded. Importing overlapping dates can produce duplicates when the bank changes transaction IDs.
6. Leave accounts for other clients unselected, even if the same bank login exposes them. For example, an account for a different legal entity should be set up in that entity's client book.
7. Choose Set up 1 account (or the count you selected). Wesley replaces the unavailable feed on the same ledger account and imports the selected range. Existing transactions, journal entries, reconciliations, and the opening balance are preserved; this reconnection does not create another opening balance.
8. Open Banking, check the linked account and new activity, and reconcile to the next statement.

You do not need to use Disconnect to restore this feed. Disconnect remains destructive. If setup is interrupted, reopen bank setup and use Retry for the saved choice.

If the existing account is missing from the choices, finish Manage accounts first and reopen setup. Reconnection is available when the old feed is unavailable and the replacement belongs to the same institution connection with matching last four digits and account type. If the original feed is still available or the identifying details differ, contact support before combining accounts.

Deselect an account or disconnect the institution

Deselecting one account through Manage accounts (Update Mode) stops future syncs for that account and marks its feed disconnected while leaving the institution, its other accounts, and the deselected account's imported history intact. Disconnecting the institution removes the whole connection and is destructive.

Before you confirm Disconnect, review every mapped account, imported transaction, related journal, opening balance, rule, and closed period. Disconnect can:

• remove transactions imported through this connection;
• unpost or delete related journals and opening-balance entries when the books allow it;
• remove accounts created only for this connection when they are not used elsewhere;
• keep accounts used elsewhere but detach their live feed;
• remove the institution connection.

Transactions already moved to another Banking account stay in that account with their related postings. Review those transactions separately if they also need to be corrected or removed.

A closed accounting period or later accounting activity can prevent some records from being removed. If Wesley reports that the disconnect did not finish, do not create a replacement connection immediately. Retry from the existing connection or contact support.

Disconnecting is not the way to preserve historical feed data while merely stopping new imports. If that is the goal, deselect the account through Manage accounts (Update Mode).

Troubleshooting

The bank is not listed

Search by the institution's legal name and online-banking URL. Plaid coverage is controlled by the provider and can change. Use statement upload or a manual banking account when a live connection is unavailable.

Plaid login fails

Sign in directly at the institution first, resolve any lock or required consent, and then retry Plaid. Wesley does not need the client's bank password outside the Plaid authorization window.

Transactions are missing

Check the account selection, sync start date, latest run status, and whether the institution limited available history. Compare against the statement. Upload only the missing range, and review for overlap before posting.

Transactions are duplicated

Look for the same activity from Plaid, statement upload, QBO/QBD, or a manual import. Use the duplicate-review state instead of posting both rows. Never assume equal amount and date alone prove a duplicate.

Disconnect is blocked

Read the error for period locks, independently used accounts, or later accounting activity. Resolve the blocking condition safely, review the affected records again, and retry. Do not delete journal history simply to force the disconnect.

For transaction actions after import, continue to Transaction Categorization.