Reconciliation Without OAuth Bank Access
Use deliberate CSV/XLSX exports instead of granting a reconciliation vendor a persistent OAuth connection to a bank account.
Try with sample files | View sample report
Problem statement
OAuth can remove manual exports, but it creates an ongoing authorization that must be approved, monitored, and revoked. For a scoped review, a temporary file can be the simpler access model.
Scope comparison
| Line item | Amount |
|---|
| Connected workflow | Ongoing authorization to supported account data |
| File workflow | One selected account and period |
| Reconcile Locally OAuth token | None |
| Automatic refresh | No |
| User-controlled scope | Export contents |
What changes when there is no OAuth connection
- There is no standing token for the reconciliation product to refresh or retain.
- The account owner decides which account, period, and columns enter the review.
- Access ends with the exported file and browser session.
- The tradeoff is manual export because new activity does not appear automatically.
What replaces the connection
- A scoped bank export for the account and period in review.
- A matching payout, order, invoice, or processor activity export.
- A final report that records matched and unresolved rows.
No-OAuth review workflow
- Define the account, period, and source systems in scope.
- Export files directly from the account-owner portals.
- Open and map the files locally without authorizing a connection.
- Review evidence and leave unsupported explanations open.
- Export the result and apply the source-file retention policy.
Access-model questions to ask
- Is continuous synchronization required for this review frequency?
- Who can authorize and revoke a connected application?
- Would a narrower export meet the same objective?
- How will source files and reports be retained?
How Reconcile Locally limits product access
- Does not request a bank login or OAuth authorization.
- Processes raw financial rows inside the browser session.
- Uses exported files across banks, platforms, and client environments.
What still needs manual review
- No OAuth does not remove the need to handle exported files securely.
- The workflow does not monitor account changes after the export.
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 Reconcile Locally use bank OAuth?
No. The workflow starts from files you export and does not request an OAuth connection to the bank account.
Is OAuth itself unsafe?
Not inherently. The decision is whether ongoing third-party access is necessary for the workflow.
What do I lose without OAuth?
Automatic refresh and continuous synchronization. A fresh review period requires a fresh export.