Compares your protected GL accounts against their subledgers and alerts you to the individual transactions that do not match, so you can go straight to the entry that caused the difference.
Jump to a specific section by clicking a link
Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts
Overview
Overview
When a GL account is protected in eAutomate, its balance is meant to be driven entirely by the subledger behind it, but manual journal entries, void and repost chains, and cost corrections can quietly break that link with nothing to tell you it has happened. We envisage this process comparing your protected GL accounts against their subledgers and sending you an alert with the individual transactions that do not match, rather than simply telling you an account is out of balance.
The alert will show the account, the period, the reference and the amount on each side, so your accounting team can go straight to the entry that caused the difference instead of working back through months of postings at close. We expect it to be configurable, so you can choose which accounts are checked, how far back it looks and how often you hear from us.
We're gauging interest right now before we start building, so let us know you're interested by subscribing.
If interest is high, we plan to start development end of Oct 2026.
Run Schedule: To be confirmed
Type of Output: To be confirmed
* * *
Sample
Sample
Coming soon
* * *
Variables
Variables
Coming soon
* * *
Alert Functionality
Alert Functionality
Coming soon
* * *
Best Practices & Tips
Best Practices & Tips
Coming soon
* * *
Related Alerts
Related Alerts
Coming soon
* * *
0 Comments