Delete or Remove Transactions in Digits
Delete or remove transactions to fix mistakes or clean up imported data from connected accounts.
Delete or Remove transactions in Digits
In Digits, not all transactions can be deleted individually. How you remove or adjust transactions depends on how they were created.
✅ Manually entered transactions
✅ Transactions imported via bank statement or CSV
✅ Entire connections (which removes all transactions from that connection)
🚫 Individual or bulk transactions from connected banks, cards, or other integrations (Plaid, Stripe, Gusto, etc.)
What to Do Instead (When Deletion Isn’t Available)
If a transaction can’t be deleted, you still have safe options:
Re-categorize the transaction
Reverse it to preserve the audit trail
Remove the connection or account
Remove Transactions Before a Certain Date
You can’t delete transactions before a specific date in bulk, unless they were created manually or uploaded from a CSV.
To remove transactions from a connected account, you can:
Adjust the connection start date to limit how much history is imported (recommended). See: Change the Start Date for a Connection
Delete and reconnect the account or connection with a new start date. See: Archive and Delete a Connection
Remove Transactions by Deleting a Connection or Account
To remove all transactions from a bank, card, or other account, archive and delete the connection.
Deleting a connection permanently removes all transactions imported from that account and will impact balances, reports, and reconciliations.
See: Archive and Delete a Connection
For bank and card connections, you can delete a single account within a connection to remove only that account’s transactions. Other connections (such as Ramp, Stripe, or payroll providers) must be deleted entirely.
Frequently Asked Questions
Can I delete all transactions at once?
Yes and no.
To remove all imported transactions, delete the related bank connection.
Manual transactions must be deleted individually or in bulk. See Editing Transactions
Why can’t I delete bank transactions individually?
Digits maintains transaction history; bank-connected data must remain traceable to the source, even if reclassified or reversed.
Should I just start over?
Starting over is a full reset and is not required for most cleanup tasks.
Only use it if you need to redo your entire setup, such as correcting a QuickBooks cutover date.
How do I remove or separate personal transactions from business transactions?
The right approach depends on where the personal transactions are coming from. Follow the path below that matches your situation.
Scenario 1: Personal and business transactions are mixed in the same bank account
If your client uses one account for both personal and business spending:
You cannot delete just the personal transactions.
Bank-connected transactions are part of the audit trail and will re-sync.
What you should do instead
Create a Personal Expenses category (or similar). See: Category Manager (Chart of Accounts)
Re-categorize personal transactions into that category.
Exclude that category from business reports, if needed.
Scenario 2: Personal and business accounts were shared under one bank login
Many banks (like Chase) allow multiple accounts under one login. If all were shared during connection, Digits will import all of them—personal included.
Step 1: Confirm what accounts were shared
Check whether both personal and business accounts were selected during the bank connection.
If yes, Digits is behaving correctly by importing them.
Step 2: Update account sharing at the bank
Some banks require changes on their own website (not in Digits).
Log in to your client's bank directly(or have them log in)
Update third-party access (via Plaid)
Deselect personal accounts
Save changes
Step 3: Remove/Re-add the connection
Deletes all transactions imported from that account
Reconnect the bank
Only business transactions will sync back in
Related:
Linking Only Business Accounts with Chase on Digits
Wells Fargo: Remove Unwanted Accounts and Their Transactions
Got a question or feedback? Our team is all ears—come say hello!
