Bank-feed exception review
Separate imported activity from verified accounting entries with an exception-first bank-feed review.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Import date range | Source reference | Exception type | Evidence needed | Reviewer | Next check |
|---|---|---|---|---|---|
| October 1 to 7 | Feed-review-01 | Pending and posted pair | Final bank entry and receipt | Bookkeeper | Match posted amount before categorizing |
- Use one row for each item described in the article.
- Record the source, unresolved difference and next action before marking an item complete.
- Review the actual business records separately. This worksheet does not connect to accounts or change your records.

A connected bank account gives your shop a stream of transactions. But your books still need someone to decide what each one means. A parts purchase, an owner transfer and a loan deposit can all land in the same feed. Count every incoming dollar as a sale, and your report gets misleading fast. Start with exceptions, then work through routine expenses. You want a smaller review queue with clear explanations, not the biggest pile of entries accepted automatically.
Use with this guide
Books bookkeeping workspace
Review the scope of Books bookkeeping workspace.
BlueFinch business dashboard
Review the scope of BlueFinch business dashboard.
Wrap accounting exports: catch duplicate payment records
Catch duplicate wrap-shop payment imports with stable transaction references. Use the export review sheet to preserve original collections and correction events.
Check your own costs: calculate your effective processing rate or upload a merchant statement for analysis.
Check what arrived, not only whether the connection is green
Open the imported period and check its start and end dates against the bank source. A successful login doesn't prove the import is complete. Write down the newest activity date available and note any missing days. If your repair shop has two checking accounts, check that both are included in the review. Don't let a combined balance hide an omitted account or a stale connection.
The Books bookkeeping workspace imports supported bank activity through an authorized connection and holds it for review. Check your actual account setup before relying on a report. Included software doesn’t mean you get a bookkeeper, payroll service, or tax return. Keep your current records handy while you check the new workspace, especially during that first reporting month.
Sources for this section: IRS: supporting business records
Resolve changing transactions before creating duplicates
Plaid shows pending and posted transactions as separate states. The posted entry can have a new ID or a different amount, and the pending one may disappear. So an illustrative $480 pending supplier charge followed by a $472 final charge doesn’t prove there’s $952 in purchases. Check the final source entry and supporting invoice before deciding there are two expenses.
Put uncertain pairs in the exception worksheet, with an internal reference. The public worksheet needs no account number, supplier banking information, or receipt image. Assign a reviewer and specify the exact missing evidence. If the feed still disagrees with the bank, investigate the connection or import history before manually creating a replacement entry that later duplicates an incoming transaction.
Sources for this section: Plaid: pending and posted transaction states
Use receipts to explain the business purpose
The IRS lists invoices, receipts, paid bills, and deposit records as support for business entries. A bank description often won’t tell you what you bought or why. A payment to a big retailer could be shop supplies, an equipment asset, or something personal. Don’t guess from the merchant name. Ask for the document, and leave any unresolved classification to whoever handles the books.
Set up a short daily handoff. The office collects missing documents, the bookkeeper checks the accounting treatment, and the owner answers questions about business purpose. A technician shouldn’t need the whole financial workspace just to explain a shop purchase. Keep attachments in the authorized record system, and limit access to people who need them.
Sources for this section: IRS: supporting business records · FTC: protecting personal information
Close the review with a measurable queue
Suppose the week starts with 28 uncategorized items. Eighteen have complete invoices, four are transfers waiting for a matching account, and six have no evidence. Processing eighteen is real progress. But don’t call all twenty-eight complete. Track how many are still unresolved and the oldest unresolved date, then assign the six missing-document requests. Revisit the transfer matches separately so they don’t inflate sales or expenses.
Use the BlueFinch business dashboard as the place to begin the review, then open the underlying workspace for the evidence. A tidy dashboard is the result of sound records, not proof of sound records. End the session when every remaining exception has an owner and a next check. Reconcile the completed period with your bookkeeper before using the figures to change prices or spending.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
- IRS: supporting business records
- Plaid: pending and posted transaction states
- FTC: protecting personal information
Use this page for general business information. It is not legal, tax, or accounting advice.