The problem
Migrating into a new accounting system, or just catching up a backlog of invoices, usually means either re-typing everything by hand or fighting a generic importer that silently drops rows it doesn't understand and leaves you reconciling the mess afterward.
How AccountDesq solves it
Each entity - customers, vendors, items, invoices, bills - gets its own import with column mapping and a review step before anything commits. Invoices and bills specifically validate against existing customer/vendor records and commit all-or-nothing: either the whole batch imports cleanly or none of it does, never a partial import that needs untangling. Bank statement import is its own path, supporting the common statement formats (CSV, Excel, MT940, BAI2, OFX/QFX, camt.053) so reconciliation can start from a real file instead of manual entry.
How it works, step by step
Pick what you're importing
Customers, vendors, items, invoices, bills, or a bank statement - each has its own dedicated import.
Upload and map columns
Bring in a CSV (or a statement file for banking) and map its columns to AccountDesq's fields.
Review before committing
See what will actually be created before anything is saved.
Import - all or nothing
Invoices and bills commit as a whole batch or not at all, so a bad row can't leave a half-finished import behind.
Connected to the rest of AccountDesq
Nothing here works in isolation - it posts through the same ledger as everything else.
In practice
A business switching from spreadsheets brings in its existing customer and vendor lists as CSVs first, then imports a backlog of unpaid invoices in one validated batch instead of re-keying each one - the whole batch either imports cleanly against the customers just brought in, or nothing does, so there's no partial mess to clean up afterward.
What this means for your business
- A real migration path from spreadsheets or another system, not a re-typing exercise.
- All-or-nothing commits on invoices and bills mean a bad row can't leave a half-imported batch to untangle later.
- Bank statement import supports the file formats banks actually export, not just a generic CSV.
Frequently asked questions
What happens if some rows in an invoice import are invalid?
Invoice and bill imports are all-or-nothing on commit - if the batch has a problem, nothing imports rather than importing the valid rows and leaving the rest to sort out manually.
What bank statement formats does AccountDesq support?
CSV, Excel, MT940, BAI2, OFX/QFX, and camt.053.
Is there a separate export tool?
No - exports are inline on each report and list page rather than centralized in one place; the Import / Export Center is specifically for bringing data in.