Reconciliation Software Without Bank Account Access
Reconcile exported bank, payout, order and invoice files in your browser without giving a reconciliation vendor bank login or OAuth access.
Direct bank feeds are useful when continuous sync is the goal. They are not the right default for every review: bookkeeping firms may prohibit third-party access, EU teams may want to minimize additional processors, and occasional reconciliations may not justify a permanent connection.
Reconcile Locally uses files you deliberately export. Raw financial rows are processed in the browser session, so the product supports structured review without becoming another service connected to the bank.
Try with sample files | View sample report
The access boundary is the feature
- No bank login, read-only mandate, or OAuth consent is required.
- You choose the account, date range, and rows included in each export.
- Raw financial files stay in the browser session.
- The workflow works from usable CSV/XLSX exports instead of a connector list.
- Matched and unresolved rows remain explicit before report export.
File-based review versus a connected reconciliation tool
| Decision point | Reconcile Locally | Typical connected tool |
|---|
| Bank OAuth or login | Not required | Usually required for bank-feed automation |
| Where raw file rows are processed | Inside the browser session | By the connected service and its infrastructure |
| Connection lifetime | No standing connection | Persists until revoked or disconnected |
| Bank and platform coverage | Any usable CSV/XLSX export | Limited to supported connectors and permissions |
| Best fit | Controlled, occasional, client-file, or privacy-sensitive reviews | High-frequency workflows that benefit from continuous sync |
What you provide instead of bank access
- A bank statement CSV/XLSX for the account and review period.
- An order, invoice, processor activity, or payout export that explains the expected cash movement.
- Optional refund, fee, reserve, or adjustment support when the first two files do not prove the difference.
A reconciliation workflow with no bank connection
- Export only the bank period and source rows needed for the review.
- Open the files without providing bank credentials or OAuth consent.
- Confirm date, amount, and reference mappings.
- Review clear matches separately from uncertain, duplicate, unpaid, and unknown rows.
- Export the report and retain source files under your own policy.
Who this access model is for
- Bookkeeping firms that receive client exports but cannot hold client bank credentials.
- EU businesses that want to reduce unnecessary third-party handling of raw financial rows.
- Teams running one-off, monthly, or irregular reconciliations.
- Reviewers using banks or platforms without a reliable connector.
When a connected tool may be the better choice
- Fresh review periods require fresh exports.
- The workflow does not continuously sync balances or post accounting entries.
- Local processing can support data minimization but does not make the wider workflow GDPR-compliant on its own.
Frequently asked questions
Does Reconcile Locally need my bank login?
No. You work from CSV/XLSX exports and do not provide a bank login, mandate, or OAuth authorization.
Do raw financial files leave the browser?
Raw bank, payout, order, and invoice rows are processed inside the browser session and are not uploaded to Reconcile Locally servers.
Is a file-based workflow always better than a bank feed?
No. A bank feed can be better for frequent automated sync. Local file review is useful when standing access is not permitted or necessary.
Does local processing make the workflow GDPR-compliant?
Not by itself. Your organization still needs its own lawful basis, access, security, retention, and processor assessment.
Choose the reason you need no bank connection
Each page addresses a distinct decision instead of repeating one generic privacy claim.
Workflow hubs
Choose the review path that matches the type of export you are trying to explain.