A vendor spend dashboard can combine cleaned bank transactions with a Vendor master Table, recurring-cost evidence, budgets and dashboards for concentration, category, trend and exceptions.
What the workflow should answer
It should answer total spend, top vendors, concentration, new vendors, recurring commitments, price increases, category budget status and which team owns the relationship.
The system is easiest to navigate when each primitive owns one concern. Feeds bring in one financial data type from selected accounts. Enrichments clean, classify, guard and watch the records in an explicit order. BankSync Tables store typed or custom relational rows with views, comments and history. Dashboards query that model and present the result.
Preserve source truth. Original amount, currency, date, account and provider identifier should remain intact. Add workflow status, owner, category, policy and formulas in separate fields. That is what makes an exception traceable.
Model the process in Tables
Create a Vendors Table with canonical name, aliases, category, owner, status, contract dates, renewal date, criticality and notes. Relate transaction rows to vendors. Merchant Cleanup can improve raw descriptions, but a reviewed relation is the governance layer. A rollup can calculate spend, transaction count, first seen and last seen; formulas can annualise only when cadence and currency are known.
Relations connect records without copying labels everywhere. Lookups expose related values; counts and rollups summarise child records; formulas calculate stored results that can be sorted, filtered, charted and read through API or MCP. Immutable field keys make automation safer when a human label changes.
Use the right view for the job
Grid supports detailed review. Board writes a status field when cards move. Calendar and Timeline write date fields when items move. Gallery works for attachment-led records, List for a calm summary and Form for intake. Views can be shared or personal and remember grouping, filters, sorts, columns and row colours.
Aggregate safely
Vendor concentration should use a stated period and spend basis. Do not mix refunds, transfers and capital purchases blindly with operating expense. Preserve negative and positive movements and model the sign convention. Strict multi-currency aggregation prevents accidental totals. Any reporting currency needs an explicit rate, date and converted value while native amounts remain available.
The vendor record readers can copy
Identity
Canonical name, aliases, category and the raw merchant patterns that map to it.
Ownership
Internal owner, criticality, approval policy and current status.
Contract context
Start, renewal and notice dates plus a link to the supporting agreement.
Spend evidence
Related transactions, period totals, first seen, last seen and recurring signals.
Build the vendor model
Clean merchant descriptors
Remove obvious noise while preserving the raw field.
Create the Vendor master
Store ownership, category and contract context.
Relate transactions
Use a reviewed vendor relation.
Add spend rollups
Calculate period spend and activity.
Enable recurring watches
Detect price changes and new subscriptions.
Add budget thresholds
Watch categories or teams.
Build concentration views
Show top vendors and category mix.
Create a renewal workflow
Use Calendar and owner fields.
Copy this build: the vendor concentration map
Imagine a growing company that knows software spend is rising but cannot say which vendors or teams drive it. Clean merchant names first, then create a Vendor master instead of treating each bank descriptor as a vendor.
Relate transactions to canonical Vendor records with category, owner, criticality, contract dates and renewal date. Roll up spend, transaction count, first seen and last seen. Enable Recurring Registry for established recurring vendors and Budget watches for categories or teams.
Build four views: top vendors, category mix, monthly trend and renewal Calendar. Add a table for new vendors and first-time merchants above the review threshold. Keep seat and utilisation claims out unless operational data is connected.
What success looks like after one week
The next budget conversation starts with vendor, owner, renewal date and source payments on one screen—not an exported card statement and a hunt for contracts.
Dashboard and watch design
Lead with total vendor spend, recurring equivalent and concentration. Add top-vendor bars, a treemap by category, monthly trend, new-vendor table and renewal Calendar. A vendor detail table should expose owner, latest activity, contract date and source transactions.
Source-applied filters recalculate aggregates and are the default. Browser filters are for presentation, not access control. Locked source filters should fail closed for client, entity or team-scoped dashboards.
Enrichments and alerts
Merchant Cleanup, Memory, Lookup Tables and Rulesets can create consistent mapping. Recurring Registry can watch new subscriptions, price increases and missed expected charges. Budget can watch category spend. Anomaly Detector can flag a first-time merchant above threshold. Review Queue provides a safe home for uncertain AI classification.
Guard steps run before Memory, lookups and rules; AI fills remaining blanks; watch enrichments observe the final record. Suppressed records do not write, teach Memory or fire alerts. Use Live Preview before enabling hard Filters, Splits or suppression.
Limits and controls
Bank data shows payments, not seats, entitlements, utilisation or complete contract terms. A SaaS optimisation workflow needs additional operational data. Present bank-based spend as evidence, not a full procurement system.
Alerts are as fresh as the feed schedule. Dashboards are beta by workspace. Sensitive operational data should remain private or workspace-scoped. External-agent authoring is a staging workflow; review any generated dashboard in the regular editor.
Operate the system
Assign an owner for feed health, review queues and model changes. Check sync history before trusting a quiet metric. Use row comments and history for decisions that need context. Review retention and permissions. A useful operations dashboard makes the next action obvious and keeps the evidence one click away.