Breadcrumbs

Investigate Cost Pool and Tower mapping with AI

Use Investigate with AI in Yarken Designer to review incomplete spend allocations and proposed Cost Pool or Tower mapping rules.

Example: Review an unallocated cloud spend group

Scenario: Cost model owner finds cloud spend not assigned to intended Cost Pool.

  1. Open affected Cost Pool month, choose Map manually then Investigate with AI.

  2. Inspect proposed mapping based on vendor, account, and service attributes; read reasoning and confidence.

  3. Check rule condition against sample records. If too broad, ask Copilot to suggest narrower condition or reject proposal.

  4. Accept and generate rule only after confirming its financial classification. Compare unallocated amount and mapping coverage afterward.

Investigate a Cost Pool allocation

  1. Go to Admin > Yarken Designer > Spend Model > Cost Pools.

  2. Find month with incomplete allocation.

  3. Select + Add on relevant month card.

  4. Choose Map manually, then Investigate with AI.

  5. In investigation window, start investigation. You can also open chat, enter custom instructions, or continue manually.

  6. Review proposed mapping rule.

  7. Expand rule to inspect reasoning, signal, condition, and confidence.

  8. Select Accept Rule if valid, or Reject if incorrect.

  9. For an accepted rule, select Generate Rule to save it.

Investigate a Tower allocation

  1. Go to Admin > Yarken Designer > Spend Model > Towers.

  2. Find month with incomplete allocation.

  3. Select + Add > Map manually > Investigate with AI.

  4. Start investigation or provide custom instructions.

  5. Review proposed Tower mapping, supporting evidence, and rule condition.

  6. Accept or reject proposal. Generate only accepted rule.

Check before accepting

Review:

  • Unallocated group and amount: Spend affected by proposed mapping.

  • Proposed rule: Destination Cost Pool or Tower.

  • Signal and reasoning: Evidence used to suggest mapping.

  • Condition: Whether rule captures intended records without overmatching.

  • Confidence and coverage: Strength of suggestion and records or spend it affects.

Check vendor, account, cost centre, and other relevant attributes against intended financial classification. Do not accept a rule based on confidence score alone. Incorrect broad conditions may affect later mappings.

Ask about the proposal

Use investigation chat, where available, to ask for supporting signals or narrower conditions. Example questions:

What signal supports this mapping?
Which records would this condition include?
Suggest narrower rule conditions using account and vendor.

If proposal is not supported, reject it or continue manually.

Related: AI Studio - Copilots.