Project Partners Blog


Posts Tagged ‘project billing’

PROJECT PARTNERS PROUDLY ACHIEVES PLATINUM PARTNER STATUS IN
ORACLE PARTNERNETWORK (OPN)

HALF MOON BAY, Calif., January 16, 2019 – Project Partners, a global leader in optimizing business processes and IT investments within project-driven organizations, today announced that it has achieved Platinum partner status in Oracle PartnerNetwork (OPN).  By attaining Platinum level membership, Oracle has recognized Project Partners for its in-depth expertise and continued excellence in providing services for Oracle applications and technology.

“We are honored to be in the highest level of the OPN Program. With our new designation as a Platinum Partner in the Oracle PartnerNetwork (OPN), Project Partners will continue to strengthen and build upon its 20+ year relationship with Oracle,” said Randy Egger, President/CEO, Project Partners.  Our global team has continually demonstrated deep application expertise and are working to obtain additional certified specializations across Oracle application solutions areas to better serve our project-centric customers.”

The company offers deep industry expertise across key Oracle applications and technologies including the Oracle ERP Cloud, Oracle E-Business Suite, and Oracle Primavera applications.  In addition, we have developed products and solutions to support and augment our customers’ off-the-shelf products.  We are proud to be widely recognized as The Experts in Solutions for Project-Driven Organizations™ and look forward to continuing collaboration, sharing industry experiences and leveraging our Platinum Partner status to enable organizations, partners and Oracle.

With its Platinum status, Project Partners will benefit with the high level of engagement, commitment and resources available to OPN partners.  Platinum members receive dedicated virtual account management support to build joint development plans and help broaden specialization areas and revenue opportunities. Additional benefits include priority placement in the OPN Solutions Catalog, one free application integration validated by Oracle, joint marketing and sales opportunities, discounted training and more. For more information about the benefits of becoming an OPN Platinum level partner, please visit: http://www.oracle.com/us/partnerships/index.htm

———————————–

About Project Partners, LLC.

Headquartered in Half Moon Bay, California | Project Partners is the global leader in optimizing business processes and IT investments within project-driven organizations. We are dedicated to helping businesses achieve their goals with smart, effective and scalable Oracle Application solutions that improve processes and deploy technology to maximize project life cycle ROI. Our business process experts understand and support customers with their evolving business models and help them drive productivity to meet the demands of the market and their organization.

Project Partners has a diverse team who is expert in leveraging Oracle’s ERP Cloud, E-Business Suite and Primavera solutions. We have global locations worldwide to support multi-geographical operations and have executed implementations for hundreds of clients who manage tens of thousands of projects, thousands of users, multiple languages and currencies. In addition, we have developed products and solutions to support and augment our customers’ off-the-shelf products.  Project Partners is proud to be widely recognized as The Experts in Solutions for Project-Driven Organizations™.

Project Partners is a proud Oracle Platinum Partner, Oracle Certified Education provider and authorized Reseller of Primavera and Oracle Cloud PPM, and Cloud Financials.  We hold an Oracle Cloud Standard certification, with specializations in Oracle® E-Business Suite™ with Projects, Primavera and Oracle Validated Integration’s in EBS.

For more information, visit: http://www.projectp.com/

———————————–

About Oracle PartnerNetwork

Oracle PartnerNetwork (OPN) is Oracle’s partner program that provides partners with a differentiated advantage to develop, sell and implement Oracle solutions. OPN offers resources to train and support specialized knowledge of Oracle’s products and solutions and has evolved to recognize Oracle’s growing product portfolio, partner base and business opportunity. Key to the latest enhancements to OPN is the ability for partners to be recognized and rewarded for their investment in Oracle Cloud. Partners engaging with Oracle will be able to differentiate their Oracle Cloud expertise and success with customers through the OPN Cloud program – an innovative program that complements existing OPN program levels with tiers of recognition and progressive benefits for partners working with Oracle Cloud.

To find out more visit: http://www.oracle.com/partners

 

# # #

 

_________________________________________________________________________________________________________

 Project Partners Blog Author: Donna Dignam | Principal Functional Consultant 
____________________________________________________________________________________________________________________

In April 2015, FASB (Financial Accounting Standards Board) issued ASU (Accounting Standards Update) 2015-05 to assist entities to determine when a customer in a cloud computing arrangement “CCA” (i.e. hosting arrangement) included a software license.

