What's new on Bromcom

Modules > Finance > Routines > Automatic Reconciliation

This update enhances the error-checking process for journal creation during Automatic Reconciliation by ensuring that incorrect journals are prevented from being posted. The system now performs real-time checks to detect errors such as unbalanced journals or missing key details, like Cost Centre or Fund Code, and rolls back any journal with errors, maintaining data accuracy and integrity. If an error is found, the journal creation is reverted, and the user receives a message stating: "It has not been possible to post this document, please contact the Helpdesk for further assistance."

The journal rollback will occur for issues such as:

• Unbalanced journals where credits and debits do not match.
• ErrSA2 value mismatches between journals and the related payroll files.
• ErrSALink issues where there is a broken link between the journal and salary records.

If the file contains multiple journal entries, only the erroneous rows will remain unresolved while correct rows will be posted successfully. For example, if 5 out of 500 rows generate errors, those 5 rows will remain unreconciled, but the remaining 495 will be processed correctly.

An Error column has been introduced in the Automatic Reconciliation screen for rows marked as 'Unreconciled' or 'Deleted'. This column will help users distinguish between errors caused by journal issues and other unreconciled entries. If a journal error is detected, the relevant error code (e.g., ErrSA2) will appear in this column.

This update adds a layer of validation to journal creation in the Automatic Reconciliation process. By rolling back erroneous journals and providing clear error reporting, it improves data integrity and makes troubleshooting easier for finance teams.