# Presentation: 143341

## Fiscal Year End CloseProcess Overview Seminar

- August 31, 2005 (Perseverance Hall)
- September 14, 2005 (937-302)

## Mentors/Instructors

- Lesta Nadel
- Helena Cheng
- Bridget Haverty
- John Speros
- Barbara Gomez
- Mary Clary

## Agenda

- The big picture
- Information sources
- The close schedule
- Project budget requirements
- Purchasing deadlines
- Accruals, prepaids & travel
- Resource adjustment policy
- Q&A and Discussion

## The Big Picture and Information Sources

- Lesta Nadel
- CFO Field Operations, EH&S

## Year End Close – Why do it?

- By act of Congress, all Federal agencies must close their books on September 30
- LBNL is an integrated contractor – this means that our financial results are rolled up with DOE’s
- All income and expense accounts must be closed out to the balance sheet and accounts reconciled
- All indirect costs must be fully distributed to directly funded projects (ie, zero indirect budget variance overall)

## How Different from Monthly Closes

- September 30 is an artificial line in the sand – equivalent to calendar year for personal income tax or selected fiscal year for businesses
- It is a summing up and accounting of all current fiscal year economic activity
- This means that some last minute costs for which invoices have not been processed will need to be accrued
- Current year cash payments for invoices for goods or services not received by 9/30 or for travel occurring after 9/30 should not be reflected in the current fiscal year expenses (pre-paid expenses)
- Suspense items (costs which have dropped out from closed projectids) must be resolved

## Year End Close Challenges

- Timely review of cost activity and pressing deadlines for corrections
- Tracking status of POs- particularly cross check of items ordered, shipped, received and posted to the ledger
- Accelerated close
- Reconciliation with other DOE sites where applicable

## Information Sources

