Understanding Alternate Accounts

In addition to the following overview, this section also discusses:

  • Alternate account mapping and SetID sharing.

  • Prerequisites.

PeopleSoft delivers alternate account functionality for its applications as an optional feature to meet the accounting and reporting requirements of multinational organizations that operate in locations, jurisdictions, or countries where statutory or local chart of accounts and reporting rules are mandatory.

By using alternate account, you can enter and maintain both a statutory (local) account value and a corporate (internal) account value at the detail transaction level within General Ledger, as well as within its feeder applications. Alternate account operates with and fully supports the conventional corporate chart of accounts that is required for internal management and external financial reporting. You can also perform year-end closing on alternate account only.

Throughout this documentation ALTACCT, AltAccount, alternate account and local or statutory account are synonymous terms and are used interchangeably.

In addition, ACCOUNT, account, and internal or corporate account are synonymous terms and are also used interchangeably.

Implementing alternate account in General Ledger and its feeder systems, such as Receivables and Payables, requires close coordination of ChartFields, business units and ledgers within the system. Alternate account is best put into place when it is a part of the original overall implementation plan; however, you can add it at a later date.

Note: Alternate account is intended to fulfill a journal line statutory, or local, reporting requirement. Non-statutory ledger reporting can best be served by using trees, summary ledgers, and PS/nVision to manipulate the account structure and fulfill corporate ledger balance reconciliation and reporting requirements. Do not use the alternate account feature for ledger-level reporting requirements that are not associated with statutory compliance. The alternate account feature increases maintenance as it requires an additional detail chart of alternate accounts.

Alternate account is designed for international companies to meet local or national statutory requirements at the journal line or transaction level. Therefore, it is available in General Ledger, as well as general ledger feeder applications, subsystems, and other products, as detailed in the following list:

  • Payables

  • Receivables

  • Asset Management

  • Billing

  • Expenses

  • General Ledger

  • Inventory

  • Cash Management

  • Deal Management

  • Risk Management

  • Order Management

  • Project Costing

  • Purchasing

General Ledger is not required to use alternate account with other PeopleSoft products.

You map ALTACCT and ACCOUNT values to one another in either a one-to-one or one-to-many relationship.

The basic level of reporting is defined by the level of detail in the statutory chart of accounts. The most common scenario is that of one or many account values mapped to one alternate account value. This mapping is done by using the Alternate Account page.

If you map one account value to one or many alternate account values, you use the Account page. The mapping of one corporate (internal) account to many statutory alternate accounts is less common. In this scenario, ALTACCT level detail does not contain the basic elements of the transactions in support of detailed alternate account reporting.

You can also provide values for ACCOUNT to ALTACCT and ALTACCT to ACCOUNT suspense. The Journal Edit process uses these entries as the suspense account and alternate account if an Account or Altacct value that is used in a journal is not mapped to an alternate account or account. Suspense entries are errors that must be corrected. If you leave the suspense fields blank, the Journal Edit process also shows the line as an error that must be corrected.

Although you can map an account to multiple alternate accounts and also map an alternate account to multiple accounts, you enter transactions in a one-to-one relationship.

When you enter a transaction in the General Ledger or its feeder systems by using a primary Account ChartField, or corporate accounts, the system also enters the transaction to the alternate account.

Similarly, when you enter a transaction to the Alternate Account ChartField, statutory accounts, the system enters the transaction to the corporate or primary account ChartField.

You can override these values by selecting other values from prompt lists that display only mapped values.

Alternate account relationships can be different for various countries or local reporting entities using PeopleSoft SetID functionality.

You can also designate an alternate account value as a Control Account to make certain that control account updates are generated only through system processes. This helps to ensure that the total of the detail that is in the various related feeder systems, such as Payables, Billing and Accounts Receivable, equals the total of the control account that is maintained by the feeder system for the general ledger.

You can do consolidations over alternate account when you designate alternate account as the anchor ChartField. This provides added flexibility for multinational companies that prepare consolidated statutory financial statements in compliance with local or government reporting requirements.

You map a corporate chart of accounts to one or many statutory charts of accounts. For example, you could have one chart of accounts for each country or local office that requires statutory accounting and reporting. When you couple this with the ability to share SetIDs, you have a very efficient solution.

