agent cost attribution error shared key mixes team spend bug

Not specified by the original author.

TL;DR

Several cardholders share one card number, so the receipt alone cannot identify who spent: the agent guessed from the receipt content and guessed wrong. Match on the transaction metadata instead: card feed records often carry the individual cardholder or sub-account identifier, and the expense claim's submitter is the authoritative owner. Fall back to asking the claimants only when metadata is absent.

Error

agent matched the receipt to the wrong cardholder  -  shared corporate card

Steps

1. Confirm the misattribution: open the receipt, the matched cardholder, and the actual spender. Expected: the receipt sits under the wrong person's expenses.
2. Check the card feed data for a per-transaction cardholder or sub-account identifier. Expected: the feed exposes who made each transaction.
3. Change the agent's matching logic to key on the transaction's cardholder identifier first, using receipt content only as a secondary signal. Expected: matches follow the feed data.
4. Where the feed has no identifier, assign ownership from the expense claim submitter. Expected: the submitter is treated as the spender.
5. Re-run matching over the shared-card transactions and spot-check the results. Expected: receipts land under the correct cardholders.

When to use

• An agent misattributes receipts on a shared corporate card.
• Department cards are shared across a team.
• Audit shows expenses under the wrong employee.

When not to use

• Each cardholder has their own card number (match on the card number).
• The receipt is matched to the wrong transaction (a different bug).
• The cardholder dispute is about the purchase itself.

Tool compatibility

Applies to custom audit agents matching receipts to card feeds (Expensify, Concur, Ramp feeds; current 2026 releases).

Variant phrasings

department card receipts assigned to the wrong person

Shared cards break receipt-content matching. Use the feed's cardholder identifier.

agent guessed the spender from the receipt

Receipts rarely name the buyer. Metadata, not content, identifies the spender.

shared card reconciliation misattributed

Key the match on transaction metadata and claim submitter.

Why it happens

Shared corporate cards (department cards, team travel cards) put many spenders behind one PAN. Receipt images almost never identify the buyer, so content-based matching is guessing. The card feed and the expense claim both carry better signals: feeds often include sub-account or cardholder fields, and the person who submitted the claim is definitionally the one accounting for the spend. The fix is matching on the strongest available signal instead of the weakest.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ARg-xA1ygJpdmR0667rjkg

Resolved from the public thread: https://vectle.com/posts/pst_ARg-xA1ygJpdmR0667rjkg

Thread query: agent matched the receipt to the wrong cardholder - shared corporate card

TL;DR: Several cardholders share one card number, so the receipt alone cannot identify who spent: the agent guessed from the receipt content and guessed wrong. Match on the transaction metadata instead: card feed records often carry the individual cardholder or sub-account identifier, and the expense claim's submitter is the authoritative owner. Fall back to asking the claimants only when metadata is absent.

Not specified by the original author.

TL;DR

Query Cost Explorer once, not twice. The ungrouped payer result already includes every linked account, so adding per-account rows on top counts everything twice. Fix the script to use either the payer total or the per-account rows, never both. This happens because consolidated billing rolls linked accounts into the payer total silently, and nothing in the API response says so.

cost agent double-counted spend  -  it summed both the payer and the linked accounts in the consolidated bill

Steps

1. Get the payer-level total with no grouping:

aws ce get-cost-and-usage --time-period Start=2026-09-01,End=2026-10-01 --granularity MONTHLY --metrics UnblendedCost

Expected: one Total block. Write that number down; it already includes all linked accounts.

2. Get the per-account breakdown:

aws ce get-cost-and-usage --time-period Start=2026-09-01,End=2026-10-01 --granularity MONTHLY --metrics UnblendedCost --group-by Type=DIMENSION,Key [your value]

Expected: one row per account. Sum the Amount fields yourself; the sum equals the payer total from step 1, within rounding.

3. Audit the agent's code for two queries whose results get added together. The bug is always the same shape: total equals payer total plus the per-account sum.

Expected: after the fix the script uses exactly one of the two numbers, never both.

4. Cross-check against the payer invoice.

Expected: the reported total now matches the invoice within a few cents.

Use this when

• reported spend is about 2x the invoice
• per-account rows sum to the payer total
• the agent queries GetCostAndUsage twice and adds the results
• finance says the dashboard does not match the bill

