Skip to main content

Edit & Duplicate Posted Transactions

Make changes to posted transactions, or reuse them as a starting point — manually or with AI

Overview

(This feature is only available for QuickBooks-connected clients.)

You no longer have to rebuild a transaction from scratch when you need to fix a mistake or create something similar. From any posted transaction, you can now:

  • Edit the transaction in place, with all of its existing data already filled in.

  • Duplicate the transaction into a new draft you can adapt for a similar scenario.

In both cases you can make changes manually or use AI Composer to update fields and adjust line items for you — so recurring and repetitive entries take a fraction of the time.

Editing a posted transaction

Choose Edit when you want to correct or update an existing transaction.

The transaction opens pre-populated with its existing data, so you're never starting over. From there you can:

  • Edit manually — change fields and line items directly, just as you would on any transaction.

  • Use AI Composer — describe the change in plain language and let AI update the fields and adjust the line items for you.

This is ideal for quick corrections and adjustments where you want to keep the original transaction and simply bring it up to date.

Duplicating a posted transaction

Choose Duplicate when you want to reuse a transaction as the starting point for a new one.

The system opens a draft copy of the transaction, so you can build on prior work instead of recreating it. This is especially useful for:

  • Similar one-off transactions that share most of the same details

  • Recurring workflows you run on a regular cadence

Once you have the draft, you can adapt it manually or with AI Composer, then post it as a new transaction.

Example: a recurring payroll journal entry

A common use case is a payroll journal entry. Starting from an existing entry, you can duplicate it and then ask AI Composer to do the heavy lifting — for example, allocating salaries by department into the appropriate classes and changing the date.

Because this kind of entry comes up every pay period, you can save it as a skill so it's ready to run again next time. (See Ask Double for more on creating and managing skills.)

Guardrails

To protect the integrity of your books, a few changes are intentionally restricted:

  • Transaction type can't be changed. When editing or duplicating, the transaction stays the same type — you can't convert one type of transaction into another.

  • The total amount is locked for most entries. For all transaction types except journal entries, you can reallocate and adjust line items, but you can't change the overall total amount.

These guardrails apply whether you're making changes manually or through AI Composer, so you can move quickly without accidentally changing reconciled transaction.

Did this answer your question?