Importing Transactions
Manually import bank transactions into Digits using a CSV file. Upload, map, and categorize the data with ease, keeping your Ledger complete even when a direct connection is not available.
Note: To trigger categorization, transactions must be added to the Ledger (for example, by importing a bank statement). Uploading files to Vault or Reconciliations does not categorize them. See How AI Works in Digitsfor more information.
Import Transactions from Bank Statements
Go to Accounting → Ledger.
Click the dropdown next to + Add Transaction → Import Bank Transactions.
Browse to select a file, or drag and drop a bank statement (PDF, PNG, JPG, and JPEG).
Click Import Statement.
✨ Once uploaded, transactions are automatically categorized and assigned to the correct parties.
Check images in imported statements are automatically extracted to Vault and matched to Ledger transactions when possible. Unmatched ones stay in the Vault for manual linking.
How to Import Transactions via CSV
Download a CSV file from your client’s bank or provider.
Go to Accounting → Ledger.
Click the dropdown next to + Add Transaction → Import Bank Transactions.
Download the CSV import template in the pop-up window.
Fill in the template with the transaction information.
Upload the completed file and map each column to the correct Digits fields.
For bank transactions, select the appropriate Bank or Credit Card category.
Click Next to review and complete the import.
✨ Once uploaded, transactions are automatically categorized and assigned to the correct parties.
Important Notes About Imports:
Account visibility: Don’t see an account? Make sure it’s set as a Bank or Credit Card subtype in Category Manager — that’s how Digits identifies eligible accounts.
Multi-account statements: If a bank statement includes more than one account, Digits detects them during import and lets you choose which account(s) to bring into the Ledger.
Journal Entries: Need to import journal entries instead? See Journal Entries in Digits.
Processing Time: Imports typically finish within 1–10 minutes, depending on file size. If processing takes longer than 30 minutes, contact Digits Support.
Editing & Deleting: Imported transactions can be fully edited or deleted as needed.
Cutover Dates: If your client migrated from QuickBooks Online (QBO), CSV imports are only allowed after the cutover date. Transactions before that date are managed by the QBO sync.
Frequently Asked Questions
Do I need a CSV import if my client uses a major bank?
Usually not. If your client’s bank connects through Plaid, transactions sync automatically. But CSV imports are still useful for historical data or unsupported accounts.
How can I export transactions from my client’s bank?
If you need to download a CSV file manually, check the bank’s export options. Here are direct guides for popular institutions:
For other banks, search your client’s online banking portal for “Export CSV” or “Download Transactions.”
What types of data can I import with CSV?
You can import transaction data, including date, amount, description, and party. Balances and statements are managed automatically by connected banks.
Why is my CSV import not showing up?
Ensure your CSV matches the template format exactly. Missing headers, blank rows, or incorrect account subtypes may cause the import to fail.
How long does it take to process an import?
Usually within 1–10 minutes, depending on file size. Larger imports may take longer.
Why aren't my transactions showing up after I uploaded a bank statement?
If you uploaded your file to Vault, it was saved for reference only. Vault does not import transactions into the Ledger.
To import transactions, go to Accounting → Ledger, then open the dropdown next to Add Transaction. From there, drag and drop your statement or upload a CSV file.
Should I import a statement if the account is already connected?
Generally, no. If an account is connected and transactions are already flowing into Digits, importing the same statement can create duplicates or confusing matching/unmatching.
Only import a statement when you’re:
filling missing history (the connection didn’t pull far enough back)
validating a period during reconciliation
working with an account that can’t connect reliably (common with certain banks or card programs)
This scenario often comes up with:
bank connections via Plaid (Chase, Wells Fargo, credit unions)
processor statements for PayPal, Square, Stripe
card programs where statements are available, but the feed is incomplete
Is there a file size or row limit for CSV imports?
No. Bank transaction CSV files of any size are supported — there's no need to split large files before uploading. Larger files may simply take a bit longer to process.
Got a question or feedback? Our team is all ears—come say hello!