Setting Up and Generating Federal Government and Statutory Reports

This chapter provides an overview of setting up and generating federal government and Statutory reports and discusses how to:

• Set up FACTS I data.

• Set up FACTS I trees.

• Process and generate a FACTS I flat file.

• Set up FACTS II data.

• Create FACTS II trees.

• Process and generate a FACTS II flat file.

• Define, generate, create, and print SF224, SF1219, and SF1220 reports.

• Define and generate the Fund Balance Reconciliation report.

• Configure the FUND_STATUS.xnv PeopleSoft/nVision Report.

• Set up federal reimbursable agreement accounts in general ledger.

• Use PSnVision for statutory reporting.

Understanding Federal Government and Statutory Reports

This section discusses:

• PeopleSoft federal government reporting.

• PeopleSoft statutory reporting.

PeopleSoft Federal Government Reporting

Federal agencies can produce these reports:

• FACTS I reports

  • FACTS I Validation Report - GLS8310

    This report is generated when you run the FACTS I Validation process. It describes any outstanding issues for each FACTS I edit that is run for your FACTS I accumulated data.

  • FACTS I Online Trial Balance - GLS8311

    This report displays the status of the general ledger account balances along with the corresponding USSGL account attributes based on each treasury symbol. The data for this report is based on the FACTS I staging tables.

• FACTS II reports

  • FACTS II Validation Report - GLS8303

    This report is generated when you run the FACTS II Validation process. It describes any outstanding issues for each FACTS II edit that is run for your FACTS II accumulated data.

  • Ledger with Attributes report - GLS7017

    Use this report to verify the ledger activity for a specific business unit, ledger, fiscal year, period range, adjustment period information, and FACTS tree group.

  • FACTS II Online Trial Balance - GLS8312

    This report enables you to view the status of the general ledger account balances along with the corresponding USSGL account attributes for a specific accounting period. The data for this report is based on the FACTS II staging tables.

• Federal Transaction Register - GLS8501

  This online report displays values at the fund, department, and TAS/TAFS levels for each accounting period along with attributes and attribute values for each ChartField.

• Federal Trial Balance - GLS8500

  This summary trial balance report displays a beginning balance, the total amount of debits and credits, and an ending balance. The data is generated for the specified ChartField combination for the fiscal year, accounting periods, and adjustment periods.

• Reconciliation by Source Report - FIN5001

• Reconciliation by ChartField - FIN5005

• Fund Balance Reconciliation Report - GLS9500

  Run this report following the Fund Balance Reconciliation process, which compares account activity and trial balance data imported from the U.S. Treasury to a federal agency's cash activity. It contains the differences between a federal agency's data and the U.S. Treasury's data.

• SF224 - Statement of Cash Transactions report.

  This monthly report sent to the U.S. Treasury identifies the dollar amounts of confirmed U.S. disbursements and collections for an agency by agency location code and fiscal month. This report is used to ensure agreement between the agency's records of disbursement and collections and those of the U.S. Treasury.

• SF224 - Statement of Cash Transaction Detail report.

  This report includes the detail transactions that make up the totals on the SF224 - Statement of Cash Transactions and the Partial 224 report, and may be used internally for reconciliation purposes.

• Partial 224 report - Statement of Cash Transactions report.

  The Partial 224 report is part of a project of the U.S. Treasury to ultimately phase out the SF224 report over the next several years by having agencies report collection and disbursement activity using the Business Event Type Code (BETC). The Partial 224 report functionality accommodates this future implementation of the BETC by excluding disbursements and collections activity that includes the BETC code. When an agency reports cash activity by the BETC codes, the agency will report only non-BETC coded cash activity and cash reclassifications using the Partial 224 report.

  Note. The Partial 224 report will not be available for use until the US Treasury implements BETC. Contact the U.S. Treasury Financial Management Service (FMS) for its schedule for implementation of the BETC. Until such time as the BETC is implemented by the FMS, continue to produce the SF224 - Statement of Cash Transactions report.

• SF1219 - Statement of Accountability report.

  This report is used to determine the accountability of disbursing officers for funds that are held outside the Department of Treasury (cash on hand) by U.S. Treasury Regional Finance Centers (RFCs) and other nonmilitary agencies that do not do their own disbursing.

• SF1220 - Statement of Transactions According to Appropriations, Funds, and Receipt Amounts.

  This report provides the U.S. Treasury with a monthly statement of payments and collections that are performed by departments and agencies that do their own disbursing.

• SF132 Apportionment and Reapportionment Schedule Report.

  This report defines the apportionment and reapportionment of each appropriation or fund account that is subject to apportionment. The PeopleSoft application provides a template that enables government to design PSnVision reports that adhere to the guidelines for this report. This report can be prepared and printed for submission to the Office of Management and Budget (OMB).

• SF133 Quarterly Report on Budget Execution and Budgetary Resources.

  This report defines whether the budgetary resources are available for obligations, whether the budgetary resources have been obligated and, if obligated, whether the obligated amounts have been spent. The PeopleSoft application provides a template that enables government to design PSnVision reports that adhere to the guidelines for these reports. This report is available in hard copy.

• Federal Agency Financial Statements.

  Federal agencies must submit these financial statements to the U.S. Congress and the OMB. The PeopleSoft-designed templates work with PSnVision and can be modified to create these financial statements based on your agency's requirements.

  • Balance Sheet presents, as of a specific time, the amounts of future economic benefits that are owned or managed by the reporting entity exclusive of items that are subject to stewardship reporting (assets), amounts owed by the entity (liabilities), and amounts that comprise the difference (net position).

  • Statement of Net Cost reports the gross cost that is incurred by the reporting agency less any exchange revenue earned from its activities.

  • Statement of Changes in Net Position reports the changes in net position for the reporting period. Net position is affected by changes in two components, cumulative results of operations and unexpended appropriations.

  • Statement of Budgetary Resources reports how budgetary resources were made available, as well as their status at the end of the period.

  • Statement of Financing reports the relationship between net obligations that are derived from an entity's budgetary accounts and net cost of operations that are derived from an entity's proprietary accounts by identifying and explaining key differences between the two accounts.

  • Statement of Custodial Activity is required for agencies that collect non-exchange revenue for the General Fund of the Treasury, a trust fund, or other recipient activities. The collecting agencies do not recognize as revenue those collections that have been or should be transferred as revenue to others. Rather, they account for sources and disposition of the collections as custodial activity on this statement.

• FUND_STATUS PeopleSoft/nVision Report.

  The U. S. federal government must comply with the Antideficiency Act, which prohibits any federal employee from entering into contracts that exceed the enacted appropriations for the year or purchasing services and merchandise before appropriations are enacted. This report provides funding information for informed management decisions. This nVision template can be modified for your agency's requirements.

  See Configuring the FUND_STATUS PS/nVision Report.

• Federal Reimbursable Agreements.

  Federal agencies and the Department of Defense (DoD) often use reimbursable funding to perform work on behalf of others and then are reimbursed for the work. A reimbursement ID is created based upon an agreement between agencies or an outside organization. This agreement is negotiated before acceptance. Agencies may bill back only the prenegotiated reimbursable amount, which makes it imperative that they can track reimbursable agreements separately from other types of funding, as well as access the current status of the reimbursable amount, billing limit, amount expended against the agreement, and the amounts collected against the agreement.

Note. Navigation paths, descriptions, and examples of most of these reports are in Oracle's PeopleSoft General Ledger Appendix A: Reports.

See Also

General Ledger Reports

PeopleSoft Statutory Reporting

The Government Accounting Standards Board (GASB) 34/35 requires state and local governments and public colleges and universities to submit basic financial statements. The PeopleSoft application provides a template that enables local and state governments and public colleges and universities to design PSnVision reports that adhere to the GASB 34/35 guidelines.

Setting Up FACTS I Data

To set up FACTS I data, use the following components:

• ChartField Attributes (CF_ATTRIBUTES)

• Account (GL_ACCOUNT)

• Fund Code (FUND_DEFINITION)

• Miscellaneous ChartFields (F2_ELEMENT_CF)

Use the FUND_CF component interface to load data into the tables for the Fund Code component. Use the ACCOUNT_CF component interface to load data into the tables for the Account component.

This section provides an overview of FACTS I reporting, lists prerequisites, and discusses how to:

• Set up FACTS I ChartField attributes.

• Set up miscellaneous ChartFields for FACTS I.

Note. The setup of miscellaneous ChartFields applies to both FACTS I and FACTS II.

See Also

Using XBRL to Produce Balance Sheets and Income Statements

Enterprise PeopleTools PeopleBooks: PeopleSoft Tree Manager, “Using PeopleSoft Tree Manager”

Understanding FACTS I Reporting

FACTS I is a federal government electronic reporting feature that federal government agencies use to report the proprietary account balances of the agency, including assets, liabilities, net position, revenues, and expenses in a pre-closing Adjusted Trial Balance (ATB) format. Agencies submit this data to the U.S. Treasury in flat file format for preparation of U.S. Audited Consolidated Financial Statements. The ATB is a list of Standard General Ledger (SGL) accounts in numerical order with pre-closing adjusted balances that are prepared on a specified date and are transmitted by fund group. The total sum of the debit balances must equal the total sum of the credit balances in an ATB. These account balances may include both governmental and nongovernmental totals and are normally stated separately.

Overview of FACTS I Setup

After you set up your U.S. SGL Account ChartFields, Fund Code ChartFields, and any other ChartFields that are used by your agency, FACTS I requires that you set up and associate the following ChartField attributes with your accounts and fund codes, as well as miscellaneous ChartFields:

• Exchange ChartField Attribute - Account ChartField.

• Custodial ChartField Attribute - Account ChartField.

• Budget Subfunction Attribute - Fund Code ChartField.

The FACTS I ChartFields are determined during implementation.

See Setting Up FACTS I Data.

Overview of FACTS I Trees

