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. Select only the accounts Wesley should sync.
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.

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.

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.

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.

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.