Understanding Accounting Status Codes

This topic explains how to interpret ACCOUNTING_STATUS_CODE values (for example, REBNP, RNBNN) in Project Cost Distribution by decoding the accounting status of the raw, burden, and burdened cost layers and linking each combination to common accounting setups and processing outcomes.

These codes summarize the accounting status of:

• Raw cost
• Burden cost
• Burdened cost

Understanding these values helps you validate accounting behavior, troubleshoot missing entries, and confirm that project and accounting configurations are working as expected.

What the Accounting Status Code Represents

The ACCOUNTING_STATUS_CODE follows a five-character structure:

R<X>B<Y><Z>

Each position represents the accounting status of a specific cost layer:

1–2	Raw cost	Base transaction cost
3–4	Burden cost	Indirect or overhead cost
5	Burdened cost	Total cost (raw + burden)

Status Values

Each layer is assigned one of the following values:

N	Not eligible for accounting
E	Accounted externally
P	Accounted by Projects

Use these values to determine whether accounting is expected and where it is generated.

How to Interpret the Code

Read the code from left to right, evaluating each cost layer independently:

• Raw cost (R<X>): Indicates how the base cost is accounted
• Burden cost (B<Y>): Indicates whether overhead cost is accounted
• Burdened cost (<Z>): Indicates whether total cost is accounted

This layered structure reflects how accounting is processed across cost components.

Why Mixed Codes Occur

You may see combinations such as REBNP or RPBNP, where different layers have different statuses.

This happens because:

• Raw cost accounting may originate from source applications or external systems
• Burden and burdened accounting are controlled by project type accounting options
• Accounting is processed at different stages depending on:
  • Burden generation
  • Cost processing
  • Accounting execution

As a result, each layer can have a different accounting outcome.

Examples

Example 1: REBNP

• R E: Raw cost externally accounted
• B N: Burden not eligible
• P: Burdened cost accounted by Projects

Interpretation:

Raw cost is accounted in the source system. Projects is configured to account at the burdened level, but not at the burden-only level.

Example 2: RNBNN

• R N → Raw not eligible
• B N → Burden not eligible
• N → Burdened not eligible

Interpretation:

The transaction isn’t eligible for accounting. This typically occurs in adjustment scenarios or when prerequisite processing hasn’t been completed.

Example 3: RPBNP

• R P → Raw cost accounted by Projects
• B N → Burden not eligible
• P → Burdened cost accounted by Projects

Interpretation:

Projects generates accounting for raw and burdened costs, but not for burden-only costs.

How to Diagnose Unexpected Values

Use the following steps to troubleshoot accounting status codes:

1. Review project type accounting options

   Confirm whether the project type is configured to create:

   • Burden cost accounting entries

   • Burdened cost accounting entries

     These settings directly determine whether burden and burdened layers are eligible for accounting.

2. Verify burden cost processing

   Ensure that burden costs are calculated and applied before accounting is executed.

3. Check the accounting source of raw costs

   If the raw cost status is E, confirm that accounting was performed in the source application.

4. Validate processing sequence

   Confirm that required processes have completed, such as:

   • Cost import and processing
   • Burden generation
   • Accounting creation

5. Review transaction eligibility

   Ensure that the transaction:

   • Is in an accounting-eligible state
   • Falls within valid accounting and project periods

Tips and Considerations

• Accounting status codes reflect current processing state, not just configuration
• A value of N may indicate:
  • Configuration settings
  • Incomplete processing
  • Ineligible transaction types
• Mixed codes are expected in environments where:
  • Multiple source systems provide costs
  • Accounting responsibility is shared between systems
• Always evaluate accounting status in conjunction with:
  • Project setup
  • Transaction source
  • Processing stage

Example Scenario

A project receives supplier invoice costs from an external system and applies burdening in Projects.

1. Raw costs are imported and already accounted externally.
2. Burden costs are calculated within Projects.
3. The project type is configured to create accounting only for burdened costs.
4. After running accounting, the transaction shows REBNP.

Result:

• Raw cost remains externally accounted
• Burden isn’t separately accounted
• Burdened cost is accounted in Projects

This confirms that accounting behavior aligns with the configured design.