Showing posts with label PS Finance. Show all posts
Showing posts with label PS Finance. Show all posts
PeopleSoft Finance General Ledger Allocations

What is Allocation and Allocation Types


Allocation is the process of allocating the assets or expenses held by one entity to other entities inorder for them to recognize their own share of amounts. This way you can allocate both monetary and statistical quantities across the entities within the organization.

Working of Allocation Process:


Allocation builds a dynamic SQL statement to select the pool rows from the Pool table. Pool

Record type of Fixed Amount is exception to this.

The dynamically generated SQL Statement contains SELECT, FROM, WHERE clause and

GROUP BY fields based on the Allocation step definition.

Query for Pool:

SELECT Clause includes the following:

1. All Target and Offset fields whose source is from pool or group by pool and basis.

2. Sums the Pool Amount field and Pool base currency amount field.

3. Ledger field

4. Currency control fields CURRENCY_CD and BASE_CURRENCY

FROM Clause includes either one of the following:

1. LEDGER table name defined in the Ledger Template for Ledger Group type.

2. Any Table

WHERE Clause includes the following:

1. All pool fields specified in the pool page

2. Business Unit specified on the Allocation Request page.

3. Fiscal Year and Accounting period derived from Timespan and Request As of Date.

4. All ledgers in the group if the pool record is a ledger group that contains multiple ledgers.

5. Non blank Currency code.

GROUP BY Fields:

All Select fields except the Amount fields.

SQL:


SELECT DEPT_ID, LEDGER, CURRENCY_CD, BASE_CURRENCY,

SUM(POSTED_TOTAL_AMT), SUM(POSTED_BASE_AMT)

FROM PS_LEDGER

WHERE BUSINESS_UNIT = ‘US001’

AND LEDGER = ‘ACTUALS’

AND FISCAL_YEAR = 2006

AND ACCOUNTING_PERIOD = 6

AND ACCOUNT = ‘500500’

AND CURRENCY_CD = ‘USD’

GROUP BY DEPT_ID, LEDGER, CURRENCY_CD, BASE_CURRENCY
Treasury Management (Cash, Deal, Risk Management) 9.1
PeopleSoft Enterprise Cash Management enables you to monitor and forecast cash requirements, perform automated bank reconciliations, distribute payments efficiently and securely, and automatically generate accounting entries. The following enhancements are planned for Cash Management Release 9.1 within these areas.
Integrated Performance Management
In Treasury Management 9.1, we plan to provide the following features to enhance integrated performance management:

Cash Sweep
The goal of the treasury function is to provide liquidity for a business while still earning a good return on its cash. To setup efficient liquidity solutions for an entire organization, many treasurers select banks that have wide geographical coverage and are in a position to offer unified cash management structures in multiple countries. This utilization of multiple banks and bank accounts adds to the complexity of cash management.
The proposed Cash Sweep functionality will allow customers to transfer funds from one account to another. This new functionality will enable treasurers to gain better control and visibility of their liquidity. They will be able to deploy liquidity prudently and take advantage of market opportunities using target balances, threshold controls, or zero balance accounts. This feature enables treasurers to benefit from higher yields and manage bank fees.
Treasury Dashboard
Organizations face complex challenges in controlling and streamlining financial processes in order to improve the bottom line. Treasurers’ lack of visibility into cash positions and daily operational tasks has created a need for a dashboard to efficiently manage their return on cash.
The Cash Management Dashboard will allow managers a unique view of the organization cash position. The dashboard provides cash position by bank or by currency, investment mix, department mix and payment by source. The Treasury Dashboard is a necessary business intelligence tool that allows managers to effectively manage cash within their organizations, saving them time and money. Dashboards streamline the work of the treasurer by providing enormous value as well as a central place to monitor the cash position, payments and investments.
Bi-Lateral Netting
Payment terms that are different in a vendor relationship from those in a customer relationship, even though the customer and the vendor are the same, is a common scenario. This scenario provides challenges in the netting of payments where organizations are not realizing the overall discount terms. In Treasury Release 9.1, we plan to delivers enhancements to netting functionality that rationalize the payables and receivables discount terms to effectively support bi-lateral netting. Organizations will be able to realize savings and financial value.



