You are on page 1of 4

Title: Account Balance to Transaction Integrity Report (P09705)

Abstract: Documents when to run this integrity report and how to interpret its results. The Account Balance to Transaction Integrity Report (P09705) is a tool to assist in locating discrepancies between the Account Balance (F0902) table and the Account Ledger (F0911) table. The report compares balances in the Acount Balance table to supporting transactions in the Account Ledger table. It prints out-of-balance conditions only and does not perform any updates. It is similar to the report-only version of the Repost Account Ledger program (P099102), but starts with the Account Balance table and compares the balances to the posted transactions in the Account Ledger table. The Repost starts with posted transactions in the Account Ledger and compares them with the Account Balance table. The Account Balance to Transaction integrity report identifies balance accounts that do not have supporting account detail. Typical causes for items showing on this report include:

Damaged F0911 records; Post program(R09801) did not complete successfully; Change in Posting Edit Code from S to L; Change in currency codes; Multicurrency settlements turned on and off; Account changed from monetary to non-monetary; Account Balances by Currency turned on or off.

Limit the data selection on this report by including any of the following:

Fiscal Year Ledger Type Company

Do not include any ledger types for which account detail does not exit (such as BA) or every account balance will be listed on the report. Run this report when an out-of-balance condition not located by the Repost Account Ledger program (P099102) exists, or if the system failed while the Post program (R09801) was running. Example of Report

In the example above, for account 1.1110.BEAR, the report shows a difference between the F0902 balance and the F0911 detail. The Repost Account Ledger program (R099102) also would have shown this difference because the account has transactions in both tables. If the Repost Account Ledger program were run in update mode, the F0902 balance would be changed to reflect the balance in the F0911 detail table. However, for account 1.1105 there is no supporting detail in the F0911 table. The Repost Account Ledger program would not report this condition because it looks at records in the F0911 table before it locates corresponding F0902 records. This condition would be found only by running the Account Balance to Transaction report. If, after researching account differences, it is determined that the F0911 records are correct, then run the Repost Account Ledger program to correct the F0902 balance records. Manually correct account balances that have no corresponding F0911 detail using a data file utility.

Title: Correcting Companies that are Out of Balance ---------------------------------------------------Abstract: Documents how to interpret the Companies In Balance integrity report and documents steps for resolution. ---------------------------------------------------COMPANIES IN BALANCE REPORT (P097001/R097001) This report has three columns where a potential out of balance condition could exist. Each company's balance should be zero in each column on the report. Depending on which column an amount appears under, there is a different resolution. The following information will provide research tools and possible recovery methods. AMOUNT IN THE PRIOR YEAR COLUMN This is usually caused from journal entries made to the prior year after the annual close was run. Recovery 1) Execute the G/L annual close for the appropriate company and fiscal year. Rerun the Companies in Balance Report. 2) If an amount still appears, change the fiscal year to the prior year through Company Numbers and Names (P00105). Rerun the Companies in Balance report. Continue this process until the out of balance amount appears in the Year to Date or PACO column. See below how to research Year to Date and PACO out of balance condition.

3) Execute a Trial Balance by BU (P09410) for the end of the previous fiscal year. Then run a Trial Balance by BU for the first period of the current fiscal year. Compare the ending balance on last year's report to the beginning balance on the current year report. If the amounts are different, then a damaged record exists in the Account Balances table (F0902) or the G/L Annual Close program (P098201) may need to be run again. 4) Run the global update programs to verify the integrity of the accounts and company numbers: Update BU.Obj.Sub to Jrnl Ent (P09806) Accounts w/o Business Units (P097041) Acct Balance w/o Acct Master (P097031) Transactions w/o Acct Master (P097021) Acct Balance to Transactions (P09705) AMOUNT IN THE YTD COLUMN This is usually caused when the Account Ledger file (F0911) does not balance to the Account Balance file (F0902), or a batch was posted out of balance. Recovery 1) PeopleSoft World - Execute the Repost Account Ledger (P099102) with the first processing option set for recalculation in the report mode only. PeopleSoft EntepriseOne - Execute the Calculate Fiscal Year and Period program (R099103) with the first processing option set to run in report mode only. If accounts appear out of balance on this report, then run it in update mode. Rerun the Companies in Balance. 2) Execute the Account Balance to Transaction Report (P09705) to see if any "dangling" F0902 balances exist without supporting F0911 detail. Rerun Companies in Balance. 3) Execute the global update programs (listed above). Rerun Companies in Balance. COMPANIES WITH OFFSETTING DEBITS AND CREDITS IN THE YTD COLUMN AN ENTRY TO THE INTERCOMPANY ACCOUNT WAS MISSED OR NOT PROPERLY RECORDED Recovery 1) Create and post a manual journal entry to the intercompany accounts for the amount. Be sure the intercompany flag in the General Accounting Constants is set to *, otherwise the system will create intercompany transactions. 2) Research and correct the Automatic Accounting Instructions for the intercompany items. 3) Research and correct the Account Master (F0901) for improper intercompany accounts. 4) Verify the Intercompany Settlements value is set properly in the General Accounting Constants. OFFSETTING AMOUNTS IN YTD AND PACO COLUMNS FOR THE SAME COMPANY The fiscal date pattern was changed after an entry was posted and the repost was run. This error indicates the company is out of balance between periods only. (Usually caused by a leap year.) Recovery 1) A leap year can cause an issue when entries are created with a G/L date of 2/29, but the period ending date was set to 2/28. If the entry is A/P or A/R, automatic entries can be created at the end of the fiscal period, which in this case would end in March. If the date pattern is changed to end on 2/29, then the Repost Account Ledger with the processing option set to recalculation must be executed. This will recalculate any entries with the G/L date 2/29 and correctly place them in the proper period ending 2/29. However, since the automatic entries were created with a G/L date ending in March, they will not be reposted into the period ending 2/29. Manual journal entries will need to be created to correct these entries. Enter two one-sided journal entries to remove the amounts from the period ending in March and add the entries to the period ending 2/29. Post these entries out of balance. 2) Reversing one-sided entries can be made to correct the period postings. AMOUNT IN PACO COLUMN An entry is posted into the next fiscal period or year that does not net to zero.

Recovery 1) Run a Trial Balance by BU (P09410) for future fiscal periods and years to locate the entry. Research and determine of if two one-sided journal entries are needed to move the amounts to the proper periods. Post these entries out of balance. 2) Run the Company by Batch Out of Balance (P09706) to determine if any batches had posted out of balance for the company showing the PACO amount. Make correcting entries as necessary. OTHER RESOLUTIONS If problems persist, check for damaged F0902 records. These would include: Records without a value in fiscal year Records without a company number Records without a ledger type Records without a short Account ID Records where the short Account ID is not updated correctly with the leading zeros. The short Account ID is an alpha-numeric field which needs all 8 digits to be populated. Records without a century Document ID: OFN-00-0067 Release: Xe and below