Hello Manager.io team,
I know this was already discussed in make-a-reversing-journal-entry topic.
While the Clone tool is a helpful manual workaround, I would like to propose the implementation of a native Automatic Reversing Entry feature, focusing on the specific benefits that “cloning” cannot provide:
1. Ensuring Audit Integrity and Tracing A manual clone creates two independent transactions with no system-level link. A native feature would allow for a Permanent Link between the accrual and its reversal. For auditors, this provides an immediate “reason for existence” for the second entry, proving it is a systematic correction rather than a manual error or a duplicated expense.
2. Eliminating Synchronization Risk (Single Source of Truth): The biggest weakness of cloning is that it requires updates to be carried out in two different places. If the original accrual amount is adjusted later, the user must remember to manually update the clone. A native auto-reversal would ensure that any change to the primary entry automatically propagates to the reversal, preventing “ghost balances” in the ledger.
3. Maintaining a “Clean” Ledger for Operational Staff When reversals are automated, the Balance Sheet for the new period is “cleared” from day one. This allows staff who handle daily payments to see accurate account balances immediately, without waiting for a senior accountant to manually clone and post adjustments.
4. Scalability for Growing Portfolios Cloning works for 2 or 3 entries, but for a business managing many accruals (salaries, utilities, interest, prepayments), the manual overhead of cloning and swapping Debits/Credits becomes a significant source of “clutter” and potential data entry errors.
Proposed Solution: Instead of a complex new module, simply adding an “Auto-reverse on [Date]” field to the Journal Entry screen would suffice. Upon saving, Manager.io could generate a “Linked Read-Only Reversal” that remains anchored to the original transaction.
This feature would significantly reducing the period-ending workload for its users.