Breadcrumbs
Home / Blog / Financial Standards / If IFRS...Then, Part 1: How IFRS Reporting Will Impact FilersWritten by Natalia Warren Wednesday, June 16 2010
Although IFRS adoption in the US is still a few years away (according to the last SEC proposal: 2014 for large accelerated filers, 2015 for accelerated filers, and 2016 for non-accelerated filers and smaller companies), some US-based issuers may have the opportunity to report financials using IFRS standards sooner, depending on their industry and relative market share. Still, the SEC has not made its final decision and won’t until at least 2011, though it has renewed its commitment to move forward with adoption.
Nevertheless, outstanding issues that are not yet resolved – and may not be before the various deadlines – will affect filers, contributing to the chaos and confusion of any significant transition in reporting requirements.
For example, IFRS does not yet have standards for the treatment of insurance contracts, recapitalization transactions, extractive activities, some common control transactions, reorganizations, and other similar transactions. Also, IFRS permits various accounting practices based on local standards, something the SEC seeks to eliminate. But even today U.S. GAAP also does not have a single standard for property, plant, and equipment or even revenue recognition.
In addition there are known differences between U.S. GAAP and IFRS. For example, IFRS does not permit accounting for inventory on a LIFO basis and instead requires FIFO which could impact taxable income based on differences in inventory valuation using the two methods.
Complications would also impact companies that invest in entities that don’t report using IFRS or private companies planning an IPO that need to switch to IFRS from a different standard. And companies that do not operate globally will be challenged to adopt IFRS both for financial reporting and auditing, e.g. reporting on the effectiveness of internal controls over financial reporting (SOX Section 404).
The SEC has asked for comments to help it assess two alternative reconciliation proposals, neither of which has yet been selected. The first proposal would require a one-time reconciliation from U.S. GAAP to IFRS1, whereas reconciliation in the second proposal would cover a three-year period. If option 2 is approved, large accelerated filers would need to reconcile 2012 – 2014, accelerated filers would reconcile 2013 – 2015, and non-accelerated filers would reconcile 2014 – 2016. In effect the companies would need to issue two sets of reports in each of the three years, one set following U.S. GAAP rules the other set using IFRS standards. Of course, some large global companies may already have to report using both.
Depending on company size and the number of times reconciliation disclosure is required, the SEC estimates modest costs for the IFRS roll-out, anywhere from 0.125% to 0.13% of revenue, a number that is expected to drop over time. However, if the SEC’s SOX compliance estimates are used as a predictor, then their cost estimates for adopting IFRS are much too low.
Although the SEC decision is not expected until 2011, the time to prepare for what appears to be an inevitable future is now. The difficulty and complexity in IFRS reporting will only be exacerbated for organizations that frequently acquire other companies, frequently reorganize, or have different charts of accounts (COAs) for various business entities. It stands to reason that compiling period-end reports for them is already difficult and will only be more so as U.S. GAAP rules morph into IFRS standards.
At the very least, organizations should move toward adopting a single COA for all business entities. At a minimum this will mean that all of the convoluted mapping during period-end consolidation will be minimized, if not completely eliminated, along with the myriad spreadsheets consumed in the effort. IFRS compounds the issue for U.S. filers accustomed to following rules by establishing standards and not publishing a recommended COA. The sky is the limit, or so it seems. But adopting a COA that can accommodate various lines of business in different countries and industries is not an insurmountable task if best practices are followed. The question then becomes, what are those best practices?
In If IFRS…Then, Part 2 we share best practices in COA design.
| < Prev |
|---|
Related Articles
- Holy Chipotle: What's Hot About a World-Class Close
- Everyone Takes the Hit: What You Can Do About It – 5 Key Business Metrics and Oracle E-Business Suite
- If IFRS...Then, Part 2: 5 Best Practices in Designing a Chart of Accounts in Oracle E-Business Suite
- Operating a Shared Service Center in R12 Using EBS
- A Dollar Today Is Worth More Than a Dollar Tomorrow
Enter your email address to sign up for our Newsletter
May Puzzle
David is often referred to as Rainman due to his peculiar ability to effortlessly figure out a certain date's day of the week. He recently displayed this talent when I asked him if there was a conflict with the upcoming Fuzzy Dice Conference and our weekly court-ordered community service. He asked the date of the convention. It was April 20th, 2012.
"Oh, that’s a Friday," he said, effortlessly. "And your sentences have you committed for the next few dozen Wednesdays so you'll be able to go." And of course he was right.
One day a few weeks ago I asked out loud in the office about the date June 5th. And of all people, my brother Tommy piped up and said "Oh, that's a Tuesday."
"That's right," said David.
Well how about Otcober 3rd?
"That's a Wednesday," said Tommy. Then I asked about Christmas Day 2012.
"Oh, that's a Tuesday." David nodded in agreement.
Do we now have two rainmen? Or had Tommy figured something out?
Solution
Here's what was going on. Tommy was using something called anchor dates. And these dates apply to each and every year. April 4th, or 4/4 we’ll call it from now on, June 6th or 6/6, 8/8, 10/10, 12/12, are all the same day of the week, each and every year.
So too are 5/9 and 9/5, May 9th and September 5th. So too are 7/11 and 11/7, and all the above dates are the same day of the week, as is the last day in February, Leap Year or not. And they’re all the same day as January 4th, it would otherwise be January 3rd, but this was a leap year, and that’s changes the anchor day from January 3rd to January 4th.
Tommy also knew that New Year's Day was a Sunday. He was sobered up by then. And he knew it was a Sunday because Christmas was a Sunday in 2011, so New Year's Day is a Sunday, so the Anchor Day for 2012, January 4th, has to be a Wednesday!
So if that's a Wednesday, then 4/4, 6/6, 8/8, 10/10, 12/12, 5/9, 9/5, 7/11, 11/7, and February 29th are all the same day of the week, and they're all Wednesdays. So when I ask for example, about October 3rd, he knew October 10th was a Wednesday, 10/10. So 10/3 must also be a Wednesday. 12/12 is a Wednesday in 2012, so it’s 12/26, which is two weeks later. So 12/25, or Christmas Day, must be a Tuesday.
Success Tips for Oracle Project Management
- Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
- Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
- If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
- Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
- Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
- Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
- Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
- Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
- Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
- Include governance, risk, and compliance management as part of the project plan.
- Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.
The Analyst Corner
John Van Decker, Research VP of Gartner, states:
"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."
Popular Articles
- Organization Setup in R12
- If IFRS...Then, Part 2: 5 Best Practices in Designing a Chart of Accounts in Oracle E-Business Suite
- 11i to R12 Decision: Upgrade or Reimplement?
- Designing a Global Chart of Accounts and Taking Advantage of Oracle® E-Business Suite Release 12
- Moving from GAAP to IFRS with Oracle EBS





