Title: |
Accruals |
Publication date: |
1/2/2012 |
Effective date: |
12/31/2011 |
BRIEF
Policy Summary
This policy establishes guidelines for accrual accounting requirements for liabilities incurred. Berkeley Lab maintains its accounts and prepares financial statements on the accrual basis of accounting in conformity with Generally Accepted Accounting Principles (GAAP). All obligations for materials received or services performed are to be recognized in the Berkeley Lab Financial Management System (FMS) in the period incurred. A balance should be maintained between the effort required to measure and accrue costs and the added value of that effort.
Who Should Read This Policy
All Laboratory employees with financial responsibilities
To Read the Full Policy, Go To:
The POLICY tab on this wiki page
Contact Information
[General Accounting Manager|../../../../../../../../../../display/rpm2/Contacts+for+Select+Operations+Functions#ContactsforSelectOperationsFunctions-GeneralAcctg]
[Payroll Manager|../../../../../../../../../../display/rpm2/Contacts+for+Select+Operations+Functions#ContactsforSelectOperationsFunctions-Payroll]
[Accounts Payable Manager|../../../../../../../../../../display/rpm2/Contacts+for+Select+Operations+Functions#ContactsforSelectOperationsFunctions-AcctsPayable]
Title: |
Accruals |
Publication date: |
1/2/2012 |
Effective date: |
12/31/2011 |
POLICY
A. Purpose
This policy establishes guidelines for accrual accounting requirements for liabilities incurred. Lawrence Berkeley National Laboratory (Berkeley Lab) maintains its accounts and prepares financial statements on the accrual basis of accounting in conformity with Generally Accepted Accounting Principles (GAAP).
B. Persons Affected
All employees with financial responsibilities at Berkeley Lab
C. Exceptions
Not applicable
D. Policy Statement
D.1 General
- All obligations for materials received or services performed are to be recognized in the Berkeley Lab Financial Management System (FMS) in the period incurred. A balance should be maintained between the effort required to measure and accrue costs and the added value of that effort. This policy is applicable to all incurred obligations for payroll, goods, services, travel, and subcontracts. If not automatically captured in the FMS, liabilities will be measured using accurate, complete, and current information available.
D.2 Procedures
- Payroll will accrue and report all payroll and related liabilities.
- Disbursements will record all nonpayroll obligations.
- The department or division will identify and report to Disbursements all other unrecorded obligations of the Laboratory. Each department or division is responsible for reviewing and analyzing the circumstances that apply to the unrecorded liability, using discretion to determine if a manual accrual is appropriate.
- An accrual is appropriate and required if it is considered material (substantial likelihood that omission of the accrual would affect or influence decisions).
D.3 Accrual Process
- To record a manual accrual in the FMS, the following information must be submitted to Disbursements by the last Thursday before the close of the last month of the accounting period and kept on file as documentation with the requesting department or division:
- Accrual amount
- Beginning and ending date of the accrual period
- Basis and justification for determining amount accrued
- Project ID
- Purchase order/subcontract number
- Resource category
- Indication that the accrual is reversing or nonreversing
D.4 Accrual Criteria
- During the Fiscal Year
- Manual accruals are not required for:
- Services. If the service was provided during the current reporting month, and the invoice was received and approved by month end
- Goods. If the item(s) and the invoice were recorded as received in the FMS in the current reporting month, or if receipt was required, and the item(s) were recorded as received in the FMS, but an invoice was not submitted. (An automatic monthly accrual would be generated in the FMS.)
- Manual accruals determined to be material are required on a fiscal quarter basis for:
- Goods. If the item(s) were received by the department or division, but an invoice was not received
- Services. If the service was provided before the end of the fiscal quarter, but the Laboratory was not billed for the services provided, or if the vendor is custom-building an item or performing on a construction subcontract, an accrual is required for the percentage of the item or subcontract estimated to be completed before the end of the fiscal quarter.
- Manual accruals are not required for:
- At Fiscal Year-End
- Manual accruals are not required for:
- Services. If the service was provided during the fiscal year, the invoice was received by Disbursements, and department or division certification was provided
- Goods. If the item(s) were recorded as received in the FMS prior to the close
- Manual accruals determined to be material are required at fiscal year-end for:
- Goods. If the item(s) were received by the department or divisions, but the invoice was not received by Disbursements by September 30, or If the item(s) were shipped but not received by September 30, and the contract covering the item(s) ordered stipulated freight on board (FOB) shipping point (the Laboratory takes possession when the item is shipped). Documentation is required for the vendor shipping date.
- Services. If the service was provided during the fiscal year, but the invoice was not received by Disbursements by September 30, or If the vendor was custom-building an item or performing on a construction subcontract, an accrual is required for the percentage of the item or subcontract estimated to be completed by September 30.
- Manual accruals are not required for:
E. Roles and Responsibilities
Each department or division is responsible for updating and maintaining an accrual worksheet identifying the current month end balance for each project and the accruals for each purchase order.
The Office of the Chief Financial Officer (OCFO) is responsible for monitoring proper documentation and reconciling the liability accrual accounts. The OCFO will conduct quarterly reviews of selected accrual transactions executed by the departments or divisions to evaluate compliance with policy and the status of the liability accrual accounts.
F. Definitions/Acronyms
Term |
Definition |
Liability |
A present obligation arising from past events that will result in probable transfer of assets or providing of services in the future |
Obligation |
The amount of an order placed, contract award, service received, or similar transaction during a given period that will require a payment during the same or a future period. Such amounts include outlays for which obligations have not been previously recorded and reflect adjustments for differences between obligations previously recorded and actual outlays to liquidate those obligations. All obligations must be supported by written documentation. |
Project ID |
A project identification number used to accumulate, manage and report costs associated with individually funded activities at the Laboratory |
Resource Category |
A type of cost grouped into similar categories. Examples include labor (contract, student, scientific, administrative), travel (foreign and local), and purchases (material and services). |
G. Recordkeeping Requirements
None
H. Implementing Documents
None
I. Contact Information
Manager, General Accounting
Manager, Payroll
Manager, Accounts Payable
J. Revision History
Date |
Revision |
By whom |
Revision Description |
Section(s) affected |
Change Type |
1/2/2012 |
1 |
M. Mock |
Re-format for wiki |
All |
Minor |
DOCUMENT INFORMATION
Title: |
Accruals |
Document number |
11.01.004.000 |
Revision number |
1 |
Publication date: |
1/2/2012 |
Effective date: |
12/31/2011 |
Next review date: |
12/31/2013 |
Policy Area: |
Accounting |
RPM Section (home) |
Financial Management |
RPM Section (cross-reference) |
11.14 |
Functional Division |
OCFO |
Prior reference information (optional) |
RPM Chapter 11, Section 11.14 |
Source Requirements Documents
DOE Accounting Handbook, Chapter 11, Liabilities
Implementing Documents
None