What This Actually Is
An Oil And Gas Accounting Manual is the document that tells your finance team how to book, classify, and report every transaction related to petroleum operations. Without one, you're guessing. With one, you're still guessing sometimes, but at least it's documented guessing. Most companies start with something borrowed from AICPA guides or industry templates, then layer in their own field rules. The result is usually a thick binder that lives on a shared drive nobody reads until an auditor shows up.
Why Companies Need a Single Source of Truth
Oil and gas accounting touches revenue recognition, joint interest billing, decommissioning liabilities, intangible drilling costs, and depletion calculations. These areas overlap in ways that trip up even senior accountants. A manual forces people to agree on treatment before disputes happen. It is not a nice-to-have. It is a control requirement for most public companies. I have seen teams debate for weeks whether a workover cost gets capitalized or expensed because two department heads interpreted the same policy differently. A clear manual prevents that kind of waste.
How to Build One From Scratch
Start with the chart of accounts. Map every GL account to a business process. Then write the policy around it. Do not do it the other way around, because then your policies will describe systems that do not exist yet. Here is the practical order most people should follow: First, catalog every transaction type across upstream, midstream, and downstream if applicable. Lease operating expenses,royalty payments, gathering fees, production revenues, impairment tests, and abandonment costs all need separate sections. Second, assign ownership. Every policy should name the person responsible for updates and enforcement. Third, include journal entry templates with required supporting documentation. Fourth, add escalation paths for edge cases.
Get the Full Details
Common Sections That Must Be Covered
Revenue recognition is always the hardest part. You need clear rules for when to book production revenue versus when to accrue it, especially with delay sale arrangements and minuscule volumes that round to zero at the well level. Joint interest billing requires its own chapter. Disputes over overhead allocations and unapproved costs generate more audit findings than almost anything else in this sector. Your manual should spell out the approval workflow and the exact threshold above which a JV participant can challenge a charge. Depletion and depreciation methods deserve honest discussion. The unit-of-production method is standard, but your manual should address what happens when reserve estimates change mid-year. I once worked through a situation where a revised P50 forecast forced us to restate depletion for three quarters retroactively, and the only reason we caught the error early was that our manual required quarterly reassessment reviews with documented sign-off.
Where Most Manuals Fall Apart
They become outdated quickly. I have seen manuals that were three years stale get handed to new hires as if they were current. The best approach is to embed version control and mandatory annual review cycles directly into the document structure, not as an appendix note that gets ignored. Another failure point is vague language. Phrases like "as appropriate" or "per management discretion" create inconsistency. Replace them with decision trees that lead to a specific outcome based on objective criteria.
Practical Implementation Advice
Do not write the entire manual alone. Gather input from land, engineering, operations, and tax. Each department holds knowledge that changes how a transaction should be recorded. If engineering says a well is proved, tax treats it differently than if it is unproved. The accounting manual needs to reflect that linkage. Use a living document format. PDF binders die on shelves. A properly permissioned shared document with change tracking and review workflows actually stays current. I recommend scheduling a quarterly review session with department heads. It takes about forty-five minutes and prevents the kind of drift that creates material weaknesses. Training matters too. A manual nobody reads provides zero protection. Pair it with onboarding checklists and periodic quizzes for staff who handle high-volume entries like daily production postings or monthly JV bill adjustments.
When a Manual Is Not Enough
If your company operates across multiple jurisdictions with different regulatory reporting requirements, a single manual will become unwieldy quickly. In those cases, consider a master policy with jurisdiction-specific addenda. It is messier to maintain but far more defensible during audits. Some organizations also struggle with software limitations. ERP systems often force accounting treatment into rigid structures that do not map cleanly to industry-specific needs. The manual should acknowledge these gaps and describe workarounds explicitly, rather than pretending the system handles everything correctly. The document itself is only as good as the culture behind it. A meticulously written manual gets ignored if leadership treats compliance as a checkbox exercise. Make it a reference tool people actually consult, and the rest follows.