**ISS Close Hotline:** **486-4684 or *****HUN-GOTH***
**Twice daily close status emails to Network distribution**
**Web Site:** _[http://www.lbl.gov/Workplace/CFO/FY05_Close.html](http://www.lbl.gov/Workplace/CFO/FY05_Close.html)_
**Will include the schedule, forms, contacts and procedure and policy documentation**
**Today at Berkeley Lab Announcements:**  **Beginning September 6****th**
-  **Will include key deadlines and LETS Sweeps with links to relevant details**
**Announcements will also be included on My Blis Portal**
**September Network Scheduled September 15th**
**A high level presentation of key changes and dates**
**Available on the web site**
**Formal Training Classes:**  **Scheduled August 31****st**** and September 14**
**A more detailed review of close functions and procedures**

## Information Sources

- FMS (Project Costing)
- Queries	(Fiscal Year End Folder)
- N-vision
- IRIS
- Cost Browser
- Reports
- BLIS
- B&R status reports

## The Schedule

- Helena Cheng
- General Accounting

## FY 2005 Close Schedule - DRAFT

## FY 2005 Close – Key Dates

- 	Three Soft Closes
- 9/09  1st Soft Close
- 9/15	2nd Soft Close
- 9/21  Final Soft Close

## FY 2005 Close

- A deadline is a deadline!

## FY 2005 Close – Key Dates

- 9/13  Final submission of FY05 proposals, awards, and waiver requests to SPO by 5:00 pm
- 9/16  Requisitions to procurement
- 9/19  Final submission of all PAF forms due to Payroll office by 8:00 am
- 9/20  Final submission of miscellaneous invoice requests to AR by 4:00 pm

## FY 2005 Close – Key Dates

- 9/22  Final requests to open projects (DOE and WFO) in FMS by noon
- 9/23  Final LETS sweep at 5:00pmAll feeders due by 8:00 pm
- 9/27  Final accruals due to AP by 2:00 pm
- 9/28  Final divisional resource adjustments due in FMS and labor adjustments due in HRIS by 10:00 am

## FY 2005 Close – Key Dates

- 10/7  Tentative – New period opens
- 	New FY06 projects opened

## Bridget HavertyBudget Office – Direct Programs

- Direct Programs, Work for Others & Indirect Budgets

- Bridget HavertyBudget Office – Direct Programs

## AGENDA

- Overview of the Close
- Communication
- Project Opening
- Preventive Maintenance
- Indirect Budgets
- Uncosted Balances
- Continuing Resolution

## APPROPRIATION LAW

***No money shall be drawn from the Treasury, but in consequence of Appropriations made by law.***
***US Constitution Article I Section 9 Clause 7***
**All of LBNL’s funding is governed by the Budget Authority we receive from Congress in our appropriations**
***Agencies may not spend, or commit themselves to spend, in advance of, or in excess of appropriations.***
***31 U.S.C. 1341  (Antideficiency Act)***
**We can’t spend before we receive the Budget Authority, and we can’t spend more than we receive in Budget Authority**
***Appropriations shall be applied only to the objects for which the appropriations were made except as otherwise provided by law.***
***31 U.S.C. 1301(a)***
**We have to spend our Budget Authority in the manner our programmatic guidance dictates**

## OVERVIEW

- The Lab is required to manage our **Costs** on all projects at the most detailed funding level
**– ****Fund Type, B&R, BRN, BRN Sub, Program task & Reimbursable Work Order #**
- We are required to manage our **Equipment and Construction Liens** at this same detailed level
- We are required to manage our DOE **Operating Liens** at the Obligational Control Level (Generally the 2 or 4 digit B&R)
**– *****If you have a lien balance that appears to be an issue you will be contacted by the Budget Office September 29******th******              7:00 am-1:00 pm***

## OVERVIEW

- Year End Close Resource Adjustments
**Should use appropriate resource categories and projects**
**Unless they are accruals, should not be reversing**
***No changes can be made to FY 2005 costs after the final round of the year end close***

## COMMUNICATION

*Direct – Bridget Haverty x4409 *_[BPHaverty@lbl.gov](mailto:BPHaverty@lbl.gov)_
*Indirect – Julia Rudniski x4302 *_[JARudniski@lbl.gov](mailto:JARudniski@lbl.gov)_
- Unlike prior years, you are not required to send resource adjustment ID’s to the Budget Office prior to posting for Rounds 2 & 3
- If you are notified to do an adjustment in later Rounds you will need to provide the journal ID to the Budget Office

## COMMUNICATION

- After each round of the Year End Close ...

- B&R Status Reports will be published on the CFO/Budget Office web page at _http://fsdwprod.lbl.gov/cfo/cfobnrList.asp_
- Email will be sent to all divisions identifying cost issues and/or notifying divisions that all cost issues have been identified

## PROJECT OPENING

**FY05 Projects – DOE, WFO & Overhead**
- Projects must be in FMS in requested status by 12:00 noon on Thursday, September 22nd
- No changes should be made to projects after 10:00 pm Thursday, September 22nd until GA opens for FY06
- Do not Close, Open, Reparent, change attributes .....
**FY06 Projects – DOE & Overhead**
- New projects for FY06 and changes to the tree for FY06 (ie effective 10/1/05 or later) will be approved
- Up to Noon, Thursday, September 22rd, please notify the Budget Office in advance
- After GA opens for FY06
**FY06 Projects – WFO**
- New FMS projects will be open after GA opens for FY06 and the awards have been generated

**Note: Labor will go through closed projects with LETS error notice**

## What should I be doing now?
Review project costs
Verify B&R’s and other funding fields for projects
Review commitment balances – open PO’s and trips
Consider what costs might need to be accrued
Make any necessary corrections prior to the September soft closes

- Review project costs
- Verify B&R’s and other funding fields for projects
- Review commitment balances – open PO’s and trips
- Consider what costs might need to be accrued
- Make any necessary corrections prior to the September soft closes

- PREVENTIVE MAINTENANCE

## INDIRECT BUDGETS

**Science Divisions**
- Organization Burden
- Recharges
**Overhead Divisions**
- Organization Burden
- Recharges
- Institutional Overhead Budgets
- G&A, Site Support, Space, Procurement, Travel, TT, NN and S&S

## At fiscal year-end, total recoveries must equal total costs on B&R YN0100000 at fiscal close 

- INDIRECT BUDGETS

## Budget Office plans for Org and Recharge budgets to have a net zero variance at year-end
Let us know of any anticipated variances
Budget Office plans for Overhead Departments to meet their budgets by pool
Let us know of any anticipated variances

- Let us know of any anticipated variances
- Budget Office plans for Overhead Departments to meet their budgets by pool
- Let us know of any anticipated variances

- INDIRECT BUDGETS

## VARIANCE EXAMPLES

- Zero variance by division vs. zero variance by cost pool:

## Timing – Occurs after the Year End Close is complete
Guidance - Will be sent to divisions and posted on the web
Justifications – when needed are for the entire uncosted balance of the program

- Guidance - Will be sent to divisions and posted on the web
- Justifications – when needed are for the entire uncosted balance of the program

- UNCOSTED BALANCES

**Total Uncosted Balance for the program**

**Σ Divisional Uncosted Balances in 9-digit B&Rs**

- =

- The Budget Office will notify divisions about which B&R’s will need a justification
- This is not a deobligation request

## As always there is the probability that we will be under a Continuing Resolution for FY06
We are still obligated to keep our costs within the funds provided
Chicago will be allocating funding based on the WAS’s that have bee received from the Programs 

- We are still obligated to keep our costs within the funds provided
- Chicago will be allocating funding based on the WAS’s that have bee received from the Programs

- CONTINUING RESOLUTION

## Procurements

- John Speros
- Procurement

## Procurement Requisitions

- Procurement will use its best efforts to process requisitions so they can cost in FY05
- Requisitions should be sent to Procurement no later than 9/16 if they are to cost in FY05
- Complex and long lead-time purchases may not cost in FY05

##   Procurement Accruals

- Accrue through Division Contacts:
- One-time Purchase Orders
- Procurement Card (PCard) purchases
- Blanket/R&D/IUT/PSA/Consultant
- B2B System Contracts

**Notes:**
Get your requisitions into Procurement by 9/16 to get them in this fiscal year. We still may not be able to process complex & long lead-time items this FY if in by 9/16.

##   Procurement – One-time POs

- One-time PO Cutoff Dates:
- Orders received by Receiving by 9/23 COB (6:30 pm) will automatically be accrued/costed in G/L
- _FOB Destination_: Orders received after 9/23 and *received* by COB 9/30 must be manually accrued
- _FOB Shipping Point_: Orders not received by 9/23 and *shipped* by 9/30 must be manually accrued
- Pickups: Deliver Packing List/Notify Receiving by 9/23
- Check IRIS or PeopleSoft to determine status; charges posted by 8 am 9/24

**Notes:**
Do not manually accrue POs you expect to be received by 9/23

##   Procurement – PCard Orders

- Procurement Card (PCard) Cutoff Dates:
- _FOB Destination_: Charges posted to the card after 9/22 and material *received* by 9/30 should be manually accrued
- _FOB Shipping Point_: Charges posted to the card after 9/22 and material *shipped* by 9/30 should be manually accrued
- Orders ≥ $1K not posted to the card by 9/22 but received (FOB Destination) or shipped (FOB Shipping Point) by 9/30 should be manually accrued
- Pickups: Deliver Packing List/Notify Receiving by 9/30
- Procurement uploads bank statement at 10 am 9/23; Buyers match charges by 11 am 9/23; Charges post to G/L by 11 am
- G/L postings for orders posted to the card through 9/22 available for lookup on 9/23 (IRIS & PCard software)

**Notes:**
Use the IRIS PCard 2 Quick Report to see if an item was posted.

##   Procurement - Blankets

- Blanket / R&D Subcontract / IUT / PSA / Consultant Agreement Cutoff Dates:
- Charges invoiced and certified by 4:00 pm 9/23 will be automatically costed to September G/L
- Charges ≥ $1K incurred between 9/23 & 9/30 should be manually accrued
- Check G/L posting on IRIS;Contact A/P Representative

##   Procurement – System Contracts

- B2B System Contract Cutoff Dates:
- Orders placed and invoiced by 9/21 COB will post to September G/L
- Orders ≥ $1K placed after cutoff date and received by 9/30 should be manually accrued
- Check G/L posting on IRIS for Boise, VWR, Sigma Aldrich; charges posted on 9/24
- See A/P Representative for others

## Accruals, Prepaids & Travel

- Barbara Gómez
- August 31, 2005

## Accruals – DOE Policy

- DOE Accounting Handbook, Chapter 11
- Liabilities recorded in financial statements shall reflect both invoices received, and accruals for any costs incurred, or assets received for which progress billings, grant reimbursement requests, and other billings have not yet been received.
- Maintain accounts on an accrual basis. Costs and revenues shall be identified with and recorded in the period in which they are incurred, even if receipt of the revenue or payment for the expenditure occurs in a subsequent accounting period.

## Goods
Items received by department, but the invoice was not received by AP
Items were shipped but not received by September 30 and the subcontract terms are FOB shipping point
Services
If the service was provided during the fiscal year but the invoice was not received
Reference LBNL Policy dated March 31, 2005

- Items received by department, but the invoice was not received by AP
- Items were shipped but not received by September 30 and the subcontract terms are FOB shipping point
- Services
- If the service was provided during the fiscal year but the invoice was not received
**Reference LBNL Policy dated March 31, 2005**

**Accrued Liabilities Policy**

**Notes:**
Note:
Materiality is considered when  preparing an accrual.
If goods are received in the system, by September 23, an accrual will not be required even an invoice was not received.

## Prepayments – DOE Policy

- DOE Accounting Handbook, Chapter 7
- Expenses should be prepaid only when required by standard business practice. Standard business practice usually requires prepayment for rent, taxes, royalties, subscriptions, and insurance.
- Prepayments shall be expensed over the period to which they apply.

## Prepayments - LBNL Guidance

- Chapter 7 of the DOE Accounting Handbook states that “Prepayments shall be expensed over the period to which they apply”.
*Example*: You owe $10,000 for a software maintenance contract that runs from July 2005 through June 2006. If you _pay the invoice_ related to this service in September, note on the certification that $2500 is to be charged to your project in FY2005 and that the $7500 balance should be booked as a pre-paid expense.
- General Accounting has a form for prepaid expenses on the OCFO website.
- We do not accrue for recharges for Lab-provided services.

## Non-PO Requests

- Must be received in Accounts Payable by 10:00 am on 9/22 for the following:
- Reimbursements and Requests for Issuance of Check
- Stipends and Honoraria
**Only emergency requests will be processed from September 23 through September 28**

## Travel for Lab Employees

- Divisions should-
- Review all open trips
- Request that Travel Department cancel those trips never taken
- Submit vouchers by cob 9/16
- Travel will accrue cost of trips which
- Are in approved status and TA’s were used
- Will have been completed by 9/30
- Prorated accrual of trips spanning September and October by # days

## Join-the-Staff & Change of Station Travel

- Divisions identify uncosted join-the-staff travel expense
- If not costed by 9/23, complete separate PO accrual form where cost is estimated to be >=$1,000
- Fax to Lisa Erspamer in Travel (FAX 486-6888)
- Lisa will validate amounts as FY’05 expenses and forward to AP for processing

## Year End Close Challenges

- What challenges do you anticipate?
- How can we help you?

## Resource Adjustments

- Mary Clary
- Financial Policy & Training

## What is a Resource Adjustment?

- 	A Resource Adjustment is an online process in which costs are transferred from one LBNL project or account to another.

## Criteria

- A Resource Adjustment is to be made only when it meets the following criteria:

**Necessary**

**Appropriate**

**Fully Documented & Justified**

## Necessary

- When the costs, as originally recorded, were:
- Charged to an intermediate cost objective & need to be allocated to final cost objectives; or
- Coded improperly, thereby, charging wrong project(s), suspense/dropout project(s), or an inappropriate resource category; or
- Where there has been a justifiable & appropriate change in decision as to where a resource is to be used.

## Appropriate

- A Resource Adjustment is appropriate only when costs are:
**Reasonable **(prudent business judgment)
**Allocable** to the receiving project (project receives benefit)
**Not expressly unallowed in Contract 31 **(via Federal Acquisition Regulations – FAR)

## Fully Documented

- Documentation is subject to audit and should be retained for **three years** according to Laboratory archiving policies.
- An email confirmation to the authorized requestor is to be retained with other supporting data.
- Documentation, including all approvals is to be maintained by the originating division

## Approval Threshold

- Resource adjustments of ≥ **$5,000** need approval from a designated approver.
- Threshold definition: The amount of total direct cost  debits or credits of the Resource Adjustment.
- Exception to threshold:
- Month end reversing adjustments/accruals by OCFO
- Recurring service center recharges require a single, annual approval

## Labor Adjustments in HRIS

- Labor adjustments are resource adjustments.
- The same rules apply!

## Justifications – Not So Good

- Moving the unallowable costs of $ from XXXXXX to the appropriate account XXXXXX.
- Project manager did not know who to contact to change project id on telephone services.
- Correction

## Justifications - Better

- Transfer travel costs to benefiting projects. Dr. XXXX erroneously charged XXXXXX for her Dec trip. Her time card shows XXXXXX should be the benefiting project.
- To reallocate Sep04 Fedex charges that inadvertently went into the division dropout acct. because the airbill was missing a project id and/or had an invalid project id listed. This RA will transfer costs to the appropriate benefiting project.
- Employee's effort went to the drop out project ID. This adjustment moves the cost to the correct project ID.

- Questions and Discussion