Fix Business Record Mistakes Honestly: Backdating and Reversals
Gazeloft 5 min read
Every business owner makes recording mistakes. You forget Friday's last sale until Saturday morning. You fat-finger ₦25,000 as ₦52,000. A customer returns goods after the sale is booked. The question is not whether errors happen; it is what your record system lets you do about them. Most systems offer two bad answers: leave the lie in the books, or delete the row and pretend nothing happened. Gazeloft offers a third: fix it honestly.
The Pain: Delete Culture and the Books You Cannot Trust
Kabiru runs a spare parts shop in Kano. In his old app, every mistake had one remedy: delete and retype. It felt harmless until the day his sales boy quietly deleted three genuine sales and pocketed the cash, and Kabiru realised the delete button had been erasing the only evidence, silently, all along. Deleted rows leave no ghost. Books full of silent deletions are not records, they are fiction with numbers.
The other classic failure is the wrong-day problem. You forget to record Thursday's ₦18,000 sale and enter it Friday. Now Friday looks like your best day of the week and Thursday looks weak. Every report built on those days, weekly trends, best-day analysis, worker performance, inherits the lie. Do that a few times a month and your "data" is a story you accidentally made up.
What honest businesses need is the accountant's old wisdom: never erase, always correct, and put things on the day they truly happened.
What Backdating and Reversals Are
Backdating. Every entry form in Gazeloft, on every space type, has a date field. Yesterday's forgotten sale can be recorded today but dated yesterday, and it lands on the right day. All aggregates follow the real date, so your daily totals, trends and comparisons stay true to when money actually moved. Note the direction: this is for placing real past transactions on their real past dates, not for inventing history.
Universal transaction reversal. Any transaction on any space type can be reversed, whether as a return or a void. Here is the honest part: the row stays in your history, flagged as reversed. Its effect on your totals becomes zero, but the record of what happened, and that it was undone, remains visible forever. Reversal also cleans up everything connected to the transaction: loyalty points awarded on the sale are clawed back, and linked part-payments are unwound too, so no orphaned side effects linger in your books.
Together they cover the two great families of error: wrong day, and wrong entry.
How to Use Them
Backdating, in the app and on the web dashboard:
- Open the entry form as usual, sale or expense, any space type.
- Find the date field on the form. It defaults to today.
- Change it to the day the transaction really happened, then submit.
- The entry lands on that day. Yesterday's totals now include it, and every report follows suit.
Reversal, in the app and on the web dashboard:
- Find the transaction in your history.
- Choose reverse, as a return or void depending on what happened.
- Confirm. The row stays in history flagged as reversed, its effect on totals becomes zero, and connected points and part-payments are clawed back automatically.
- If the transaction should have existed differently, for example wrong amount, now record the correct version, backdated to the real day if needed.
Reversal is a protected permission, so you decide which workers can do it. A cashier who cannot delete and cannot reverse can only add, which means the audit trail is complete by construction.
Worked Example: Kabiru's Messy Week, Cleaned Honestly
Three things go wrong in Kabiru's week:
Monday: he closes late and forgets to record his last sale, a fan belt and filters for ₦18,000 cash. Tuesday morning he opens the sale form, enters ₦18,000, and sets the date to Monday. Monday's total rises from ₦74,500 to ₦92,500, which is the truth. His week chart shows Monday as the strong day it really was.
Wednesday: his boy records an alternator sale as ₦52,000 instead of ₦25,000. The mistake is spotted at the evening count when the drawer disagrees with the app by exactly ₦27,000. Kabiru reverses the ₦52,000 entry, it stays in history flagged as reversed with zero effect, and records the correct ₦25,000 sale dated Wednesday. Anyone auditing the week later can see precisely what happened: an error, its reversal, and its correction. Nothing hidden.
Friday: a mechanic returns a ₦31,000 starter motor that turned out to be the wrong model, and takes a refund. Kabiru reverses the original sale as a return. The sale row remains in history, flagged, its ₦31,000 removed from totals. The customer had earned loyalty points on that purchase; the reversal claws them back automatically, so the points balance cannot be gamed by buy-and-return tricks.
End of week, Kabiru's books show exactly what his drawer shows, and, just as valuable, they show every stumble on the way there. When his accountant cousin reviews the quarter, the flagged reversals answer questions before they are asked. Compare that with his old delete-and-retype books, where a ₦27,000 discrepancy would have been an unsolvable argument, probably settled the traditional way: deducted from the sales boy's salary whether he deserved it or not, and remembered by both of them for years.
Tips and Pitfalls
- Backdate the same week, not the same quarter. The feature is for yesterday's forgotten sale, not for reconstructing March in June. Memory fades fast; correct fast.
- Reverse, never work around. Do not "fix" a wrong sale by recording a fake expense to balance it. That is two lies stapled together. One reversal plus one correct entry is the clean path.
- Guard the reversal permission. Give it to yourself and perhaps a trusted manager. Cashiers should add, not undo.
- Review reversed rows weekly. A healthy shop has a few reversals. A worker whose entries need reversing daily has a training problem, or something worse, and the flagged history will show you which.
- Edits keep the original time of day. When you correct an entry, its time stays true, so your peak-hours picture stays honest too.
Books You Can Defend
The mark of trustworthy records is not that they contain no mistakes. It is that every mistake left a visible, honest scar. Build books you could hand to a partner, a lender or your own conscience without flinching. Start keeping them today at gazeloft.com.
Frequently asked questions
Does backdating change my old reports?
Yes, in the right way. Aggregates are keyed to the real transaction date, so the backdated entry appears in that day's totals and every report that includes it.
Is a reversed transaction deleted?
No. The row stays in history flagged as reversed. Its effect on your totals becomes zero, but the record remains visible, which is the whole point.
What happens to loyalty points on a reversed sale?
They are clawed back automatically, along with linked part-payments, so no side effects survive the reversal.
Can every worker reverse transactions?
No, only those you grant the reversal permission. It is protected precisely so corrections always have a known author.
Which space types support these features?
All of them. Every entry form has the date field, and reversal is universal across every space type.
Tags: reversals, corrections, data integrity, backdating