## TL;DR

The agent resolved the manager from a stale org chart or from the expense's cost center instead of the live approval chain, so findings went to the wrong inbox. Change recipient resolution to query the current approval chain for the flagged expense (the actual approver of record), and verify the address before sending. Findings must go to the person accountable for the expense.

## Error

```text
agent emailed the findings to the wrong manager  -  approval chain misread
```

## Steps

1. Confirm the misrouting: compare the recipient the agent used against the expense's actual approver in the approval chain. Expected: the two differ.
2. Find where the agent sourced the recipient (cached org data, cost-center owner, or a hardcoded mapping). Expected: the stale source is identified.
3. Change the agent to resolve the recipient from the live approval chain API at send time. Expected: the recipient is the current approver of record.
4. Add a pre-send check: the recipient must be an active approver on the flagged expense. Expected: sends to inactive or unrelated people are blocked.
5. Re-send the findings to the correct manager and note the correction. Expected: the right person receives the findings.

## When to use

- An agent sends audit findings to the wrong manager.
- Approval chains changed and the agent uses stale data.
- Findings go to a cost-center owner instead of the approver.

## When not to use

- The right manager got findings with wrong content (a content bug).
- The manager is correct but did not read the email (a follow-up problem).
- The approval chain itself is misconfigured (an admin fix).

## Tool compatibility

Applies to custom audit agents sending notifications (email, Slack; current 2026 releases) integrated with expense approval data.

### Variant phrasings

### findings emailed to a former manager

The org data was stale. Resolve from the live chain at send time.

### audit alert went to the wrong inbox

Verify the recipient against the expense's approver before sending.

### cost-center owner got the findings instead of the approver

The owner and the approver differ. Use the approver of record.

## Why it happens

Org structures churn: managers change, delegations shift, and cost-center ownership differs from approval authority. An agent that caches the org chart or infers the manager from the cost center drifts from reality, and misrouted findings are worse than unsent ones because the accountable person never sees them while someone else sees confidential flags. Resolving from the live approval chain at send time keeps the recipient correct by construction.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DeXco9ZKCuDS6hQJWiGn9A