Managing Treasury Accounting

This chapter provides an overview of the Treasury Management accounting process and discusses how to:

• Establish accounting templates.

• Process accounting entries.

• Manage accounting entries.

• Review accounting information.

• Maintain fiscal period closure.

Understanding the Treasury Management Accounting Process

You use accounting templates to define the ChartFields used for various kinds of accounting activities, called accounting events. By associating accounting templates with accounting events, you can automate most of the accounting process. In addition, you can also manually adjust accounting entries and create ad-hoc entries.

Accounting Templates

The accounting template depicts the correct accounting and debit/credit configuration for a given treasury transaction/business event. For example, the purchase of a U.S. Treasury bond may involve the construction of two debit lines, Bonds Receivable and Unamortized Bond Discount, as well as one credit line, Cash. The accounting template for this type of transaction would include three predefined records to depict this particular debit/credit configuration.

The accounting template contains the following characteristics:

• A unique template ID.

• Options that determine how the correct ChartField combination is selected.

• An attribute (calculation type) that describes how the accounting monetary amount is calculated or derived.

• An attribute that designates whether the accounting build requires review.

Accounting Events

An accounting event describes the treasury business process activity that triggers the construction of a pending accounting build.

PeopleSoft delivers the following treasury accounting event types with the system:

• Deal transactions.

• Facility, deal, wire, and letter of credit fees.

• Bank transfers.

• Bank statement processing transactions.

• Hedges.

• EFT requests.

• Internal account interest.

• Investment pool transactions.

To automate accounting entries, you assign each accounting event type to a corresponding accounting template for all accounting events except Bank Transfers. Bank Transfers do not have accounting templates as the accounting is derived from the bank and business unit of the bank. The template controls which ChartFields and monetary amounts to use in each accounting entry.

For treasury deals, you define the accounting event at the instrument level. You associate each instrument with various accounting events, depending on the instrument base type. In addition, you define each accounting event based on the accounting treatment (Held to Maturity, Available for Sale, Trading, or Other) and assign each accounting template to the appropriate accounting treatment. At deal entry, you select the appropriate accounting treatment. The system then automatically associates the appropriate accounting template, based on the instrument type's accounting treatment.

The following diagram illustrates the process flow:

Process flow for treasury accounting

Interunit and Intraunit Processing in Accounting

The PeopleSoft centralized processor generates the due-to/due-from entries for both interunit and intraunit balancing. Treasury Management provides functionality to support interunit and intraunit processing using the centralized processor on the Accounting Template and Accounting Entries pages.

Interunit and Intraunit Balancing Methods

Interunit refers to balancing transactions that involve two general ledger business units. The bank accounts contain the ChartFields and the rules by which their values should be determined.

Intraunit refers to balancing transactions within same general ledger business unit in which the transaction involves more than one value on the lower level balancing ChartField. For all transactions that Treasury Management generates, the system obtains the ChartFields from either the bank account or an accounting template. Inherited ChartFields get their values from the corresponding ChartField on the offsetting entry.

Treasury System Transaction Definitions

To facilitate interunit and intraunit processing, you segregate your interunit and intraunit payable and receivable accounts by the type of transaction. The interunit and intraunit system transactions are a predefined list of transactions, with one system transaction for each major type of Treasury transaction that generates interunit and intraunit entries. By defining transaction codes and associating them with system transactions, you control the level by which you segregate your Interunit and intraunit balances.

Important! PeopleSoft delivers predefined system transactions, which you can view on the System Transaction Definition page. You should not change the information on this page because it affects the intraunit and interunit processing.

See Running the Centralized Interunit and Intraunit Processor.

Intraunit and Interunit Accounting Entries Generation Using the Centralized Processor

Here’s an overview of the process:

1. Specify an anchor entry in the accounting template as a model for any interunit and intraunit entries.

   The anchor entry may not be a line where the ChartField is determined by Bank Account.

