Import lets you preload Books with the past activity from another bookkeeping system. You can run it during onboarding (from the wizard’s Import history step) or anytime later from Books → Imports.
Supported source files
| System | Report | How to export |
|---|---|---|
| myPTez | Transaction Detail Report | Reports → Category/Transaction Reports → Transaction Detail Report. Pick the date range, choose Excel as the format, and download. |
| Membership Toolkit | General Ledger Detail | Accounting → Reports → General Ledger Detail. Pick the accounts and date range you want, click Refresh, then Download as Excel. |
| Any other system | Generic CSV (Volo Cash template) | See Import and export with CSV for the template + column reference. Export your data from your current system into the template’s column layout, save as CSV, and upload. |
Picking the wrong report is the most common cause of failed imports. Each system has many reports — only the ones listed above are accepted.
What happens after upload
The wizard walks you through four steps before anything is written to your books:
- Accounts. Every bank/cash account we found in your file shows up here. Merge it with one of your existing accounts, create it fresh, archive it (for old accounts that aren’t in use anymore), or ignore it (drops every transaction touching that account).
- Categories. Same idea for budget categories. You can merge with an existing budget item, create a new one, or skip the category (drops its transactions).
- Matches. If any imported transactions look like they’re the same as expenses already in your books (matching check numbers, amounts, dates, payees), we surface them here so you can confirm before the import re-creates them.
- Summary. A preview of what will be created, with the chance to roll back to any prior step.
Nothing lands in the books until you confirm on the summary step. If you change your mind later, you can roll back an import from the same page — every entry it created gets removed, and any silent corrections to existing accounts get undone.
Common problems
“We couldn’t read that file.” Usually means the source picker is set to the wrong system, or the file isn’t the right report. Double-check the table above and try again.
Some rows are missing. The committed view lists any rows we couldn’t bring in. Click Download CSV to see all of them with the reason. The most common skip reasons are:
- No allocations. A bank row with no category breakdown that isn’t a transfer.
- Skipped category. The row’s category was set to Skip on the categories step.
- Unbalanced. The postings on a journal entry didn’t sum to zero — usually a sign of an export edge case. Enter these manually from Books → New entry.
Default account got merged. During onboarding, the most-active imported account is proposed as a merge into your default Checking. You can change this on the Accounts step.
Source not listed?
If your organization uses a different bookkeeping system, email us at contact@volocash.com — tell us what system and we’ll work with you to add support.