# Starting Over in Digits: Removing Transactions, Connections, and Client Data

Sometimes a client’s setup needs a reset—the wrong bank was connected, personal accounts were included, or the books were started incorrectly.

This article explains **what you can and can’t delete in Digits**, and the **cleanest ways to start fresh** without breaking the audit trail or creating more cleanup later.

***

### Deleting or Removing Specific Transactions

<details>

<summary> Which Transactions Can be Deleted (and Which Can't)</summary>

| You Can Delete                                                                           | You Can't Delete                                                                                                                |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| :white\_check\_mark: Manually entered transactions                                       | :no\_entry\_sign: Single or Bulk transactions from connected banks or cards, or other integrations (Plaid, Stripe, Gusto, etc.) |
| :white\_check\_mark: Entire bank connections (and all transactions from that connection) |                                                                                                                                 |
| :white\_check\_mark: Transactions imported via bank statement or CSV                     |                                                                                                                                 |

**What to Do Instead (When Deletion Isn’t Available)**

If something can’t be deleted, you still have safe options:

* **Re-categorize** the transaction
* **Reverse** it to preserve the audit trail
* **Exclude** it from reports (when appropriate)
* **Remove the entire bank connection** (if the wrong account was connected)

</details>

<details>

<summary>Can I delete all transactions at once?</summary>

Not with a single click.

To remove *all imported transactions*, [delete the related bank connection](https://help.digits.com/firms-connections/manage-connections). Manual transactions must be deleted individually or in bulk. See: [Editing Transactions](https://app.gitbook.com/s/uIztBwoMl2RW5oGzS0cZ/editing-transactions "mention")

</details>

<details>

<summary>Why can’t I delete bank transactions individually?</summary>

Because Digits maintains an audit trail, bank-connected data must remain traceable to the source, even if reclassified or reversed.

</details>

<details>

<summary>Removing a Bank Connection (and All Its Transactions)</summary>

If the wrong bank account was connected, the fastest way to clean things up is to delete the connection.

See [manage-connections](https://help.digits.com/firms-connections/manage-connections "mention")for complete details.

{% hint style="warning" %}
Deleting a connection permanently removes *all transactions imported from that account* and impacts balances, reports, and reconciliations.
{% endhint %}

</details>

### Changing/Editing the Cutover Date

<details>

<summary>Understanding Cutover Dates in Digits</summary>

Digits uses two different cutover dates, depending on how data enters the system. Knowing which one applies will help you avoid surprises when starting over or reconnecting data.<br>

**1. Top-Level Cutover Date (QuickBooks Only)**\
If you migrate from QuickBooks Online (QBO), Digits sets a top-level cutover date during the initial migration.

* This date determines the earliest data Digits will pull from QuickBooks
* It applies across the entire company
* It cannot be changed after setup

See: [QuickBooks Cutover Date](https://app.gitbook.com/s/ZJRjnc8NFWHCOqIwdbuI/firms-quickbook-cutover-date "mention")

**2. Connection-Level Cutover Dates (Banks, Cards, Payroll, etc.)**\
Each individual connection (banks, credit cards, payroll, Stripe, Gusto, etc.) also has its own cutover date.<br>

* These cutover dates can be adjusted; however, a connection-level cutover date can never come before the top-level QBO cutover date. If you try, Digits will still respect the top-level QBO date.
* They control how far back Digits pulls data for that specific connection
* You can move them forward or backward as needed

{% hint style="info" %}
**A connection-level cutover date can never come before the top-level QBO cutover date.**\
If you try, Digits will still respect the top-level QBO date.
{% endhint %}

</details>

<details>

<summary>How do I reset the cutover date for an integration other than QuickBooks? </summary>

If your cutover date is for a bank, card, or integration

You **can change it**.

* Each connection (bank, credit card, payroll, Stripe, Gusto, etc.) has its own cutover date
* These can be adjusted at any time
* However, they **cannot go earlier than a QuickBooks cutover**, if one exists

How to change it:

1. Go to **Connections**
2. Click **Manage** next to the connection
3. Update the **Cutover Date**
4. Save changes

***

**Other Alternatives:**

If the cutover date you chose isn’t going to work, you have two options:

* **If you’re still early in setup,** you can delete the connection, which removes all the transactions, and reconnect it. See [manage-connections](https://help.digits.com/firms-connections/manage-connections "mention")
* **If you’re already live:** You can adjust balances or activity using **journal entries** to account for anything that needs to be corrected after the cutover. See: [Journal Entries in Digits](https://app.gitbook.com/s/C8lA0vSyGH87vzqfraRC/journal-entries "mention")

</details>

<details>

<summary>Changing the Cutover Date on QuickBooks</summary>

Once the cutover date is set, it cannot be changed.&#x20;

</details>

<details>

<summary>Can I set a future cutover date for QuickBooks?</summary>

No — the cutover date can’t be set in the future.

The cutover date marks the point when Digits becomes the system of record and begins using real accounting data. As a result, the cutover date must be today or a date in the past.

</details>

### &#x20;Business & Personal Accounts

<details>

<summary>How do I remove or separate personal transactions from business transactions? </summary>

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)](https://app.gitbook.com/s/uIztBwoMl2RW5oGzS0cZ/category-manager "mention")
* 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:**&#x20;

[linking-specific-chase-accounts](https://help.digits.com/firms-connections/linking-specific-chase-accounts "mention")

[wells-fargo-remove-transactions](https://help.digits.com/firms-connections/wells-fargo-remove-transactions "mention")

</details>

### Starting Over

<details>

<summary>How do I delete everything in Digits and start over? </summary>

There’s no global reset, but you still have two options:

<mark style="color:red;">**Option 1:**</mark> Remove a Connection (and all its transactions)

See [manage-connections](https://help.digits.com/firms-connections/manage-connections "mention")for complete details.

{% hint style="warning" %}
Deleting a connection permanently removes *all transactions imported from that account* and impacts balances, reports, and reconciliations.
{% endhint %}

***

<mark style="color:red;">**Option 2:**</mark> Delete and Readd the Client

Deleting the client and re-adding them will give you a new slate. See: [Adding/Removing Clients](https://app.gitbook.com/s/vSRL2TlhlioIo7LGLhmQ/adding-removing-clients "mention")

This is a good fit if:

* You need to change the QuickBooks cutover date
* Personal and business transactions are mixed
* You want to restart from scratch early on

This creates a clean setup without risking duplicated or misaligned data.

</details>

<details>

<summary>Can I reset my client's ledger and start over? </summary>

There’s no global reset, but you still have two options:

<mark style="color:red;">**Option 1:**</mark> Remove a Connection (and all its transactions)

See [manage-connections](https://help.digits.com/firms-connections/manage-connections "mention")for complete details.

{% hint style="warning" %}
Deleting a connection permanently removes *all transactions imported from that account* and impacts balances, reports, and reconciliations.
{% endhint %}

***

<mark style="color:red;">**Option 2:**</mark> Delete and Readd the Client

Deleting the client and re-adding them will give you a new slate. See: [Adding/Removing Clients](https://app.gitbook.com/s/vSRL2TlhlioIo7LGLhmQ/adding-removing-clients "mention")

This is a good fit if:

* You need to change the QuickBooks cutover date
* Personal and business transactions are mixed
* You want to restart from scratch early on

This creates a clean setup without risking duplicated or misaligned data.

</details>

***

{% columns %}
{% column width="66.66666666666666%" valign="middle" %}
Got a question or feedback? Our team is all ears—come say hello!
{% endcolumn %}

{% column width="33.33333333333334%" valign="middle" %}

<p align="center"><a href="https://app.gitbook.com/s/x8QKZsFt122QPdcslRDC/contact-us" class="button primary" data-icon="envelope-open-text">Contact Digits Support</a></p>
{% endcolumn %}
{% endcolumns %}

***