2. Process treasury accounting using the Automated Accounting process (TR_ACCTG), which invokes the centralized processor. The centralized processor automatically creates any necessary offset entries tagged with a source identifier label, System IU (viewable on the Additional Details tab of the Accounting Entries page) and inserts this data into the accounting tables.

3. If you make any changes to an accounting entry line, you must click the Update Accounting button to invoke the centralized processor and regenerate accounting entries.

See Also

Entering Accounting Template Information

Processing Automated Accounting

Product Interface and System Transaction Categorization

Establishing Accounting Templates

To define accounting templates, use the Accounting Templates component (ACCTG_TEMPLATES_GBL).

This section discusses how to:

1. Enter accounting template information.

2. Define additional substitution criteria.

3. Link accounting events with the associated accounting template.

Pages Used to Establish Accounting Templates

Entering Accounting Template Information

Access the Accounting Templates - Template page.

Requires Review	Select to force review of the accounting transactions that use this template. When selected, the system assigns error-free accounting entries using this template a Provisional status. To finalize the provisional entry, use the View/Approve Entries page to review and to change the status to Final. If Require Review is not selected, the system assigns error-free accounting entries using this template a Final status.
Source Type	Source of the accounting entry, either BSP (bank statement processing), Deals, Fees, Hedge Accounting, Interest, EFT Requests, or Investment Pools.
Status	Indicate if this accounting template is Active or Inactive. This determines which templates are available to users. The system selects only active accounting templates for display and use. This feature enables you to: Retain all the accounting templates you create, both current and discontinued. Research the accounting for all your accounting entries, whether the respective accounting template is active or not. When an accounting template is marked inactive it is not available for processing, but is retained for historical reference. If you need to review accounting entries processed by an inactive accounting template, the template is still present in the system.
Document Type	Select the document type that will be used as the basis for assigning document sequencing numbers to these types of transactions. See Defining Document Sequencing.
VAT Defaults	Click to access the VAT Defaults Setup page. The VAT Defaults Setup page is a common page used to set up VAT defaulting for all PeopleSoft applications processing VAT transactions. On this page you can define accounting template defaults as applicable. You must first specify one of the accounting lines as a VAT applicable line to establish VAT defaults for this template. See Working with VAT.

Line Detail Tab

Select the Calc Type (calculation type) to use on each template line—this varies depending on the source type. For deal-related calculation types, you must also specify a transaction line and leg of the deal.

The following table lists each available calculation type by source type.

ChartField Tab

Enter the appropriate ChartField values.

Stat (statistic)	Select a statistics code for the specific accounting line. This field is editable on the accounting entry.
VAT Line	Click to specify that VAT is applicable for this accounting line. You can specify VAT options only for accounts with: The VAT Applicable Flag check box selected on the Account page. See Adding Account Values. Source types of BSP or Fees.

See Also

Entering Accounting Template Information

Using Statistics

Defining Additional Substitution Criteria

Access the Accounting Templates - Substitution Rule page.

Use substitution rule functionality to make minor adjustments to templates without having to rebuild them. For example, you might require that certain departments perform deal accounting on deals by dealers, by specifying criteria for each dealer’s user ID. Using this example, when the DEALER_OPRID equals a particular dealer, such as BIA1, then the department ChartField equals 13000.

Linking Templates with the Associated Accounting Events

Accounting events are linked with their corresponding accounting templates on various pages, which is defined in this table:

Processing Accounting Entries

In this section, we discuss how to run the Automated Accounting process (TR_ACCTG). During processing, the program “calls” the centralized processor to generate inter/unit and intraunit balancing (IU_PROCESSOR).

These diagrams illustrate the inbound and outbound transaction processes.

Outbound transaction process

Inbound transaction process

Understanding the Automated Accounting Build Process

The Automated Accounting process populates the treasury accounting event calendar with transaction reference information, event type, event date, template ID, and processing state.

