Cleanups
Double is an effective tool for cleanups, but there are a few important considerations to ensure maximum value during cleanup and catch-up work. One key concept is how transaction data is fetched.
What to know about transaction data in Double
For performance reasons, Double pulls the last 12 months of transaction data for a given close period.
For example, in a client’s September 2025 close, transaction data is pulled from October 2024 through September 2025.
Current year cleanups
We recommend opening a close period for the latest month, then working from there.
More on starting & accessing closes 👉 here!
All transaction review reports can be run on a YTD filter.
Past year cleanups
For multi-year cleanups, we recommend creating a single December close for each year you are working on.
For example, when performing a cleanup for 2023–2024, the following is recommended:
A December 2023 close (shows all transactions Jan '23 - Dec '23)
A December 2024 close (shows all transactions Jan '24 - Dec '24)
The latest close in the current year (shows all of 2025 so far)
Read more on how to start and navigate to closes for prior periods here:
Cleanups for tax returns
When reviewing a client’s books for a tax return, it is recommended to create a close for December of that year.
Best Practices
Cleanups: Connecting a new file to an unconnected client
❗ If there is an unconnected client that WILL need a QuickBooks or Xero integration soon, prior-year closes should not be added until the integration is finalized. ❗
Here's why
When an Unconnected Client is added, no file review tasks exist because there is no connected file to review.
Once the client is connected, file review tasks are automatically added to the latest close.
When an older close is created in Double, tasks from the latest close are copied to that older close.
If an older close is created before the client is connected, it will not include any review tasks, and connecting the file later will not retroactively add them.
Asking questions in the Client Portal
One additional point to note is that the client portal is not segmented by close period.
When a question is asked from any close:
All questions appear in a single location in the client portal.
Based on the transaction date, it may be necessary to navigate to a close period that includes access to the relevant transaction data in order to code the transaction.
For example, to view a client’s response to a coding question related to a 2023 transaction, navigation to the December 2023 close is required.
If an open question exists on a transaction that is only visible in a prior close, the question will display an Old Close tag. 👇
