Partnership Accounting Part IV, currency and volumes.
In previous entries about partnership accounting, I have discussed the unique nature of accounting for partners in this proposed new networked application environment. In Part I, and Part II, I included how the membership of a producer within the joint operating committee might contribute capital, lands or leases, capability or intellectual property to the table. That these values would need to be identified, quantified and equalized before the partnership accounting was completed. The role of chairman would be somewhat diminished and be more equal to the other participants active participation .
In Part III I raised the issue regarding changes in the working interest shares of a property based on certain criteria or events. Imposing a cutoff in which these changes take place within the month. I also discussed the need to account for both accounting months and production months.
Today in Part IV I want to raise the issue of currencies. The operation of a facility may be in a remote area of the globe and be owned by two or more producers located in other countries. This may be a likely scenario considering today's makeup of producers.
I also want to reiterate how this system is built and its impact on the producer. Genesys software will be the core of the application that does the majority of the processing. Developers that build the core will also have plug-ins of their own that will deal with the unique data, information and regulations of a certain jurisdiction. These interfaces will need to handle the presentation of data in the appropriate accounts at the appropriate values. The core algorithm will calculate the nuances of the data elements and the presentation of these will be done by the partner providing the plugin.
Therefore, a producer in Texas may have partners from Canada and Great Britain involved in a large facility in the capital of Turkey. To represent the involvement of each partner in the currency they are regulated to report in, is up to the Genesys core with data representation in each of the four countries mentioned. A difficult task in this era of large currency fluctuations.
Currency translations can take on two distinct characteristics depending on the type of account. The asset's need to be reported at the lower of cost or market value. How is this impacted on each producer if the currency in use by the partner is the U.S. and the Turkish dollar declines precipitously. What happens to some debt or obligation if your home currency declines and your debt is denominated in U.S. dollars?
The second type of currency translation are those that would be associated with the revenue and expense type of accounts. These could also disrupt the makeup of the partnership accounting particularly if the U.S. dollar were to decline to record levels. Does this make the property represent a disproportionate value to each one of the partners?
Another issue respecting these accounts, what if the firm had paid a cash call at the beginning of the work and their was a large currency adjustment between the time the cash call was paid and the monthly statement of operations or expenditures was issued. How are these going to be handled.
The purpose in raising these points in partnership accounting should be clear. The number and types of transactions are taking on a multitude of exceptions that need to be addressed. To make this system functional and useful in this environment will be a test of the technologies. Difficult at this point, but I am confident that given the right amount of time the Java developers will have made the system able to accommodate all these various data elements. I therefore assign the technical risk as low.
In Partnership Accounting Part V, I will be discussing the difficulties in dealing with production volumes. How they are recorded, balancing, custom fees, custom products etc.
[Partnership-Accounting][Genesys][Java]