Key Concepts: Account Reconciliation Cloud – Application Design – Standardized Artifacts

Published January 16 2020 by Nick Boronski
Back to insights

Core Components: Standardized Artifacts

The prior post in this blog series explains how Display Options serve as a core component for customizing the end-user experience in both a cosmetic and functional way depending on the type of reconciliation being performed. However, it is also important for the application to have a standard look and feel. The third core component to Formats, standardized artifacts, is useful in reducing the burden of administrative maintenance. Account Reconciliation Cloud offers a lot (and I mean A LOT) of flexibility in allowing administrators and power users to customize profiles individually. This is a good function, and I would not change it. But while having the capability to set up each profile with unique Custom Attributes, Instructions, and Rules might sound good on paper, actually maintaining said application can be a full time job - precious headcount that most companies are not able to spare.

Enter standardized artifacts within Formats. By including these customizations at the Format level, administrators can guarantee that all existing and, more importantly, future profiles that utilize that Format will automatically inherit these changes. The application clearly delineates Format-level artifacts from profile-level artifacts for administrators and power users through the lockbox icon. All inherited Format-level artifacts display this icon when editing the profiles. However, this distinction is unnoticeable to end users - who only experience a seamless list when completing the reconciliation. This component of Formats is strictly an administrator tool for quality control.


[Screenshot 1a: Standardized artifacts placed at the Format level display with a lockbox indicaton]


[Screenshot 1b: From an end user standpoint, there is no distinction. Standardizing artifacts at the Format level is strictly an administrator tool for managing the application]

However, not every reconciliation has the same requirements or the same artifacts to standardize. Therefore, new Formats are sometimes created to better categorize which reconciliations should be set up with the same rules and custom attributes while maintaining quality control over those groups of profiles. In some situations, the recommended setup may even come full circle to a variant of the Oracle pre-built Formats. As an example, if all bank-related reconciliations require unique rules that are not needed for any other account type, it may make sense to create a Format specifically for bank reconciliations. Ultimately, this is set up on a case-by-case basis depending on how the administrator wants to slice-and-dice the Profile maintenance.

I have discussed how Standardized Artifacts in Formats can reduce the administrative burden while providing a seamless experience for end users. The next post will round out the four core components with a discussion of the unique features that are only available natively when designing Formats.

For comments, questions, or suggestions for future topics, please reach out to us at  Visit our blog regularly for new posts about Cloud updates and other Oracle Cloud Services such as Planning and Budgeting, Financial Consolidation, Account Reconciliation, and Enterprise Data Management.  Follow Alithya on social media for the latest information about EPM, ERP, and Analytics solutions to meet your business needs.

Product Manager - Financial Close & Consolidations

Contact us