You also must set up FACTS I trees. These trees determine how the posting level ChartField values roll up to the detail values that are mandated by the U.S. Treasury for FACTS I reporting. After you set up your FACTS I trees, you add them to a FACTS tree group. When you are ready to process your FACTS I data, you identify this FACTS tree group on the Generate FACTS I, Validation Report, and Trial Balance page. The FACTS I trees are:

• Transfer Agency Tree (Common to FACTS I and FACTS II).

  This tree consists of transfer agency levels that contain associated Transfer Agency ChartField ranges where the sum of the accounts roll up into a total amount for each transfer agency to report. Note that the Transfer Agency ChartField is specified on the Miscellaneous ChartFields page under FACTS II Definition. The totals for each transfer agency can also roll up into a total for all the agencies and their associated accounts at a summary level for reporting purposes. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Bureau tree.

  This tree consists of a hierarchy of bureau levels with the ledger values that roll up into them. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Department tree.

  This tree consists of a hierarchy of department levels with the ledger values that roll up into them. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Fund Group tree.

  This tree consists of Fund Group levels with the fund ChartField values that roll up into them. All of these fund group levels and associated fund values roll up to a summary level for reporting purposes. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Account tree.

  This tree consists of levels of Account Types (Assets, Liabilities, and so on) where the totals of associated Account ChartField values roll up into one total for each level, which in turn can roll up into a larger total. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Exchange/Account tree.

  This tree is used to perform the FACTS I validation edits 30 through 33. The tree identifies accounts that require the Exchange attribute value.

• Custodial/Account tree.

  This tree is used to perform the FACTS I validation edits 40 through 43. The tree identifies accounts that require the Custodial attribute value.

• Budget SubFunction/Account tree.

  This tree is used to perform the FACTS I validation edits 52 and 53. The tree identifies accounts that require the Budget Subfunction attribute value.

