Accounting
Invoice Crowd's Bank Reconciliation matches an uploaded bank statement against the income, expenses, bills and payments you recorded, and closes only when the server-calculated difference is exactly zero. Each new statement opens at the last closed balance, and matches and any authorized reopen stay auditable.
What is actually available
Analysis, import, matching, close and reopen are separate guarded stages. A statement line never becomes a ledger fact merely because it was uploaded.
Before durable import
Invoice Crowd accepts CSV/TXT, XLS/XLSX, OFX-family files, QIF, CAMT-style XML, MT940 and BAI2 up to 10 MB. It scans at most 30 rows for a header and rejects unsafe or unsupported shapes.
The server stores a private temporary copy, fingerprints the exact file and recomputes the preview. Changed account, period or closing-balance settings require a new analysis.
No automatic accounting writes
Every row must fall inside the period, use one positive economic direction and match the accounting currency. Running balances are checked forward or reverse when present.
An unmatched line can open a prefilled Income or Expense form, and Bank Rules you create can suggest its income or expense category. The user reviews and saves it through the normal accounting path; import never auto-posts Income, Expense, Bill or Journal entries.
Durable audit trail
The server row-locks the statement and selected ledger facts, rejects stale or out-of-scope IDs, recomputes every amount and closes only when withdrawals and deposits exactly cover the statement. Matched entries then stay frozen until the statement is reopened.
A user with accounting.reverse may reopen a closed statement with a reason between 5 and 500 characters. Original statements and matches remain; reversal actor, time and reason are recorded.
Reconciliation controls
The workflow keeps each business's data separate and protects source records, currency meaning, simultaneous edits and the record of reversals, rather than trusting a spreadsheet preview.
The uploaded file is staged privately and deleted after a successful durable import.
The same file cannot be analyzed twice in the same owner, business and account scope.
Normalized row fingerprints prevent repeat imports while occurrence ordinals retain legitimate duplicates.
Successful mappings are reused only for the same business and account header fingerprint.
Formula calculation and XML network/entity expansion are disabled.
Declared currency must match the business accounting currency; no conversion is inferred.
The browser cannot supply an accepted difference or forge selected totals.
Owner, business, account, period and unreconciled state are independently queried.
Each selected ledger fact receives source-aware match evidence.
Close and reopen lock the record, so an out-of-date request made at the same time is refused.
Import and close require accounting.post; reopen requires accounting.reverse.
Original statement, matches, actor, time and reason are retained.
Questions
Supported extensions are CSV, TXT, XLS, XLSX, OFX, QFX, QBO, QIF, XML/CAMT, STA/MT940 and BAI/BAI2, up to 10 MB and within the row, column and parser limits.
No. Obtain a supported structured export from the bank. The current workflow does not claim OCR or image parsing.
No. It creates normalized statement evidence. A user may open a prefilled Income or Expense form for an unmatched line, but must review and save it normally.
No. Server-authorized selected entries must exactly cover the bank withdrawals and deposits and the server-calculated difference must be zero.
Yes, by a user with accounting.reverse who supplies a 5–500 character reason. Reopen preserves the original evidence and records reversal actor and time.
No. Invoice Crowd does not link to your bank. Upload a supported structured bank statement, review the server-calculated preview and reconcile it against recorded activity in the same account and period.
Yes. Once a statement is closed, the next one opens at that statement's closing bank balance, and recorded entries that had not cleared yet are offered again. A cheque written on 30 January and cleared on 2 February can be reconciled on the February statement.
Yes, but it never posts anything on its own. It pairs each bank line with at most one recorded entry of the same direction and amount dated within three days, and you confirm the matches before closing. Bank Rules you create (New Rule: When, Contains, Category, Priority) suggest the income or expense category when you create an entry from an unmatched line.
Import the statement, review the normalized rows, create any missing source records deliberately and close only when the server proves exact coverage and zero difference.
