SpendHQ error preferred supplier spend not separated from tail spend

• The workflow fails with this exact problem: SpendHQ error preferred supplier spend not separated from tail spend. - The same failure repeats on retry with unchanged inputs. - A task in this workflow is blocked until this is resolved.

Reproduce the failure on one named run and record the full problem text plus the record involved. Verify: The SpendHQ report is opened, a supplier known to be preferred is shown inside tail spend, and the preferred flag or list entry for that supplier is shown missing or mismatched, so the error is reproduced on demand.

Check the source of truth before changing anything. Verify: Compare the suppliers classed as preferred in the report against the current preferred supplier register and check the normalised supplier names on both sides for mismatches.

Apply the specific fix described in the TL;DR on that single record first. Verify: the single failing run now behaves as the fix predicts, or the corrected output is visible on the record.

Check neighbouring records or steps that share the same template, library entry or integration setting, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.

Rerun the original task on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the task completes and the original problem does not appear.

Record the fix, the triggering input and the verification result on the run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the rerun result, and it is saved with the run.

Resolved from the public problem: https://vectle.com/posts/pstlGN9n3ZFzG8YI5yxVifiA

Problem query: SpendHQ error preferred supplier spend not separated from tail spend

TL;DR: In SpendHQ, preferred supplier spend is not separated from tail spend because the preferred supplier list the report uses is out of date or the supplier records were normalised to names that no longer match that list, so preferred suppliers fall into the unclassified tail bucket. Fix it by opening the report definition, checking which supplier list or flag drives the preferred split, refreshing that list from the current preferred supplier register, re-matching the normalised supplier names against it, then refreshing the report and confirming known preferred suppliers now appear in the prefer

Fixes a Coupa spend analytics error where the tail supplier count changes after a supplier hierarchy update. Use when tail spend counts shift right after a hierarchy change with no new transactions. Not for genuine new supplier onboarding.

Freeze the comparison. Run the tail supplier report for the same period and the same spend threshold twice, noting the count before and after the hierarchy update. Expected: only the count and grouping changed, total spend for the period is unchanged.

Export the supplier lists from both runs and diff them. Expected: the difference is a named set of suppliers that moved, not a broad unexplained change.

Check each moved supplier in the supplier hierarchy. Expected: its parent or rollup node changed during the update, which explains why it entered or left the tail count.

Decide how the tail report should treat parent rollups: count suppliers at leaf level or at parent level, and confirm that choice with the spend analytics owner. Expected: one stated counting rule.

Rebuild or refresh the hierarchy mapping used by the report, then re-run the report for the original period. Expected: the tail count is stable across a second run with no hierarchy changes in between.

Annotate the report for the update date so readers do not read the count jump as procurement behaviour. Expected: the published report carries a note naming the hierarchy update as the cause.

Resolved from the public problem: https://vectle.com/posts/pst_rBlH-M09lFjmRfESqdsEoQ

Problem query: Coupa spend error tail supplier count changes after hierarchy update

TL;DR: A hierarchy update regroups suppliers, so suppliers that were counted under a parent can move into or out of the tail bucket without any spend changing. Re-run the tail analysis against the same date range before and after the update, check whether the moved suppliers changed parent, and rebuild the hierarchy mapping used by the report. If the same suppliers appear under a new parent with identical spend, the count change is a mapping effect, not new tail spend.

Not specified by the original author.

TL;DR

Fix this in SpendHQ by acting on the exact problem first: in SpendHQ, extend the normalisation rules to strip legal suffixes, punctuation and spacing differences before matching, then merge the five name variants into the canonical supplier, because each variant currently survives as its own supplier, and confirm spend by supplier now shows one combined total. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one supplier or supplier group first, then rerun the full scope and reconcile the results.

SpendHQ supplier normalization error same supplier counted under five names

Use this when

• The operation in SpendHQ fails with this exact problem: SpendHQ supplier normalization error same supplier counted under five names.
• The same failure repeats on retry with unchanged inputs.
• Work described as a supplier count, a spend by supplier report or a consolidation plan 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 an analytic or policy judgement in the result. That is an owner decision, not this failure.

Steps

1. Reproduce the failure on one supplier or supplier group in SpendHQ and record the full problem text plus the record, group or period 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: in SpendHQ, extend the normalisation rules to strip legal suffixes, punctuation and spacing differences before matching, then merge the five name variants into the canonical supplier, because each variant currently survives as its own supplier, and confirm spend by supplier now shows one combined total. Verify: the single failing scope now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring items, meaning suppliers sharing the same naming patterns, 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 SpendHQ 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 legal supplier record, the invoice register and the SpendHQ supplier table, 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 run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

SpendHQ supplier normalization error same supplier counted under five names

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 - SpendHQ supplier normalization error same supplier counted under five names

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

SpendHQ 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

Name matching that respects punctuation and legal suffixes treats trivially different spellings as different companies, and busy suppliers accumulate the most variants.

Edge cases

• The underlying data, mapping or rules changed after the failing run started. Refresh the current 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 rule, filter or schedule can hide more than one cause.
• The source systems disagree on the correct value. The source of truth for this check is the legal supplier record, the invoice register and the SpendHQ supplier table; record which source won and why.

Compatibility: SpendHQ at current versions, plus the ERP, card feed or procurement system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

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

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

Thread query: SpendHQ supplier normalization error same supplier counted under five names

TL;DR: Fix this in SpendHQ by acting on the exact problem first: in SpendHQ, extend the normalisation rules to strip legal suffixes, punctuation and spacing differences before matching, then merge the five name variants into the canonical supplier, because each variant currently survives as its own supplier, and confirm spend by supplier now shows one combined total. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one supplier or supplier group first, then rerun the full scope and reconcile the results.