Client Reconciliation Without Bank Account Access
Reconcile client exports without asking for bank credentials or holding an ongoing connection to the client's bank account.
Try with sample files | View sample report
Problem statement
A bookkeeping firm may own the reconciliation while its policy prohibits staff or vendors from holding client bank credentials. A controlled export handoff provides the needed rows without standing account access.
Example access handoff
| Line item | Amount |
|---|
| Client exports | Bank statement and payout detail |
| Bookkeeper receives | Scoped CSV/XLSX files |
| Bank login shared | No |
| Standing connection created | No |
| Final output | Review-ready reconciliation report |
Why a client-file handoff can be the right boundary
- The client keeps control of the bank login and chooses the exact account and date range exported.
- The reviewer receives the rows needed for the engagement without gaining standing access to future activity.
- A repeatable file checklist is easier to audit than shared credentials.
- The completed report can preserve open items without changing the bank or accounting system.
Client file request
- Bank export for the agreed account and period with date, amount, description, and reference fields.
- Orders, invoices, payouts, or processor activity covering the same review window.
- Refund, fee, reserve, or adjustment detail only when an open difference needs it.
Client-safe reconciliation workflow
- Send a written file request naming the account, period, format, and columns.
- Have the client export the files without sharing credentials.
- Confirm periods, currencies, and signed amounts before matching.
- Review matches and exceptions in separate report sections.
- Return the report and apply the engagement retention policy.
Firm policy checks
- Confirm who is authorized to export and deliver each file.
- Use the firm's approved transfer channel.
- Document retention and deletion rules.
- Keep weak-reference matches open for review.
How Reconcile Locally supports the handoff
- Processes raw client exports in the browser session.
- Keeps matched, review, unpaid, duplicate, and unknown items separate.
- Standardizes output without requiring one bank connector across every client.
What still needs manual review
- Clients must deliver fresh exports for each review period.
- The firm still controls authorization, secure transfer, retention, and professional review.
Do not want to connect a bank account?
Compare a browser-local exported-file workflow with a typical connected reconciliation tool.
Content review and sources
Written and reviewed by the Reconcile Locally product team. Last reviewed June 7, 2026.
Guidance is checked against current product behavior and first-party documentation where available. Reconciliation results still require human review.
Frequently asked questions
Does the bookkeeper need the client's bank password?
No. The client exports the agreed bank period and sends the file through the firm's approved handoff process.
Can this work across different banks?
Yes, when each bank can produce a usable CSV/XLSX export with mappable date, amount, and reference fields.
Does this replace a client data-handling policy?
No. The firm still controls authorization, transfer, storage, retention, and deletion around the browser session.