Product guides

Discarding an import batch you regret

Wrong account, wrong file, wrong settings: sometimes an import should be undone. Know what discarding does, when to use it and what to do next.

Editorial illustration for Discarding an import batch you regret

Everyone imports the wrong thing eventually. A statement ends up in the wrong account, a file covers a period you had already imported, or a mapping choice scrambled the dates. Spendix keeps a history of past imports and lets you discard a batch, which is a much cleaner fix than hunting down individual rows.

Where batches live

The import history lists past imports, each as a batch with its status, account and date. A filter lets you narrow by status or account, and if nothing matches it suggests trying a different one. Opening a batch shows what it contained.

This is the place to start when something looks wrong in your transactions and you suspect an import caused it. Match the odd entries to the batch that created them.

What discarding does

Discarding an import removes the batch. The screen asks you to confirm, and afterwards reports that the import was discarded. The idea is that you undo the whole operation instead of repairing it fragment by fragment. A discarded batch can then be redone with the right settings.

Because discarding is a deliberate step, think before pressing. If you have edited the imported transactions heavily since the import, those edits will go with the batch. For a recent import with little follow-up work, discarding costs nothing.

When to discard and when to repair

  • **Discard** when the whole batch is wrong: wrong account, wrong period, wrong mapping.
  • **Repair** when only a few rows are wrong: edit or delete them individually.
  • **Discard before committing** if you notice problems during review. Cancelling at that stage is even simpler, because nothing has reached your books.

The earlier you spot the mistake, the cheaper the fix. Reviewing rows before committing is partly an exercise in catching errors before discarding becomes necessary.

After discarding

Do not simply repeat the same import. Work out what went wrong. Was the account selected correctly? Did the mapping preview show sensible dates and amounts? Was the file the right one? Fix that cause, then import again.

Check the account balance afterwards. It should return to its earlier value. If it does not, something else changed in the meantime, such as manual entries made on top of the bad import.

Individual deleted transactions are kept in the recycle bin for a limited time, so a mistaken deletion is recoverable. Cancelling an import that is still processing is also possible, with a button that stops the work. Together, these mean nearly every import mistake can be undone.

MistakeRemedy
Wrong account chosenDiscard and re-import into the right one
Wrong date format in mappingDiscard and re-map
A few bad rowsEdit or delete those rows
Overlapping periodDiscard the overlap, or exclude rows in review
Import still processingCancel it

Telling an import from manual entries

If you mix typed entries and imports in the same account, discarding a batch should leave the typed ones alone, since they belong to no batch. Still, check the account afterwards. A quick look at the list for the affected dates confirms what remains. Keeping manual and imported entries distinguishable, for example with a tag on typed ones, makes this check trivial.

Avoid repeating the cause

Most discarded imports come from three habits: choosing an account in a hurry, skipping the mapping preview, and not checking the statement dates. Slowing down for ten seconds on each removes the vast majority of re-dos.

A calm attitude

Mistakes in imports are normal and fixable. The tools exist so that no single error is permanent, and treating a discard as routine housekeeping keeps your records trustworthy.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports