Accounting
Invoice Crowd has no direct bank integration. There is no screen where you choose your bank and sign in. You download a statement from your bank as CSV, XLS or XLSX, import it, and match the rows against the invoices, bills and payments already recorded. A staging layer can also hold transactions posted in from a source you control, and those rows join the same review queue.
Last updated:
How it works
Imported rows are normalized and held for review. They become staged bank rows, not accounting entries, so you still match and close the reconciliation deliberately.
Nothing is fetched on your behalf.
Download the account statement from your bank and upload it. Invoice Crowd reads the file, previews what it found and lets you correct the column mapping before anything is staged. No bank login, no credentials and no third-party aggregator are involved.
A bank-feed connection can hold transactions supplied from your own source. They are normalized into the same shape as imported statement rows, so the review step does not change.
Nothing becomes a book entry on arrival.
You review the pending rows and import them into a Bank Reconciliation session for one account and period. They become ordinary staged reconciliation rows, not final accounting transactions.
Reconciliation compares imported rows with recorded activity. An unmatched row can prefill an income or expense form, but the user must save it and choose what closes.
Stated plainly, because it decides whether the product suits you.
Invoice Crowd does not link to bank accounts. There is no in-app flow to pick your bank and sign in, and no automatic bank feed is offered on any plan. If you need transactions to arrive on their own, a product with mature bank feeds is the better fit, and the Xero comparison says so.
Importing rows does not mark any source transaction reconciled, post a payment or change a balance. The session still needs deliberate matching and a close.
Built in
Statement import, pending transactions, the reconciliation hand-off and the boundary.
Download the account statement from your bank and upload it. Invoice Crowd reads the file, previews what it found and lets you correct the column mapping before anything is staged. No bank login, no credentials and no third-party aggregator are involved.
A bank-feed connection can hold transactions supplied from your own source. They are normalized into the same shape as imported statement rows, so the review step does not change.
You review the pending rows and import them into a Bank Reconciliation session for one account and period. They become ordinary staged reconciliation rows, not final accounting transactions.
Reconciliation compares imported rows with recorded activity. An unmatched row can prefill an income or expense form, but the user must save it and choose what closes.
Invoice Crowd does not link to bank accounts. There is no in-app flow to pick your bank and sign in, and no automatic bank feed is offered on any plan. If you need transactions to arrive on their own, a product with mature bank feeds is the better fit, and the Xero comparison says so.
Importing rows does not mark any source transaction reconciled, post a payment or change a balance. The session still needs deliberate matching and a close.
See provider, account and sync status.
Review normalized rows before import.
Use supported manual or sandbox transaction paths.
Provider sync needs deployment credentials and access tokens.
Match imported rows and close the session.
See the reports and record surfaces around the feed.
Questions
No. Invoice Crowd has no direct bank integration and no in-app flow for choosing your bank and signing in. Bank transactions arrive by importing a statement you download from your bank as CSV, XLS or XLSX.
No. No plan includes an automatic bank feed. Reconciliation is designed around a statement file, which needs no provider setup and shares no banking credentials with anyone.
No. Invoice Crowd holds normalized feed rows as pending. Selected rows import into Bank Reconciliation, where the user reviews matches and saves any missing entry deliberately.
The rows become staged Bank Reconciliation lines for the chosen account and period. The ordinary reconciliation workflow handles matching, missing-entry creation and close.
No. Import and reconciliation close are separate steps. A row is not treated as reconciled merely because the provider returned it or the user staged it.
Yes. Invoice Crowd also supports CSV, XLS and XLSX statement import through the smart mapping wizard, so a provider connection is optional.
Stage provider transactions, choose what to import, and reconcile them in the same deliberate workspace as a bank statement.
