UPDATE: Reclassification Entries for Projects Due to Sub-Ledger Accounting Rules

June 7, 2017

We have posted the reclassification entries for Sub-Ledger Accounting (SLA) issue 1; and SLAs 2, 8 and 11, which have affected accurate processing of transactions between the Projects sub-ledger and the general ledger. Configuration changes and re-class entries are now complete for the 11 SLA rules. Read the email on SLA rules, 1, 2, 8 and 11.

 

May 24, 2017

We have posted the reclassification entries for Sub-Ledger Accounting (SLA) issues 5 and 9, which have affected accurate processing of transactions between the Projects sub-ledger and the general ledger.

Configuration changes have been made to the 11 SLA rules to correct system processing. Re-class entries have been made for seven SLA rules – 3, 4, 5, 6, 7, 9, and 10. We expect to implement and post the remaining re-class entries by the end of next week. Read the email update on SLA rules 5 and 9.

 

May 16, 2017

This page summarizes information, instructions, and action plans to resolve the 11 identified Sub-Ledger Accounting (SLA) issues affecting the propriety of processing transactions between the Projects sub-ledger and the general ledger. In general, correcting these items involves following a 3-step approach for each of the 11 issues.

  1. Develop, test and implement system configuration changes to correct the processing on a go-forward basis.
  2. Develop, test, and post correcting transactions that will, in effect, nullify erroneous automated SLA system transaction processing; and post the transactions as originally intended, applying the desired configuration change logic (termed “re-class entries”).
  3. Reverse manual journal entries, if any, performed by various units as an interim work-around correction.

Read the initial email on the 11 Sub-Ledger Accounting issues, including details on SLA rules 3, 4, 6, 7 and 10.

Resources