Skip to main content

What Happens When You Change an Extraction Type After Syncing to Your Accounting Software

Learn what happens when you change an extraction type after a document has already been synced, and what actions you may need to take.

Written by Jess B
Updated over a week ago

Note: This article applies to supported accounting software integrations such as Xero and QuickBooks Online.

What happens when you change the extraction type?

When you change the extraction type of a synced document:

  • Tofu creates a new transaction for the new type

  • Tofu will attempt to delete or void the old transaction.

Important: Changing the extraction type creates a new transaction. It does not update the original one.

Example

If a document was originally synced as an AP Bill but should actually be an AR Invoice:

  • Tofu creates a new AR Invoice

  • The old AP Bill is not converted

  • Tofu tries to clean up the old AP Bill

  • If it cannot be cleaned up automatically (with auto-publish off), you will need to manually sync deletion in your accounting software

The same logic applies when switching between:

  • AP Bill

  • AR Invoice

  • Direct Expense


How to find extractions that need manual cleanup

You can identify extractions that need manual cleanup in two ways:

1. Look for the status label

Extractions that require action will show a Manual cleanup label in the Extractions panel.

2. Use the filter

To quickly find all affected extractions:

  1. Open the Filter menu in the Extractions panel

  2. Go to Extraction status

  3. Select Manual cleanup


What does “Manual cleanup” mean?

You’ll see a Manual cleanup label or banner when the original transaction still needs attention.

This means:

  • The transaction still exists in your accounting software

  • Tofu could not remove it automatically

This can happen when:

  • The transaction cannot be changed in your accounting software

  • You deleted the extraction while auto-publish is off, so the transaction remains in your accounting software

You may see a message like:

Why cleanup might fail

Sometimes your accounting software won’t allow changes.

This usually happens when the transaction is:

  • Already paid

  • Has payments or credit notes applied

  • Reconciled or locked

When this happens, the transaction must be fixed manually in your accounting software.


What should you do after switching?

After changing the extraction type:

  1. Click Sync

  2. Tofu will try to delete or void the original transaction

  3. If it can’t be removed, delete or update it directly in your accounting software

  4. Once done, click Mark as resolved in Tofu


What happens when you click Sync?

Clicking Sync will attempt to delete or void the transaction in your accounting software.

However, what happens next depends on the transaction’s state:

  • If the transaction can still be changed
    Clicking Sync will successfully delete or void it in your accounting software, even if auto-publish is turned off

  • If the transaction cannot be changed (for example, it has payments or credit notes allocated, is reconciled, or locked). The cleanup will fail, and you may see an error such as:

    • “Bad Request: You cannot delete invoice. Manual cleanup action is required”

    • or “Validation error: The status ‘voided’ cannot be applied because payments or credit notes are allocated”

In these cases, you will need to delete or adjust the transaction directly in your accounting software. Once done, you can mark it as resolved in Tofu.


What happens when you click “Mark as resolved”?

Clicking Mark as resolved will remove the banner and delete the extraction in Tofu.

However, this does not guarantee that the transaction has been deleted or updated in your accounting software.

Make sure the cleanup has been completed before marking it as resolved.


Key takeaway

  • Changing the extraction type creates a new transaction but does not remove the original one.

  • Always check if the original transaction still exists in your accounting software and remove it if needed to avoid duplicates.

Did this answer your question?