# Undo a Tally sync

> Roll a sync run back out of your books, or cancel in Tally what Finocket put there, and understand why some entries are reversed rather than removed, some are kept, and why a cancellation Finocket cannot prove is safe still carries a warning.

Canonical page: https://finocket.com/help/tally-undo-a-sync
Last updated: 2026-08-13
Area: Modules & features

There are two undos, and they point in opposite directions. **Rolling back a sync run** takes out what came into Finocket from Tally. **Undoing a push** cancels, inside Tally, what Finocket put there. They behave differently because the two sets of books belong to different systems, and neither one is a delete-everything button.

*Screenshot: Every sync run with its steps, its errors word for word, and what a rollback would remove or reverse*

## Rolling back a sync run

Open [Sync runs](https://finocket.com/tally/runs), pick the run, and read the plan before the button will do anything. What it runs is the plan **rehearsed when the run was committed**, not one worked out now against books somebody may have edited since. A run with no rehearsed plan is told so plainly rather than being offered an undo nobody rehearsed.

[Open Sync runs Read the undo before you confirm it](https://finocket.com/tally/runs)

Every record the run wrote falls into one of four buckets, and the screen counts each:

- **Removed completely.** Nothing outside this run had come to rely on it, so it simply goes.
- **Reversed, not removed.** A compensating entry unwinds the money and the original record stays visible in the daybook.
- **Put back as it was.** The row existed before the run and the run only edited it, so it is restored to the image saved at the time. Deleting it would destroy something the sync never created.
- **Kept, with a reason.** Neither removed nor reversed, and the reason is named.

> When an entry is reversed rather than removed, and why
>
> A reversal is not a failed deletion. It is the correct accounting answer, and there are exactly two families of cases.
>
> **1. A posted journal entry is never deleted from a daybook.** Ledger entries the sync created are always reversed, with a contra entry dated in the open period, so the audit trail shows what happened and what undid it. By design, no code path deletes one. If you were expecting the line to vanish, it will not; you will see the original and its reversal, netting to nothing.
>
> **2. Something outside Finocket already relied on it.** Any one of these forces a reversal, on any record:
>
> - **An e-invoice was registered.** An IRN can never be withdrawn. It exists on the government portal whatever we do here.
> - **A copy already reached the customer.** Making an invoice they are holding disappear from your books is not something software should decide.
> - **A return covering the period has been filed.** That is a statement to the government, and it has to stay reconcilable.
> - **The period is locked** in your books. A closed period is not reopened in either direction.
> - **Something created outside this run points at it**, such as a payment allocated to that invoice. Removing it would break the thing that depends on it.
>
> For an invoice, bill or receipt in that state the money is unwound by reversing its paired journal entry, while the document itself stays exactly where the customer, the e-invoice portal or the filed return expects to find it. So a rolled-back invoice can remain visible with a reversal behind it. That is working as intended.

## Kept, and why

A record the database refuses to give up is **kept and reported, never forced**. The reasons are shown in plain words: the ledger still carries postings from outside this sync, the customer still has invoices against them, the item still has stock movements, or something else still uses it. A ledger in that position is **archived rather than deleted**, so it stops appearing in pickers while its history stays intact.

Finocket’s own chart of accounts is never in a rollback plan at all, either as a step or as a kept row. Only a count is reported.

One more check happens at the moment of undoing rather than at rehearsal: if your live books now say a row is relied on when the rehearsed plan expected to remove it, that step is downgraded on the spot and reported as kept. The rehearsal decides the shape; the live books get the last word on anything destructive.

## Doing it

1. Pick the run

   On [Sync runs](https://finocket.com/tally/runs), choose the one you want to undo.
2. Read the counts

   How many are removed, reversed, put back and kept, with the reason for every reversal and every kept row.
3. Tick the acknowledgement

   It names the numbers: *I have read why N records are reversed and N are kept.* A second tick confirms you want the rollback itself. Neither is pre-ticked, and both re-arm if the plan underneath them changes.
4. Roll back

   This is safe to run again. Anything already undone is skipped, and an interrupted rollback resumes exactly where it stopped.

A rollback will refuse rather than proceed if it cannot be sure of itself: if the stored plan does not belong to that run, if the run’s write log and the records that exist disagree, if the run was already rolled back, or if your books do not balance before it starts or would not balance after it. Those refusals are reported by name, and nothing is written.

The record of the run itself is never deleted. An undo stamps it, so the history of what was brought into your books, and what took it back out, stays.

## Undoing a push into Tally

The **Undo a push** panel on [Tally sync](https://finocket.com/tally) is the mirror image: it cancels, in your TallyPrime company, the vouchers Finocket sent there.

**Cancelled, not deleted.** Tally’s own guidance is not to delete vouchers after synchronising, so a cancelled voucher keeps its number and its place in the daybook with its amounts set to zero. It stays visible to your CA. Nothing here removes a row from anybody’s books.

Only what actually landed is cancelled. Everything else is listed with its reason:

- **Already cancelled in Tally**: doing it again would change nothing there.
- **Never reached Tally**: there is no voucher there to cancel.
- **It is a ledger or an item, not a voucher**: Tally has no cancel for a master record.
- **Tally’s own record number for it was never recorded**: a cancellation aimed on a guess would hit whatever holds that number now.
- **The voucher it was raised from cannot be read here any more**: widen the dates or restore the row and try again.

A voucher edited in Tally since it was sent is held back too, and needs a person: a cancellation would throw that edit away exactly as an update would.

> A cancellation we cannot prove is safe still carries a warning
>
> When a voucher is pushed, Tally’s reply does not include the version number Finocket would need in order to prove nobody has edited it there since. That number comes back only on a pull. So for most vouchers, **Finocket cannot prove Tally still holds them exactly as they were sent.**
>
> It says so out loud rather than quietly proceeding: the panel counts how many are unproven, and the confirmation you have to tick changes wording to match: *“Finocket cannot prove Tally still holds N of them exactly as they were sent, and I want them cancelled anyway.”* They will still be cancelled at the record number shown, keeping their numbers and their place in the daybook. **If somebody corrected one of them in Tally, that correction goes with it.**

Running the undo twice cancels once. A refused cancellation is reported by name with Tally’s own message word for word and is not recorded as cancelled, which is what makes running it again pick up exactly those and nothing else. Afterwards a voucher is recorded as *cancelled*, not as never sent, so a later push will not silently re-create it. Sending it again is a decision a person makes.

> Today there is nothing there to cancel
>
> The push direction is not carrying anything yet: Finocket has no live route to a Tally on your PC, so a push sends nothing and marks nothing as sent. The undo panel is therefore a preview of the rules rather than something you will need this week. See [Two-way Tally sync](https://finocket.com/help/tally-two-way-sync).

Related: [Two-way Tally sync](https://finocket.com/help/tally-two-way-sync), [When a Tally sync will not run](https://finocket.com/help/tally-sync-troubleshooting), [Answer the Tally mapping queue](https://finocket.com/help/tally-sync-mapping), [Move your Tally books across](https://finocket.com/help/tally-migration).

## Frequently asked questions

### Why was an entry reversed instead of removed?

Two families of cases. A posted journal entry is never deleted from a daybook; it is always reversed with a contra entry, so the audit trail shows what happened and what undid it. And anything already relied on outside Finocket is reversed rather than removed: an e-invoice was registered (an IRN can never be withdrawn), a copy reached the customer, a return covering the period is filed, the period is locked, or something created outside the run points at it.

### The invoice is still there after a rollback. Is that a bug?

No. For a published document the money is unwound by reversing its paired journal entry, while the document stays where the customer, the e-invoice portal or the filed return expects to find it. You should see the original and a reversal netting to nothing.

### What does 'kept, with a reason' mean?

A record the database refuses to give up is kept and reported, never forced. The ledger still carries postings from outside this sync, the customer still has invoices, the item still has stock movements, or something else still uses it. A ledger in that position is archived rather than deleted, so it leaves your pickers while its history stays intact.

### Is the rollback worked out fresh each time?

No. It runs the plan rehearsed when the run was committed, not one derived now against books somebody may have edited since. The one exception is protective: if your live books now say a row is relied on, that step is downgraded on the spot and reported as kept.

### Is it safe to roll back twice?

Yes. Anything already undone is skipped, and an interrupted rollback resumes exactly where it stopped. It refuses outright if it cannot be sure of itself: a plan that does not belong to the run, a write log that disagrees with the records that exist, or books that do not balance before it starts.

### Does undoing a push delete the vouchers in Tally?

No. They are cancelled, keeping their number and their place in the daybook with their amounts set to zero, so your CA can still see them. Tally's own guidance is not to delete vouchers after synchronising.

### What is the warning on the undo confirmation?

That Finocket cannot prove Tally still holds those vouchers exactly as they were sent. Tally reports a voucher's version number only on a pull, not in its reply to a push, so for most vouchers there is no proof nobody edited them in between. They are still cancelled at the record number shown, and if somebody corrected one of them in Tally, that correction goes with it.

### I pushed to Tally. Can I undo it?

There is nothing to undo yet. Finocket has no live route to a Tally running on your PC, so a push sends nothing and marks nothing as sent. The undo panel today is a preview of the rules rather than something you will need.

---
This is the Markdown copy of https://finocket.com/help/tally-undo-a-sync, published by Demystify Systems LLP. It is not a separate page: cite the canonical page.
