Professional Documents
Culture Documents
Presenters
Migration from Blackline to Oracle Account Reconciliation Cloud
Kevin Kleiner – Sr. Director, Financial Accounting, Tribune Publishing
Joe Guillotte – Director, Financial Accounting, Tribune Publishing
Ashwin Tandon – Principal Consultant, Infosys
Rahul Bansal – Technology Lead, Infosys
Tim Gaumont – Director, Product Management, Oracle
Quick Survey to get to know the audience
• If you are using Blackline, are you using Transaction Matching in Blackline?
FY 2017 Gross
Revenue Employees
$1.5 billion 5,600
Our Current Financial systems PeopleSoft ERP, Microsoft AX, Blackline
Partnerships Infosys
(Implementation partner)
INFOSYS ORACLE
End to End Program Involvement of ARCS
Management, Design &
Build Migration, Testing,
product development
leadership for product
Peak
team size - 4
User Training and Go- issues and
LIVE enhancements
Onsite-
offshore
ratio - 35 : 65
Decision – Why did we choose to move from Blackline to Oracle ARCS
4 Transaction matching
• Flexibility to assign due dates based on risk ratings (Our Favorite !!!)
– Ability to manage employee’s time better
– Enhanced control to manage close cycle
Mappings Mappings for loading data would be created automatically using the profiles template as given.
Historical Reconciliations Historical reconciliations from Blackline would be migrated to ARCS using excel templates and creating as-is
reconciliations from blackline
Historical Reconciliations – Historical data from blackline recons would be migrated using pre-mapped balances functionality of ARCS where a
Data reconciliation would have Source System Balance (General Ledger) and/or Subledger Balance depending on the
format of the account profile.
Historical Reconciliations - Historical transactions from blackline recons would be migrated using excel templates for loading transactions into
Transactions reconciliations month-wise into all the existing historical reconciliations. We would also enable special configuration
to auto-submit and auto-approve this reconciliations if the unexplained difference or unexplained balance is zero.
Approval Workflow For approval workflow to migrate from Blackline to ARCS, preparer and approvers from Blackline would be
converted to preparers and reviewers in ARCS as is. Additionally, more levels of approvers (reviewers in ARCS)
can be added.
1
Infosys Blackline to ARCS Transaction Matching migration 0
Match Process ARCS has the capability to configure multiple match processes in a single reconciliation type. This will help to define matching
between any two data sources in a single recon type resulting in lesser configuration of matching rules
Matching Rules In a single match process, we define multiple rules where different attributes (balancing attribute, accounting date, Reference
numbers etc.) are used to match transactions. These can be 1-1, 1-Many, Many-1 and Many-Many.
Historical In-Transit transactions While migrating from Blackline to ARCS, the existing unmatched transactions can be imported as is into ARCS with little
formatting to ensure in-transit matching of the same with future transactions being posted in next month financial cycle.
Filtering and Custom Attributes In Blackline, filters are applied over data and then matching rules are defined over it. If the same data is to be matched against
a different data source, you have to clone the source. To overcome this in ARCS, we use custom calculated attributes which
are derived using specific conditions and then matching rules are defined on a broader category rather than on filtered data in
Blackline. This helps in removing the effort to clone the data for matching again.
The Infosys Blackline to ARCS Framework is the first self deployable ARCS solution to be published on Oracle Cloud Market
Place . You can download the artifacts at
https://cloudmarketplace.oracle.com/marketplace/en_US/listing/43397817
ARCS Solution Components
11
Data Flow Diagram
Risk Ratings
• How have you defined your risk ratings across your accounts?
• At Tribune, accounts are classified as Key and Non-Key which are translated to High Risk and Medium Risk
accounts and are having different due dates. Other companies using ARCS have 3 or 4 or more levels of risk
rating categories assigned.
• Setting different due dates allows preparers to concentrate on high risk accounts first and complete their
reconciliation process in a risk averse & streamlined manner.
• The key win here over other competitors in reconciliation space is that Administrators or Automated process can
update the due dates as needed in the system for any specific account without affecting the underlying structure
of reconciliation. Changes can be made for only current month or for all the future months as required by
business.
Match Processes (Combination of Matching Rules)
• How do you currently configure your matching processes?
• At Tribune, we have many match passes happening, which the Cash being a 4-way reconciliation.
• Tribune defines multiple match processes like GL vs AR AMEX Credit Card, AR AMEX Credit Card vs AMEX
Processor, AMEX Processor vs Bank, and even sometimes bypass middle Data Sources and match GL vs Bank in a
single Match Type – you can define as many Match Processes as needed.
Auto-Reconciliation Rules
• How do you currently auto-reconcile your accounts?
• At Tribune, we have a three types of inbuilt auto reconciliations rules are configured.
• Also Tribune wanted to customize reconciliations to auto-close based on certain parameters and hence
configured custom rules for each format. Some of them are below.
• In ARCS you can have your transactions getting loaded continuously without having to stop them to analyze your
in-transit transactions whether matched or unmatched. In Blackline ,Tribune had to stop loading transactional
data into their transaction matching solution to analyze the in-transits after month end and had to start loading
them again only after they had completed their month end matching process.
• With ARCS solution they did not have to go through the same painful and delaying process again as ARCS has
seeded out of the box capability to match your in-transit transactions and show them on the reconciliation
dashboard for easy analysis and reporting.
Matching Rules
• How have you defined your matching rules for your transaction matching?
• Depending on the nature of data sources and respective transactions to be matched; we configured various
types of matching rules like:
– 1-1
– 1-Many
– Many-1
– Many-Many
• Each rule has its own significance and incorporates the filtering mechanism achieved using custom attributes so
that we do not have to write separate matching rules for separate business units
Tribune Publishing Company – Next Steps
20
Solution Dashboards, Data Sources Match Processes and Custom Attributes
Below are snapshots from our solution for ARCS Transaction Matching at Tribune Publishing showcasing Reconciliation Dashboards,
Match Processes and Custom Attributes.
• To change above formats and convert / map them to ARCS specific and readable .csv formats MuleSoft tool was used and .bai to .csv
converter was developed in-house by Infosys
• This helped us in delivering the ARCS TM solution in desired, effective and quick manner
Quick Glance – Infosys EPM practice
Planning
Consolidation & reporting
4 out oftop15
Finance Institute
7 out oftop10
Manufacturing
Financial Services
37% 47%
4 out oftop 10 Automotive OEM Americas APAC
Consulting Hi-Tech Companies CPG, Apparels
Support 4 out oftop10 Retail, Logistics
Financial Transformation
3 out oftop10
Global Telcos
Apparel Brands
4 out oftop 5 Energy, Communications & 12%
Platform & operations CPG Companies Services EMEA
Cloud adoption Healthcare and Life Sciences
25
Infosys Credentials in Reconciliations space - Summary
• 2 Infosys ARCS case studies were presented at Oracle Open World 2017
– Excel based Reconciliations to cloud with ARCS in 11 weeks for a Semiconductor US major
– Migration from Blackline to ARCS for a US Publishing house
• First Oracle partner to have an ARCS based solution published on Oracle cloud
marketplace.(https://cloudmarketplace.oracle.com/marketplace/en_US/listing/43397817)
• Performed a 4 week transaction matching proof of concept for a ecommerce company to load 2 million transactions from
two sources and match them based on rules provided. ( Loading and Matching of 2 million transactions was completed in
less than 25 minutes in ARCS)
• Infosys was involved in multiple year roll out of one of the largest ARM (On premise Account recon Manager)
implementations . The manufacturing client was part of the Oracle early adopter program and Infosys leverages all the
expertise and best practices from that implementation to implement best in class reconciliation solution
– The time, effort and learnings of the ARM implementation are equivalent to several ARM implementations
• Infosys has a reconciliation COE which includes process consultants with expertise in reconciliation domain and support
clients with their AR and AP back office operations.
• Strong alliance and partnership with Oracle ARCS product development team for creating solutions , future road mapping
and beta testing of new features
• Two ongoing implementations for ARCS (Recon Compliance and Transaction Matching)
26
Q&A
Share your feedback on this
session via Twitter
#InfosysAtOOW
THANK YOU
© 2018 Infosys Limited, Bengaluru, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change without notice.
Infosys acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except as expressly permitted,
neither this documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, printing, photocopying, recording or
otherwise, without the prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.