With the Manage the Reconciliation Close app, you can set the reconciliation close status, view reconciliation differences by reason code, trigger an approval workflow, and generate reconciliation statements.
In the following image, these are the key points:
- Because the variance for US and CA is over the threshold, it appears in red.
- The Elimination Status is Initial because elimination has not been run yet.
- The Workflow Status is Approved and the Reconciliation Status is Closed.
- In the details, you can find the leading and partner amounts, add comments, and download the document as a PDF file.
When closing the reconciliation, any variances outside the tolerance generates an approval workflow for users who are on the reconciliation team. In the resulting inbox, the trading partner data is displayed. The user can then approve or reject the approval request. They can also download a PDF with the summary.
Workflow Status: This status is relevant for the reconciliation cases that require an approval workflow to close reconciliation. The possible workflow statuses are Waiting, Ready, In Process, Error, and Completed. Only when the workflow is completed, that is, the reconciliation close request is approved, can the reconciliation close status be set to Closed.
Elimination Status: This is the execution status of the IC Balance Sheet Elimination consolidation monitor task. It's only relevant for the reconciliation case that is consolidation related and is assigned with the elimination method SC001 in configuration step Define Elimination Methods. The following statuses are possible:
Initial: The elimination task hasn't been executed yet.
In Process: The elimination task is initiated and running.
Completed: The elimination task has finished successfully.
Failed: The elimination task ran into an error, for example, due to system error or misconfiguration. The error details can be viewed in the Task Logs app.
Outdated: The elimination task was once executed and finished successfully, but after that, a new matching run was triggered and brought new posting data, which makes the prior Completed status outdated. Therefore, the elimination task needs to be executed again.