When specific processing events occur (as shown in the following table), the program that builds automatic accounting entries selects any unprocessed transactions from the treasury accounting event calendar and copies them into the Accounting Entries table.

Once the underlying data is established, the Automated Accounting process works as follows:

1. Selects unprocessed records with the correct event date from the Accounting Event table.

   • Process inbound cash flows unconditionally upon receipt of cash.

   • Process outbound cash flows after transactions have been approved and sent to the bank.

2. Constructs the ChartField combination according to the appropriate accounting template.

3. Retrieves the correct monetary amount according to the calculation type.

Pages Used to Process Accounting Entries

Processing Automated Accounting

Access the Automated Accounting page.

Note. The process creates accounting entries even if errors occur. Use the Accounting Entries page to correct any errors, then change the status from Error to Provisional. Use the View/Approve Entries page to change the Provisional to Final.The accounting entries are then ready for General Ledger. You do not have to rerun the Automated Accounting process.

Managing Accounting Entries

This section discusses how to:

• Adjust accounting entries.

• Create ad hoc accounting entries.

• Review and approve accounting entries

• View the accounting summary.

Common Elements for this Section

Pages Used to Manage Accounting Entries

Adjusting Accounting Entries

Access the Accounting Entries page.

Event	Displays a descriptive label for the accounting entry, based on the source code value.
Source Code	Displays the accounting entry source, as processed by the Automated Accounting process, or entered on a manual Accounting Entry.
Source ID	Displays the unique identification number on the source side for the accounting entry.
Acctg Date (accounting date)	Displays the date the entry was processed through Automated Accounting, or entered as a manual Accounting Entry.
Status	Indicates the current condition of the accounting entry. Values are: Provisional: The entry is not finalized. You can make any required changes. Error: An error exists within the accounting entry. The system assigns this status—you cannot select it. Once you correct an error, change the status to Provisional. After the status has been changed to Provisional use the View/Approve Entries page to change the status to Final. The entry is then ready for the Journal Generator process—you do not need to reprocess it. Final: The entry is ready for Journal Generator processing and is free from errors. Until the entry is actually processed through the Journal Generator process, you can continue to make changes to it, even if the status is Final. Once the Journal Generator processes the entry, the distribution status changes to Distributed, indicating it has been posted to a General Ledger journal and no further modifications can be made.
Acctg Template (accounting template)	Displays the name of the accounting template attached to the accounting entry. Note. If you use General Ledger, you can automatically reverse any unrealized gain/loss accounting generated by Treasury Management at the next accounting period. You need to create a journal template for this type of treasury accounting and enable the feature for automatic journal reversal. You must assign this journal template to the treasury accounting template in order for General Ledger to perform the automatic reversals.
Error	Indicates the error source of an automated accounting entry. Values are: None: No error condition exists. This appears when status is provisional or final. Unbalanced: Debits do not equal credits, or debits and credits are not equal, but refer to different General Ledger business units. CF Combo Error (ChartField combination error): The ChartField generated is invalid. No Exchange Rate: The currency exchange rate for the applicable currency pair is missing. The base amount could not be converted to the accounting entry currency. Account Not Specified: The account was undefined, and the amounts cannot be distributed. IU Processor Error: The centralized processor encountered an error. Review the accounting entries, correct any errors, then click the Update Accounting button to regenerate accounting.
Requires Review	If selected and uneditable, this indicates the Review Required option is enabled in the accounting template on which this was based.
Integration Status	Displays the status of the integration between Treasury and PeopleSoft EnterpriseOne General Accounting. This field only appears if the integration is enabled on the Installation Options - Treasury page. The values are: Pending: The entry is ready to be sent to the Integration Broker for transmission to the EnterpriseOne General Accounting. Sent:The entry has been sent to the Integration Broker. Received: The accounting entries have been loaded into the EnterpriseOne staging table. Loaded: The accounting entries have been loaded into the EnterpriseOne application tables. Posted: The accounting entries have been posted to the EnterpriseOne General Accounting. Error: Indicates that the accounting entry contain erroneous data or an error occurred somewhere in the data transmission process and must be resent. Note. If an entry must be resent, the integration status can be changed to Pending unless the integration status is already displayed as Posted. See Defining Treasury Installation Options. See PeopleSoft EnterpriseOne 8.12 Application Integrations with PeopleSoft Enterprise Applications, “Using the PeopleSoft Enterprise Treasury with PeopleSoft EnterpriseOne General Accounting Integration”

