This chapter provides overviews of the Contracts core structure, products, contract classifications, and business units, and discusses how to define contracts business units for government contracting.
Government contracts functionality relies on the Contracts core structure to support its features and processing. Whether you are managing only government contracts or both government and non-government contracts, you must first set up your Contracts core structure and then setup any additional underlying structural requirements for government contract processing to utilize the features and functions of your Contracts system. For setting up additional Contracts features that are shared by other applications, see PeopleSoft Enterprise Application Fundamentals 8.9 PeopleBook.
Note. All tables and setup specific to Contracts are discussed in the PeopleSoft Enterprise Contracts 8.9 PeopleBook.
This section provides overviews for:
Contracts core structure.
Products.
Contract classifications.
Setting up your Contracts core structure includes setting up any control tables, business units, accounting structure, products, installation defaults, and so on that support the processing and management of your contracts, billing, and revenue generation.
This section identifies the required setup for general processing of a government contract. Additional required setup for a specific government contracts sub-features is covered in the remaining government contracts chapters of this PeopleBook.
The following table identifies all of the required and optional tasks to set up your Contracts core structure:
Setup Task |
Purpose |
Reference |
Define installation level setting for Contracts. |
To set up your processing settings at the overall system level, you must define your options on the Installation Options-Contracts page. You can define processing settings for the accounting date that is used for revenue recognition, limit processing, and forecasting. For rate-based contract lines assigned to fee types (cost-plus), you must indicate whether you are separating billing and revenue. This setting is key to cost-plus contract line processing as it controls whether the revenue fields, links and pages become visible and available for use. |
|
Define Contracts business units. |
Contracts business units are identification codes that represent a high-level organization of business information. Contracts, accounting rules, fees, rates and progress payment settings are all defined by the contracts business unit. |
|
Define accounting distributions. |
Accounting distributions enable the system to create accounting entries for amount-based contract lines. Valid unbilled accounts receivable, revenue, and deferred revenue (optional) account distribution codes must be assigned to contract lines before the contract can be activated, bills can be generated, and revenue can be processed for amount-based contract lines, prepaids, and progress payment amounts. |
|
Define accounting rules. |
Accounting rules enable the system to create accounting entries for rate-based contract lines and rate-based contract lines that are assigned to fee types (cost-plus). Valid unbilled accounts receivable and revenue accounting distributions must be defined, and assigned to the accounting rules before bills can be generated and revenue can be processed for rate-based contract lines and rate-based contract lines that are associated with fee types (cost-plus). Note. If you select the Separate Billing and Revenue checkbox on the Installation Options-Contracts page, the system uses the PSRV2 analysis type when processing revenue accounting entries for rate-based contract lines associated with fee types (cost-plus). Therefore, in addition to defining accounting rules used for bill processing, you must also define a separate accounting rule for revenue (REV) to generate revenue accounting entries. |
|
Define contract statuses. |
Contract statuses provide a visual indicator of where the contract is within the contract life cycle and designates when a contract is available for look-up and processing. Contract statuses are user-defined and are associated with a processing status that controls the contract's eligibility for processing. |
|
Define contract types. |
Contract types enable you to define categories for your contracts for reporting purposes. If you are using contract milestones, you can also use contract types to limit the types of contracts in which you can use a specific milestone. Examples of contract types could include Health and Human Services or Defense Contracts. |
|
Define billing and revenue plan templates (optional). |
Billing and revenue plan templates enable you to automate billing and revenue plan setup. Billing plans are required and are used to process bills for contract line items, fees and progress payments requests. Revenue plans are required to process revenue accounting entries for contract line items and fees. If you do not define billing or revenue plan templates, then you must manually set up billing and revenue plans for your contract lines and progress payments requests before you can process bills and recognize revenue. |
|
Define billing plan detail templates (optional). |
Billing plan detail templates enable you to automatically override the billing defaults that are defined for a contracts billing business unit and contract header. |
|
Define billing summarization templates (optional). |
Summarization templates enable you to define criteria that the system can use to summarize billing plan lines. |
|
Define legal entities. |
Legal entities are used in Contracts to track the legal entity within your company who signs a particular contract. |
|
Define milestones (optional). |
Milestones can control the timing of billing and revenue recognition processing for amount-based contract lines, incentive and award fees. Setting up milestones can include defining milestone classifications, milestone templates, and custom SQL statements to use for milestone conditions. |
See Defining Milestones. |
Define amendment types. |
Any changes to an active contract's products, terms, or conditions is controlled by amendment processing. Amendment types enable you to define classifications of modifications that can be made to an active contract. |
|
Define amendment reasons. |
Amendment reasons enable you to define quick explanations as to why an amendment is performed. |
|
Define email notification workflow and support teams (optional). |
Support teams represent key personnel in your organization that are involved in the contract life cycle. You can set up email notification and workflow so that specific support team members are notified when the status of a particular contract changes. |
|
Define products. |
You must define the products that represent the good and services that you deliver in your contracts, including the specification of Contracts attributes. Once defined, you add these products to your contract lines. Contract lines are the basis for your billing and revenue recognition activities. Only amount and rate-based products can be associated with government contracts. Renewable products are not eligible for government contracts. |
|
Define rate sets and rate plans. |
Rate sets enable you to define allowable expense rates for your rate-based contract lines and rate-based contract lines that are assigned to fee types (cost-plus) and enable the system to create billable and cost rows. Rate plans enable you to bundle multiple rate sets together to define a sequence of costing and rate applications that enable the system to calculate both your direct and indirect costs. |
See Rate Setup. |
Your core contractual obligations are the products and services that you provide to your customer. Before you can bill or recognize revenue for your contract, you must define a standard set of products, associate any attributes such as pricing structure and accounting information, and then add them to your contract.
You can only add amount or rate-based type products to government contract lines. Amount and rate-based products are associated with a price type of Amount or Rate, respectively. Your government contracts may contain either type of product, or a combination of both of these product types. Similar to Contracts core functionality, certain government contracting sub-features are designed specifically for amount-based contract lines, such as progress payments, while other sub-features are designed specifically for rate-based contract lines, such as limits, cost-plus, and withholding.
The following table identifies the product type and the government contracting features that are specific for that product type:
Product Type |
Government Contracting Feature |
Amount-based products |
|
Rate-based products |
|
See Also
The Contract Classification field is used to distinguish government contracts from other types of contracts that you may manage. Contracts supports the following contract classifications:
Federal Reimbursable Agreement
Government
Internal
Standard
Contract classifications appear on the contract header and are associated with specific attributes and functionality. To take advantage of the features and functions that are available for government contracts, you must install the Contracts, Project Costing and Billing applications, and select the contract classification of government.
See Also
This section provides an overview of Contracts business units and discusses how to define Contracts business units.
Contracts business units represent an operational subset of your business organization. Whether you work exclusively with government funded contracts or with a combination of government and non-government contracts, the Contracts business unit is the backbone of the contracts system and must be defined before you can create or manage any of your contracts.
When defining a contracts business unit, it is important to consider the relationship of your Contracts application with other PeopleSoft applications that you are implementing. For example, you must associate a General Ledger business unit to a Contracts business unit for the system to create revenue accounting entries. Any Billing business units that are assigned to a Contracts business unit must point to the same General Ledger business unit that was associated with the Contracts business unit. Use Billing business units when you generate invoices for the contract.
When defining a contracts business unit, you can define many setup and processing attributes to automate the setup and management of the contract. After the contract is created, you can override many of these values at the contract line level to customize the contract to your specific customer's needs.
For example, you can control the ability to set and override the deferred revenue settings for the contract line at the Contracts business unit level. If the deferred revenue option is selected at the product group option level, and the deferred revenue override option is selected, the user can override the defaulted deferred revenue settings and clear the deferred revenue check box for the contract line. Otherwise, this default cannot be overridden if the deferred revenue override option is not selected.
If the Deferred Revenue Override checkbox is not selected, and if the deferred revenue option is not selected at the product group level; the deferred revenue option is unavailable for the contract line, and the Deferred Revenue tab does not appear.
To define Contracts business units for your government contracts, use the Contracts Definition component (BUS_UNIT_TBL_CA).
See Also
Defining Contracts Business Units
Page Name |
Object Name |
Navigation |
Usage |
Set Up Financials/Supply Chain, Business Unit Related, Contracts, Contracts Definition, BU Definition |
Create a new business unit definition or modify an existing one for your government contracts. |
||
Set Up Financials/Supply Chain, Business Unit Related, Contracts, Contracts Definition, Defaults |
Specify field value defaults that the system uses to automatically populate fields on the contract for contract processing and management. |
||
Set Up Financials/Supply Chain, Business Unit Related, Contracts, Contracts Definition, Processing Options |
Define processing attributes to incorporate flexibility and automation in your Contracts system when managing revenue or performing billing and revenue credits and adjustments. |
||
Set Up Financials/Supply Chain, Business Unit Related, Contracts, Contracts Definition, Fee Definition |
You must associate cost-reimbursable (cost-plus) contract lines with a fee type for the rate-based contract line to have cost-plus functionality. Contracts support the fee types of Fixed, Award, Incentive and Other. You must define each fee type and its associated attributes at the business unit level. The fee type definition is used by the system to calculate the appropriate fees for the cost-plus contract line. |
Access the Contracts Definition - BU Definition (Business Unit Definition) page.
Business Unit |
When you first add a business unit, you must provide a description and specify a value in the Default SetID field. Clicking the Create BU button adds the Contracts business unit to the system tables, displays additional fields that must be completed and hides the Create BU button after the process is complete. |
Integration
GL Unit (General Ledger Unit) |
Associate each Contracts business unit with a general ledger business unit. General Ledger business units define the accounting processing for associated Contracts business units. All contracts created for this Contracts business unit use this General Ledger business unit to generate entries that interact with General Ledger. After you create government contracts using this business unit, the general ledger business unit should not be modified or your ledgers might become out of sync. |
OM Unit (Order Management Unit) |
Select a default PeopleSoft Enterprise Order Management business unit for contracts that are created under this Contracts business unit. You can only select Order Management business units that are linked to the same General Ledger business unit as this Contracts business unit |
BI Unit (Billing Unit) |
Select a default Billing business unit for contracts that are created under this Contracts business unit. You can only select Billing business units that are linked to the same General Ledger business unit as this Contracts business unit. |
Currency
Currency Code |
Select a default currency for contracts that are created using this business unit. |
Rate Type |
Select the group of exchange rates that are used to convert contract currency amounts to the base currency of the General Ledger system. You set up rate types when defining your general options. |
Security
Enforce Contract Status Security |
Select to limit the list of users who can change the status of a contract to only those to whom you have given security access on the User Preferences - Contracts page. |
Delete Internal Notes |
Select to enable users to delete internal notes. |
Update Internal Notes |
Select to enable users to update internal notes. |
Access the Contracts Definition - Defaults page.
Contract
Contract Admin (Contract Administrator) |
Select a contract administrator to associate to this business unit. This value automatically populates the contract administrator field on the contract header when a government contract is created using this business unit. |
Contract Type |
Select a contract type to categorize your contracts for reporting purposes. The value that you select automatically populates the contract type field on the contact header when a government contract is created using this business unit. |
Dist Rule Code (Distribution Rule Code) |
Select the distribution rule code to associate to the Contracts business unit. Distribution rules identify the distribution accounting that the system associates with an amount-based contract line. The distribution rule code identifies the distribution rules to use for a particular product when the product is selected for the contract within this Contracts business unit. You can define any number of combination criteria and hierarchy for the distribution rules. These rules identify the accounting distribution sets and determine in what order to apply them. |
Unbilled AR (Unbilled Accounts Receivable) |
When revenue is managed from Contracts, revenue is recorded to an unbilled accounts receivable account. When billing occurs, Billing generates an offsetting entry. The system uses the unbilled accounts receivable account that are defined at the business unit level as the high-level default value for every contract that is created under this business unit. |
Legal Entity |
Select a legal entity to appear by default for contracts created using this business unit. While this legal entity is not directly linked to the legal entity in General Ledger, this field enables you to capture your organization's legal entity that enters into a contractual agreement with the customer. This value, which is a default on the contract, can be overridden. This value automatically populates the appropriate field on the contract header. |
Billing Plan
Bill Type |
Select a default bill type for contracts that are created under this Contracts business unit. The bill type represents the category of activity that is being billed. |
Bill Source |
Select to enable Billing to identify from where the billing activity came and then to associate default billing information with that billing activity. |
Taxes
Ship From |
Select from location codes that are defined on the Location Definition page. This value is a default for each contract but can be overridden on the billing plan. |
Prepaid Tax Timing |
Select the timing of when prepaids are taxed. Select from Tax on Initial Bill or Tax on Utilization. This value appears by default on the prepaid setup for contracts created using this business unit. You can override this value on the prepaid setup pages. |
Progress Payment Rates
Enter the progress payment rate percentage as defined by the Federal Acquisition Regulations (FAR). This value appears by default on the Progress Payment Terms - General page and can be overridden at the progress payment terms level. |
|
Enter the progress payment liquidation rate percentage as defined by the Federal Acquisition Regulations (FAR). This value appears by default on the Progress Payment Terms - General page and can be overridden at the progress payment terms level. |
Access the Contracts Definition - Processing Options page.
Revenue Management Options
Select the Deferred Revenue Override check box to indicate whether a user can override the deferred revenue option on the contract line. The deferred revenue option can be selected at the product group option level to automatically populate the deferred revenue settings on a contract line when a product that is associated with that product group option is added to the contract. Note. The deferred revenue feature only applies to amount-based contract lines. After a contact is in Active processing status, you cannot modify the deferred revenue options for the contract line. Instead, you must make any modifications using amendment processing. |
|
Select this override check box to indicate whether a user can override the revenue recognition method on a contract line. Revenue recognition methods dictate the type of revenue recognition plan or template that can be associated with a contract line. The contract line can inherit its revenue recognition method from the product definition. When this override check box is not selected, the system processes the revenue for the contract line using the default revenue recognition method. |
|
Edit Combinations |
Select the Edit Combinations check box if you want the Accounting Rules Process (PSA_ACCTGGL) to run the combination edit process for transactions that are processed by the Transaction Billing Processor. Note. The Edit Combinations feature is only used by the Transaction Billing Processor. Government contracts do not use this feature. |
Proration Method |
Provides the rules that the system uses to determine how much to apportion to each event for revenue plans with a revenue recognition method of apportionment. Select from:
|
Future Period Accounting Dates |
Select the date to use as the accounting date for apportionment revenue recognition events. Select from:
|
On Demand Options
Bill Plan Detail Template ID |
Select a bill plan detail template ID to override the fields on the billing plan for on-demand contracts. If you select a template on this page, the billing plan detail template overrides the corresponding fields on the billing plan when a billing plan is created. |
Note. The On Demand Options feature is used by the Transaction Billing Processor for PeopleSoft Enterprise Real Estate Management and PeopleSoft Enterprise Customer Relationship Management. Government contracts do not use this option.
Renewal Options
Review Timing |
Enter a value in days. The system uses this value to determine when you must begin reviewing renewable contract lines. You can override this value for each renewable contract line on the Review Renewals page using either the control or default settings that you select on this page. |
Control |
Select the Control option to enable users to override the Review Timing Days field on the Review Renewals page with a value that is greater than or equal to the value that is entered in the Review Timing field. |
Default |
Select the Default option to enable users to override the Review Timing Days field on the Review Renewals page with a value that is less than, greater than, or equal to the value that is entered in the Review Timing field. |
Note. The Renewal Options feature is not used by government contracts.
Line Amendment Default Options
Select this option to enable the system to adjust billing events retroactively when a contract line is cancelled or the contract line amount is modified during amendment processing. The option that is selected at the business unit level can be overridden at the contract line level. If this option is not selected at the business unit or contract line level, the user can only adjust any remaining future events for the contract line. |
|
Select this option to enable the system to adjust revenue events retroactively when a contract line is cancelled or if the contract line amount is modified during amendment processing. The option that is selected at the business unit level can be overridden at the contract line level. If this option is not selected at the business unit or contract line level, the user can only adjust any remaining future events for the contract line. |
Note. Line Amendment Default Options only apply to amount-based contract lines. These options can be selected independently of one another.
Access the Contracts Definition - Fee Definition page.
For cost reimbursable contract lines, an organization must be able to calculate direct costs, indirect costs, and fees, and report these calculations to the government to receive proper payment for their services. Contracts enables organizations to calculate and track these costs using the cost-plus functionality associated with government contracts.
To calculate fees, you must first set up the fee definitions at the business unit level. Once defined, you must associate a fee type to the rate-based contract line to enable cost-plus functionality. The system uses the fee definition to calculate appropriate fees for the contract line.
Only one fee definition can be set up for each fee type that is defined for a business unit. Multiple fee types can be associated with a singular contract, but only one fee type can be assigned to a singular contract line.
Select the fee type for which you will define fee calculation criteria. You must set up fee definitions for every fee type that will be associated to cost-plus contract lines on contracts that were created under the business unit. Contracts supports the following four fee types:
Note. Fee Type is a required field. |
BIL Analysis Group (Billing Analysis Group) |
Select the billing analysis group that contains the transaction analysis types that are included in the billing fee calculations. Note. This is a required field. |
REV Analysis Group (Revenue Analysis Group) |
Select the revenue analysis group that contains the transaction analysis types that are included in the revenue fee calculations. Note. This is a required field if Separate Billing and Revenue is selected on the Installation Options - Contracts page. This field is hidden if Separate Billing and Revenue is not selected on the Installation Options - Contracts page. |
Analysis Type |
Select the analysis type to stamp on the target billing fee rows that are created from the billing fee worksheets. The billing target fee attributes analysis types identify rows for bill processing for the contract lines. Note. The analysis type selected must be associated with the PSWKS analysis group in Project Costing. This is a required field. |
Source Type |
Select the source type to stamp on the target billing fee rows that are created from the billing fee worksheets. Note. Only one source type can be selected for the target billing fee row. This is a required field. |
Category |
Select the category to stamp on the target billing fee rows that are created from the billing fee worksheets. Specifying a category is optional, but enables you to further identify the billing fee row that is created. For example, you can identify billing fee rows for fixed fees as CPFF (Cost-Plus Fixed Fee). Only one category can be selected for the target billing fee row. Only categories that were previously defined in Project Costing can be selected. |
Subcategory |
Select the subcategory to stamp on the target billing fee rows that are created from the billing fee worksheets. Specifying a subcategory is optional, but enables you to further identify the billing fee row that is being created. Only one subcategory can be selected for the target billing fee row. Only subcategories that were previously defined in Project Costing can be selected. |
The data that you enter in this section stamps the target revenue fee rows that are created by fee processing. If the Separate Billing and Revenue option is selected on the Installation Options - Contracts page, then you must complete this section. However, this section is hidden if the Separate Billing and Revenue option is not selected on the Installation Options - Contracts page.
Analysis Type |
Select the analysis type to stamp on the target revenue fee rows that are created from the revenue fee worksheets. Revenue target fee attribute analysis types identify rows for revenue recognition processing for the contract lines. Note. The analysis type that you select must be associated with the PSRV2 analysis group in Project Costing. This is a required field. |
Source Type |
Select the source type to stamp on the target revenue fee rows that are created from the revenue fee worksheets. Note. Only one source type can be selected for the target revenue fee row. This is a required field. |
Category |
Select the category to stamp on the target revenue fee rows that are created from the revenue fee worksheets. Specifying a category is optional, but enables you to further identify the revenue fee row that are being created. For example, you can identify revenue fee rows for fixed fees as CPFF (Cost-Plus Fixed Fee). Only one category can be selected for the target revenue fee row. Only categories that were previously defined in Project Costing can be selected. |
Subcategory |
Select the subcategory to stamp on the target revenue fee rows that are created from the revenue fee worksheets. Specifying a subcategory is optional, but enables you to further identify the revenue fee row that is being created. Only one subcategory can be selected for the target revenue fee row. Only subcategories that were previously defined in Project Costing can be selected. |
Source Type |
Select the Project Costing ChartField source types that you want to fully exclude in the fee calculations for the fee type defined under the Contracts business unit. You can exclude as many source types as needed, but you cannot use a wildcard in this field. The system cannot calculate billing or revenue fees when you use a wildcard. Note. The system will exclude any source types that are selected on this page from both billing and revenue fee calculations. |