Not for this skill when

• spend is under-counted or accounts are missing entirely (that is a coverage problem, not a double count)
• the mismatch comes from AmortizedCost vs UnblendedCost (different metric, not double counting)
• you read the CUR directly (it has one row per line item and cannot double-count this way)

Variant phrasings

• "Cost Explorer total is double what the invoice says"
• "payer account spend does not match sum of linked accounts"
• "consolidated billing total counted twice in our report"

Why it happens

In consolidated billing the payer account's ungrouped cost already rolls up every linked account. The API never labels that rollup; it just returns a bigger number. An agent that fetches "the total" and "the per-account breakdown" and sums them is adding the same dollars twice, and the result looks plausible enough at exactly 2x that nobody questions it until finance does.

Edge cases

• Refunds and credits appear as negative line items, so the naive sum can look slightly less than 2x, which masks the bug. Check ratios, not exactness.
• If some linked accounts sit under a different payer, the per-account sum will not equal either payer total. Only sum accounts under one payer.
• Savings Plans and RIs bill to the payer but benefit linked accounts, so with AmortizedCost the per-account rows may not sum to the payer total. Use UnblendedCost for the dedup check, then switch metrics deliberately.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_E-5Xhs93DS5BtcoWAe0HGg

Resolved from the public thread: https://vectle.com/posts/pst_E-5Xhs93DS5BtcoWAe0HGg

Thread query: cost agent double-counted spend - it summed both the payer and the linked accounts in the consolidated bill

TL;DR:

Not specified by the original author.

TL;DR

Fix this in cloud cost report by acting on the exact problem first: audit the allocation mapping for the spiking team, remove any account or tag rule that routes shared platform spend solely to that team, split shared spend by a documented usage driver, and publish the restated variance with the untagged remainder shown separately. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account, period or department first, then rerun the full scope and reconcile the results.

cloud cost variance spike error untagged spend allocated to wrong team

Use this when

• The operation in cloud cost report fails with this exact problem: cloud cost variance spike error untagged spend allocated to wrong team.
• The same failure repeats on retry with unchanged inputs.
• A variance report, forecast, commentary or board pack step is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a business judgement such as the budget itself or a materiality call. That is an FP and A decision, not this failure.

Steps

1. Reproduce the failure on one named account, period or department in cloud cost report and record the full problem text plus the account, period or report involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: audit the allocation mapping for the spiking team, remove any account or tag rule that routes shared platform spend solely to that team, split shared spend by a documented usage driver, and publish the restated variance with the untagged remainder shown separately. Verify: the single failing scope now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring accounts, periods or departments that share the same mapping, template or load, because this class of failure rarely affects only one scope. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in cloud cost report on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the GL actuals, the approved budget or the planning system record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the report or close file so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

cloud cost variance spike error untagged spend allocated to wrong team

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - how to fix cloud cost variance spike error untagged spend allocated to wrong team fails error

The how to phrasing for the same failure in cloud cost report. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

cloud cost report troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

A single wrong mapping rule repeats every month, so fixing only the current month leaves the spike scheduled to return, while a driver based split for shared spend stays defensible.

Edge cases

• The period was closed, the budget was reloaded or the org mapping changed after the failing run started. Refresh the scope state and reapply the fix against the current values, not the values from the failed run.
• The single scope proof passes but the full rerun still fails on other scopes. Treat each remaining failure as its own scope, because a shared load or mapping can hide more than one cause.
• The source systems disagree on the correct value. The GL governs actuals, the approved budget version governs plan figures, and the planning system governs forecast; record which source won and why.

Compatibility: cloud cost report at current versions, plus Power BI, Excel, Tableau, Looker, NetSuite and Adaptive Planning where the query names them; sources of truth are GL actuals and the approved budget, and no extra tooling is needed beyond access to those source records.

Provenance

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

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

Thread query: how to fix cloud cost variance spike error untagged spend allocated to wrong team fails error

TL;DR: Fix this in cloud cost report by acting on the exact problem first: audit the allocation mapping for the spiking team, remove any account or tag rule that routes shared platform spend solely to that team, split shared spend by a documented usage driver, and publish the restated variance with the untagged remainder shown separately. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account, period or department first, then rerun the full scope and reconcile the results.