If a CCA includes a license to internal use software, the software license is accounted for by the customer as an intangible asset.  Basically, the intangible asset is recognized for the software license, and the payments or said license made over time are recognized as a liability.  If no software license is included in the contract, the company should account for the arrangement as a service contract, and the fees associated with the hosting service of the arrangement are expensed as incurred.

The Update did not give any guidance regarding the implementation costs for activities performed in a cloud computing arrangement as a service contract.  Since the FASB guidance in this area was not explicit, the Board decided to issue an Update to specifically address the resulting diversity in practice.

Who Is Affected by ASU 2018-154?

These Amendments on the accounting for implementation, setup and other upfront costs (commonly referred to as implementation costs) apply to entities that are a customer in a hosting arrangement that is a service contract.  Oracle Cloud computing arrangements where a license is sold to the customer along with a hosting arrangement with Oracle Cloud would be one such customer.

Main Provisions of ASU 20184

The Update’s intent is to align the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal use software and hosting arrangements that include an internal-use software license.  The current accounting for the service element of a hosting arrangement is not affected.

It is up to the company to determine which implementation costs to capitalize as an asset related to the service contract and which to expense.  Costs to develop or obtain internal use software that could not be capitalized under Subtopic 350-40, such as training costs and certain data conversion cost, also cannot be capitalized for a hosting arrangement that is a service contract.  The company in a hosting arrangement that is a service contract determines which project stage an implementation activity relates to.  Project stages include preliminary project stage, application development stage or post implementation stage.  Costs incurred for the application development stage are capitalized, while those costs related to the preliminary project stage or the post implementation stage are expensed as the activities are performed.

In addition, the company is required to amortize the capitalized implementation costs over the terms of the hosting arrangement.  The term of the hosting arrangement includes the noncancellable period of the arrangement plus periods covered by:

  1. Option to Extend – customer must be reasonable expected to exercise this option
  2. Option to Terminate the Arrangement – where the customer is reasonably expected NOT to exercise this option
  3. Option to Extend or Not to Terminate – where the vendor has control of exercising the option.

Impairment guidance, as if the costs were long-lived assets, and abandonment are to be applied based upon the existing guidance in SubTopics 350-40 and 360-10, respectively.

Income Statement presentation by the entity should be the same line item as the fees associated with the hosting service of the arrangement.  Similarly, classification of payments for capitalized implementation costs in the Statement of Cash Flows are done in the same manner as payments made for fees associated with the hosting arrangement.  In the Statement of Financial Position, capitalized implementation costs are presented in the same line item that a prepayment for fees associated to the hosting arrangement would be presented.

How is This Different and Why is it an Improvement?

Currently, GAAP does not specifically address accounting for implementation costs associated with a HASC.  Therefore, the Update improves current GAAP as it clarifies accounting and aligns the accounting for implementation costs for hosting arrangements, regardless of whether a license is conveyed.

For consulting firms, the new standards present an improved selling point as costs that were previously required to be expensed can now be capitalized.  For capital intensive industries, where cloud applications are being considered and dismissed due to financial considerations around increased expenses (and resulting decreased profitability metrics) due to cloud implementation, the new standard allows a way to capitalize the costs associated to both the license and the implementation and development costs around getting that application stood up.

When Does This New Update Take Affect?

For public entities, the amendments are effective for fiscal years beginning after December 15, 2019 and interim periods within those fiscal years. For all other entities, annual reporting periods beginning after December 15, 2020, and interim periods within annual periods beginning after December 15, 2021 are required.  Early adoption is permitted at any time.

The amendments in this Update should be applied either retrospectively or prospectively to all implementation costs incurred after the date of adoption.

Have Questions?
Simply reach out to us and our experts will immediately assist, provide additional information,
and answer any of your questions.

P: #1.650.712.6203  |   Email: cfryc@projectp.com

 

Author: Wendy Lamar | Managing Principal Consultant | Project Partners
Oracle E-Business Suite R12 Project Certified Implementation Specialist


Through this three (3) part educational web-series, Project Partners will arm you with critical steps and insight into a Project Financials cost-effective solution. This unique solution offering will assist administratively burdened organizations like yours to effectively manage Project Financials around Capital spend through all phases of the Capital Lifecycle (Concept Definition, Funding Approvals, Execution, Reporting, and Managing Project Costs).

WHY CAPITAL PROJECTS? – WEBINAR REGISTRATION INFORMATION