Accounting Entries

ChartFields Tab

Select the ChartFields tab.

Stat (statistic)

If a statistics code is set for this accounting line on the template, that code displays here. You can edit this field. Select a statistics code—the associated UOM displays for the selected code. You must also enter a Statistic Amount with which to measure the statistic.

See ChartField Values.

Additional Details Tab

Select the Additional Details tab.

Line Source

Displays either Treasury for accounting lines generated by the treasury accounting program, or System IU for accounting lines generated by the centralized processor.

Journal Tab

Select the Journal tab.

Combo Status	Indicates whether the ChartField combination that the system built based on the accounting template is Valid or Invalid.
GL Status (General Ledger status)	Provides information on the entry’s posting status. Possible values include: Distributed: Distributed to a General Ledger journal. Hold: An error condition exists; the entry must be corrected before Journal Generator can process it; or the entry requires review. None: The entry has been created without errors, but has not been processed by the Journal Generator process.
Ledger Group	Indicates the general ledger group associated with the General Ledger Unit on the accounting line.
Ledger	Indicates the general ledger associated with the General Ledger Unit on the account line.

See Also

Establishing Accounting Templates

Reviewing VAT Accounting Entries

Creating Ad Hoc Accounting Entries

Access the Accounting Entries page.

The Source Code, Source ID, Event, and Accounting Template fields are optional.

• If you complete the Source Code, Source ID, and Event fields, the system can create a link between the manual and the automated accounting results.

• If you input manual entries on a recurring basis, you can create and use an accounting template to minimize the data entry process for these entries. Any template you create displays in the Accounting Template field. When you select an accounting template for this ad-hoc entry, the system automatically populates the accounting lines with the template data.

To create ad hoc accounting entries:

1. Enter the Business Unit and optionally, an Accounting ID. Click Add.

2. Select an accounting Event from the following field values:

   • (none)

   • AOCI Adjustment

   • AOCI Reclassify

   • Amortize Adj of Carrying

   • Barrier Rebate Payment

   • Commodity Cash Difference

   • Commodity Settlement

   • Deal Booking

   • Deal Maturity

   • Derecognize Firm Commitment

   • Discount Accrual

   • Fair Value Hedged Item G/L

   • Fee Accrual

   • Firm Commitment to Carrying

   • Forward Points Accrual

   • Generic Cash Flow

   • Initial Payment

   • Interest Accrual

   • Interim Principal Payment

   • Mark to Market

   • Maturity Payment

   • Option Cash Difference

   • Option Exercise

   • Option Premium Accrual

   • Periodic Payment

   • Premium Payment

   • Sell / Buyback

   • Transaction Fee

   • Will Not Occur - AOCI Reclassify

3. Specify a Source Code.

4. Select a specificSource ID of the selected Source Code.

5. Review the Acctg Date (accounting date) for accuracy.

6. The default Status for ad-hoc entries is Provisional. Do not change this setting.

7. The Require Review check box is automatically selected for ad-hoc entries. You cannot clear this check box.

8. (Optional) Enter a Description.

9. Select an Acct Template (accounting template).

10. Enter at least one debit and one credit line to balance the entry, and select one line as the IU Anchor.

11. Enter an Account and any other ChartFields for each line.

12. Select TR_ENTRIES for the Journal Template.