• FACTS I Transaction Partner tree.

  This tree has levels that represent the categories of transaction partners (federal (F) and non-federal (N) and the breakdown of those categories, such as X for Non-Federal and E for Non-Federal Exception. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Transaction Partner/Account tree.

  This tree is used to perform the FACTS I validation edits 20 through 23. The tree identifies accounts that require the Transaction Partner attribute value.

• Accts. Req. Attributes (accounts requiring attributes) tree.

  The levels of this tree indicate the U.S. Treasury attributes that are required for FACTS I and their associated accounts.

Note. The use of the FACTS I Trading Partner tree is basically equivalent to the use of the FACTS II Transfer Agency tree.

See Setting Up FACTS I Trees.

Overview of FACTS I Processing

After you set up your data and trees, perform these steps to load the Master Appropriation File (MAF) data and generate a FACTS I flat file to send to the U.S. Treasury.

1. Import the U.S. Treasury MAF, FACTS I SGL account, and Trading Partner data.

2. Run the GL_FACTS I application engine to:

   • Generate and store the FACTS I data.

   • Validate the generated FACTS I data and note any errors.

   • Create the FACTS I flat file, provided the validation is error free.

3. Print the FACTS I Validation report.

4. If necessary, correct any validation errors and repeat the cycle until the validation is error free.

See Processing and Generating a FACTS I Flat File.

Prerequisites

Before setting up FACTS I data or regulatory reporting data, complete these procedures:

• Set up FACTS I business units.

• Set up FACTS I SGL accounts.

• Define ChartFields.

See Also

Defining and Using Account Types and Attributes

Pages Used to Set Up FACTS I Data

Setting Up FACTS I ChartField Attributes

The following table describes two account attributes and one fund code attribute. You can use the predefined data that the PeopleSoft application provides in the sample database as a guide to set up your ChartField attributes and link them to your agency's appropriate accounts and fund codes.

Access the ChartField Attributes page.

See Setting Up FACTS I ChartField Attributes.

See Also

Enterprise PeopleTools PeopleBooks: PeopleSoft Tree Manager, “Creating Trees”

Understanding ChartField Summarization with Trees

Setting Up Miscellaneous ChartFields for FACTS I

The two fields that you set up for FACTS I in Miscellaneous ChartFields are Federal or Non Federal Partner and Transfer Agency. The setup of these two fields applies to both FACTS I and FACTS II.

You can change delivered ChartField specifications to any configurable ChartField. For example, you can associate the FACTS I Data Element Transfer Agency with ChartField 2 or any of the configurable ChartFields.

Access the Miscellaneous ChartField page.

See Specifying Miscellaneous ChartFields.

Setting Up FACTS I Trees

To set up FACTS I trees, use the following components:

• Tree Manager (PSTREEMGR)

• FACTS Tree Group (FACTS_TREE_GRP)

• TableSet Control (SET_CNTRL_TABLE1)

This section discusses how to:

• Set up a FACTS I (FACTS II) Transfer Agency tree.

• Set up a FACTS I Bureau tree.

• Set up a FACTS I Fund Group tree.

• Set up a FACTS I Department tree.

• Set up a FACTS I Account tree.

• Set up a FACTS I Exchange/Acct. (account) tree.

• Set up a FACTS I Custodial/Acct. (account) tree.

• Set up a FACTS I Budget Subfunction/Acct. (account) tree.

• Set up a FACTS I (FACTS II) Transaction Partner tree.

• Set up a FACTS I Transaction Partner/Acct. (account) tree.

• Set up a FACTS I accounts requiring attributes tree.

• Set up a FACTS I (FACTS II) Tree Group.

• Configure TablesSet Control for FACTS I processing.

• Configure TableSet Control record group data for FACTS I.

• Configure TableSet Control trees for FACTS I.

Pages Used to Set Up FACTS I Trees

See Also

Setting Up FACTS I Data

Setting Up a FACTS I (FACTS II) Transfer Agency Tree

Create the Transfer Agency tree using PeopleSoft Tree Manager based on this example.

This tree contains nodes for each of the transfer agencies and is used by both FACTS I and FACTS II. If you have decided to use the same ChartField for both Transfer Agency and Transfer Account, then the values in your ledger for that ChartField will represent both Transfer Agency and Transfer Account at the same time. The tree will allow the program to translate the ledger’s combination Transfer Agency/Account value to the Transfer Agency value that is required by U.S. Treasury.

Setting Up a FACTS I Bureau Tree

Using PeopleSoft Tree Manager, set up a FACTS I Bureau tree similar to this example for your organization.

The node values at one level of the tree represent the values that the U.S. Treasury is expecting in the FACTS I flat file. You select this level on the FACTS Tree Group page.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager, ”Introduction to PeopleSoft Tree Manager”

Summarizing ChartFields Using Trees

Setting Up a FACTS I Fund Group Tree

Using PeopleSoft Tree Manager, set up a Fund Group tree similar to this example for your organization .

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I Department Tree

Using PeopleSoft Tree Manager, set up a Department tree similar to this example for your organization .

This tree consists of a hierarchy of department levels with the ledger values that roll up into them. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I Account Tree

Using PeopleSoft Tree Manager, set up an Account tree similar to this example for your organization.

For FACTS I reporting, the Account value is four characters; the node value is 1000 at the ACCDT_TYPE level in the FACTS_ACCOUNT tree.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I Exchange / Acct Tree

Using PeopleSoft Tree Manager, set up an Exchange/Account tree similar to this example.

Note. The FACTS I Exchange / Acct tree requires three nodes: T, X, and X OR T. The node names must be named exactly as specified.

See Also

Enterprise PeopleTools PeopleBook: People Soft Tree Manager

Setting Up a FACTS I Custodial / Acct Tree

Using PeopleSoft Tree Manager, set up a Custodial/Acct tree similar to this example.

Note. The FACTS I Custodial / Acct tree requires three nodes: S, A, and S OR A. The node names must be named exactly as specified.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I Budget Subfunction / Acct Tree

Using PeopleSoft Tree Manager, set up a Budget Subfunction tree similar to this example.

Note. The FACTS I Budget Sunfunction / Acct tree requires no specific node name. This tree has to list only those accounts that require this attribute to be reported.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I (FACTS II) Transaction Partner Tree

Using PeopleSoft Tree Manager, set up a FACTS I Tran Partner tree similar to this example.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I Transaction Partner / Acct Tree

Using PeopleSoft Tree Manager, set up a Transaction Partner / Acct. tree similar to this example.

Note. The FACTS I Transaction Partner / Acct tree requires three nodes: N, F, and N OR F. The node names must be named exactly as specified.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I Accounts Requiring Attributes Tree

Using PeopleSoft Tree Manager, set up a FACTS I Accounts Req Attributes tree similar to this example.

Note. The FACTS I Account Req Attributes tree differs from the FACTS II tree of the same name in that it requires only three nodes: TRADING_ PARTNER, FED_NONFED, and BUDGET_SUBFUNC. The node names must be named exactly as specified.

See Also

PeopeTools PeopleBook: PeopleSoft Tree Manager

Setting Up a FACTS I (FACTS II) Tree Group

Access the FACTS Tree Group page.

Common Trees and Tree Levels	Select the Transfer Agency Tree name and the Tree Level that you created for your organization. This tree is used by both FACTS I and FACTS II.
FACTS I Trees and Tree Levels	Associate the appropriate tree names and the tree levels that you created for your organization with each of the PeopleSoft tree names. These are FACTS I trees only.
FACTS II Trees and Tree Levels	Associate the appropriate tree names and the tree levels that you created for your organization with each of the PeopleSoft tree names. These are FACTS II trees only.

Configuring TableSet Control for FACTS I Processing

Carefully choose the setIDs to be used for the FACTS Tree Group and the FACTS I Trees and configure the TableSet Control setIDs accordingly. Incorrect configuration could result in the unavailability of tree group names or tree names in prompt lists on pages, or in the inability of the FACTS I process to retrieve data.

If your organization has only one business unit and you use only one setID to set up your ChartFields, trees, and tree groups, then your TablesSet Control setIDs should all be the same and do not need changing. Also, if you use more than one business unit that uses the same default setID, then the Control Tables should not need to be modified. However, check the TableSet Control pages for each business unit and setID, using their values as the Set Control Values, to ensure that all tables and trees are using the same setID. Note that the Tree Group table is in the new GL_15 Federal Reports Record Group in the TableSet Control Record Group page.

If you use more than one SetID in your organization for setting up your ChartFields, trees, and tree groups, then you must make sure that each setID that you use is set up correctly in TableSet Controls. The setIDs used in the following steps or chart are only examples:

1. Set up your FACTS I ChartFields, trees, and tree group using the FEDRL SetID.

2. Identify the general ledger business unit (for example, FED01) that you want to use for FACTS I processing.

   Access the SetControl Value (FED01) in TableSet Control. The Default SetID on the TableSet Control Record Group page is the default setID that you set up for the general ledger business unit.

3. Find the GL_15 Federal Reports Record Group and select the setID (FEDRL) for GL_15 to match the setID (FEDRL) that you used to create your tree group.

   The FACTS Tree Group table is a part of the GL_15 Record Group and must have the same setID. This step enables the Tree Group drop-down list box to appear on the Accumulate FACTS I Data page so that you can select a FACTS Tree Group to process.

4. Verify whether the Default SetID (SHARE) on the TableSet Control Record Group page is the same (YES) or not the same (NO) as the setID that you used to set up your trees.

   The FACTS I processes normally refer to the Default SetID in the TableSet Control Record Group page and uses the default setIDs to retrieve the FACTS I tree.

5. If YES, you can save and exit TableSet Control.

6. If NO, you must enter each tree on the TableSet Control - Tree page that has a setID that is different from the Default SetID on the TableSet Control - Record Group page.

7. If you run FACTS I processing on multiple business units, repeat these steps.

Configuring TableSet Control Record Group Data for FACTS I

Access the Record Group page.

Set Control Value	To run the FACTS I Accumulation and Validation processes, you must enter a business unit. The business unit that you use is the set control value that you select to ensure that the FACTS I tree group and trees are accessible during FACTS I processing.
Default SetID	This is the default setID for the general ledger business unit that you entered as your Set Control Value and that you intend to use for processing FACTS I.
Record Group ID and Description	Find the record group ID, GL_15 Federal Reports. This record group contains the FACTS Tree Group table.
SetID	Select a setID for this record group that matches the setID that you used to set up the FACTS Tree Group to use in the Accumulate FACTS I Data process. The selected setID enables you to display a list of FACTS Tree Groups and select the Tree Group name in the Accumulate FACTS Data page that you want the FACTS I process to access. Note. You do not need to change anything on either of the TableSet Control pages if you use only one setID as the default for the business unit that you intend to use for FACTS I processing and for setting up your FACTS I ChartFields, trees, and tree group.

Configuring TableSet Control Trees for FACTS I

Access the TableSet Control - Tree page.

Processing and Generating a FACTS I Flat File

This section discusses how to:

• Load MAF and FACTS I Data.

• Review FACTS I MAF data.

• Set up and generate a FACTS I flat file.

Pages Used to Process and Generate a FACTS I Flat File

Loading MAF and FACTS I Data

Access the Load FACTS I Data page.

FACTS I MAF, SGL Accounts, and Trading Partners	Select one of these options to load the FACTS I MAF, SGL Accounts, or Trading Partner data from a file sent by the U.S. Treasury to general ledger. This data is loaded into database tables for later use when you run the validation. These files are available for download from the U.S. Treasury.
Attached File	Enter the location of the selected file, for example: C:\temp\<filename>.
Run	Select to access the Process Scheduler Request page and run the GL_FACTSIMAF Application Engine process.
	Click to attach the FACTS I file that you want to load.
	Click to delete the attached file in the Attached File field. This action deletes only the file attachment. If you have already clicked this button to upload the file, clicking this button does not delete the data from the database table.
	Click to open and review the contents of an attached FACTS I file.

Reviewing FACTS I MAF Data

Access the Review FACTS I MAF page.

ATB Code	Select a U.S. Treasury code that is associated with a MAF file.
Department	Select if you want to narrow your search to MAF data for a specific department.
Bureau	Select if you want to narrow your search to MAF data for a specific bureau.
Fund Group	Select if you want to narrow your search to MAF data for a specific fund group.
Change Status	Select one of these values: Add Change Delete No Change
Review Status	Select one of these values: Disapprove In Process Review Submitted
	Click this button after you enter the FACTS I MAF criteria.

Setting Up and Generating a FACTS I Flat File

Access the Generate FACTS I File, Validation Report and Trial Balance page.

Language	Select the language for this FACTS I report (only if the language is other than English).
Business Unit	Select the business unit.
Ledger	Select the ledger that applies to this report and is associated with this business unit.
Fiscal Year	Enter the fiscal year that applies to this FACTS I report.
From Period and To Period	Enter the begin and end accounting period range that applies to this FACTS I report. These fields are required.
FACTS Tree Group	Select the FACTS tree group that is associated with your FACTS I trees and tree levels.
Adjustment Period	Select the adjustment periods to include in the output file and select the Include Adjustments check box. You can add more than one row.
Include Adjustments	Select to include adjustment amounts in the output file.
Balance Forward	Select to include beginning balances in the output file.
Include Closing Adjustments	Select to include any adjustment that was made during closing in the output file.
Treasury Symbol Attribute	Select the Treasury Symbol attributes to include in the output file.

Setting Up FACTS II Data

To set up FACTS II data, use the following components:

• Contact Information (F2_CONTACT)

• ChartField Attributes (CF_ATTRIBUTES)

• Fund Code (FUND_DEFINITION)

• Account (GL_ACCOUNT)

• Miscellaneous ChartFields (F2_ELEMENT_CF)

• FACTS II Attribute Cross Reference (F2_ATTRIB_XREF)

• Treasury Symbol Cross Ref (F2_TSYM_XREF)

Use the FUND_CF component interface to load data into the tables for the Fund Code component. Use the ACCOUNT_CF component interface to load data into the tables for the Account component.

This section provides an overview of FACTS II reporting, lists prerequisites, and discusses how to:

• Enter FACTS II contact information.

• Create the preparer file.

• Set up ChartField attributes.

• Link attributes ChartFields.

• Select ChartField attributes.

• Link account attributes and values to account ChartFields.

• Specify miscellaneous ChartFields.

• Maintain program reporting category (PRC) codes.

• Set up ChartField attribute cross-references.

• Select attribute cross-references for FACTS II accounting edits.

• Load MAF data.

• Review MAF file.

• Set up the FACTS II Treasury Symbol cross-references.

Understanding FACTS II Reporting

FACTS II is a federal government electronic reporting of budgetary account data that is used for quarterly reporting to the U.S. Treasury. It must:

• Record financial transactions with the required attributes.

• Import data from the U.S. Treasury MAF for use in FACTS II processing.

• Accumulate fund, account, and other relevant data.

• Perform accounting edits on the FACTS II input files.

• Produce a FACTS II Accounting Edit Validation report.

• Generate a FACTS II flat file to send to the U.S. Treasury as input to GOALS.

Note. FACTS I is a separate feature that produces proprietary accounting data in the FACTS I file format for the U.S. Treasury.

See PeopleSoft Federal Government Reporting.

Overview of FACTS II Setup

To set up FACTS II data:

1. Enter the FACTS II contact data.

2. Create the preparer file and send it to the U.S. Treasury.

3. Set up the Account and Fund Code ChartField attributes and attribute values.

4. Associate the appropriate attribute values with the Fund Code and Account ChartField values.

5. Specify the Miscellaneous ChartFields for PRC, Cohort Year, Federal or Non-Federal Partner, Transfer Account, and Transfer Agency.

6. Set up the attribute cross-reference data.

7. Review your ChartField attributes for accuracy.

8. Load the MAF data that was obtained from the U.S. Treasury with any associated PRC codes.

9. Review the MAF data containing Treasury Symbols.

10. Set up the Treasury Symbol cross-reference data.

11. Review and maintain the PRC codes.

Overview of FACTS II Trees

You must set up these FACTS II trees and a FACTS tree group:

1. FACTS II Acct Rollup tree.

   This tree enables an agency's posting accounts to roll up to the SGL account structure that is required for FACTS II reporting.

2. FACTS II Cohort Year tree.

   This tree enables any agency's cohort year ChartField values to roll up to a cohort year structure for FACTS II reporting.

3. FACTS II Category A tree.

   This tree represents the Category Program ChartField values, the three-digit program sequence number, and the Category A program descriptions that are required by the FACTS II Treasury input file.

4. FACTS II Category B tree.

   This tree represents the Category Program ChartField values, the three-digit program sequence number, and the Category B program descriptions that are required by the FACTS II Treasury input file.

5. Accounts Requiring Attributes tree.

   This tree represents the U.S. Treasury attributes and their associated accounts.

6. Transfer Agency tree.

   This tree represents the U.S. Treasury department's two-digit federal transfer agency codes and the ledger values that are translated to these codes.

7. Transfer Account tree.

   This tree represents the Treasury department’s four-digit federal transfer account codes and the ledger values that are translated to these codes.

8. Transaction Partner tree.

   This tree represents the three types of transaction partners—Federal, Non Federal, and Non Federal Exceptions—that are translated to these codes.

9. Set up the FACTS tree group using the appropriate tree names and levels for the trees listed previously.

Overview of FACTS II Processing

To generate and process FACTS II data.

1. Run the GLS8302 process to accumulate the FACTS II data.

2. Review the accumulated FACTS II data for accuracy.

3. Run the GLS8303 process to validate the FACTS II data.

4. Review the validation results and, if necessary, correct configuration or other data, and repeat steps 1 through 3.

5. Create the FACTS II flat file to send to the U.S. Treasury.

6. Run GLS7017 Ledger with Attributes Report to verify the accuracy of the data.

7. Send FACTS II file to the U.S. Treasury.

Note. These rules are defined in the U.S. Treasury’s SGL Account Attributes Required for FACTS II Reporting of Detailed Financial Information on the U.S. Treasury’s website.

Prerequisites

Before setting up FACTS II data or regulatory reporting data, complete these procedures:

• Set up FACTS II business units.

• Set up FACTS II SGL accounts.

• Define ChartFields.

See Also

Defining and Using ChartFields

Pages Used to Set Up FACTS II Data

Entering FACTS II Contact Information

Access the FACTS II Contact Information page.

Contact ID	Enter a U.S. Treasury ID number to add or modify information about your agency’s FACTS II contact personnel.
First Name and Last Name	Enter the first and last names of the FACTS II preparer.
Phone Number, Phone Ext, Fax Number, and Email Address	Enter the telephone number, phone extension, fax number, and email address of the preparer.
Mother's Maiden Name	For security purposes, enter the maiden name of the preparer’s mother.
Supervisor Name, Supervisor’s phone number, and Supervisor’s Phone Ext.	Enter the name, phone number, and phone extension of the preparer’s supervisor.
Agency Name	Enter the name of the agency that is responsible for submitting FACTS II data.
Bureau Name	If the FACTS II data represents a bureau or division of the agency, enter that name.
Address Line 1, Address Line 2, City, State, Country, and Postal Code	Enter the agency’s street address (the second line is for information such as building or suite number), city, state, country, and postal code.
Last Update Date/Time	Each time you save this record, this field is updated.

Creating the Preparer File

Access the FACTS II - Create Preparer File page.

Contact File	Enter a contact file name with a .TXT extension. Do not enter the entire path.
Reporting Year and Reporting Month	Enter the year and month for this FACT II submission.
Preparer Identification	Select the preparer’s identification number. You can select more than one.
Run	Click to access the Process Scheduler Request page to run the Create FACTS Preparer File process (GL_F2CONTACT).

Setting Up ChartField Attributes

Access the Attributes - ChartField Attribute page.

Note. You can also use ChartField Attributes for non-FACTS II purposes.

Most field values on this page are based on the ChartField Attributes table that follows the field descriptions for this page.

Important! FACTS I and FACTS II rely on only one attribute being associated with each respective ChartField. The option to allow multiple values per attribute should not be used with FACTS I and FACTS II attributes.

ChartField Attributes Table

The ChartField Attributes table lists the ChartField attributes that you must set up for FACTS II:

Linking Attributes ChartFields

Access a ChartField such as Account, Fund Code, or Budget Reference that requires attributes.

Attributes

Click this link to associate the ChartField attributes that you set up for FACTS II with the appropriate Account value (or Fund Code ChartField value on the Fund Code page or Budget Reference ChartField value on the Budget Reference page) that is required for FACTS II reporting.

Selecting ChartField Attributes

Access the ChartField Attributes page.

After selecting the Attributes link, a row that contains values for SetID, ChartField Value, Effective Date, and Field Name appears.

See Also

Adding Fund Code Values

Linking Account Attributes and Values to Account ChartFields

Access the appropriate Account page.

Specifying Miscellaneous ChartFields

Access the Miscellaneous ChartFields page.

Note. You can change the delivered ChartField specifications to any configurable ChartField. For example, the FACTS II Data Element FED_NONFED is associated with Transaction Partner. You can change this to any other configurable ChartField. However, you must use different ChartFields for each of the FACTS II Data Elements. The exceptions to this rule are the ChartFields for Transfer Account and Transfer Agency. They can use the same configurable ChartField or two different ChartFields. In this example, Trading Partner is associated with both of these FACTS II Data Elements. Your decision to use either a single ChartField for Transfer Agency and Transfer Account or separate ChartFields has an effect on how you will enter data into your ledger. Some of these ChartField names are the result of a ChartField configuration.

See Also

Adding Fund Code Values

Adding Account Values

Maintaining PRC Codes

Access the Program Reporting Category page.

Maintain PRC codes by MAF Treasury Symbol.

Enter a MAF Treasury Symbol and view its existing PRC codes and the descriptions that you downloaded from a MAF or that you manually entered using this page.

Setting Up ChartField Attribute Cross-References

Access the FACTS II - Attribute Cross Reference page.

Note. Existing customers who are implementing this enhancement should reopen the Attribute Cross Reference and Accounting Edits pages and enter the ChartField Attribute names for the new data elements that are introduced by this enhancement.

Description	These are the predefined attributes that the FACTS II processes requirements of the U.S. Treasury.
ChartField	The PeopleSoft application predefines the Field Name for ACCOUNT, FUND_CODE. and BUDGET_REF.
ChartField Attribute and ChartField Attribute Value	Select the ChartField attributes and attribute values that you defined as cross-references to each data element. Note. The values selected are only examples.

Selecting Attribute Cross-References for FACTS II Accounting Edits

Access the Accounting Edits page.

ChartField Attribute and ChartField Attribute Value

Select the attributes and attribute values that you defined to cross-reference each of the predefined data elements that is listed on this page.

Note. Refer to Review FACT II Data, Detail Attributes to review attributes for each ChartField value for a selected business unit and period.

Loading MAF Data

Access the Load MAF Data page.

Click the Add Attachment button and type the path and file name, or click the Browse button to navigate to the MAF location. Click the Upload button to store the file as an attachment. The file name appears in the Attached File field. At the beginning of each fiscal year, the U.S. Treasury sends a MAF containing the U.S. Treasury account fund symbols (TAFS) for a specific agency along with the preparer and certifier IDs for each symbol. With this data, the U.S. Treasury sends a spreadsheet containing the attributes for each SGL account. You can use this spreadsheet to validate that your data is set up correctly.

Run

Click to upload the file using the PS/GL MAF Load (F2_MAF_LOAD) process. This process loads the file’s data to the appropriate database table.

Note. The Add, Delete, and View Attachment buttons work the same way as they do for FACTS I.

See Loading MAF and FACTS I Data.

Reviewing the MAF File

Access the Review MAF Data page.

MAF T.Symbol (master accounting file treasury symbol)	Stores the Treasury Symbol in the format that is defined by the U.S. Treasury for FACTS II processing. This Treasury Symbol is different from the Treasury Symbol format that is required by most other U.S. Treasury reporting.
MAF Seq Num (master accounting file sequence number)	The U.S. Treasury supplies this number. If the U.S. Treasury sends the agency a new MAF file, this number is incremented.
Record Type 7 TAS (record type 7 treasury appropriation fund symbol)	The application displays a three-digit numeric code that is attached to the end of the Treasury Appropriation Fund Symbol. This code identifies the type of fund resources, such as Fund Held Outside of the Treasury, Authority to Borrow from the Treasury, and Unrealized Discounts.
Dept Reg (department regular)	Displays a regular (versus a transfer) department number that is associated with this MAF Treasury Symbol.
Dept Trans (department transfer)	Displays a transfer (versus a regular) department number that is associated with this MAF Treasury Symbol.
Fiscal Year TAS (fiscal year treasury appropriation fund symbol)	Displays the funding period of the appropriation that applies to this MAF Treasury Symbol.
Main Acct (main account)	Displays the main account that is used for this MAF Treasury Symbol.
Sub Acct (sub account)	Displays a sub account that is used for this MAF Treasury Symbol.
Acct Split Seq (account split sequence)	Displays the account split that is provided by the Office of Management and Budget interface file. Any number that is greater than 000 is an account split.
Pre-closing Balance	Displays this department's remaining appropriation balance prior to the close of the fiscal year.
Net Outlays	Displays the net collections and disbursements that are reported to date to the U.S. Treasury by this department for the current fiscal year.
Master Preparer Ind (master preparer indicator)	Identifies whether a master preparer is required. This value is only necessary if an account split applies to this account.
Acct Split Alloc Ind (account split allocation indicator)	Indicates whether the master preparer divided the account balance among the members of an account split.
Preparer Identification	Displays the FACTS II preparer’s name for this department.
Chapter	Displays the chapter number that is used in the U.S. Treasury's Annual Report.
GOALS Flag (Government On-line Accounting Link System flag)	Indicates that the FACTS II file can be imported to the Government On-line Accounting Link System (GOALS).
Appropriation Flag	Indicates that an appropriation is associated with this MAF Treasury Symbol.
Certify Flag	Indicates whether this MAF Treasury Symbol is required by the Budget Reports Branch of the Financial Management Service.
Borrow Flag	Indicates whether a borrowing source is required for this MAF Treasury Symbol.
Bulk/Non-Bulk Flag	Y indicates that you want to send the FACTS II information in a bulk transfer file. N indicates that you want to send the FACTS II information in a non-bulk transfer file.
FMS Source Indicator (Financial Management Services source indicator)	The FMS interface indicator.
OMB Source Indicator (Office of Management and Budget source indicator)	The OMB interface indicator.

Setting Up the FACTS II Treasury Symbol Cross-References

Access the Treasury Symbol Cross Reference page.

SetID	Select the setID that applies to the FACTS II reporting data.
Treasury Symbol Attribute	Select the attribute that corresponds to the MAF Treasury Symbol.
MAF Treasury Symbol (master accounting file treasury symbol)	Select the MAF Treasury Symbol, which is imported from the U.S. Treasury MAF file.
Cancelling Year	Select this option if the Treasury Symbol is beyond the cancelling year. FACTS II determines the cancelling year by adding six years to the last year of availability. You must select this option to enable Edit 10 to process.
After Expiration Year	Select this option if this Treasury Symbol expired. If a Treasury Symbol expires, zero-balanced rows cannot be reported to the FACTS II Import file. To identify the accounts that are associated with an expired Treasury Symbol, you must select the Ignore on Expiration (IGN_ON_EXP) attribute and select Y for the attribute value on the Attribute Xref page.

Creating FACTS II Trees

To set up FACTS II trees, use the following components:

• Tree Manager (PSTREEMGR)

• FACTS Tree Group (FACTS_TREE_GRP)

• TableSet Control (SET_CNTRL_TABLE1)

This section discusses how to:

• Use trees to control the roll-up of ChartField data.

• Create a FACTS II Account Roll-up tree.

• Create a Cohort Year tree.

• Create a Category A tree.

• Create a Category B tree.

• Create the Accounts Requiring Fund Attributes tree.

• Create the Transfer Agency tree.

• Create the Transfer Account tree.

• Create the Transaction Partner tree.

• Create a tree group for FACTS II.

• Configure TableSet Control for FACTS II processing.

• Configure the TableSet Control Record Group page.

• Configure the TableSet Control Tree page.

Pages Used to Create FACTS II Trees

See Also

Using Trees to Summarize ChartFields

Enterprise PeopleTools PeopleBooks: PeopleSoft Tree Manager

Using Trees to Control Roll-Up of ChartField Data

Your Account, Fund Code, or other ChartField values may not match those specified by U.S. Treasury for reporting purposes. To accommodate these mandates, you must create trees that contain nodes representing the account or other ChartField values required by the U.S. Treasury for FACTS reporting. Under these nodes, you specify the actual detail values that are used in your ledgers, which roll up into the U.S. Treasury values for reporting. The FACTS II process finds the tree node names when it accumulates reporting data and uses these names when it creates the reporting files. In general, the tree node names should follow the field specifications of the U.S. Treasury file.

You use the PeopleSoft Tree Manager to create all trees. You can use the tree names, level names, and structure IDs that appear in the following examples, or you can create your own.

You can copy an existing tree structure or create a new one.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

Creating a FACTS II Account Roll-up Tree

Create a FACTS II Account Roll-up tree in PeopleSoft Tree Manager similar to this example. Before you create this tree, you must define your Account ChartField values and determine your detail structure.

The FACTS II Account Roll-up Tree stores the hierarchical relationship between SGL accounts that you report to the U.S. Treasury for FACTS II and an agency’s posting accounts. The FACTS II Accumulation process uses this tree to roll up the posting level account ChartField values into the SGL accounts. Each agency may have a different combination of lower-level posting accounts that roll up to an SGL account structure that is mandated by the U.S. Treasury for FACTS II reporting. Determine the lowest level of detail that you need for your Account ChartField structure to capture all possible combinations of USSGL accounts and FACTS II attributes, as well as additional agency-specific posting detail.

Your agency can use any tree and level names as long as you specify these names on the FACTS II Tree Group. You must create the FACTS II Account Roll-up Tree to run the Accumulate FACTS II Data process.

Creating a Cohort Year Tree

Create a Cohort Year tree similar to this example.

Create a Cohort Year tree at the COHORTYEAR tree level for each cohort year based on your agency’s reporting needs. Enter the appropriate detail values that identify which ChartField values (loans) roll up to a particular cohort year.

The Cohort Year tree is the exception to the rule that the FACTS II tree node names should always match the values that are required by US Treasury. In this instance, Cohort Year values in the FACTS II file are only two positions. However, the tree is set up with four character node names to keep it consistent with the Cohort Year tree in earlier releases, as well as with the way the program derives the Cohort Year values. The program will take the third and fourth character of the node name to derive the FACTS II file Cohort Year values, for example, 2005 becomes 05 in the FACTS II file.

The Accumulate FACTS II Data process uses this tree to identify ChartField values that represent loans associated with a cohort year for the production of the FACTS II Treasury input file. In this example, the loan numbers roll up to the COHORTYEAR tree level, which contains the cohort year information that is required for FACTS II reporting. You may also use a different configurable ChartField for this purpose. Because an agency may have projects that are not loans and are not associated with a cohort year, this tree is used to distinguish between the two types of project ChartField values. Each agency should determine the ChartField structure that it needs to satisfy its cohort year requirements.

Note. You must set up the ChartField values prior to creating this tree.

Creating a Category A Tree

Create a Category A tree in PeopleSoft Tree Manager based on this example.

The Accumulate FACTS II Data process uses this tree to identify category A programs and to extract the three-digit program sequence number and category A program description that is needed for the production of the FACTS II Treasury Input file. Your agency may have programs that are both category A and non-category A programs. This tree is useful to distinguish between the two. Each agency should determine the ChartField structure that satisfies its category A and non-category A reporting requirements. The tree level that is specified on the FACTS Tree Group page identifies the node values and node descriptions that contain the three-digit sequence number and category A program description, respectively.

The OMB supplies and requires the input of Program Reporting Categories for Category A apportioned funds when an SGL account contains a Y in the Program Rpt Code (program reporting code) column of the Fiscal 200X USSGL Account Attributes Required Table. The OMB provides valid Program Reporting Categories from which Federal Program Agencies (FPAs) can choose. The OMB list of Program Reporting Categories serves as a control table or as a reference table for FACTS II reporting.

FPAs cannot use the OMB-supplied program reporting numbers with the FPA's own titles. The FPA is also restricted by FACTS II from using the default program number and description, 99 All Programs, with other OMB program codes and descriptions or the FPA's custom program codes and descriptions.

If OMB does not provide specific program reporting categories, then the FPA can use the default program reporting number (99) and description (All Programs).

While an FPA can use numbers and descriptions for program reporting categories in addition to those that are supplied by the OMB , they cannot use the 99 All Programs program reporting category with any other codes. If the FPA attempts to add the 99 All Programs category to existing program reporting categories for obligation activity, the FACTS II rejects that input because the 99 All Programs category can only be used by itself.

You can use any tree name and level name as long as you specify the desired tree name and level name on the Accumulate FACTS II Data page. This tree is required for the Accumulate FACTS II Data process (GLS8302).

Note. You must set up Program ChartField values before creating the Category A tree.

Creating a Category B Tree

Create a Category B tree in PeopleSoft Tree Manager based on this example.

The Accumulate FACTS II Data process uses this tree to identify category B programs and to extract the three-digit program sequence number and category B program description that is needed for the production of the FACTS II Treasury Input file. Your agency may have programs that are both category B and non-category B programs. This tree is useful to distinguish between these two types of programs. Each agency should determine the ChartField structure that satisfies its category B and non-category B reporting requirements. The tree level that is specified on the FACTS Tree Group page identifies the node values and node descriptions that contain the three-digit sequence number and category B program description, respectively.

You can use any tree name and level name as long as you specify the tree name and level name that you want on the Accumulate FACTS II Data page. This tree is required for the Accumulate FACTS II Data process (GLS8302).

Note. You must set up Program ChartField values before creating the Category B tree.

Creating the Accounts Requiring Fund Attributes Tree

Create an Accounts Requiring Fund Attributes tree using PeopleSoft Tree Manager based on this example.

The FACTS II Accounts Requiring Attributes tree stores the relationship between the ChartField attributes that are required for FACTS II processing and their associated SGL accounts.

This tree filters out the attributes for accounts that do not require certain attributes to be reported. After the FACTS II Accumulation process accumulates all the attribute data, it checks the accumulated attributes against this tree to determine whether they are required to be reported. If the attribute is not required, it is removed from the staging table and is not included in the FACTS II file. To determine the attributes to be reported for any given account, the program takes the account from the ledger (such as 4119) and searches for the account in the FACTSII_ATTRIBUTES tree. The account may appear under numerous nodes depending on which attributes are required for that specific account. Wherever the program finds the account in the tree, the attribute is considered as required for reporting. If the program has previously accumulated an attribute value for the account, but is unable to locate the account under that respective attribute’s node, the accumulated attribute value will be excluded from the FACTS II file.

The F2_REQ_ATTR_ACCTS Tree and ACCOUNT Level are examples of values that the FACTS II processes can use. You can create your own tree name and level name, as long as you specify the tree name and level name on the FACTS Tree Group page. You must set up this tree to run the Accumulate FACTS II Data process (GLS8302) and the GL Activity with Attributes Report (GLS7017).

Make sure that this tree consists of all accounts that are required by the U.S. Treasury for each attribute. If your agency does not use an account that the U.S. Treasury requires, then the agency does not have to define the account on this tree. The fund code and account ChartField attributes are predefined and delivered in the PeopleSoft sample data.

Four node names must be named exactly as specified:

• PUBLIC_LAW

• FED_NONFED

• TRF_AGENCY

• TRF_ACCT

All other nodes must be named exactly the same as the attributes that are listed on the Attribute Xref page. For example, if the user has called their Authority Type attribute AUTH instead of AUTHORITY, then the node name must be AUTH.

These attribute nodes are not required on the Accounts requiring Attributes tree:

• The Normal Balance, Debit and Credit, and Begin End attributes because they are always required to process FACTS II. The program does not check against this tree for these attributes.

• The TAFS status attribute because it is not required in the FACTS II flat file.

• The Transfer To/From and Deficiency Flag because these values will be derived by the U.S. Treasury.

Note. The U.S. Treasury’s SGL Account Attributes Required for FACTS II Reporting of Detailed Financial Information defines these rules. This information is available at the U.S. Treasury Department’s website.

Creating the Transfer Agency Tree

Create the Transfer Agency tree using PeopleSoft Tree Manager based on this example.

This tree contains nodes for each of the transfer agencies. If you have decided to use the same ChartField for both Transfer Agency and Transfer Account, then the values in your ledger for that ChartField will represent both Transfer Agency and Transfer Account at the same time. The tree will allow the program to translate the ledger’s combination Transfer Agency/Account value to the Transfer Agency value that is required by the U.S. Treasury.

Creating the Transfer Account Tree

Access Tree Manager to create the FACTS II Transfer Account tree.

This tree contains nodes for all the U.S. Treasury transfer accounts. The leaves are made up of ChartField values from your ledger representing Transfer Accounts. If you decide to use the same ChartField for both Transfer Agency and Transfer Account, then the values in your ledger for that ChartField will represent both Transfer Agency and Transfer Account at the same time. The tree allows the program to translate the ledger’s combination Transfer Agency/Account value to the Transfer Account value that is required by U.S. Treasury.

Creating the Transaction Partner Tree

Access Tree Manager to create the FACTS Transaction Partner tree.

The three nodes on this tree represent the three types of Transaction Partners: Non-Federal, Federal, and Non-Federal Exception. The leaves represent all the detail transaction partner ledger data that roll up into each type of Transaction Partner for FACTS II processing.

Before this release update, you had to set up variations of account numbers to indicate whether the account used in any particular transaction pertained to another federal organization. You did this by adding suffixes to account numbers. For example, the suffix G was added to account 1610 to create account 1610G. Also, the XPARTNER attribute was only capable of indicating one attribute value at a time. Now, the PeopleSoft system enables you to use one of the configurable ChartFields to record the Transaction Partner attribute. This means that the Transaction Partner attribute is independent of the Account ChartField, which eliminates the need to create and use variations of the same account.

If you are an existing customer, you can use the new separate ChartField approach or you can continue to use the multiple account approach. If you have used the multiple account approach in the current year, you must continue to use this approach until you get to the end of the year because all of your existing year-to-date data uses this method.

If you are using the older method, your Transaction Partner tree is designed differently and should be based on the following example:

Node ALL - All Transaction Partners

• Node E - NonFederal Exception

  • 1010 E

  • 1020E

• Node F - Federal

  • 1010G

  • 1020G

• Node X - Non Federal

  • 1010X

  • 1020X

Creating a Tree Group for FACTS II

Access the FACTS Tree Group page.

See Setting Up a FACTS I (FACTS II) Tree Group.

Configuring TableSet Control for FACTS II Processing

Carefully choose the setIDs to be used for the FACTS Tree Group and the FACTS II Trees, and configure the TableSet Control setIDs accordingly. Incorrect configuration can result in the unavailability of tree group names and unavailability of tree names in prompt lists on pages, or in the inability of the FACTS II process to retrieve data.

If you have only one business unit in your organization and use only one setID to set up your ChartFields, trees and tree groups, then your TablesSet Control setIDs should all be the same and do not need changing. Also, if you use more than one business unit that uses the same default setID, then the Control Tables should not need to be modified. However, check the TableSet Control pages for each business unit and setID, using their values as the Set Control Values, to ensure that all tables and trees use the same setID. Note that the Tree Group table is in the new GL_15 Federal Reports Record Group in the TableSet Control Record Group page.

If you use more than one SetID in your organization for setting up your ChartFields, trees, and tree groups, then you must make sure each setID that you use is set up correctly in TableSet Controls. The setIDs used in the following steps are only examples; your organization might use different setIDs.

1. Set up your FACTS II ChartFields, trees, and tree group using the FEDRL SetID.

2. Identify the general ledger business unit (for example, FED01) that you want to use for FACTS II processing.

   Access the SetControl Value (FED01) in TableSet Control. The Default SetID on the TableSet Control Record Group page is the default setID that you set up for the general ledger business unit.

3. Find the GL_15 Federal Reports Record Group and select the setID (FEDRL) for GL_15 to match the setID (FEDRL) that you used to create your tree group.

   The FACTS Tree Group table is a part of the GL_15 Record Group and must have the same setID. This step enables the Tree Group drop-down list box to appear on the Accumulate FACTS II Data page so that you can select a FACTS Tree Group to process.

4. Verify whether the Default SetID (SHARE) on the TableSet Control Record Group page is the same as the setID that you used to set up your trees.

   The FACTS II processes normally refer to the Default SetID in the TableSet Control Record Group page and use the default setIDs to retrieve the FACTS II tree.

5. If YES, you can save and quit TableSet Control.

6. If NO, you must enter each tree on the TableSet Control - Tree page that has a setID that is different from the Default SetID on the TableSet Control - Record Group page.

7. If you run FACTS II processing on multiple business units, repeat these steps.

Configuring the TableSet Control Record Group Page

Access the TableSet Control - Record Group page.

Set Control Value	To run the FACTS II Accumulation and Validation processes, you must enter a business unit. The business unit that you use is the set control value that you select to ensure that the FACTS II tree group and trees are accessible during FACTS II processing.
Default SetID	This is the default setID for the general ledger business unit that you entered as your set control value and that you intend to use for processing FACTS II.
Record Group ID and Description	Find Record Group ID GL_15 Federal Reports. This record group contains the FACTS Tree Group table.
SetID	Select a setID for this record group that matches the setID that you used to set up the FACTS Tree Group to use in the Accumulate FACTS II Data process (GLS8302.) The selected setID enables you to display a list of FACTS Tree Groups and select the Tree Group name in the Accumulate FACTS Data page that you want the FACTS II GLS8302 process to access. Note. You do not need to modify either of the TableSet Control pages if you use only one setID as the default for the business unit that you intend to use for FACTS II processing and for setting up your FACTS II ChartFields, trees, and tree group.

Configuring the TableSet Control Tree Page

Access the TableSet Control - Tree page.

Tree Name

Add any FACTS II trees that are set up using a setID that is different from the default SetID on the Record Group page.

Processing and Generating a FACTS II Flat File

This section discusses how to:

• Review the FACTS II data setup.

• Accumulate the FACTS II data.

• Review the FACTS II header information.

• Review the FACTS II detail balances.

• Review the FACTS II detail attributes.

• Review and modify FACTS II footnotes.

• Validate the FACTS II data.

• Create the FACTS II file.

• Run the Ledger with Attributes report.

Note. Make sure you have completed all the preceding FACTS II tasks before you start the tasks in this section.

Pages Used to Process and Generate a FACTS II Flat File

Reviewing the FACTS II Data Setup

Access the Review ChartField Attributes page.

SetID, ChartField, Attribute, Attribute Value, and As Of Date

Select the appropriate criteria for a query that enables you to verify that your attributes are set up correctly before you run the Accumulate (GLS8302) process.

Accumulating the FACTS II Data

Access the Accumulate FACTS II Data page.

Unit	Select the business unit for this FACTS II data.
Report ID	Enter the FACTS II report identification for your agency.
Reporting Year and Reporting Month	Enter the reporting year and month for this FACTS II file.
Fiscal Year	Enter the fiscal year for this FACTS II data.
FACTS Tree Group	Select the FACTS tree group for FACTS II processing.
From Period and To Period	Enter the accounting periods for this accumulated data for the previously entered fiscal year.
Include Closing Adjustments	Select to include closing adjustments in your FACTS II data.
Adjustment Period	Select the adjustment periods that you want to include in the accumulation of this FACTS II data. You have one or more rows.
Treasury Symbol Attribute	Select the Treasury Symbol attribute that is associated with the funds that you are using in your FACTS II data.
Preparer ID and Certifier ID	Select the ID of the preparer of the data for this Treasury Symbol attribute and the ID of the person who certified this preparer’s FACTS II data.

Reviewing the FACTS II Header Information

Access the Review FACTS II Data - Header Information page.

Reviewing the FACTS II Detail Balances

Access the Detail - Balances page.

This page contains all of the detail information for a specific fund code and its associated general ledger and FACTS II accounts.

Reviewing the FACTS II Detail Attributes

Access the Detail - Attributes page.

You can review the attribute values that are assigned to each FACTS II fund code and account.

Reviewing and Modifying FACTS II Footnotes

Access the Footnotes page.

Enter necessary footnotes based on your organization's data.

Note. Review this information thoroughly before continuing with your FACTS II processing.

Validating the FACTS II Data

Access the Validate FACTS II Data page.

Unit	Select the business unit for this FACTS II reporting.
Report ID	Enter the Report ID that you entered to accumulate the FACTS II data.
Display Full Numeric Field	If you report amounts larger than 15 integers and 2 decimal places, select this option to display full numeric fields consisting of 23 integers and 3 decimal places on the Validation report. The validation process performs edits against the account balances that are generated by the accumulation process. It compares the current period net outlay amount entered with the amount that was extracted in edit 12 and generates a report that indicates a pass or fail for each edit.

Creating the FACTS II File

Access the Create FACTS II File page.

Report ID	Enter the accumulated and validated FACTS II report ID.
Business Unit	Select the business unit for this FACTS II data.
SGL Acct File (SGL account file)	Enter the name of the FACTS II flat file. You must use a .TXT file extension. Do not enter a path.
Treasury Symbol Attribute	Select one or more Treasury Symbol attributes for this FACTS II data.

Running the Ledger with Attributes Report

Access the Ledger with Attributes Report page.

Run	Click to generate the Ledger Activity report (GLS7017) containing the specified business unit ledger’s fund and account attributes for the specified fiscal year and period range. This report can include journal detail and draws its data from the Cohort Year tree and level and the Accts Req Fund attributes tree and level.
Display Full Numeric Field	Select if you report amounts larger than 15 integers and 2 decimal places. Full numeric fields consisting of 23 integers and 3 decimal places will appear on the report.

Defining, Generating, Creating, and Printing SF224, SF1219, and SF1220 Reports

To set up agency location codes (ALCs) and government wide accounting (GWA) reporting options for reporting, use the Agency Location component (AGENCY_LOC_CD).

To create SF224, Partial SF224, SF1219, and SF1220 reports, use the SF1219 Report Definition component (SF1219_DEFN) and the SF224/ SF1220 Report Definition component (SF224_SF1220_DEFN).

This section provides an overview of SF224/1220, Partial SF224, and SF1219 reporting and discusses how to:

• Define agency location codes. .

• Define government wide accounting (GWA) reporting options.

• Define the SF224/SF1220 report accounts.

• Define the SF224/SF1220 entry events.

• Define SF224/1220 undeposited accounts.

• Generate the SF224/SF1220 report data.

• Print the SF224 report and create the flat file.

• Define the SF1219 report.

• Print the SF1219 report.

• Print the SF1220 report.

• Create the SF1219/1220 flat file.

Understanding SF224/1220 and SF1219 Reporting

Using the ALC field on the Journal Header page, agencies can record cash transactions by journal entry directly to the general ledger. The journal header ALC field can be used by the system to select cash entries that were entered directly to the general ledger for reporting through the SF224 and Partial SF224 reports. Journal entries made directly to the general ledger are usually made for the recording of undeposited cash, or collections.

Undeposited collections are amounts received by an agency that have yet to be deposited with the U.S. Treasury. Some agencies receive small amounts of money that they deposit once a week. Agencies book these amounts to an undeposited collections account until they are officially deposited with the U.S. Treasury.

The Financial Systems Integration Office (FSIO) has issued Core Systems Requirements that impact the SF224 and the electronic interface that is used to report cash receipt and cash disbursement activity by ALC to the U.S. Treasury. The FSIO Core System Requirements are based on new Governmentwide Accounting (GWA) Partial 224 Business Rules . The GWA business rules set the stage for ultimately phasing out the SF-224 report over the next several years to be replaced by the Partial SF224 report. The new GWA Business Rules dictate how specific activity is to be excluded from SF224 reporting as the U.S. Treasury systems are modified in the future. When agencies can finally report cash activity by the BETC codes, the agencies will report only non-BETC coded cash activity and cash reclassifications using the Partial SF224 report.

The U. S. Treasury will be implementing the BETC for federal agencies to use to identify and report specific information about cash receipt and disbursement transactions in lieu of that provided by the SF224 report. The BETC is being implemented by the U.S. Treasury during the next few years for IPAC (collections and payments), Cashlink II (collections), Electronic Certification System (payments), and for the Treasury Disbursement Office (TDO) systems.

Agency financial systems will be modified so that the BETC code can be specified for all cash transactions. The evolution of the BETC drives the need for agency financial systems in the short term to be configurable so as to identify those interfaces (IPAC, CA$HLINK, TDO Payments) as they are modified to pass BETC with the associated cash activity to the U.S. Treasury.

GWA rules requires that the new Partial 224 business rules include business activity and reporter category codes for classifying ALCs. The Partial 224 business rules identify how to report cash activity based on these new codes.

The GWA Business Activity that you specify for each ALC drives the following functionality related to the SF224 report:

• Identifies the type of cash activity that is applicable for the ALC for reporting to the U.S. Treasury.

• Limits the data extracted for the SF224 report based on the specific Business Activity code defined for the ALC.

• Drives the Business Exception Activity report so actual data that is not applicable for a particular ALC is presented on the exception report to be identified and corrected by the Agency.

The GWA Reporter Category code is specified to identify those interfaces, such as IPAC, CA$HLINK and TDO Payments, that have been modified to interface the Business Event Type Code (BETC) to cash activity with the U.S. Treasury.

Both the GWA Business Activity and the Reporter Category codes can be setup in anticipation of the delivery by the U.S. Treasury of the BETC codes.

When an agency system is finally ready to pass cash information to the U.S. Treasury using the BETC codes, the agency will select the appropriate Reporter Category so that the transaction data for the ALC can be excluded from the SF224 report. BETC implementation by an Agency goes hand in hand with the GWA Reporter Category.

The GWA Reporter code that you define for each ALC drives functionality in the software related to the SF 224 that:

• Identifies which agency systems and ALC are ready to interface the BETC with its cash activity to the US Treasury.

• Limits the data extracted for the Partial 224 based on the specific GWA Reporter Category code defined for the ALC.

• Determines whether cash reclassification from one Treasury Symbol to another needs to be reported on the Partial 224.

After setting up your system, you can define and generate the balance reports in either an electronic or printed format based on transactions that include associated entry events that flow from PeopleSoft Payables, Purchasing, and Receivables into PeopleSoft General Ledger.

These reports include:

• SF224 Statement of Cash Transactions report and the Partial SF224 report can be printed or submitted electronically to the U.S. Treasury.

  Note. The Partial 224 report will not be available for use until the U.S. Treasury implements BETC.
  
  Contact the U.S. Treasury Financial Management Service (FMS) for its schedule for implementation of the BETC. Until such time as the BETC is implemented by the FMS, you must continue to produce the full SF224 - Statement of Cash Transactions report.

• SF1220 Statement of Transactions According to Appropriations, Funds, and Receipt Accounts report can be printed separately or combined with the SF1219 report and submitted electronically.

• SF1219 Statement of Accountability report can be printed separately or combined with the SF1220 report and submitted electronically.

The following internal reports can be used to assist in the preparation of the submitted reports:

• SF224 Transaction Detail Report (GLS8400) displays the detail transactions that make up the totals on the SF224 - Statement of Cash Transactions and the Partial SF224 report, and can be used internally for reconciliation purposes.

• SF224 Business Activity Exception Report (GLS8410) displays transactions that should not be recorded for a particular Agency Location Code (ALC) based on the Business Activity Type code for that ALC.

  The report reflects data from PeopleSoft Accounts Receivable and Accounts Payable. PeopleSoft General Ledger journal entry activity is not included in the report.

• ALC GWA Reporting Options Report (GLS8411) displays Agency Location Codes by setID and prints the ALC, agency Name, Business Activity Type, and all related GWA Reporter Category Codes by descending effective date and status.

Note. The SF224 Statement of Cash Transactions and the SF224 Transaction Detail reports can be generated as full or partial reports based on the GWA Reporter Category for the ALC.

See Also

General Ledger Reports

Pages Used to Create SF224, SF1219, and SF1220 Reports

Defining Agency Location Codes (ALC)

Access the Agency Location Code page.

Agency Location Code

Enter an 8 digit numeric value for the ALC unless the Non-Treasury Disbursed option is to be selected. If the ALC payments are made outside the U.S. Treasury system and the Non-Treasury Disbursed option is selected, the system does not enforce the 8 digit edit.

Non-Treasury Disbursed ALC

Click if the ALC does not use the US Treasury to carry out payments or if the ALC is authorized to do its own payments outside the U.S. Treasury. The SF224 process does no use ALCs for which this option is checked because the SF224 process only reports on cash activity that goes through the U.S. Treasury. Note. If you set this option incorrectly for an ALC and save it, the incorrect ALC and option will remain because you cannot delete the rows online. You must define a new ALC with the appropriate option.

Defining Government Wide Accounting (GWA) Reporting Options

Access the GWA Reporting Options page.

The business activity you define for the ALCs on this page determines what type of cash transaction activity you report on the SF224 Statement of Cash Transactions report.

Business Activity and Reporter Category Combinations

The system requires that the business activity type and reporter category codes are a valid combination. The system displays a warning message if the combination is invalid.

This table shows valid and invalid combinations:

Defining the SF224/1220 Report Accounts

Access the SF224/1220 Definition - Accounts page.

Effective Date	Displays the system date, which you can change.
Status	Select Active.
Range	Click to enter a range of values in the From Account and To Account fields to identify the range of accounts to use for this report and save the page. If Range is not selected, you can enter a From Account value as a single instance. The page also displays a description and indicates the type of account. For example, A is an asset and L is a liability account.

See Also

Setting Up ChartField Attributes

Linking Account Attributes and Values to Account ChartFields

Defining the SF224/1220 Entry Events

Access the SF224/1220 Definition - Entry Events page.

Source Tran, (source transaction) Entry Event, and Collect/Disburs (collection/disbursement)

Select the source transactions, their associated entry event, and whether each transaction is a collection or a disbursement for this report, and save the page.

Defining SF224/1220 Undeposited Accounts

Access the Define SF224/1220 - Undeposited Accts (undeposited accounts) page.

From Account and To Account

Enter a range of undeposited accounts to use on the report. Add as many rows as necessary to set up the accounts. Undeposited collections are amounts received by an agency that have yet to be deposited with the U.S. Treasury. Agencies typically receive small amounts of money that they deposit once a week. The agencies book these amounts to an undeposited collections account until they are officially deposited with the U.S. Treasury. Because these amounts are typically entered in the general ledger by manual journal entry, the ALC field on the journal header can be used to identify undeposited amounts on the SF224 and Partial SF224 reports.

Generating the SF224/SF1220 Report Data

Access the Generate SF224 / 1220 Data page.

Note. This option generates the data and moves it to a table.

Standard Form	Select SF224, SF224 Partial, or SF1220 to generate the data. Note. The SF224 option only selects an ALC if the GWA Reporter Category is Non-Reporter. In addition, the SF224 Partial option only selects those ALC's where the GWA Reporter Category is other than Non-Reporter.
Business Unit	Select the business unit for the organization that is submitting this report.
Agency Location Code	Select an ALC for the reporting agency or leave the field blank and all ALCs for the setID derived from the business unit are processed. Leaving the ALC field blank is only a valid option for SF224 or SF224 Partial.
Calendar ID	Select the appropriate calendar to apply to this selected report.
Fiscal Year	Select the fiscal year to apply to the selected report.
Accounting Period	Select the accounting period that applies to the selected report.
Accounting Close Date	Enter or select the close date of the accounting period.
Disbursing Officer	Select the ID of the disbursing officer. Select this only for SF1220 reports.
Supplemental Number	Use this field to track monthly submission counts. The default value is 0. You must modify this number manually if you submit a subsequent adjustment 224 report during the same accounting month.
Run	Save the page and click this button to run the SF224/SF1220 SQR Report Generate process to update the report staging tables.

Note. You can print the SF224 and Partial SF224 report and create a flat file by selecting the Run SF224/Create file. You can print the SF1220 report by selecting Run SF1220 Report.

Printing the SF224 Report and Creating the Flat File

Access the Run SF224 Report/Create File page.

This page is identical to the Generate SF224/SF1220 Data page with the exception that you can only print and create a flat file for the SF224 and Partial SF224 reports.

Note. When choosing the value for theStandard Form field, the SF224 option only selects an ALC if the GWA Reporter Category is Non-Reporter. The SF224 Partial option only selects those ALC's where the GWA Reporter Category is other than Non-Reporter.

See Also

Generating the SF224/SF1220 Report Data

General Ledger Reports

Defining the SF1219 Report

Access the SF1219 Report Definition page.

Report Line, Account, Entry Event Source Transaction, and Entry Event

Select the values that you want to apply to this report based on each report line that you add and select.

Printing the SF1219 Report

Access the Print SF1219 Report page.

This page requires the same information as the SF224/SF1220 Generate page. However, the disbursing officer name is not required and does not appear on the page, and you can print only the SF1219 report. After submitting FMS Forms 1219 and 1220, the disbursing officer may submit a supplemental report to adjust data. You can use the Supplemental Number field on the run control page to manually increment the number of reports that were submitted within a given period.

See Also

Generating the SF224/SF1220 Report Data

General Ledger Reports

Printing the SF1220 Report

Access the Run SF1220 Report page.

This page requires the same information as the SF224/SF1220 Generate page with the exception that you can print only the SF1220 report.

See Also

Generating the SF224/SF1220 Report Data

General Ledger Reports

Creating the SF1219/1220 Flat File

Access the 1219/1220 File page.

This page requires the same information as the SF224/SF1220 Generate page, including the name of the disbursing officer and this officer's phone number.

See Also

Generating the SF224/SF1220 Report Data

Defining and Generating the Fund Balance Reconciliation Report

To define and generate a Fund Balance Reconciliation report, use the Reconciliation Rpt Definition component (FUNDBL_RCN_DEFN).

This section provides an overview of fund balance reconciliation reporting and discusses how to:

• Define the general ledger accounts to reconcile.

• Define entry events to reconcile.

• Import the U.S. Treasury data.

• Generate the Fund Balance Reconciliation report.

Understanding Fund Balance Reconciliation Reporting

Federal agencies use the Fund Balance with Treasury (FBWT) account to reconcile with U.S. Treasury's Financial Management Service (FMS) records. This reconciliation is essential to enhancing internal controls, improving the integrity of various U.S. government financial reports, and providing a more accurate measurement of budget results.

The PeopleSoft Fund Balance Reconciliation processes enable you to:

• Import the monthly account activity and trial balances, which includes the banking system and any warrant activity, from the U.S. Treasury and compare it with your agency's general ledger cash activity.

• Define a reconciliation report that compares your agency's general ledger accounts and entry events that are required by the reconciliation process with the U.S. Treasury data.

• Generate a Reconciliation Report (GLS9500) that lists any differences between your agency's data and the U.S. Treasury's data by Fiscal Year, Accounting Period, and TSYMBOL.

See Generating the Fund Balance Reconciliation Report.

Pages Used to Define and Generate a Fund Balance Reconciliation Report

Defining the General Ledger Accounts to Reconcile

Access the Fund Balance Reconciliation - Account Definition page.

From Account and To Account

Enter one account or a range of accounts that you want to reconcile with the U.S. Treasury data. Add rows as needed and save the page.

Defining Entry Events to Reconcile

Access the Fund Balance Reconciliation - Entry Event Definition page.

Entry Event and Collection or Disbursement

Select the entry event code that applies to this reconciliation, and select whether it is a collection or a disbursement. Add entry rows as needed and save the page.

Importing the U.S. Treasury Data

Access the Fund Balance Reconciliation - Import Treasury Files page.

GOALS File Type (government online accounting link system file type)

Select the type of file that you are importing from the U.S. Treasury GOALS. Values are: Receipt Account Ledger Receipt Account Trial Balance Und Appropriation Acct Ledger (undisbursed appropriation account ledger) Und Appropriation Acct TB (undisbursed appropriation account trial balance) Save the page.

Attached File

Click the Add icon to attach the file in the field. Click the Delete icon to detach the file. This action does not delete the file from your server. Click the View icon to open and display the contents of the file. You must attach the file before you can view it. Save the page. Important! Files must be entered in logical pairs. Account Ledger Activity and Account Trial Balance must be selected for the same data type. Data type is either Undisbursed Appropriations or Receipts.

Note. These buttons work the same as the buttons on the Load FACTS I Data page.

See Loading MAF and FACTS I Data.

Generating the Fund Balance Reconciliation Report

Access the Generate Reconciliation Report page:

Report Request Parameters

Enter the parameters and click the Run button to run the Fund Balance with Treasury Recn (fund balance with treasury reconciliation) process, GLS9500 SQR Report to compare the data that you defined for this reconciliation with the U.S. Treasury data and produce a report that defines any differences in the data.

See Also

General Ledger Reports

Configuring the FUND_STATUS PS/nVision Report

Federal government agencies require one or more available funds reports for each TAFS/TAS that is subject to FACTS II reporting requirements.

To configure the FUND_STATUS PS/nVision report, use the Tree Manager component (PSTREEMGR).

This section discusses how to:

• Maintain the FED_RC02_ACCOUNTS tree.

• Define the FUND_BALANCE nVision report layout.

• Request and distribute the FUND_BALANCE report.

Pages Used to Configure the FUND_STATUS PS/nVision Report

Maintaining the FED_RC02_Accounts Tree

Access the Tree Manager page and the FED_RC02 Accounts Tree.

Account tree FED_RC02_ACCOUNT is delivered specifically for Fund Status reporting. Changes to the tree, including node description, account hierarchy, and so on, are reflected when you run the nVision report.

See Enterprise PeopleTools PeopleBooks: PeopleSoft Tree Manager.

Defining the FUND_BALANCE nVision Report Layout

Access the Scope Definition page.

The nVision Layout FUND_STATUS is processed with the Scope definition FUND_STAT which contains Fund, Department ID, and Program Code as selection criteria.

For each unique combination of Fund, Department, and Program values, you can generate a Microsoft Excel spreadsheet based on the year-to-date balances in the Ledger table.

The following example shows the Microsoft Excel worksheet that lists the available fund information for Fund F200, Department 42000, Program P2000:

You can view this spreadsheet at three different levels corresponding to the levels in the FED_RC02_ACCOUNTS tree by clicking the 1, 2, or 3 button in the upper left corner of the worksheet.

Level 1 (button 1) shows only the four summarized totals:

• Total Resources

• Fund Distribution

• Spending Activity

• Balances Available

Level 2 (button 2) shows detail line items under each group.

Level 3 (button 3) shows the balances for each account, as defined in the account tree.

Requesting and Distributing the FUND_BALANCE Report

Access the PeopleSoft/nVision Report Request page.

The delivered Report Request creates worksheets that are named after the Department ID and the Program Code that you specify in the File Template edit box:

%RID%_d%SFV.DEPTID%_p%SFV.PROGRAM_CODE%.xls

Directories that are named after the Fund names are created, as specified in the Directory Template edit box:

Fund_%SFV.FUND_CODE%

See Enterprise PeopleTools PeopleBook: PS nVision

Setting Up Federal Reimbursable Agreement Accounts in General Ledger

To set up federal reimbursable agreement accounts in PeopleSoft General Ledger, use the Reimbursable Agreement Account component (RMC18_SETUP).

This section provides an overview of federal reimbursable accounts in PeopleSoft General Ledger and discusses how to set up reimbursable agreement accounts.

Understanding Federal Reimbursable Accounts in General Ledger

Federal agencies and the DoD often use reimbursable funding to perform work on behalf of others and then are reimbursed for the work. A reimbursement ID is created based upon an agreement between agencies or an outside organization. This agreement is negotiated prior to its acceptance. Agencies may only bill back the prenegotiated reimbursable amount, which makes it imperative that they are able to track reimbursable agreements separately from other types of funding, as well as access the current status of the reimbursable amount, billing limit, amount expended against the agreement, and the amounts collected against the agreement.

Federal agencies and the DoD also operate under a revolving fund. Several organizations within these two groups operate much like a business in that they charge for goods and services, and any proceeds they receive from sales finance the fund. These organizations must be able to bill for goods and services and track the status of the bills and any collection activity.

PeopleSoft Contracts enables the user to review this information required by the government on the Reimbursable Agreement Inquiry page. To take advantage of this inquiry, you must set up the Reimbursable Agreement Account information. On this page, you define the accounts for the type of amount in the Reimbursable Agreements inquiry:

• Advanced Amount equals the sum of the amounts in SGL accounts 2310, 5200, and the Unbilled AR account based on the specified search criteria for the inquiry.

• Advanced Remaining Amount equals the sum of SGL account 2310 for the specified search criteria for the inquiry.

• Billed Amount equals the Advanced Amount less 2310.

• Earned Amount equals the sum of SGL account 5200 for the specified search criteria for the inquiry.

• Unbilled Amount equals the sum of the Unbilled AR account for the specified search criteria for the inquiry.

• Obligated Amount equals the sum of amounts in SGL accounts 4802, 4872, 4882, 4801, 4871, and 4881 for the specified search criteria for the inquiry.

• Expended Amount equals the sum of amounts in SGL accounts 4902, 4972, 4982, 4901, 4971, and 4981 for the specified search criteria for the inquiry.

• Collected Amount equals the sum of amounts in SGL account 1023 for the specified search criteria for the inquiry.

• Committed Amount.

See Also

Managing Contracts

Page Used to Set Up Federal Reimbursable Agreement Accounts in General Ledger

Setting Up Reimbursable Agreement Accounts

Access the Reimbursable Agreement Account page.

See Also

Working with Federal Reimbursable Agreements

Using PSnVision for Statutory Reporting

You can fulfill your GASB 34/35 statutory reporting requirements using PSnVision and a PeopleSoft template.

This section provides an overview of GASB 34/35 reporting.

Understanding GASB 34/35 Reporting

The GASB 34 /35 requires state and local governments and public colleges and universities to submit basic financial statements. The PeopleSoft application provides a template that enables local and state governments and public colleges and universities to design the following PSnVision reports that adhere to the GASB 34/35 guidelines:

• Government-wide Statements

  A statement of net assets and activities.

• Government Fund Statements

  A balance sheet and a statement of revenues, expenditures, and changes in fund balances.

• Proprietary Fund Statements

  A statement of net assets, a statement of revenues, expenditures, and changes in fund balances, and a statement of cash flows.

• Fiduciary Fund Statements

  A statement of fiduciary net assets and a statement of changes in fiduciary net assets.

• Budget Comparison Statements

  The original budget, the final appropriated budgets for the reporting period, and the actual inflows, outflows, and balances that are stated on the government’s budgetary basis.