One account value identified by a SetID can be mapped to 1 or many alternate account values. In turn, 1 alternate account value identified by a SetID can be mapped to 1 or many account values. However, any given account or alternate account can be a part of only 1 such mapping.

The following rules govern mapping:

  • Within the same SetID, an account can only be mapped once to an alternate account in the same SetID. In turn, within the same SetID an alternate account can only be mapped once to an account in the same SetID.

  • If you attempt to map a given account to an alternate account or map an alternate account to an account that is already mapped within the same SetID, you receive an error message indicating that the account or alternate account is already mapped.

  • Within a given SetID, you can map an account to multiple alternate accounts as long as each alternate account is in a different SetID; an alternate account that is within a given SetID can be mapped to multiple accounts as long as each account is in a different SetID.

Consider the following examples:

Example 1 - Account>AltAcct Mappings (Same SetID for Account and Alternate Account):

Mapping #3 is not valid because ALTACCT 101000 is already mapped in Mapping #1 within the same SetID to ACCOUNT 100100.

Mapping #5 is not valid because ACCOUNT 140100 is already mapped in Mapping #4 within the same SetID to ALTACCT 140000.

Mapping #

ACCOUNT SetID

ACCOUNT

ALTACCT SetID

ALTACCT

Is Mapping Valid?

#1

MFG

100100

MFG

101000

Yes

#1

MFG 

100100

MFG

101002

Yes

#2

MFG

109000

MFG

101003

Yes

#3

MFG

109100

MFG

101000

No

#4

FS

140100

FS

140000

Yes

#4

FS

140101

FS

140000 

Yes

#5

FS

140100

FS

140500

No

Example 2 - Account>AltAcct Mappings (Different SetIDs for Account and Alternate Account):

In Example 2, Mappings #1 and #2 have an ACCOUNT value mapped to several ALTACCT values having different SetIDs.

Mapping #3a is not valid because the same ACCOUNT value in the same SetID (101000 in CORP) is already a part of the one account to many alternate account mappings in Mapping #1.

Mapping #3b is not valid because the same ALTACCT value in the same SetID (101003 in FRNC) is mapped to the same SetID (CORP) for the account values.

Likewise, mapping #4 is not valid because the same ALTACCT value in the same SetID (106001 in SPAN) is mapped to the same SetID (CORP) for the account values.

Mapping #

ACCOUNT SetID

ACCOUNT

ALTACCT SetID

ALTACCT

Is Mapping Valid?

#1

CORP

101000

FRNC

101001

Yes

#1

CORP

101000 

FRNC

101002

Yes

#1

CORP

101000 

SPAN

102001

Yes

#1

CORP

101000 

SPAN

101002

Yes

#1

CORP

101000 

GMNY

103001

Yes

#1

CORP

101000 

GMNY

103002

Yes

#2

CORP

105000

FRNC

105001

Yes

#2

CORP

105000

SPAN

106001

Yes

#2

CORP

105000

GMNY

107001

Yes

#3a

CORP

101000

FRNC

101003

No

#3b

CORP

100000

FRNC

101003

No

#4

CORP

110000

SPAN

106001

No

Prompting for Account and Alternate Account and TableSet Sharing

To enable prompting for ACCOUNT and ALTACCT for a specific business unit, you must set up the appropriate SetIDs for these prompts by creating tableset sharing definitions.

The following are examples of tableset sharing definitions for ACCOUNT and ALTACCT:

Set Control Value

Business Unit

TableSet Record Group

ACCOUNT SetID

ALTACCT SetID

M60

M60

FS_05

CORP

 

 

 

FS_40

 

FRNC

M61

M61

FS_05

CORP

 

 

 

FS_40

 

SPAN

M62

M62

FS_05

CORP

 

 

 

 

 

GMNY

In the above table, each business unit that is defined by the set control value has access only to the designated SetIDs for the specific business unit. For example, when you create a journal for Business Unit M60, the prompting on ACCOUNT and ALTACCT appears as CORP and FRNC, respectively. Business Unit M60 does not have access to any ACCOUNTS or ALTACCTS under any other SetIDs.