NABU-1538: clarify Spend vs Supplier Analysis minimum-spend filter#1835
Merged
TedBaileyCodat merged 6 commits intoMay 27, 2026
Merged
Conversation
The Annual Supplier Minimum Spend threshold only filters the Supplier Analysis tab — Spend Analysis tab totals are calculated across all suppliers. Add a note and tighten the Customer-tab row to set the right expectation when the threshold is non-zero. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Shorten the *Excludes suppliers with annual spend below* row so prettier's markdown table check stays green; the detailed Spend vs Supplier divergence already lives in the :::note added under the Spend Analysis tab. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Rephrase the Insight cell to active voice ("The Supplier Analysis tab
omits suppliers below this threshold")
- Rewrite the :::note to drop passive voice, the "is not"/"non-zero"
constructions, the spaced em-dash, and "will" — keeping the same
meaning
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Tim-Hoare
approved these changes
May 27, 2026
btownsendio
approved these changes
May 27, 2026
pmckinney-codat
approved these changes
May 27, 2026
…sis-minimum-spend-glossary
|
Link check results for preview deployment (https://codat-docs-git-NABU-1538-spend-analysis-minimum-spend-glossary-codat.vercel.app): |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
:::noteunder the Spend Analysis tab section makes the divergence explicit: when the threshold is non-zero, Spend Analysis Overall totals will exceed the sum of Supplier Analysis supplier rows.Pairs with the glossary update in
reports-generation(NABU-1538-spend-analysis-minimum-spend-glossary).Context
NABU-1538 — Amex (Peacocks) flagged a totals mismatch between the two sheets. Root cause:
AnnualSupplierMinimumSpendis applied to Supplier Analysis only. Decision was to document the behaviour rather than change the report.Test plan
npm run format:mdx:checkagainstdocs/spend-insights/reports/spend-analysis.md(Prettier was not run locally — no node_modules)npm run buildto confirm Docusaurus renders the new:::noteadmonition