Articles

Google "finance transformation" and you’ll find a plethora of information about how operating models and processes are being rethought and brought up to date. You’ll be presented with a ton of results that explore how the latest technologies can be employed to eliminate waste and get fast, accurate results. But there is one area that has lagged behind and hasn’t always been subject to the same approach — the intercompany function.

Intercompany accounting is a by-product of corporate expansion. It’s what happens when a company grows until it includes multiple legal entities, any number of which may be subsidiaries located in different countries.

Earlier this month saw the second incarnation of the Ascend user conference — a collaboration between Oracle Applications & Technology Users Group (OATUG) and Oracle HCM Users Group (OHUG).

We're living in a time of increased business complexity where supply chains and markets have become ever-more global and interconnected.

Something as simple as a software update can cause you hours of frustration. Intercompany is the last action to occur during period close, so there’s little time to compensate for reconciliation issues, such as software updates.

Intercompany accounting is typically downplayed, oversimplified, and hastily swept under the rug so you can “deal with it on another day”. While this may have been acceptable back in the day, today’s consequences are becoming harsher, and companies need to realize that it’s finally time to tidy up the situation.

Some organizations find that Oracle EBS doesn’t offer some of the specific functionality they need to successfully address their intercompany accounting needs. They often turn to customized solutions—either in-house or via an external team—to meet their bespoke requirements; however, this can be costly and time consuming. Here’s how to extend EBS accounting without customization.

Organizations are facing increasing numbers of challenges when managing intercompany transactions. These challenges spiral into other issues, such as improper or inadequate reporting, which can lead to serious consequences, including warnings, fines, or worse.

An in-house development team can be an attractive prospect thanks to reduced project costs and greater control of the system being created. When it comes to managing intercompany transaction software, however, in-house teams aren’t the only option available to you. Here’s why you shouldn’t use them for AGIS implementation.

As a combined result of company evolution and globalization, changes in regulations, and increased scrutiny from auditors, it’s becoming easier for companies to adopt improper or inadequate intercompany accounting practices. Unfortunately, this can have serious and costly consequences.