13. Click Update Accounting to run the centralized processor function, which creates any necessary offset entry lines and saves the manual accounting entry.

If the debits and credits do not balance, you receive an error message and the accounting entry is not saved. Make the necessary corrections, and then save the page.

Note. Once the Journal Generator processes the entry, the distribution status changes from None to Distributed, and no further changes can be made.

See Also

Adjusting Accounting Entries

Reviewing and Approving Accounting Entries

Access the View/Approve Entries page.

Note. Use PeopleSoft Security functionality to identify which users have access and approval privileges to provisional accounting entries. You can define permission lists and accessible pages for a specific UserID.

See Also

Enterprise PeopleTools 8.48 PeopleBook: Security Administration

Viewing the Accounting Summary

Access the Accounting Summary page.

Reviewing Accounting Information

You can inquire on various aspects of your accounting activity.

Common Elements Used in this Section

Pages Used to Review Accounting Information

Maintaining Fiscal Period Closure

This section discusses how to maintain fiscal period closure functionality.

Fiscal Period Summary Page

The Fiscal Period Summary page enables you (or those users with end-of-period accounting responsibilities) to manage your fiscal period close process and the integrity of closed fiscal periods. Once you close a fiscal period, system processes prevent users from running Treasury Management accounting processes for that period. This helps ensure accurate end-of-period reporting and analytical results, as any additional accounting for the period is transferred to and handled by the next accounting cycle. This type of fiscal period close is considered a “soft-close” of your accounting ledger, as the closure only occurs in the Treasury Management product, not the General Ledger product.

If another user (such as an accounting clerk) attempts to run accounting on entries of the closed fiscal period, the system will not run the accounting request. Functionality on the Automated Accounting and the Process Scheduler pages prevents the process request from occurring.

When you close or reset an entry or entries in a series of entries, the system enforces closing or resetting the entries in a certain logical order. This is to maintain the integrity of your Treasury Management accounting entries. You can also reset (open) any fiscal period that may have been closed in error. The system tracks and displays your most recent action for each fiscal period row on the Audit Detail page, providing an activity log.

In addition, individual business units can maintain their own Treasury Management close cycle calendars, independent of the close cycle performed for the general ledger. This means one of your Treasury business units can close using a weekly calendar, while another Treasury business unit can close using a monthly calendar.

Prerequisites

Before configuring the Fiscal Period Accounting Summary page:

• Confirm that only those users who need access to this page have access permission, as defined in the permission lists associated with their user profile.

• Verify that the Treasury business units you will use in this page are defined with a Calendar ID on the Treasury Options page (BUS_UNIT_OPT_TR).

See Also

Defining Business Calendars

Defining Treasury Business Unit Options

Enterprise PeopleTools 8.48 PeopleBook: Security Administration

Page Used to Maintain Fiscal Period Closure

Maintaining Fiscal Period Closure

Access the Fiscal Period Summary page.

When you add rows to existing fiscal period information, the system automatically populates the Fiscal Year and Period fields with the next chronological period.

Note. Rows must be closed in ascending entry order, from first entered row to last entered row. For example, if you wish to close Fiscal Year 2002, Period 2, you must first close Fiscal Year 2002, Period 1. Conversely, rows must be reset in descending entry order. Using the previous example, you need to reset (or open) Fiscal Year 2002, Period 2, before you can reset Fiscal Year 2002, Period 1.

To close a fiscal period:

1. Enter the Business Unit and a Calendar ID. Click Add.

2. Select a Fiscal Year.

3. Select an accounting Period.

4. If you want to close this fiscal period, select the Close Acctg (close accounting) check box.

To reset a closed fiscal period:

1. Click Reset. The system enables theFiscal Year and Period fields, and automatically clears the Close Acctg (close accounting) check box.

2. In Reset Reason, overwrite any existing text with the reason for the fiscal period reset.

The Audit Detail page lists audit information for each row.