CLICK TO REGISTER HERE for our FINAL PART (3) of the three (3) part series as we explore how Project Partners has addressed the pain associated with AFE’s and the manual efforts.  We will showcase how we’ve developed an easy to use Authorization for Expenditure solution that extends the functionality of Oracle EBS Projects applications and walk you through the solution focused around project costing to your specific business requirements, robust functionality, and use of authorizations for expenditures to further efficiency gains and extensive return on investments.

MISSED PART 2?  Don’t Worry…CLICK HERE to get a downloadable recording so you will be up-to-speed!   

Have Questions?
Simply reach out to us and our experts will immediately assist, provide additional information, and ensure you have associated playbacks. We look forward to your attendance, and will set up a call to fully understand your needs, and offer next steps around a Project Financials cost-effective solution that best fits your organization.

P: #1.650.712.6203 Email: cfryc@projectp.com

By Ravi Shankar, PgMP, PMP, PMI-RMP and PMI-SP

Oracle E-Business Suite (EBS) Projects Applications Release 12 provides rich functionality to support multi currency processing capabilities in the areas of accruing revenue and generating invoices.  Revenue is always processed in the project functional currency, as distinct from the project currency and project funding currency.  Revenue amounts derived in the billing transaction currency (invoice processing currency) are converted to project functional, funding and project currency during the revenue generation process.  The Release 12 EBS system tracks and posts the revenue, unbilled receivables and unearned revenue in both the functional and billing transaction currency to the general ledger, thereby giving full visibility, both at the project level and in the general ledger, of the details of revenue in the different currency options. Read the rest of this entry »

Introduction

Oracle Projects may be integrated with Inventory and WIP. This integration allows the tracking of project related transactions in Inventory and WIP. Some of those transactions will be interfaced to Oracle Projects. The simplest Inventory transactions that will be cost collected and imported to Oracle Projects are miscellaneous inventory transactions.

  • Miscellaneous Issue from stock to a project,
  • Miscellaneous Receipt from a project into stocks.

Those miscellaneous transactions are imported into Projects from any Inventory organization, whether or not the organization was classified as Project Manufacturing Organization. In a PJM organization those transactions are eligible for cost collection only if the stock locator is of another project or has no project at all.

The following transactions will be cost collected and imported into Oracle Projects only when executed within a PJM organization:

  • Items receipts of a project related purchase orders for inventory destination. The items are delivered into a project locator of the inventory organization.
  • Items issued from a project locator to WIP job (work order) of other project, or from a non project locator to a project work order.
  • Project Transfers transactions which move items from one project locator to another project locator on the same organization, or from a non project to a project locator.
  • Inter Organizations transfers from a project locator or non-project locator to another project locator in the receiving organization.
  • Resources charging WIP work orders, which are project related. Resources may be employees’ labor time, outside processing supplier costs, machine usages etc.

Cost Management invokes the cost processor program for each inventory and WIP transaction, one by one, following their creation order. It calculates the cost amount of each transaction and may generate the accounting lines. When cost processor is responsible for generating accounting, it uses the accounts set up of Cost Groups and WIP Accounting Class. In a PJM organization you assign each project to the organization, and enter the project parameters. Among them you link a project to a single cost group and may link it to various WIP Accounting Classes. Cost Management system also offers some extensions that may be implemented for changing those default accounts.

Accounting Options for PJM Organization

When Project Manufacturing is enabled for all or certain inventory organizations, there are (starting 11.5.10) several alternative options for accounting, which differ in scope and path. On the setup form of a PJM organization you should select one value for each one of the following parameters:

  • GL Posting Option:
    • Manufacturing: All inventory and WIP transactions are accounted by Cost Management process in Inventory, and sent from Inventory to GL. The project-related transactions are interfaced from Inventory to Projects as accounted.
    • Projects: Inventory is not interfacing any material or WIP transactions to GL. The project-related transactions are interfaced from Inventory and WIP to Projects.
  • Account Option: This option is applicable only if GL posting option is selected as Projects.
    • Send Accounts to PA: Inventory and WIP transactions are interfaced to Projects with the accounts defined by the source. However, Projects will interface those to GL.
    • Use Auto Accounting: Inventory and WIP transactions are imported into Projects unaccounted. Oracle Projects is responsible for distributing those expenditures using Auto Accounting rules.

Inventory miscellaneous transactions imported from a PJM organization will always be accounted by Auto Accounting rules in Projects.

