Deleted the Wrong Transaction? Now You Can Restore It

TamilAccounting now lets you delete a posted transaction into a restorable state and bring it back fully posted — ledger, stock, document chain and cash payment included. A safety net for everyday mistakes.

VVaradharaj V
Varadharaj V
Jul 10, 2026 · 4 min read
Deleted the Wrong Transaction? Now You Can Restore It

Everyone removes the wrong thing occasionally — a “duplicate” invoice that wasn’t a duplicate, a delivery voided before you noticed the payment attached to it, a journal cleared in the wrong month. Until now, voiding a posted transaction in TamilAccounting was final: the document was gone, and rebuilding it — every line, the customer’s payment, the stock movement, the order-and-delivery chain — was a manual chore. TamilAccounting now gives your important transactions a safety net. Deleting moves a document into a restorable Deleted state instead of destroying it, and you can bring it back — fully posted — in two clicks.

Delete without the fear

When you delete a posted transaction, it leaves your ledgers, reports and registers immediately, exactly as a void would — so your accounts stay correct and your totals are right. The difference is that the document is not thrown away. It is set aside in a Deleted state, tagged with who removed it and when, ready to be restored.

You choose this at the moment of deletion. On a transaction’s view, the Void action now offers a Restorable option for the document types that support it. Pick it, and the transaction is parked safely rather than wiped.

One place to find everything you removed

Open Setup → Deleted & Voided Transactions to see a single register of everything that has been voided or deleted, newest first. Permanently-voided documents sit alongside restorable Deleted ones, and the restorable rows carry a Restore action. You no longer have to remember what you removed or dig through the audit trail — it is all in one list.

Bringing a transaction back

Restore is designed to put things back exactly as they were, with the right behaviour for each kind of document:

DocumentWhat happens when you Restore
Sales invoicePosted live again in full — ledger, stock and status restored. If it was a cash sale, the customer’s payment is re-created and re-applied, so the invoice returns already marked Paid.
Credit notePosted live again, with its ledger entries put back.
Delivery notePosted live again, with stock and the order status restored. A direct delivery — one that created its own order behind the scenes — is rebuilt together with a fresh order.
Journal entry, bank payment, bank depositReopened in a ready-filled entry screen for you to review and post — ideal when the original date falls in a closed period and you need to give it a new one.

For invoices, credits and deliveries there is nothing else to do: click Restore, confirm, and the document is back. For journals and bank entries you get the prefilled form, so you stay in control of the date and any allocations.

A quick example

You void a customer’s sales invoice, thinking it was keyed twice — then realise the customer’s payment was already applied to it. In the old world that meant re-creating the invoice line by line and re-linking the payment by hand. Now you open Deleted & Voided Transactions, click Restore on that invoice, and confirm. It comes straight back, posted, with the payment re-applied and the invoice showing Paid again. The whole recovery takes seconds.

Built-in safeguards

Restoring is careful, not blind:

  • A confirmation prompt asks you to confirm before anything is posted, so an accidental click is easy to cancel.
  • The original document number is reused when it is still free. If it was taken in the meantime, a new number is assigned automatically and you are told which one — no dead ends, no manual renumbering.
  • Over-delivery and over-invoicing are prevented. If, while a document was deleted, its source was used again by a newer document, restoring it would double-count the goods or the value — so TamilAccounting blocks the restore and tells you to remove the newer document first. A restore can never inflate your quantities or your figures.
  • Manual allocations are flagged. If a deleted invoice had payments or credits you had allocated by hand, you are reminded to re-apply them after restoring.

Deleted, voided — always clearly labelled

Open a document that has been removed and you are never in doubt about its state. A restorable Deleted transaction shows a Deleted ribbon, a note of who removed it and when, and a single Restore button — every other action is hidden, so you cannot act on a document that is not live. A permanently-voided one shows a Voided notice. Live documents are untouched and keep their full set of actions.

Why it matters

  • Mistakes stop being expensive. A wrong delete is a two-click fix, not an afternoon of re-keying.
  • Your books stay correct throughout. A deleted transaction is out of the ledger the moment you remove it, and back in — correctly — the moment you restore it.
  • Nothing vanishes silently. Every delete is recorded and visible in one register, which auditors and reviewers appreciate.
  • Cash, stock and document chains come back together. You are not left reconnecting a payment or rebuilding an order by hand.

A note on scope

Most day-to-day sales, delivery, credit, journal and banking documents are covered. A few specialised documents still use the classic permanent void; where that is the case, the Restorable option is simply not offered — so you always know exactly where you stand before you act.

Filed under: Sales Banking
Share this article
VVaradharaj V
Written by

Varadharaj V

Founder & CEO of TamilAccounting. A full-stack technologist from Karur, Tamil Nadu — building cloud-native, multi-country ERP for the next decade. 9+ years across GST, VAT, ZATCA, FTA and white-label reseller systems.

Try It Yourself

Run your entire business on one ERP.

Sales, purchases, inventory, manufacturing, HR & payroll, banking, tax filings — already linked. Free trial, no credit card.

Start Free Trial
Global Coverage

Multi-Country ERP — One Platform

Supports GST (India), VAT (UAE, South Africa, Egypt, Iraq, Botswana), and local compliance across all regions.

🇮🇳 India (GST)
🇦🇪 UAE (VAT)
🇸🇦 Saudi Arabia
🇶🇦 Qatar
🇧🇭 Bahrain
🇴🇲 Oman
🇰🇼 Kuwait
🇪🇬 Egypt
🇮🇶 Iraq
🇿🇦 South Africa
🇧🇼 Botswana
🇲🇾 Malaysia
🇸🇬 Singapore
🇦🇺 Australia
🇬🇧 United Kingdom
🇺🇸 USA
🌏 & More Regions