Miscellaneous withholding claims will be paid using a regular voucher (15A claim form). The required fields for these payments are Business Unit, Account, Fund, Class and Budget Reference. The department field should be left blank. The following crosswalk defines which Account is to be used in relation to the current FAAC code.
Miscellaneous withholdings are currently paid from the 99x fund. The agencies use the following account (FAAC) lines.
The payments will use the following Account numbers:
For example, in the ICS system, the payment of Credit Union withholdings is paid using OSF Form 14 and coded with the following:
In the CORE system, the claim is made using OSF Form 15A and coded with the following:
Effective Sept. 1, 2008, all item IDs that contain an alpha at the end will no longer be available for creating purchase orders (POs), requisitions (REQs) and contracts. Any of these Item IDs that are on current contracts will be unavailable the day after the contract ends.
Effective Oct. 1, 2008, the Department of Central Services (DCS) will inactivate all item IDs that contain an alpha at the end. To keep agencies from having issues with POs/REQs, the requisitions and purchase orders must be closed. Upon request a list of POs/REQs can be provided to the agency.
Create a Release from a Statewide Contract (Added - May 15, 2008)
Due to the upgrade and the application of the maintenance packs a couple of issues have been resolved.
Miscellaneous Warrant Date Change (Added - Feb. 25, 2008)
After the 8.9 upgrade in November 2007, warrants processed through the daily pay cycle were dated for the date they were available for release, which was the next scheduled business day. This has caused a timing difference for the warrants created on the last day of the month and the ALLTRANS Warrant file extract. Effective Feb. 25, 2008, warrants will be dated the same day they are created. In order to transition to the current date, warrants created Feb. 22, 2008, were dated Saturday, Feb. 23, 2008. This will be important when running reports that prompt by payment date.
Finalizing Vouchers (Added - Oct. 18, 2007)
The Office of State Finance (OSF) recently identified a current business process that will not work after the upgrade to PeopleSoft/Oracle Financial System version 8.9, which is scheduled for implementation on Nov. 8, 2007.
The process that is changing is finalizing an accounts payable (AP) voucher in months after it is created. The system is designed to allow a user to finalize a voucher at the time it is created, but not months later. The designed process works very well when combined with proper use of quantities, schedules and receiving on purchase orders (POs). However, most agencies do not discover, until after a voucher is paid, that it was the final payment to be made against a particular PO or PO line, or that a certain voucher was not applied to the PO when it was paid. It is usually at that point that the final button is checked and the voucher is sent back through the budget-checking process. This applies the voucher properly to the PO and relieves the encumbrance.
After the financial system upgrade, the only AP vouchers that can successfully go back through budget-checking are those that were created in an open AP period. The OSF business process requires that each AP period is closed after 60 days. This means that only the current month and one previous month are open at any one time. Therefore, any vouchers created prior to Oct. 1, 2007, needing these types of corrections must be finalized and re-budget-checked prior to the system shutdown at 5 p.m. on Nov. 8, 2007. After that date, any vouchers that require finalizing that were created in October 2007, must be finalized prior to Dec. 1, 2007, and so on. Download detailed instructions (.doc, 2 pp, 31.5 KB)about this process.
As fiscal appropriations are lapsing at this same time, it is presumed that agencies would be performing these finalizations prior to Nov. 8 already as part of the close out procedures. However, if you are unable to complete your review and finalizations prior to this deadline, it will be necessary to file an OSF Help Desk case to determine how to resolve the particular voucher, PO or budget issue. Please call the OSF Help Desk at 866 521-2444 or (405) 521-2444 or send an or e-mail to HelpDesk@osf.ok.gov. Help Desk cases will be worked in the order received.
New Deposits journal entry query in Financials (Added - Sept. 18, 2007)
A new deposits journal entry query is now available that includes the "Long Description" field from the journal entry header page.
The query name is OCP_0058_GL_WITH_DESCR. This is the same query that produces the deposits report (OCP_0058_GL) but includes the DESCR (Long Description) field.
The query prompts for the “From” and “To” Business Unit and “From” and “To” journal dates.
Instructions for Summary of Receipts and Disbursements (Added - Sept. 14, 2007)
The Summary of Receipts and Disbursements Report has been changed to omit pages with no activity, and to break out onto separate pages the Agency Special Accounts. The instructions for running the report have changed.
After the process has run to success, click on the Process Name hyperlink and select the last process listed to view the report. Finally, click the View Log/Trace hyperlink to the PDF file.
Warrant Cancellations and Reissues (Added - June 21, 2007)
The Warrant Cancellation form (MWC form) has a column asking if the warrant should be replaced. If the warrant replacement does not require a change to the vendor ID on the Invoice Information page of the voucher, then the warrant can be replaced. Otherwise, the Office of State Finance (OSF) will cancel the warrant and the agency will need to re-enter the invoice. This will ensure that the correct payment information is maintained in the state’s accounts payable system and the correct encumbrances are liquidated.
Examples of when warrants can be replaced are as follows:
Vouchers Processed Against Purchase Orders (Added - June 14, 2007)
A new report has been developed for Purchasing, Accounts Payable and General Ledger users. The report, named "Vouchers Processed Against PO" will enable users to identify issues with vouchers posting incorrectly against a purchase order (POs).
Report Navigation: Purchasing > Purchasing Reports > Vouchers Processed Against PO
The purpose of the Voucher Processed Against PO report is to identify variances between voucher amounts that liquidate an encumbrance versus the voucher actual expended amount.
Listing of Required Report Parameters
- PO Balance = All
+ Includes all PO Distribution lines that have vouchers budget checked against them regardless of available balance.
- PO Balance = 0
+ Includes PO distribution where the PO Encumbrance = Vouchers Expended.
- PO Balance > 0
+ Includes PO distribution where the PO encumbrance is greater then Vouchers Expended. Variance between Vouchers Liquidated and Vouchers Expended should be Vouchers Finalized.
- PO Balance < 0
+ Includes PO distribution were the PO Balance for the Voucher
Key data elements of the report include the following:
The POs listed on report will NOT meet either of the below qualifications
The Report balances to the PO Activity Page and PO Accounting page:
The report identifies variances between the PO Accounting and the PO Activity pages. For example, the voucher amount liquidated encumbrance versus actual voucher expended amount.
If you have questions, please call the OSF Help Desk at 866 521-2444 or (405) 521-2444 or send an or e-mail to HelpDesk@osf.ok.gov.