Diagnose Why Costs Did Not Capitalize

This topic provides the steps to diagnose why transactions did not capitalize and explains how the assistant describes the current blocker and next step.

Diagnose by Project Review

After you drill into a project-level result group, ask the assistant to diagnose the displayed transactions.

The assistant checks capitalization prerequisites and identifies the current blocker preventing asset lines from being generated.

Example blockers include:

No eligible project asset exists
Accounting is not complete
Project assets are not assigned
Project or task setup prevents capitalization
Capital event setup is incomplete
A transaction was already capitalized

Diagnose by Transaction Number

Use this workflow when you already know which transactions need investigation.

Steps to Diagnose by Transaction Number

Open the assistant.
Enter up to 50 transaction numbers.
Ask why those costs did not capitalize.
Review the blocking reason and recommended action.

This approach is useful when transaction numbers already came from a report, reconciliation, or earlier review.

Follow-Up Questions

After diagnosis, you can ask follow-up questions about the latest result without restating all prior details.

For example, you can ask about:

The task associated with the diagnosed transactions
The current result set already under discussion
A different issue group or summary already shown in the conversation

Example

A project accountant drills into one task group and wants to know why the displayed transactions did not capitalize.

Here's a sample conversation that the project accountant can have with the assistant:

User: Group by task
Assistant: Here is the pending capitalization summary grouped by task.
User: row 3
Assistant: Here are the transactions for task PJC_DCI_SEP-5.0.
User: Diagnose everything

This example shows that the assistant can move from a grouped summary to transaction-level diagnosis without requiring the user to restate the full context.