Use the file your bank exports
Upload CSV, TXT, XLS, XLSX, OFX, QFX, QBO, QIF, CAMT-style XML, MT940 or BAI2 up to 10 MB. Scanned PDFs and images are not parsed.
- Structured formats only
- 10 MB upload limit
- No OCR claim
Accounting feature status
Reconcile from an uploaded bank statement
Invoice Crowd does not connect to Plaid, Yodlee or another live bank-data provider. Download a supported structured statement from your bank, upload it to Bank Reconciliation, review the server-generated preview and close only after recorded activity exactly covers the statement. Historical bank-feed records remain read-only evidence; they are not synchronized or imported.
- Manual statement upload only
- No bank credentials shared
- Historical feed evidence stays read-only
Last updated:
What is actually available
Bring bank activity in without inventing a live connection
The current workflow is file-based and deliberate. Importing bank rows never creates accounting entries or marks anything reconciled by itself.
Upload a structured statement
Private, bounded processing
Parse without trusting the browser
The server detects and normalizes dates, amounts, debit and credit direction, currency and running balance. Unsafe XML, spreadsheet expansion and unsupported row shapes fail closed.
- Server-authoritative preview
- No spreadsheet formula calculation
- XML network access disabled
Review before import
Nothing posts automatically
Correct the mapping and inspect every row
Header and column detection are assistance. The user can correct the mapping before import, and the server re-reads the private source rather than trusting client preview values.
- Header scan is bounded
- Locale-aware amount and date handling
- Mapping stays business and account scoped
Reject duplicates and overlap
The exact file hash is unique within the owner, business and account scope. Normalized row fingerprints prevent overlapping imports while retaining legitimate repeated transactions.
- Exact duplicate file rejected
- Overlapping rows skipped
- Repeated legitimate rows preserved
Reconcile deliberately
Import is not reconciliation
Match against recorded activity
Imported rows enter the Bank Reconciliation workspace. An unmatched line can prefill an Income or Expense form, but the user must review and save through the normal accounting workflow.
- No automatic accounting post
- No automatic payment
- User reviews missing entries
Close at exact zero, with audit evidence
Closing succeeds only when server-authorized ledger entries exactly cover the statement and the server-calculated difference is zero. A permitted reopen records the actor, time and reason.
- Exact-zero close
- Durable match evidence
- Audited reopen
Current boundary
Current bank-feed and statement-import boundary
Historical provider records remain read-only evidence. Invoice Crowd does not run a live provider sync or allow those records to change current accounting data.
-
No live bank connection
There is no bank-picker, bank-login or provider onboarding widget.
-
No live Plaid or Yodlee connection
No provider scheduler, token store or transaction-sync service is executed.
-
Historical rows preserved
Historical connection and transaction records remain read-only for continuity and audit evidence.
-
Manual upload only
The supported path begins with a structured statement file downloaded from the bank.
-
Wide structured-format support
CSV/TXT, XLS/XLSX, OFX family, QIF, CAMT-style XML, MT940 and BAI2 are supported within parser limits.
-
No scanned PDF import
Images and scanned statements need a structured export from the bank.
-
Duplicate protection
Exact files and overlapping normalized rows are rejected or skipped in the same account scope.
-
Tenant scoped
Owner, business profile, account, currency and period are verified server-side.
-
No ledger writes on import
Statement rows are evidence to reconcile, not accounting entries.
-
No currency conversion
A statement must use one ISO currency matching the accounting-currency account.
-
Exact-zero close
Client-supplied difference values are ignored and the server recomputes the close.
-
Audit-preserving reopen
Authorized reversal keeps the original statement, match history and reason.
Questions
Bank feed availability, answered
Does Invoice Crowd connect directly to my bank?
No. Invoice Crowd does not currently connect directly to a bank-data provider. Upload a supported structured statement from Bank Reconciliation instead.
Can I connect Plaid or Yodlee?
No. There is no active provider onboarding, token storage, scheduler or transaction-sync service. Historical provider rows remain read-only evidence only.
Which statement files can I upload?
CSV, TXT, XLS, XLSX, OFX, QFX, QBO, QIF, CAMT-style XML, STA/MT940 and BAI/BAI2 are accepted within the documented size, row and parser limits.
Does importing a statement create accounting entries?
No. Import creates normalized reconciliation rows. An unmatched line can prefill an Income or Expense form, but a user must review and save it normally.
Can a reconciliation close with a difference?
No. The server requires selected, authorized ledger activity to cover the statement exactly and the calculated difference to be zero.
Why keep this bank-feed URL?
It gives existing links and search visitors the current availability boundary and directs them to the supported manual statement workflow instead of presenting a false integration.
Use the bank evidence your accounting can prove
Download a structured statement, preview and import it, then reconcile against the records already in the correct business, account, currency and period.
- No bank credential sharing
- No automatic accounting writes
- Close and reopen stay auditable