Bank Feed
Your bank and your books, in agreement
Connect once. Transactions arrive already matched to the bills, invoices and payments you have in EasyeSuite — so reconciliation becomes a review instead of a re-entry.
A sample reconciliation queue of five bank transactions. A $5,340.00 wire out is proposed against bill payment BILLPYMT-002954. A $750.00 cheque, number 5090, is already applied to BILLPYMT-002943. A $213.71 eBay deposit is proposed against receipt RECEIPT-001188. A $140.00 Intuit charge was categorized automatically as Software by a rule. A $20.00 wire fee is unmatched and needs a decision.
What the connection can and cannot do
Connected to your bank, never in control of it
The link runs through Plaid, the same layer most major finance apps use. Three guarantees hold from the first sync onward.
Read-only
It cannot move money
You sign in at your bank, not here. EasyeSuite holds a token that reads transactions and balances — there is no payment capability on the connection at all.
- Credentials stored
- None
- Payment capability
- None
Approval
Nothing posts without your say-so
Every match is a proposal that waits for you. A line reaches your ledger when you confirm it — or, if you wrote a rule that covers it, on the terms you already set. Either way the posted line stays linked to the record it settled.
- Auto-posted
- Only by your rules
- Reversible
- Unmatch and re-decide
Scope
Only the accounts you choose
Map an account to the ERP bank it belongs to and switch its feed on. Anything you leave unmapped is never pulled, and disconnecting revokes the link at Plaid too.
- Unmapped accounts
- Not synced
- On disconnect
- Token revoked
Automatic matching
Most of the queue is answered before you open it
The matcher looks for one ERP record that explains the line. When exactly one fits, it proposes. When two could fit, or none, it leaves the line for you rather than guessing.
the rule
- Amount
- Exact, same currency
- Date window
- ± 5 days
- Cheque numbers
- Any date at all
- Ambiguity
- Left for a human
what it searches
- Bill payments
- Money out
- Vendor prepayments
- Money out
- Customer refunds
- Money out
- Payment receipts
- Money in
The rest of the queue
For a line with no record yet, two honest answers
A bank line is evidence that money moved. If nothing in the ERP represents it, something has to be created — and how much paperwork it deserves is a judgement only you can make.
Categorize
One balanced journal entry
The bank side is fixed; you pick where the other half lands. Right for bank fees, interest, a transfer — money with no counterparty worth tracking.
- Creates
- Journal entry
- Good for
- Fees, interest, transfers
Create expense
A real vendor bill
The vendor is resolved from the merchant name and the payment is recorded from this same transaction. Use it when the charge deserves a payable you can report on.
- Creates
- Bill + payment
- Good for
- Anything with a vendor
Rules
Teach it once
Match on merchant, description or amount. A rule can suggest a category for you to confirm, or categorize outright — your choice, per rule.
when
Description contains “INTUIT”
then
Categorize as Software Subscriptions
Beyond the live feed
Coverage for the accounts a connection cannot reach
CSV statement import
For a bank outside the network, or history older than the connection. Imported rows match, categorize and reconcile exactly like synced ones.
Reconciliation statement
Bank balance against book balance for a period, with the outstanding items between them listed — the view an accountant asks for at close.
Cash-flow insights
Money in against money out, by month and by category, drawn from the very transactions you just reconciled.
Questions
What people ask before connecting
What the connection can reach, what it can never do, and what happens to a transaction once it arrives.
Stop reconciling by hand, start reviewing instead
See what a connected bank feed does to your month-end — in a short walkthrough with our team.