NetSuite purchase-order dashboard for marketing & finance with inline budget editing
Build an internal dashboard workflow that gives the marketing team a live view of their purchase orders and lets approved people adjust budget figures inline. Trigger it with an HTTP route (e.g. /marketing-po) that serves a web dashboard. Gate all routes behind tenant SSO, and further restrict data access to an email allowlist so only approved viewers see the numbers and only approved editors can change them. Build it as three cooperating steps: A dashboard page — a React/Tailwind single-page app that renders its shell immediately, then fetches data client-side from the data endpoint (same origin, carrying the SSO session). Show KPI summaries (total line value, total unbilled, PO and line counts), charts (spend by vendor, by PO status, by month), and a line-item table grouped under each PO with per-PO subtotals. Count all amounts per line item so the full PO value is never repeated across lines. Present it with a strong, distinctive visual identity rather than a generic dashboard look. Make the data-fetch URL branch-aware. A data endpoint — a JSON API route that pulls marketing purchase-order line items from your ERP/accounting system (I used NetSuite SuiteQL — swap in whatever finance system you use), filtering to the marketing departments at the line level. For each line return PO number, date, vendor, status, department, description, the full line amount, and the amount unbilled. Enforce the viewer allowlist here and return 403 for anyone not approved. A budget store — an API route backed by a persistent volume that holds manual overrides to the budget. GET returns the current overrides plus whether the caller may edit; POST (editors only) saves updated overrides. The dashboard loads default budget figures from a bundled CSV and merges these overrides on top. Read-only against the finance system; the only writes are budget overrides saved to the workflow's own storage. Tools used: NetSuite (SuiteQL REST API, custom OAuth connector), React, Tailwind
What this prompt builds
This workflow pulls NetSuite purchase-order line items for Marketing, reconciles them to the correct budget areas, and displays them in a gated dashboard with budget-vs-actual comparisons, vendor/status/quarter breakdowns, and a searchable PO register. Finance can edit budget figures inline, which are saved for everyone, eliminating manual SuiteQL pulls and spreadsheet reconciliation. Access is restricted to SSO plus a named viewer allowlist so real figures stay with approved Finance people.
The problem
Marketing and finance teams struggle to track committed spend against budget when purchase-order data lives in NetSuite. PO amounts are buried across transaction lines, easily double-counted if rolled up incorrectly, and legacy line items often map to the wrong budget area—making it nearly impossible to see, at a glance, how much has actually been committed. This workflow transforms raw NetSuite purchase-order line items into a live dashboard that shows budget vs. actual by team and area, spend by vendor and quarter, and a searchable PO register with per-line amounts and unbilled totals—all without anyone having to log into NetSuite or wrangle SuiteQL exports. Budget figures can be edited inline and saved for the whole team, and access is gated to SSO plus a named allowlist so real financial data stays with approved viewers.
Solution and impact
The workflow pulls Marketing POs directly from NetSuite via SuiteQL, counts spend per line to eliminate double-counting, reconciles legacy items to the correct budget area, and renders everything as a clean dashboard: FY27 budget vs. committed spend with over/under flags, breakdowns by vendor/status/quarter/team, and a searchable register showing what's still unbilled. Finance can edit budget baselines inline—saved immediately for everyone—so the dashboard stays current without CSV re-uploads. Marketing and finance teams get accurate, self-serve spend visibility in seconds instead of recurring manual pulls and spreadsheet wrangling, while SSO and email-allowlist gating ensures real figures stay restricted to approved viewers.