Banking Integration

What the banking integration does

Eclipse uses Plaid as the bookkeeping bank-feed layer. Once connected, Eclipse can import transactions, surface review work, and help route activity into reconciliation and expense workflows.

Stripe is used separately for subscriptions and invoice payments. It is not the bank-feed connection used for bookkeeping cash activity.

Before you connect

make sure you are in the correct organization or workspace
use the bank login that has access to the accounts you want Eclipse to read
decide which checking, savings, or card accounts should actually sync

Connect a bank account

Open Settings > Integrations > Plaid or start from the banking connections view.
Choose Connect Bank or Connect with Plaid Link, then review and accept the bank data consent.
Search for your financial institution and complete the secure Plaid sign-in.
Select the accounts you want Eclipse to monitor.
Choose how Eclipse should use each account:
- Business account includes the balance in business cash and enables reconciliation.
- Personal with business use imports an evidence feed but keeps the personal balance and ordinary personal activity outside the books.
- Don’t import leaves the account disconnected from transaction ingestion.
Save account setup. If an account fails to save, retry that account in the same dialog.
Let the initial sync finish, then review imported activity in banking. Pending means the bank is still preparing data; check the last successful transaction sync rather than the connection date.

Eclipse does not create expenses or ledger entries until this account-purpose step is complete.

Review a personal account with business use

The banking workspace opens mixed-personal accounts in Possible business so you do not have to review the full personal feed.

Choose Business to add a category, purpose, receipt, or partial business amount. Eclipse records only the business portion and treats it as paid personally.
Choose Personal to exclude the transaction from accounting and hide it from the default queue.
Select repeated transactions from the same merchant to decide them together.
After confirming a business purchase, you can save a trusted future rule. Eclipse shows the rule scope first; broad merchants such as Amazon or Walmart require an extra exact-amount condition.

Known invoice or payout receipts can be matched from a personal feed, but an unmatched deposit cannot create business revenue on its own. A dedicated business account is still the simplest long-term setup, but it is not required.

Features

Automatic transaction import
review queues for uncategorized, needs-info, or suspicious activity
AI category suggestions that show confidence, source evidence, ledger effect, audit context, shown/edited audit history, and the undo path before you trust them
banking rule previews for draft and saved rules, including matched recent transactions, bank text beside cleaned merchant text, outflow and inflow totals, execution mode, ledger effect, review controls, and audit trail before you save automation
ecommerce rule starters and source-specific rule packs on /automations for Shopify cash clearing, Stripe direct payments, Amazon seller cleanup, and shipping label purchases, with connected-source recommendations, setup progress, lifecycle stage, required evidence, ledger guardrails, review cadence, operator action, risk labels, and previews for configured starters
automation history on /automations for banking rule create, edit, enable/disable, delete, bank workbench actions such as needs-info and unmatch, approval decisions, recent transaction-match activity, AP payment-run actions, AR invoice/payment/reminder actions, close task/period-lock actions, visible-row workflow counts, 7/30/90-day cross-workflow summaries, row-level audit/workflow drilldowns, and AP/AR/close audit handoffs
guided reconciliation workflows with beginning balance, statement ending balance, statement date, optional statement upload and field extraction, optional service charge, optional interest earned, start preview, linked statement evidence, difference clues, evidence-backed narrative summaries, and saved report history
guarded unmatching for unposted source links, with reconciliation and ledger-posting blocks when a transaction is already final
exact-sum matching from one bank outflow to one or more expenses, committed as one accounting action so every expense link, required journal, payment record, and audit entry either finishes together or rolls back together
due high-confidence match suggestions save their confirmation evidence and final match status together; safe retries do not create a second confirmation or count the same match twice
connection health and reconnect prompts when a bank feed goes stale
account cards that show bank-feed balance, mapped ledger balance, and bank-vs-ledger difference when the account is connected to the chart of accounts
visibility into account-level cash activity

Security

Plaid provides the connection layer. Eclipse does not use the Plaid link flow to move money. The bookkeeping connection is used to read account activity and support reconciliation workflows.

If Plaid consent expires, Eclipse stops the connection and retires the stored access credential. Existing imported transactions and accounting history remain in the workspace; reconnect the institution to resume new imports.

Disconnect a bank

Disconnect stops new imports and asks Plaid to revoke bank access. Existing transactions, account records, and accounting history remain available. If revocation or local cleanup fails, Eclipse reports the failure and you can retry. You can connect the bank again later.

Common next steps after connecting

review newly imported transactions
confirm categories for the first batch of activity
reconnect stale items if the institution requires re-authentication
make sure cash activity is landing in the correct organization

If something looks wrong

Check the connection status and last sync time first. Most issues fall into one of three buckets:

the feed needs re-authentication
the wrong accounts were selected during setup
imported activity needs review before it shows up the way you expect

Need help? Contact support