This chapter provides an overview of 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.
Defining component TAS and BETC elements in compliance with reporting requirements.
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 PS/nVision for statutory reporting.
This section discusses:
PeopleSoft federal government reporting.
PeopleSoft solution for Treasury Account Symbol (TAS) format transition.
PeopleSoft statutory 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. It also displays 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 the federal agency data and the U.S. Treasury 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 the 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 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, continue to produce the SF224 - Statement of Cash Transactions report.
Note. The U.S. Treasury is requiring federal agencies to begin using new formats for the Treasury Account Symbol (TAS) when reporting cash transactions through the FMS 224 Reports and IPAC transactions.
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 PS/nVision 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 PS/nVision reports that adhere to the guidelines for these reports. This report is available in hard copy.
Federal Agency Financial Statements
Federal agencies must submit the following financial statements to the U.S. Congress and the OMB. The PeopleSoft-designed templates work with PS/nVision 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.
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
Federal Agencies are required to begin using new formats for the Treasury Account Symbol (TAS) when reporting cash transactions through the FMS 224 Reports and IPAC transactions. Component TAS elements will provide federal agencies and Treasury the ability to sort, filter, and analyze data based on each independent piece of the component TAS. The Treasury has adopted a phased approach to the transition from 20-character to 28- character componentized TAS and Business Event Type Codes (BETC).
PeopleSoft GL provides a configurable solution to accommodate the valid combinations of TAS and BETC for FMS 224 reports and when entering and reporting IPAC transactions to the Department of Treasury. This configuration also anticipates the handling of valid TAS and BETC combinations to be downloaded in the future from the Treasury SAM website when the U S Treasury is ready to make the information available.
See Generating the Fund Balance Reconciliation Report.
Government Accounting Standards Board (GASB) statements 34 and 35 require 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 PS/nVision reports that adhere to GASB 34/35 guidelines.
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 PeopleBook: PeopleSoft Tree Manager, "Using PeopleSoft Tree Manager"
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.
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.
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.
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.
Import the U.S. Treasury MAF, FACTS I SGL account, and Trading Partner data.
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 free of errors.
Print the FACTS I Validation report.
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.
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
Page Name |
Definition Name |
Navigation |
Usage |
ChartField Attribute |
CF_ATTRIBUTES |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Configure, Attributes, ChartField Attribute |
Enter the ChartField attributes and attribute values that are listed in the Attributes table. |
Account |
GL_ACCOUNT |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Define Values, ChartField Values, Account |
Access the Account ChartField that you want to associate with selected ACCOUNT ChartField attributes on the ChartField Attributes page. |
Fund Code |
FUND_DEFINITION |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Define Values, ChartField Values, Fund Code |
Access the Fund Code ChartField that you want to associate with selected FUND_CODE ChartField attributes. |
ChartField Attributes |
CF_ATTRIB_VALUES |
Click the Attributes link on the Account or Fund Code ChartField pages. |
Select a ChartField attribute and attribute value that applies to either the selected Fund Group or selected Account ChartField. |
F2_ELEMENT_CF1 |
General Ledger, Federal Reports, FACTS II Definition, Miscellaneous ChartFields |
Set up ChartFields for Federal or NonFederal Partner, and Transfer Agency. |
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 Attribute page (Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Configure, Attributes, ChartField Attribute).
Note. In the sample data, these Attributes are located under the FEDRL setID.
Field Name |
ChartField Attribute Name |
Description |
Allow Multiple Values per Attr |
ChartField Attribute Value (Description) |
ACCOUNT |
EXCHANGE |
Indicates whether the revenue balance that is reported is exchange revenue or non-exchange revenue. |
Warning! This check box should NOT be selected. |
X (Exchange Revenue) T (Nonexchange Revenue) |
ACCOUNT |
CUSTODIAL |
Indicates whether the reported balance is custodial or noncustodial and reported by the agency in a Statement of Custodial Activity or in a separate footnote of a custodial activity. |
Warning! This check box should NOT be selected. |
S (Custodial) A (Noncustodial) |
FUND_CODE |
BUDGET_ SUBFUNC |
Subfunctions used in the classification of data according to major purpose served (for example, income, security, or national defense). |
Warning! This check box should NOT be selected. |
Three-digit budget functional classification subfunction. Each 3-digit budget subfunction code that is contained in the MAF represents a subfunction that is grouped under one of 19 functions. |
See Also
Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager, "Creating Trees"
Understanding ChartField Summarization with Trees
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 (General Ledger, Federal Reports, FACTS II Definition, Miscellaneous ChartFields).
See Specifying Miscellaneous ChartFields.
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 TableSet Controls for FACTS I processing.
Configure TableSet Controls record group data for FACTS I.
Configure TableSet Control trees for FACTS I.
Page Name |
Definition Name |
Navigation |
Usage |
Tree Definition and Properties |
PSTREEDEFN |
Tree Manager, Tree Manager, Create New Tree, Tree Definition and Properties Enter a tree name and click the Add button. |
Create a new tree, beginning with the tree definition to identify the tree name, related structure ID, setID, and any other rules or characteristics of the tree. Upon clicking OK, you are directed to the Enter Root Node for Tree page where you define levels and root node. Once done, the OK button directs you to the Tree Manager page to build your tree. |
Tree Manager |
PSTREEMGR |
Tree Manager, Tree Manager, Find an Existing Tree |
Access an existing tree with options that enable you to access and modify the tree definition and properties, print, and configure tree display options. |
FACTS_TREE_GRP |
General Ledger, Federal Reports, Define FACTS Tree Group, FACTS Tree Group |
Contains all of the FACTS I trees and the roll-up level. This page is identified on the run control page for FACTS I reporting and processing. |
|
TableSet Control - Record Group |
SET_CNTRL_TABLE1 |
PeopleTools, Utilities, Administration, TableSet Control, Record Group |
Defines all the record groups based on a specific Set Control Value and their associated setIDs. Also identifies the default setID of the PeopleSoft General Ledger business unit. |
TableSet Control - Tree |
SET_CNTRL_TABLE2 |
PeopleTools, Utilities, Administration, TableSet Control, Tree |
Set up tree values on this table if your setID for your business units do not match your default setID. |
See Also
Create the Transfer Agency tree using PeopleSoft Tree Manager based on the following 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 combination Transfer Agency/Account value of the ledger to the Transfer Agency value that is required by U.S. Treasury.
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
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
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
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.
Note. To display tree levels on the tree, click the Display Options link and select the Display Levels check box. Click the Update button.
See Also
Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager
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: PeopleSoft Tree Manager
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
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
Using PeopleSoft Tree Manager, set up a FACTS I Tran Partner tree similar to this example.
See Also
Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager
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
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
Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager
Access the FACTS Tree Group page (General Ledger, Federal Reports, Define FACTS Tree Group, FACTS Tree Group).
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. |
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 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 are only examples:
Set up your FACTS I ChartFields, trees, and tree group using the FEDRL SetID.
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 - Record Group page. The Default SetID designated at the top of this page is the default setID that you set up for the general ledger business unit.
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 selection enables the Tree Group list box to appear on the Accumulate FACTS I Data page so that you can select a FACTS Tree Group to process.
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.
If YES, save and exit TableSet Control.
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.
If you run FACTS I processing on multiple business units, repeat these steps.
Access the Record Group page (PeopleTools, Utilities, Administration, TableSet Control, Record Group).
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 intend to use for processing FACTS I. |
Record Group ID and Description |
Find the GL_15 Federal Reports record group ID. 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 to select the Tree Group name on 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. |
Access the TableSet Control - Tree page (PeopleTools, Utilities, Administration, TableSet Control, Tree).
Note. PeopleSoft General Ledger uses the Default SetID on the TableSet Controls page to determine which trees a business unit can access. If a business unit's Default SetID is different from the SetID under which a tree is built, you must list each of those trees separately on this page so that they are accessible by the business unit for processing and reporting.
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.
Page Name |
Definition Name |
Navigation |
Usage |
RUN_FACTSI_MAF |
General Ledger, Federal Reports, FACTS I, Load Facts I Data |
Loads MAF data, SGL Accounts, or Trading Partner data into the PeopleSoft General Ledger databases. |
|
REVIEW_FACTSI_MAF |
General Ledger, Federal Reports, FACTS I, Review FACTS I MAF |
Review data for a selected ATB Treasury MAF file. |
|
RUN_CNTL_FACTSI |
General Ledger, Federal Reports, Generate FACTS I, Generate FACTS I File, Validation Report and Trial Balance |
Select the criteria that are necessary for PeopleSoft Application Engine to generate a FACTS I flat file to upload to the U.S. Treasury's Government Online Accounting Link System (GOALS) and run a FACTS I Validation Report and a FACTS I Trial Balance. |
Access the Load FACTS I Data page (General Ledger, Federal Reports, FACTS I, Load Facts I Data).
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>. |
|
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. |
Run |
Select to access the Process Scheduler Request page and run the GL_FACTSIMAF Application Engine process. |
Access the Review FACTS I MAF page (General Ledger, Federal Reports, FACTS I, Review FACTS I MAF).
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:
|
Review Status |
Select one of these values:
|
|
Click this button after you enter the FACTS I MAF criteria. |
Access the Generate FACTS I File, Validation Report and Trial Balance page (General Ledger, Federal Reports, Generate FACTS I, Generate FACTS I File, Validation Report and Trial Balance).
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. |
Trial Balance |
|
Treasury Symbol Attribute |
Select the Treasury Symbol attributes to include in the output file. |
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.
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.
To set up FACTS II data:
Enter the FACTS II contact data.
Create the preparer file and send it to the U.S. Treasury.
Set up the Account and Fund Code ChartField attributes and attribute values.
Associate the appropriate attribute values with the Fund Code and Account ChartField values.
Specify the Miscellaneous ChartFields for PRC, Cohort Year, Federal or Non-Federal Partner, Transfer Account, and Transfer Agency.
Set up the attribute cross-reference data.
Review your ChartField attributes for accuracy.
Load the MAF data that was obtained from the U.S. Treasury with any associated PRC codes.
Review the MAF data containing Treasury Symbols.
Set up the Treasury Symbol cross-reference data.
Review and maintain the PRC codes.
You must set up these FACTS II trees and a FACTS tree group:
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.
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.
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.
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.
Accounts Requiring Attributes tree.
This tree represents the U.S. Treasury attributes and their associated accounts.
Transfer Agency tree.
This tree represents the U.S. Treasury department's three-digit federal transfer agency codes and the ledger values that are translated to these codes.
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.
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.
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:
Run the GLS8302 process to accumulate the FACTS II data.
Review the accumulated FACTS II data for accuracy.
Run the GLS8303 process to validate the FACTS II data.
Review the validation results and, if necessary, correct configuration or other data, and repeat steps 1 through 3.
Create the FACTS II flat file to send to the U.S. Treasury.
Run GLS7017 Ledger with Attributes Report to verify the accuracy of the data.
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.
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
Page Name |
Definition Name |
Navigation |
Usage |
F2_CONTACT_INFO |
General Ledger, Federal Reports, FACTS II Definition, FACTS II Contact Information, FACTS II Contact Information |
Contains contact information about the person or persons who are responsible for preparing and certifying FACTS II data for each of the appropriations and sending it to the U.S. Treasury in the Preparer file. Only preparers may change an appropriation symbol's SGL accounts or other related information. |
|
F2_RUN_CONTACT |
General Ledger, Federal Reports, FACTS II Creation, Create Preparer File |
Runs the Application Engine GL_F2 CONTACT, which creates the Contact Information Record and Contact Information Record Trailer (Input) record in the indicated input file and creates an output flat file to send to the U.S. Treasury. |
|
Attributes - ChartField Attribute |
CF_ATTRIBUTES |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Configure, Attributes, ChartField Attributes, ChartField Attribute |
Enter the Fund Code and Account ChartField attributes and attribute values. |
Fund Code |
FUND_DEFINITION |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Define Values, ChartField Values, Fund Code |
Access the Fund Code ChartField to associate with FUND_CODE ChartField attributes. |
Account |
GL_ACCOUNT |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Define Values, ChartField Values, Account |
Access the Account ChartField to associate with ACCOUNT ChartField attributes. |
ChartField Attributes |
CF_ATTRIB_VALUES |
Click the Attributes link on an Account or Fund Code page to access the ChartField Attributes page. |
Select the ChartField attributes to associate with the selected ChartField value. |
F2_ELEMENT_CF1 |
General Ledger, Federal Reports, FACTS II Definition, Miscellaneous ChartFields, Miscellaneous ChartFields |
Select ChartFields to use for recording Program Reporting Category, Cohort Year, Transfer Agency, Transfer Account, and Transaction Partner information. |
|
F2_PROG_RPT_CAT |
General Ledger, Federal Reports, FACTS II Definition, Program Reporting Category, Program Reporting Category |
Maintain PRC codes by MAF Treasury Symbol. Identify the origin of the PRCs as either resulting from user-defined values or values downloaded from a MAF file. |
|
F2_ATTR_XREF |
General Ledger, Federal Reports, FACTS II Definition, Attribute Cross Reference, Attribute Cross Reference |
Enables each agency to decide on the names of the fund and account attributes to be used in FACTS II processing. Each agency can either create its own names or use the names that are presented in this documentation. |
|
Accounting Edits |
F2_ATTR_XREF_EDIT |
Click the Accounting Edits tab on the Attributes Cross Reference page. |
Specify the ChartField Attributes and Attribute values that are applicable to the accounting edits. |
F2_RUN_MAF |
General Ledger, Federal Reports, FACTS II Creation, Load MAF Data |
Load the MAF data from a file that is sent by the U.S. Treasury to the government agency to review in PeopleSoft General Ledger. |
|
F2_MAF_INQUIRY |
General Ledger, Federal Reports, FACTS II Review, Review MAF Data |
Review the MAF data that is sent by the U.S. Treasury based on a selected MAF Treasury Symbol. Add, review, and MAF data. |
|
F2_STAGE_HDR |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data Click the Header Information tab if the page does not appear. |
Enter the criteria to display the appropriate FACTS II data on the remaining pages for review. |
|
F2_STAGE_DTL1 |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data Click the Detail Balances tab. |
Displays the FACTS II detail account balances based on the selected business unit and the criteria that is entered on the Header Information page. |
|
F2_STAGE_DTL2 |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data Click the Detail Attributes tab. |
Displays the ChartField attributes associated with specific ChartFields based on the criteria that is entered on the Header Information page. |
|
F2_STAGE_FTNT |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data Click the Footnotes tab. |
Displays the FACTS II footnote information that is associated with the selected business unit and the criteria that is specified on the Header Information page. |
|
F2_TSYM_XREF |
General Ledger, Federal Reports, FACTS II Definition, Treasury Symbol Cross Ref, Treasury Symbol Cross Reference |
Select the Treasury Symbol attribute that corresponds to the Treasury Symbol that is included in the MAF. |
Access the FACTS II Contact Information page (General Ledger, Federal Reports, FACTS II Definition, FACTS II Contact Information, FACTS II Contact Information).
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. |
Access the FACTS II - Create Preparer File page (General Ledger, Federal Reports, FACTS II Creation, Create Preparer File).
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). |
Access the Attributes - ChartField Attribute page (Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Configure, Attributes, ChartField Attribute).
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.
SetID |
Displays the setID that is set up for your FACTS II data. ChartField attributes are based on a setID so that they can be associated with more than one ChartField. |
Field Name |
Enter the type of ChartField that each ChartField attribute applies to. Values are FUND_CODE and ACCOUNT and are based on the ChartField Attribute table. |
Attribute |
Enter a ChartField attribute from the ChartField table or define your own attribute names for your organization. These names and values are associated with the ChartField names and values that are required by the U.S. Treasury on the Attribute Cross Reference page. |
Description |
Enter the description of this ChartField attribute from the ChartField Attributes table or create your own description. |
Allow Multiple Values per Attr (allow multiple values per attribute) |
Warning! Do not select this check box for FACTS I or FACTS II ChartField attributes. |
ChartField Attribute Value |
Enter each attribute value from the ChartField Attributes table or define your own values. |
Description |
Enter the description of each attribute value from the ChartField Attributes table or create your own description. |
The ChartField Attributes table lists the ChartField attributes that you must set up for FACTS II:
Field Name |
Attribute |
Description |
Allow Multiple Values |
ChartField Attribute Value (Description) |
FUND_CODE |
BEA |
Budget Enforcement Act |
This check box should NOT be selected. |
D (Discretionary) M (Mandatory) Note. These are Treasury values. |
FUND_CODE |
BORROW |
Fund borrowing source |
This check box should NOT be selected. |
P (Public) T (Treasury) F (Federal Financing Bank) Note. These are Treasury values. |
FUND_CODE |
CATEGORY |
Apportionment category code |
This check box should NOT be selected. |
A (Category A) B (Category B) C (Category C - Not subject to apportionment.) Note. These are Treasury values. |
FUND_CODE |
EX_UNEXP |
Expired or unexpired authority |
This check box should NOT be selected. |
E (Expired Authority) U (Unexpired Authority) Note. These are Treasury values. |
FUND_CODE |
REIMBURSE |
Funding authority indicator |
This check box should NOT be selected. |
D (Direct Authority) R (Reimbursable Authority) Note. These are Treasury values. |
FUND_CODE |
TSYMBOL |
Treasury Symbol |
This check box should NOT be selected. |
Each agency enters its own Treasury Symbol values and descriptions. Example: 19X0192 (No Year Revolving Fund) 19X0202 (No-Year Fund) |
BUDGET_REF |
YR_OF_BA |
Year of Budget Authority |
This check box should NOT be selected. |
BAL (Outlay from balances that are brought forward from previous year.) NEW (Outlays from new Budget Authority.) |
ACCOUNT |
ADV_FLAG |
Advance Flag |
This check box should NOT be selected. |
F (Advance in Future Year) P (Advance in Prior Year) X (Not Applicable) |
ACCOUNT |
AUTHORITY |
Authority type |
This check box should NOT be selected. |
B (Borrowing Authority) C (Contract Authority) P (Appropriation) S (Spending from Offsetting Collections) D (Advance Appropriation) L (Proceeds of Loan Asset Sales with Recourse) |
ACCOUNT |
AVAIL_TIME |
Budget resource availability |
This check box should NOT be selected. |
A (Available in the current period.) E (Available in the subsequent period.) |
ACCOUNT |
BEGIN_END |
Begin or end balance code |
This check box should NOT be selected. |
B (Report Beginning Balance to Treasury) E (Report Ending Balance to Treasury) Y (Report both Beginning and Ending Balances to Treasury.) |
ACCOUNT |
DEB_CRED |
Debit/Credit indicator |
This check box should NOT be selected. |
CR (Normal Credit Balance) DR (Normal Debit Balance) |
ACCOUNT |
DEF_INDEF |
Definite/Indefinite flag |
This check box should NOT be selected. |
D (Definite) I (Indefinite) |
ACCOUNT |
FACTSII |
FACTS II SGL account indicator |
This check box should NOT be selected. |
Y (FACTS II Account) |
ACCOUNT |
FUNCTION |
OMB Function Code |
This check box should NOT be selected. |
D (Defense) NND (Non-Defense) |
ACCOUNT |
IGN_ON_EXP |
Ignore on expiration. |
This check box should NOT be selected. |
Y (Yes, ignore on expiration.) N (No, do not ignore on expiration.) |
ACCOUNT |
RT7 |
Record type 7 This attribute indicates the RT7 value for a specific account. This edit is used in the processing logic for the PreEdit and Edit 6 in the FACTS II Validation process. |
This check box SHOULD BE selected. |
911 (Discount on Investments) 921 (Imprest Fund) 941 (Contract Authority) 951 (Authority to Borrow from Treasury) 961 (Exchange Stabilization Fund) 962 (Authority to Borrow from the Public) 971 (Investments in Public Debt Securities) 972 (Investments in Agency Securities) |
ACCOUNT |
PRE-EDIT |
Pre-edit Identifies the valid RT7 values for a specific account. Some accounts may have multiple RT7 values. |
This check box should NOT be selected. |
911 (Discount on Investments) 921 (Imprest Fund) 941 (Contract Authority) 951 (Authority to Borrow from Treasury) 961 (Exchange Stabilization Fund) 962 (Authority to Borrow from the Public) 971 (Investments in Public Debt Securities) 972 (Investments in Agency Securities) |
ACCOUNT |
EDIT1 |
Edit 1 Validates that the ending DR balances of budgetary accounts within a fund equal the ending CR balance of budgetary accounts within a fund. |
This check box should NOT be selected. |
EXCLUDE (Exclude form Accounting Edit 1 DR-CR Valuation.) |
ACCOUNT |
EDIT2 |
Status of Funds and Total Resources Balances. This edit simulates the calculation of Lines 7 and 11 from SF133. |
This check box should NOT be selected. |
ST_BEGIN (Status of Funds, Beginning Balance) ST_CURRENT (Status of Funds, Current Indicator) ST_ENDING (Status of Funds, Ending Balance) ST_CR_TO_DR (4060, 4070, 4210, and 4310, ST or TO Indicator) TO_BEGIN (Total Resources, Beginning Balance) TO_CURRENT (Total Resources, Current Balance) TO_ENDING (Total Resources, Ending Balance) |
ACCOUNT |
EDIT3 |
Resources ChartField less Obligation ChartField Resources ChartField less Obligation ChartField. This edit validates that the beginning balance budgetary debits equal the beginning balance credits. |
This check box should NOT be selected. |
S1 (Resources Carried Forward less Obligations Carried Forward) S2 (Equal Unobligated Status Carried Forward) |
ACCOUNT |
EDIT4 |
Zero balance by Quarter 4 for accounts Budgetary accounts that are related to anticipated items are not allowed to have balances at the end of the 4th quarter. This edit checks that each of the accounts with an EDIT4 account attribute have a balance that is equal to zero. |
This check box should NOT be selected. |
ZEROBYQ4 (Zero Balance by the Fourth Quarter for Anticipated Accounts) |
ACCOUNT |
EDIT5 |
Fund Equity and Fund Resources Balances This edit checks that the sum of the fund resources accounts must equal the sum of the equity accounts for each appropriation symbol. |
This check box should NOT be selected. |
FE_END (Fund Equity, Ending Balance) FR_BEGIN (Fund Resources, Beginning Balance) FR_END (Fund Resources, Ending Balance) FR_END_BC (Fund Resources, Ending Balance, Authority B or C) |
ACCOUNT |
EDIT6 |
Beginning and Ending Balances This edit will find the sum of either the beginning or ending balance for each account that has a like RT7 value and compare it with the pre-closing balance from the Treasury MAF. |
This check box should NOT be selected. |
BEGIN (Beginning Balance) END (Ending Balance) |
ACCOUNT |
EDIT7 |
Edit fund balance with Treasury calculation. This edit compares the ending balance of accounts 1010, 4350, and 4391 for each non-RT7 appropriation symbol with the pre-closing balance on the MAF file. |
This check box should NOT be selected. |
FBWT_CALC (Fund Balance with. Treasury) |
ACCOUNT |
EDIT8 |
Perform balance checks of disbursements versus collections as determined by an outlay formula and the disbursement and collections reported in the SF-133 Report on Budget Execution. |
Y An account can have multiple EDIT8 attribute values based on the formula. |
L12_1 (Line 12 Beg Bal) L12_2 (Line 12 Beg Bal, Gov Code E/F) L13_1 (Line 13 End Bal) L13_2 (Line 13 End Bal, Gov Code E) L14A_1 (Line 14A End Bal) L14A_2 (Line 14A End Bal, Gov Code E) L14A_3 (Line 14A End Bal, Gov Code E/F) L14B_1 (Line 14B End Bal, Gov Code E) L14B_2 (Line 14B End Bal, Gov Code E/F) L14C_1 (Line 14C End Bal) L14D_1 (Line 14D End Bal) L15A_1 (Line 15A End Bal) L15A_2 (Line 15A Beg/End Bal) L15B_1 (Line 15B End Bal) L15B_2 (Line 15B Beg/End Bal) L3A1_1 (Line 3A1 End Bal) L3A2_1 (Line 3A2 Beg/End Bal) L3A2_2 (Line 3A2 Beg/End Bal, Gov Code E/F) |
ACCOUNT, continued |
EDIT8, continued |
Perform balance checks of disbursements versus collections as determined by an outlay formula and the disbursement and collections reported in the SF-133 Report on Budget Execution. |
Y An account can have multiple EDIT8 attribute values based on the formula. |
L3B1_1 (Line 3B1 Beg/End Bal) L3B2_1 (Line 3B2 Beg/End Bal, Gov Code E/F) L3D1_1 (Line 3D1 End Bal) L3D2_1 (Line 3D2 End Bal) L3D2_2 (Line 3D2 Beg/End Bal) L4A_1 (Line 4A End Bal) L8A1_1 (Line 8A1 End Bal, Reimb D, Cat A) L8A1_2 (Line 8A1 Beg/End Bal, Reimb D, Cat A) L8A2_1 (Line 8A2 End Bal, Reimb D, Cat B) L8A2_2 (Line 8A2 Beg/End Bal, Reimb D, Cat B) L8A3_1 (Line 8A3 End Bal, Reimb D, Cat C) L8A3_2 (Line 8A3 Beg/End Bal, Reimb D, Cat C) |
ACCOUNT ,continued |
EDIT8, continued |
Perform balance checks of disbursements versus collections as determined by an outlay formula and the disbursement and collections reported in the SF-133 Report on Budget Execution. |
Y An account can have multiple EDIT8 attribute values based on the formula. |
L8B1_1 (Line 8B1 End Bal, Reimb R, Cat A) L8B1_2 (Line 8B1 Beg/End Bal, Reimb R, Cat A) L8B2_1 (Line 8B2 End Bal, Reimb R, Cat B) L8B2_2 (Line 8B2 Beg/End Bal, Reimb R, Cat B) L8B3_1 (Line 8B3 End Bal, Reimb R, Cat C) L8B3_2 (Line 8B3 Beg/End Bal, Reimb R, Cat C) |
ACCOUNT |
EDIT10 |
Cancellation Edit This edit is used for all cancelling Treasury Appropriation/Fund Symbols (TAFS). It checks for zero balances in reimbursable orders, receivables, obligations, payables, and unobligated balances. A footnote is required if any of the columns 7, 8, 9, 10, or 11 are negative. |
This check box should NOT be selected. |
GROUP1 (Group 1 [2108 Column 7] must be 0) GROUP2 (Group 2 [2108 Column 9] must be 0) GROUP3 (Group 3 [2108 Column 10] must be 0) GROUP4 (Group 4 [2108 Column 11] must be 0.) |
ACCOUNT |
EDIT11 |
This edit validates that the sum of certain accounts has a normal Debit or Credit balance. |
This check box should NOT be selected. |
GROUP1 (Group 1 [2108 Column 7] Normal DR Balance) GROUP2 (Group 2 [2108 Column 9] Normal DR Balance) GROUP3 (Group 3 [2108 Column 10] Normal CR Balance) GROUP4 (Group 4 [2108 Column 11] Normal CR Balance ) GROUP5 (Footnote is always required.) |
ACCOUNT |
EDIT12 |
Collections and Disbursements Accounts ( Outlay Edit) This edit compares the sum of the EDIT12 accounts for the from and to period that is specified on the Accumulate FACTS II Data run control panel, with the Treasury supplied Outlay Amount. |
This check box should NOT be selected. |
COLLECTIONS (Collections Account) DISBURSEMENTS (Disbursements Account) |
Access a ChartField such as Account, Fund Code, or Budget Reference that requires attributes (Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Define Values, ChartField Values, Account).
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. |
Access the ChartField Attributes page (click the Attributes link on the ChartField Value page).
After selecting the Attributes link, a row that contains values for SetID, ChartField Value, Effective Date, and Field Name appears.
ChartField Attribute |
Select the appropriate ChartField attribute for this ChartField Value. |
ChartField Attribute Value |
Select the ChartField attribute value for this ChartField attribute. You can add as many rows as needed of ChartField attributes and ChartField attribute values for the selected ChartField value (in this example, Account 4042). |
See Also
Access the Miscellaneous ChartFields page (General Ledger, Federal Reports, FACTS II Definition, Miscellaneous ChartFields, Miscellaneous ChartFields).
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.
Description |
The PeopleSoft application predefines theProgram Reporting Category Cohort year, Federal or Non Federal Partner, Transfer Account, and Transfer Agency data elements and descriptions. |
ChartField Name |
Select a configurable ChartField for each FACTS II Data Element. Because Transfer Agency and Transfer Account are related, you can assign the same configurable ChartField to them, if you want, or set them up with separate configurable ChartFields. All other FACTS II data elements must be associated with different configurable ChartFields. |
See Also
Access the Program Reporting Category page (General Ledger, Federal Reports, FACTS II Definition, Program Reporting Category, Program Reporting Category).
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.
Category |
Valid PRC values are 001 to 999. |
Description |
The description can vary for a Category depending on the MAF Treasury Symbol. |
Source |
Identifies the origin of a FACTS II Program Reporting Category as user-defined values or as values downloaded from a MAF file. |
Last Updated By Operator ID |
Identifies the operator ID that last manually entered or modified a PRC code value or description. |
Access the FACTS II - Attribute Cross Reference page (General Ledger, Federal Reports, FACTS II Definition, Attribute Cross Reference, Attribute Cross Reference).
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. |
Access the Accounting Edits page (General Ledger, Federal Reports, FACTS II Definition, Attribute Cross Reference, Accounting Edits).
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.
Access the Load MAF Data page (General Ledger, Federal Reports, FACTS II Creation, Load MAF Data).
|
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 date from the file 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.
Access the Review MAF Data page (General Ledger, Federal Reports, FACTS II Review, Review MAF Data).
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 increased incrementally. |
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 the remaining appropriation balance for this department 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 Online Accounting Link System flag) |
Indicates that the FACTS II file can be imported to the Government Online 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. |
Access the Treasury Symbol Cross Reference page (General Ledger, Federal Reports, FACTS II Definition, Treasury Symbol Cross Ref, Treasury Symbol Cross Reference).
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. |
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.
Page Name |
Definition Name |
Navigation |
Usage |
Tree Definition and Properties |
PSTREEDEFN |
Tree Manager, Tree Manager, Create New Tree, Tree Definition and Properties |
Create a new tree to identify the tree name, related structure ID, setID, and any other rules or characteristics of the tree. |
Tree Manager |
PSTREEMGR |
Tree Manager, Tree Manager, Find an Existing Tree, Tree Manager. |
Access an existing tree with options that enable you to access and modify the tree definition and properties, and print and configure tree display options. |
FACTS_TREE_GRP |
General Ledger, Federal Reports, Define FACTS Tree Group, FACTS Tree Group |
Contains all of the FACTS II trees and the roll-up level. This page is identified on most of the run control pages for FACTS II reporting and processing. |
|
TableSet Control - Record Group |
SET_CNTRL_TABLE1 |
PeopleTools, Utilities, Administration, TableSet Control, Record Group |
Defines all the record groups based on a specific set control value and their associated setIDs. Also identifies the default setID of the general ledger business unit. |
TableSet Control - Tree |
SET_CNTRL_TABLE2 |
Tools, Administration, TableSet Control, Tree |
Set up tree values on this table if your setID for your business units do not match your default setID. |
See Also
Using Trees to Summarize ChartFields
Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager
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
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.
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 the reporting needs of your agency. 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 before you create this 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 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 custom program codes and descriptions of the FPA.
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.
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 you create the Category B 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.
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 combination Transfer Agency/Account value of the ledger to the Transfer Agency value that is required by the U.S. Treasury.
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 combination Transfer Agency/Account value of the ledger to the Transfer Account value that is required by U.S. Treasury.
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
Access the FACTS Tree Group page (General Ledger, Federal Reports, Define FACTS Tree Group, FACTS Tree Group).
See Setting Up a FACTS I (FACTS II) Tree Group.
FACTS II Trees and Tree Levels |
The FACTS Tree Group page lists all of the tree names that are required for FACTS II processing. Select the name of your FACTS II tree that represents the listed Tree Name. Select the tree level to be used for summarizing your FACTS II data. |
Configuring TableSet Controls for FACTS II processing is the same as described for FACTS I.
See Configuring TableSet Controls for FACTS I Processing.
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.
Page Name |
Definition Name |
Navigation |
Usage |
Review ChartField Attributes |
ATTR_INQ |
Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Review, Review ChartField Attributes |
Enables you to review the attributes for FACTS II processing before running the FACTS II Accumulation (GLS8302) process. |
F2_RUN_GLS8302 |
General Ledger, Federal Reports, FACTS II Creation, Accumulate FACTS II Data |
Accumulate FACTS II data and load it into staging tables. |
|
F2_STAGE_HDR |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Header Information |
Select data to set up the Staging Header information; enter the net period outlay that is to apply to the FACTS II file. |
|
F2_STAGE_DTL1 |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Detail - Balances |
Review all of your FACTS II ACCOUNT and FUND CODE detail balances, including other ChartField details that apply. |
|
Detail - Attributes |
F2_STAGE_DTL2 |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Detail - Attributes |
Review the assigned attributes and attribute values for each FACTS II ACCOUNT and FUND_CODE. Displays the ChartField attributes associated with specific ChartFields based on the criteria entered on the Header Information page. |
F2_STAGE_FTNT |
General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Footnotes |
Enter footnotes for each FACTS II account and fund code where applicable. |
|
F2_RUN_GLS8303 |
General Ledger, Federal Reports, FACTS II Review, Validate FACTS II Data, Validate FACTS II Data |
Validate the accumulated data and create a report that indicates whether the Accounting Edit processes passed or failed and describes the reason that the edit passed or failed. |
|
F2_CREATE_FILE |
General Ledger, Federal Reports, FACTS II Creation, Create FACTS II File |
Create the FACTS II flat file to send to the U.S. Treasury to upload to GOALS. |
|
RUN_GLS7017 |
General Ledger, Federal Reports, FACTS II Reports, Ledger with Attributes Report |
Generate a FACTS II report for a specific business unit, ledger, fiscal year, period range, adjustment period information, and FACTS II Cohort and Acct Req Fund attributes tree-level data. You can also indicate that the numeric field can be 23 integers and 3 decimal places. |
Access the Review ChartField Attributes page (Set Up Financials/Supply Chain, Common Definitions, Design ChartFields, Review, Review ChartField Attributes).
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. |
Access the Accumulate FACTS II Data page (General Ledger, Federal Reports, FACTS II Creation, Accumulate FACTS II Data).
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. |
Trial Balance |
Select whether to include closing adjustments and balances 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. |
Access the Review FACTS II Data - Header Information page (General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Header Information).
Access the Detail - Balances page (General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Detail - Balances).
This page contains all of the detail information for a specific fund code and its associated general ledger and FACTS II accounts.
Access the Detail - Attributes page (General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Detail - Attributes).
You can review the attribute values that are assigned to each FACTS II fund code and account.
Access the Footnotes page (General Ledger, Federal Reports, FACTS II Review, Review FACTS II Data, Footnotes).
Enter necessary footnotes based on your organization's data.
Note. Review this information thoroughly before continuing with your FACTS II processing.
Access the Validate FACTS II Data page (General Ledger, Federal Reports, FACTS II Review, Validate FACTS II Data, Validate FACTS II Data).
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. |
FACTS Tree Group |
Select to validate FACTS II data for a particular FACTS Tree Group. |
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. |
Access the Create FACTS II File page (General Ledger, Federal Reports, FACTS II Creation, Create FACTS II File).
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. |
Access the Ledger with Attributes Report page (General Ledger, Federal Reports, FACTS II Reports, Ledger with Attributes Report).
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. |
To define component TAS and BETC elements for FMS 224 reporting and IPAC transactions, use the Define Agency Identifier component (TAS_AGENCY_ID), the Define Main Account component (TAS_MAIN_ACCT_DFN), and the Treasury Account Symbol Definition component (TAS_DEFN).
This section provides an overview of the TAS and BETC requirements and discusses how to:
Define agency identifiers.
Define main accounts.
Define Treasury Account Symbols (TAS).
Associate attributes to the Treasury Account Symbol (TAS).
Federal agencies are required to use newly-formatted Treasury Account Symbols (TAS) when reporting cash transactions and to use valid combinations of Treasury Account Symbols/Business Event Type Codes the Department of Treasury publishes when entering and reporting IPAC Transactions. The Treasury has adopted a phased approach to the transition from a 20 character to a 28 character componentized Treasury Account Symbol (TAS). The current system is designed to use one 20 character string formatted TAS. This phased approach will allow for the reporting of the Treasury Account Symbols in the future using four different formats:
Federal Agencies are required to begin using new formats for the Treasury Account Symbol (TAS) when reporting cash transactions through the FMS 224 Reports and IPAC transactions. Component TAS elements will provide federal agencies and Treasury the ability to sort, filter, and analyze data based on each independent piece of the component TAS. The Treasury has adopted a phased approach to the transition from 20-character to 28- character componentized TAS and Business Event Type Codes (BETC).
PeopleSoft GL provides a configurable solution to accommodate the valid combinations of TAS and BETC for FMS 224 reports and when entering and reporting IPAC transactions to the Department of Treasury. This configuration also anticipates the handling of valid TAS and BETC combinations to be downloaded in the future from the Treasury SAM website when the U S Treasury is ready to make the information available.
Page Name |
Definition Name |
Navigation |
Usage |
TAS_AGENCY_ID |
General Ledger, Federal Reports, TAS/BETC, Define Agency ID, Define Agency Identifier |
Enter the three-digit Agency Identifier code and description. |
|
TAS_MAIN_ACCOUNT |
General Ledger, Federal Reports, TAS/BETC, Define Main Accounts, Define Main Account |
Enter the Main Account and description. |
|
TAS_DEFN |
General Ledger, Federal Reports, TAS/BETC, Define TAS, Treasury Account Symbol Definition |
Define the Treasury Account Symbol (TAS), which is identified by selecting its component key field values, Agency Identifier and Main Account. Associate its components and attributes, such as BETC, Fund Code, and TAS Formats. |
|
BETC_DEFN |
Select the Attributes tab from the Treasury Account Symbol Definition page and click the BETC link. |
Enter associated BETC codes and related information for the Treasury Account Symbol. |
|
FUND_CODE_DEFN |
Select the Attributes tab from the Treasury Account Symbol Definition page and click the Fund Code link. |
Enter associated Fund Codes by setID for the Treasury Account Symbol. |
|
TAS_FORMAT_DEFN |
Select the Attributes tab from the Treasury Account Symbol Definition page and click the TAS Formats link. |
Displays the various derived TAS formats that are used as follows: String, GWA TAS, and Partial 224. |
Access the Define Agency Identifier page (General Ledger, Federal Reports, TAS/BETC, Define Agency ID, Define Agency Identifier).
Agency Identifier and Description |
Enter an agency identifier (three-digit numeric value) and description. This is one of two key fields (along with the Main Account) that identifies the Treasury Account Symbol (TAS). Valid values are 000 through 999. If you enter fewer than three digits, the system supplies leading zeros (left). This value populates the TAS_AGENCY record. |
Access the Define Main Account page (General Ledger, Federal Reports, TAS/BETC, Define Main Accounts, Define Main Account).
Main Account and Description |
Enter a main account (four-digit numeric value) and description. This is one of two key fields (along with the Agency Identifier) that identifies the Treasury Account Symbol (TAS). Valid values are 0000 through 9999 and you must enter all four digits. This value populates the TAS_MAIN_ACCT record. |
Access the Define TAS page (General Ledger, Federal Reports, TAS/BETC, Define TAS, Treasury Account Symbol Definition).
To find an existing value or add a new Treasury Account Symbol, select an Agency Identifier and a Main Account TAS that serve as key fields to identify the TAS.
|
Click to add a new TAS after selecting the agency identifier and main account. Upon adding, or after searching for an existing value, you are directed to the Components tab. |
Access the Treasury Account Symbol Definition page - Components tab (click the Add button on the Define TAS search page).
Supply components information for the Treasury Account Symbol.
Sub Class (government online accounting link system file type) |
Enter a two-digit numeric sub class value or leave blank if not applicable. Valid values are 00 through 99. |
Sub-level Prefix |
Enter a two-digit numeric sub-level prefix value or leave blank if not applicable. Valid values are 00 through 99. |
Allocation Transfer Agency (government online accounting link system file type) |
Enter a three-digit numeric allocation transfer agency identifier value or leave blank if not applicable. Valid values are 000 through 999. You can enter only one digit and the system fills in leading zeros. |
Begin Period of Availability and End Period of Availability |
Enter a four-digit year for beginning and ending availability. |
Availability Type |
Select the availability type value if you do not select a period of availability. Values are:
|
Sub Account |
If you select this check box, you must configure an associated Fund Code for the TAS. |
Start Date and End Date |
Select a start and end date for future use. |
Internal TAS (internal treasury account symbol) |
If you select this check box, you must configure an associated Fund Code for the TAS. This field is required for IPAC transactions. |
Access the Treasury Account Symbol Definition page - Attributes tab.
Treasury Account Symbol Description |
Enter up to a sixty-character componentized TAS description. |
BETC (business event type code) |
Click this link to access the BETC page where you associate BETC codes with the TAS. |
Fund Code |
Click this link to access the Fund Code page where you associate fund codes with the TAS. |
TAS Formats |
Click this link to access the Fund Code page where you associate fund codes with the TAS. |
Associating TAS with Business Event Type Codes (BETC)
Access the Business Event Type Code page (click the BETC link from the Treasury Account Symbol Definition page - Attributes tab).
Use this page to configure the Business Event Type Code information associated with the componentized TAS.
BETC (business event type code) |
Enter up to an eight-character BETC code. |
Description |
Enter up to a 50-character description of the BETC code. |
Payment Or Collection |
Select either Payment or Collection to designate the nature of the associated business event type code. |
Adjustment |
Select this check box to designate this BETC code as an adjustment. |
Active/Inactive |
Select Active or Inactive to indicate whether this BETC code is currently applicable. |
Associating TAS with Fund Codes
Access the Fund Code page (click the Fund Code link from the Treasury Account Symbol Definition page - Attributes tab).
Use this page to associate fund codes for the componentized internal TAS. Select a Fund Code by SetID.
Note. Each componentized TAS can link more that one Fund Code. But these fund codes must have different Set ID. Each Fund Code can be related to a componentized TAS only, the relationship is 1 to 1. Error messages: "Set ID %1 has been entered"; "Fun
Viewing the TAS Formats
Access the TAS Formats page ( (click the TAS Formats link from the Treasury Account Symbol Definition page - Attributes tab).
This page displays the various TAS formats that are required to accommodate the U.S. Treasury's phased approach to the transition from a 20-character to a 28-character componentized TAS. This phased approach allows for the reporting of the TAS that is required when reporting cash transactions and to use valid combinations of TAS/BETC that the Department of Treasury publishes when entering and reporting IPAC transactions.
String |
Displays the 20-character TAS format that is required for the current FMS 224 report. |
GWA TAS (Government wide Accounting and Reporting Modernization Project) |
Displays the 26–character component-based GWA TAS representing the agency appropriation in GWA. |
Partial 224 |
Displays the expanded 27 character concatenated string format that is required for Partial 224 reporting. |
To set up agency location codes (ALCs) and Government-wide Accounting and Reporting (GWA) 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 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.
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 affect 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 GWA Partial 224 Business Rules . The GWA business rules set the stage for ultimately phasing out the SF224 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 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
Page Name |
Definition Name |
Navigation |
Usage |
AGENCY_LOC_CD |
Set Up Financials/Supply Chain, Common Definitions, Agency Location Codes, Agency Location, Agency Location Code |
Define agency location codes by set ID for federal payment schedules and reporting purposes and provides for ALC name, location, address, and telephone information. |
|
AGENCY_LOC_CD2 |
Set Up Financials/Supply Chain, Common Definitions, Agency Location Codes, Agency Location, Agency Location Code, GWA Reporting Options |
Assign a Business Activity and one or more effective dated Reporter Categories to an Agency Location Code. When an agency system is ready to pass the BETC code to the U.S. Treasury, the agency will select the appropriate Reporter Category so that the data can be excluded from the SF224 report. |
|
SF224_SF1220_DEFN1 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, SF224/1220 Report Definition, Accounts |
Add the range of accounts to access and use for this report. |
|
SF224_SF1220_DEFN2 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, SF224/1220 Reports Definition, Entry Events |
Add the source transactions and entry events, and indicate whether this transaction is a collection or disbursement for this report. |
|
SF224_UNDEP_ACC |
General Ledger, Federal Reports, SF224/ 1219/ 1220, SF224/1220 Reports Definition, Undeposited Accounts |
Identifies a range of undeposited accounts to use for reports. |
|
RUN_SF224_SF1220 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, Generate SF224/1220 Data |
Runs the GLSF224G SQR process to update the staging tables. |
|
RUN_SF224_SF1220 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, Run SF224 Report/Create File |
Runs GLSF224P SQR to print the report. Also runs GL_224_1220 Application Engine to create a SF224 flat file. |
|
SF1219_DEFN |
General Ledger, Federal Reports, SF224/ 1219/ 1220, SF1219 Report Definition, SF1219 Report Definition |
Set up report lines for each account, its associated entry event source transaction, and associated entry event. |
|
RUN_SF1219 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, Run SF1219 Report, Print SF1219 Report |
Runs the GLSF1219 SQR Report process to print the SF1219 Statement of Accountability report. |
|
RUN_SF224_SF1220 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, Run SF1220 Report |
Runs the GLSF224P SQR Report process to print the SF1220 report. |
|
RUN_SF1219 |
General Ledger, Federal Reports, SF224/ 1219/ 1220, Create SF1219 Report/Create File, Create SF1219 Report/Create File |
Runs the GL1219PR SQR report and the GL_1219_1220 Application Engine to create a flat file. |
Access the Agency Location Code page (Set Up Financials/Supply Chain, Common Definitions, Agency Location Codes, Agency Location, Agency Location Code ).
Agency Location Code |
Enter an 8-digit numeric value for the ALC unless the Non-Treasury Disbursed ALC option is to be selected. If the ALC payments are made outside the U.S. Treasury system and the Non-Treasury Disbursed ALC 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 not use ALCs for which this option is selected 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. |
IPAC Document Reference Number
IPAC (Intra-governmental Payment and Collection system) is designed to transfer funds between government agencies and provide the capability to include descriptive information related to each transaction. This descriptive information assists with monthly reconciliation.
IPAC Bulk Prefix |
Enter a 3-digit alphanumeric prefix to be used by PeopleSoft in creating unique document reference numbers (to differentiate from the Department of Treasury document reference numbers) for those Agency Location Codes that are used to send payments and collections. |
IPAC Bulk Counter |
Enter the beginning number from which to increment the sequential counter for the document reference number. |
See PeopleSoft Enterprise Payables Preface.
See Oracle's PeopleSoft Enterprise Receivables Preface.
Access the GWA Reporting Options page (Set Up Financials/Supply Chain, Common Definitions, Agency Location Codes, Agency Location, Agency Location Code, GWA Reporting Options).
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 |
Select the business activity type for the agency location code. The business activity type identifies the types of transactions an ALC reports on the SF224 Statement of Cash Transactions report. The business activity type specifies which systems the ALC utilizes at the U.S. Treasury to process cash transactions. Options include:
|
Reporter Category |
Select a GWA reporter category code. The reporter category code identifies which systems are supporting the BETC code for detailed transactions. This also drives whether an ALC is ready to use the Partial 224 reporting capabilities. The business activity and reporter category combination you define determines what cash reclassification transactions you report on the Partial 224 report. Options include:
This field is effective dated and can be made active or inactive because BETC codes will be phased in over time. Note. Select Non Reporter until the Partial 224 report is applicable. The reporting of cash reclassifications for the new Partial 224 report is not applicable until the U.S. Treasury completes their requirements for Business Event Type Codes (BETC). The U.S. Treasury plans on phasing in the BETC requirements towards the end of 2006. Contact the U.S. Treasury for more information. |
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:
Business Activity Type |
Valid Reporter Category Code |
Invalid Reporter Category Code |
CashLink Only |
|
|
IPAC Only |
|
|
IPAC and CashLink |
|
|
IPAC and TDO Payments |
|
|
IPAC, CashLink and TDO Payments |
|
No reporter category codes are invalid with this business activity. |
TDO Payments Only |
|
|
TDO Payments and CashLink |
|
|
No Business Activity Type |
Non Reporter |
|
Access the SF224/1220 Report Definition - Accounts page (General Ledger, Federal Reports, SF224/1219/1220, SF224/1220 Report Definition, Accounts).
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
Access the SF224/1220 Definition - Entry Events page (General Ledger, Federal Reports, SF224/1219/1220, SF224/1220 Report Definition, Entry Events).
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. |
Access the Define SF224/1220 - Undeposited Accts (undeposited accounts) page (General Ledger, Federal Reports, SF224/1219/1220, SF224/1220 Report Definition, Undeposited Accts).
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. |
Access the Generate SF224 / 1220 Data page (General Ledger, Federal Reports, SF224/1219/1220, Generate SF224/1220 Data).
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 for which 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 |
For SF1220 reports only, select the ID of the disbursing officer. |
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.
Access the Run SF224 Report/Create File page (General Ledger, Federal Reports, SF224/1219/1220, Run SF224 Report/Create File).
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 ALCs for which the GWA Reporter Category is other than Non-Reporter.
See Also
Generating the SF224/SF1220 Report Data
Access the SF1219 Report Definition page (General Ledger, Federal Reports, SF224/ 1219/ 1220, SF1219 Report Definition, SF1219 Report Definition).
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. |
Access the Print SF1219 Report page (General Ledger, Federal Reports, SF224/ 1219/ 1220, Run SF1219 Report, Print SF1219 Report).
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
Access the Run SF1220 Report page (General Ledger, Federal Reports, SF224/ 1219/ 1220, Run SF1220 Report).
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
Access the Run SF1219 Report/ Create File page (General Ledger, Federal Reports, SF224/ 1219/ 1220, Run SF1219 Report/Create File, Run SF1219 Report/Create File).
This run control allows you to run the GL1219PR SQR report (print the SF1219 report) and the GL_1219_1220 Application Engine to create a flat file of both reports.
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
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.
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.
Page Name |
Definition Name |
Navigation |
Usage |
FUNDBL_RCN_DEFN1 |
General Ledger, Federal Reports, Fund Balance Reconciliation, Define Report Definition, Account Definition |
Enter the General Ledger accounts that you want to reconcile with the U.S. Treasury data. |
|
FUNDBL_RCN_DEFN2 |
General Ledger, Federal Reports, Fund Balance Reconciliation, Define Report Definition, Entry Event Definition |
Enter the Entry Event codes and select whether they are a collection or disbursement to reconcile with the U.S. Treasury data. |
|
LOAD_FUNDBL_REQ |
General Ledger, Federal Reports, Fund Balance Reconciliation, Import Treasury Files |
Select the GOALS file type and attach the file containing the U.S. Treasury data. |
|
RUN_FBRECON_RPT |
General Ledger, Federal Reports, Fund Balance Reconciliation, Generate Reconciliation Report |
Enter the data to run the reconciliation process and generate the Fund Balance Reconciliation report. |
Access the Fund Balance Reconciliation - Account Definition page (General Ledger, Federal Reports, Fund Balance Reconciliation, Define Report Definition, Account Definition).
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. |
Access the Fund Balance Reconciliation - Entry Event Definition page (General Ledger, Federal Reports, Fund Balance Reconciliation, Define Report Definition, Entry Event Definition).
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. |
Access the Fund Balance Reconciliation - Import Treasury Files page (General Ledger, Federal Reports, Fund Balance Reconciliation, Import Treasury Files).
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:
|
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.
Access the Generate Reconciliation Report page (General Ledger, Federal Reports, Fund Balance Reconciliation, Generate Reconciliation Report):
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
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.
Page Name |
Definition Name |
Navigation |
Usage |
Tree Manager |
PSTREEMGR |
Tree Manager, Tree Manager, Tree Manager |
Review an existing tree, tree levels, or a tree definition. |
Scope Definition |
NVS_SCOPE_DEFN |
Reporting Tools, PS/nVision, Define Scope, Scope Definition |
Defines the scope for generating a PS/nVision report. |
nVision Report Request |
NVS_REPORT_RQST |
Reporting Tools, PS/nVision, Define Report Request, nVision Report Request |
Enter the data that is necessary to run a PS/nVision report. |
Access the Tree Manager page and the FED_RC02_ACCOUNTS Tree.
Account tree FED_RC02_ACCOUNTS 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 PeopleBook: PeopleSoft Tree Manager.
Access the Scope Definition page (Reporting Tools, PS/nVision, Define Scope, Scope Definition).
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.
Access the PeopleSoft/nVision Report Request page (Reporting Tools, PS/nVision, Define Report Request, nVision Report Request).
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 (click the Scope and Delivery Templates link):
%RID%_d%SFV.DEPTID%_p%SFV.PROGRAM_CODE%.xls
Directories that are named after the Fund names are created, as specified in the Directory Name Template edit box:
Fund_%SFV.FUND_CODE%
See Enterprise PeopleTools PeopleBook: PS/nVision.
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.
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
Page Name |
Definition Name |
Navigation |
Usage |
RMC18_SETUP |
General Ledger, Federal Reports, Define Reimbursable Account, Reimbursable Agreement Account |
Set up general ledger Account ChartFields for each of the Reimbursable Agreement Amount Types that are predefined for the page. |
Access the Reimbursable Agreement Account page (General Ledger, Federal Reports, Define Reimbursable Account, Reimbursable Agreement Account).
Amount Type |
Select the amount types that appear in the Reimbursable Agreements Inquiry in PeopleSoft Contracts. |
Account |
Select the Account ChartField that applies to each amount type. A description and example of how the amounts in the inquiry are derived for each amount type resides in the PeopleSoft Contracts PeopleBook, "Federal Reimbursable Agreements" chapter. |
Account Action |
Select either Addor Deduct. This selection describes the action taken on the detail amount for the account when you are combining them into the higher level amount type. |
See Also
Working with Federal Reimbursable Agreements
You can fulfill your GASB 34 and 35 statutory reporting requirements using PS/nVision and a PeopleSoft template.
This section provides an overview of GASB 34 and 35 reporting.
GASB statements 34 and 35 require 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 PS/nVision reports that adhere to the GASB 34/35 guidelines:
Governmentwide 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.