Several points regarding these options are worth noting when implementing Project Manufacturing:

  • When selecting the Projects value for the GL Posting option, only transactions that are cost collected into Projects are accounted and posted in GL. All other inventory transactions, which are not charged to projects, will not be affecting any GL accounts. Any inventory transaction that represents a change in the physical on-hand value of inventory without adding or reducing any value to the project accumulated cost will not be cost-collected nor accounted in GL.
  • WIP transactions represent resources adding value to the project-work-orders; hence those are always cost collected into Projects, and always accounted.
  • PO delivery transactions into Inventory or Shop-Floor, and any subsequent correction or return transactions will always be accounted and interfaced to Projects as well. This is true for non-project purchase orders as well.
  • When selecting the Projects value for the GL Posting option you have to enable a project number as a Common Project on the PJM organization setup form. In a PJM organization, users may enter transactions without project and task. By enabling a common project the system will capture any WIP and Inventory transactions with no project data, and interface those to Projects, all assigned to the predefined common project and task.

In the following paragraphs I would like to explain the advantages of interfacing unaccounted Inventory and WIP transactions to Projects.

Many companies use to apply indirect costs on top of direct costs. In Inventory and WIP you may setup overhead rates, and the cost processor calculates the additional cost elements, material overhead and resource overhead. Those overhead materials are cost collected and interfaced as separate burden expenditures. The alternative tool for applying overhead is the burdening functionality of Oracle Projects. Projects will not allow burdening of externally accounted transactions. However, when expenditures are imported as not accounted, Oracle Project’s burdening functionality can process the PJM transactions, and apply burden costs to those expenditures. The ability to use Project Burden allows companies to apply systematically the same burden multipliers on PJM and all other expenditures charged to the projects. For example, employees may sometime charge work order in WIP or charge directly a project and task on their timecard. Using this feature the burden calculation may be shared, and you could save the maintenance of duplicate rates schedules. In addition, Projects’ burdening allows for updates to the burden rates. The ability to re-burden and apply final burden multipliers, replacing the provisory initial multipliers is a unique feature available in Projects. There is no way to revise overhead rates in Inventory. Last point in favor of using project burdening over inventory overhead is the ability to treat differently the burden amounts based on project types. Company may choose to use burden on separate expenditure items (summarized burden items) for contract projects, but use burden on the same item for capital projects.

Some companies also need to account differently for billable versus not billable expenditures. Such feature is easily done in Projects, and is a lot more complex to achieve using the accounting engine of Cost Management in Inventory. You may set up transaction control in Oracle Projects to derive the billability of Inventory and WIP expenditure items. With the expenditure items marked as billable, you can use Auto Accounting rules of Projects to generate the appropriate accounting based on billability.

The accounting generation for project expenditures is easily configured and maintained when you use only Oracle Projects’ Auto Accounting. Companies which need to account for PJM transactions using rules based on project attributes, project organization, project classification, will find the easiest solution is to use Auto Accounting. Alternatively, achieving the same project-based accounting in Cost Management; would require developing the Accounting Generation Extension. This is a separate tool based on workflow engine, which requires extra development and maintenance effort. Even when you are using SLA in Oracle release 12, the configuration of accounting rules for Project’s source transactions is easier than the need to additionally configure similar rules for Inventory’s source transactions.

Sending all project-related transactions to GL through one source – Projects – eliminates the need to reconcile between project costs and their respective journal entries generated and posted by Inventory. Using the single path also eliminates the need to manage the period close of the inventory organization. Since Inventory would no longer be an accounting source, the closing of accounting periods for each inventory organization can be obsoleted.

All the above mentioned factors call for using a unified tool for generating project-based accounting. Those points become clear advantages when meeting the following two characteristics: Inventory and WIP transactions of a PJM organization are mostly project related; and when accounting rules are based on projects flows of revenue versus costs. If, on the other hand, the majority of Inventory cost is non project, you might not use the recommended method above.

In cases where companies require accounting in GL for significantly high amounts of the Inventory Materials asset account, the alternative method may be favorable. In these cases, using the classic Inventory flow for accounting and interface directly to GL has indeed a significant advantage. When there is high value of non-projects transactions in a PJM organization, those costs will charge a single common project. Oracle Projects, however, does a poor job in accounting for the balance of on-hand inventory by the end of each period. Oracle Projects setup at a PJM organization might not be a good solution for physical inventory based accounting.