A chartfield is a set of numbers and codes associated with a particular grant, fund, activity of a grant or fund, department, etc.  Chartfields are not all that complicated; however, they can be confusing at first.  Below is a picture of a typical chartfield area:

An item that is missing from this chartfield, but required for all chartfields, is the Business Unit.  The reason the Business Unit field is not present here is because it was asked for in the top portion of this document since it is absolutely essential that it be properly field out.  This field and the other chartfield fields are discussed in detail below.


This refers to the entity that is expending or receiving funds.  For instance, typically you will see, “BKCMP,” which stands for “Bakersfield Campus,” in this field.  Another Business Unit that may be seen is, “BKFDN,” which stands for “Bakersfield Foundation.”

This field defines the type of expense (accounts beginning with a “6”) or revenue (accounts beginning with a “5”).  The values in this field are independent of any other field as they are derived from State account codes and are used for State audit purposes.  For instance: a person purchasing office supplies would use the account code 660003 since the description for that account code is “supplies and services.” 

This specifies which fund the money will come from or go into.  These funds are campus fund accounts.  For instance: BK001 refers to the campus general fund, where as MT020 refers to the majority of Grant Funds. 
Note: Some grants are large enough that they will be given their own Fund Code other than MT020.

This specifies the department that the funds will go to or come from.  This is required as it tells you who is asking for the funds to be spent or received.  For instance: the Grants department is D10730.  If procurement receives a requisition order from the Grants department asking for items to be purchased using the MU001 fund code, they would call the Grants office and ask why we are attempting to use funds from ASi fees. 

This field is used to indicate expenditures or revenues that are incurred from campus-wide or group activities without a specified end-date.  Examples of a program are the campus mail-delivery system, the Antelope Valley satellite campus, and the Campus Reserves.   Program codes are not typically used for projects.

This is an important field for our office as it refers to projects that have a specified start and end date.  Typically this means grants.  All of our grants have associated codes with them, usually something like: G10140.  This code will be found within the, “Project” field. 
Note: Some grants are large enough that they will be given their own Fund Code other than MT020.

This code is typically used to provide more details and is used at the discretion of the Administrator for the associated project/ program/ fund.  For instance, a paper program might include revenue from the use of copiers and the use of printers.  The chartfields for those would have the same account code ( 580090 – “Revenue Other” ) but nothing to delineate between the revenues earned from copiers and the revenue earned from printers.  To be able to get this information, class codes would be implemented (C0001 ---> C0050 are user defined) to better describe the source of revenues.  Class codes are also good to use when tracking expenses by person within a particular program or grant if needed.

Chartfield Example
A completed chartfield will typically look something like the following:

Bus. Unit:        Account:         Fund:      Department:   Program:        Project:            Class:
BKCMP          660003            MT020   D10730                                G10140           C0001

In this example, the business unit doing business is the Bakersfield Main Campus (a.k.a. “CSUB”), the budget statement account being expensed is 660003 (all accounts that start with “6” are expense accounts), the money is coming from the Grant Fund and the transaction is being charged to the NSF grant project under the Grants Department.



Share/Bookmark



Accounts Payable
The Accounts Payable application is used to enter vouchers (online or
batch) and make payments to vendors. Major Accounts Payable business
processes are:
• Vendor Maintenance (shared with Purchasing).
• Non PO Vouchers
• PO Vouchers
• Matching with PO and Receiver
• Payments
• Vendor Contracts
• Accounting Entries to General Ledger
• Asset transactions to Asset Management



Share/Bookmark


General Ledger
The budgets, budget checking rules, ledgers, and chart of accounts are
setup in General Ledger.
The major General Ledger processes are:
• Manage/maintain budgets.
• Maintain chart of accounts.
• Journal entries.
• Maintain ledgers.
• Close ledgers.
• Run allocations.
• Receive accounting entries from all other modules.
• Reporting.



Share/Bookmark



Share/Bookmark