QuickBooks Online Advanced Performance Centre: Custom KPI Dashboards

Short answer: the reports list answers a specific question once. The Performance Centre answers the question you keep asking, on a dashboard, in chart form. They are built for different jobs and a good Advanced setup uses both.

What the reports list does well. It is a library. You open a saved report like Profit and Loss by Class, set a date range, and look at the row-level detail. It is the right tool when you need to drill into specific transactions, reconcile an account, or answer a question that requires the underlying numbers in tabular form. Reports are best for the work that happens at month-end close, during audit prep, and when you need to look up a single transaction or vendor activity. The reports list is also where bookkeepers spend most of their time.

What the reports list does poorly. It is not made for trend visibility. Opening Profit and Loss, comparing this quarter to last quarter, and trying to spot whether gross margin is drifting requires you to scan rows and do math in your head. It is not made for at-a-glance management review. An owner who logs in once a week does not want to open six reports and cross-reference them. And it is not made for visual comparison. A chart of revenue by customer over the trailing 90 days tells you in one glance what 12 lines of a custom report would tell you in three minutes of scanning.

What the Performance Centre does well. It is a dashboard layer. You build charts from the same underlying data the reports use, pin them to a dashboard, and check the dashboard at a glance. The charts are visual. They show trends. They highlight threshold breaches because you can color-code against targets. They let you filter and group quickly. For a busy owner or CFO who has 90 seconds on a Monday morning to check the health of the business, the Performance Centre is the right tool.

What the Performance Centre does poorly. It does not give you the underlying transactions. If a chart shows revenue dropped 18 percent in the last 30 days, the dashboard tells you that fact but does not show you which customers stopped paying or which invoices got voided. To answer those questions, you still have to drill into reports. The Performance Centre is also limited in the calculations it can perform. You cannot build a complex ratio like LTV-to-CAC inside the chart wizard. The math has to happen in the underlying data source.

How they work together. The dashboard surfaces the signal. The reports library lets you investigate the signal. When the AR days chart shows DSO climbing from 38 to 47 over six weeks, you click into the AR aging report to see which customers are responsible. The dashboard is the first thing the owner looks at. The reports library is where the bookkeeper and CPA do their work. We set up both for every Advanced client.

What changes when you build a dashboard culture. The biggest shift is in how the management conversation happens. Without a dashboard, the monthly review meeting starts with “let me pull up the reports.” With a dashboard, the meeting starts with “I noticed gross margin is down 3 points, why?” The conversation moves faster, lands on real questions sooner, and produces better decisions. We have seen client meetings shrink from 90 minutes to 30 minutes purely because the dashboard surfaces the issues that need discussion before the meeting starts.

The standard reports list still has one big advantage. Reports can be exported to Excel with full row-level detail, which is what your accountant or auditor will ask for at year-end. Dashboard charts export only as PDFs or images, which are useful for board packs but not for audit work. So even at clients with mature dashboards, the reports library remains the primary export path for compliance work. For more on how to set up the reports side of the equation, see our QBO Advanced custom reports guide.

One thing to know about data freshness. Both the reports list and the Performance Centre read from the same underlying QBO data, so they refresh on the same cadence. When you post an invoice, both the report and the chart will reflect it on the next page load. This matters because some clients assume the dashboard is on a delay (it is not) or that the reports are more current (they are not). Both are live views of the same data.

How to know if you are using the right tool. If you are running the same three or four reports every Monday and eyeballing them for trends, that work belongs on a Performance Centre dashboard. If you are running a different report every time you need to answer a different question, the reports library is the right home. If you find yourself building the same custom report over and over with different date ranges, that is a dashboard candidate. The pattern we look for: any report you would describe as “the one I always run”. Is a chart waiting to be built.

One more thing about access and roles. The Performance Centre and the reports list have different permission implications. A user can have report access without dashboard access, and vice versa, through custom roles. We sometimes scope a controller to have full reports access (for the close work) and a CFO to have dashboard access only (for management review) so that each person sees what they need without the noise of the other view. That separation is hard to set up but pays off in clarity. See our custom roles guide for the mechanics.

The honest tradeoff. A well-built Performance Centre dashboard takes 4 to 8 hours of work to design and refine. A working reports library takes 0 hours because QBO ships with one. So the question is not “which is better”. But “is the dashboard worth the setup time?” For any business where the owner or CFO looks at QBO more than weekly, yes. For a business where the bookkeeper handles everything and the owner only sees the year-end summary, the dashboard is a nice-to-have but not essential. Most of our Advanced clients fall into the first category and the dashboard becomes one of the things they wonder how they lived without.

Six KPIs cover almost every service business we work with. A seventh and eighth get added if the business is billable-hour driven or subscription-based. The trick is not finding more metrics. It is finding the right ones and resisting the urge to add a tenth or eleventh because something seems important.

1. Gross margin percentage. Revenue minus direct cost of delivery (labor, contractors, software directly tied to client work), divided by revenue. For a professional services firm like accounting, law, or consulting, the target range is 55 to 70 percent. For a creative agency, 40 to 55 percent. For a managed services or IT services firm, 35 to 50 percent. The reason gross margin matters more than net margin for a small business: net margin includes a lot of discretionary spend (owner salary, office, software, marketing) that the owner can control. Gross margin tells you whether the core delivery is profitable, which is the question that matters first.

2. Trailing 90-day revenue trend. A line chart of revenue, grouped by week, for the last 90 days. The 90-day window smooths weekly noise while still being sensitive to real change. Watching only monthly revenue means a slowdown that started 4 weeks ago does not show up until the next month closes, which is 30 to 60 days late. The 90-day trailing view catches the slowdown earlier. For service businesses where revenue is project-based and lumpy, the chart should be set to a moving average or to revenue recognized rather than revenue invoiced, depending on how you book under ASC 606.

3. AR days (DSO). Accounts receivable balance divided by average daily revenue, trailing 90 days. The target for a healthy service business is 35 to 45 days. Above 50 days means either (a) you are signing contracts with terms that are too generous (net 60 instead of net 30), (b) your collections process is loose, or (c) your customers are themselves having cash trouble. Below 30 days is excellent and usually indicates a tight billing operation. We have helped clients drop DSO by 9 to 14 days using a combination of automated reminders, more aggressive deposit requirements, and tighter contract terms. Each day of DSO is real working capital tied up. For a $3M business, dropping DSO by 10 days frees up about $82,000 of working capital.

4. Cash on hand, in weeks of operating expense. Cash plus equivalents, divided by average weekly operating expense (trailing 13 weeks). Express the answer in weeks, not dollars. The reason: a dollar number does not tell you whether the cash is enough. $250,000 of cash is comfortable for a business spending $30,000 a week (8 weeks of runway) and dangerous for a business spending $90,000 a week (2.8 weeks of runway). The target floor for a stable service business is 13 weeks, or one quarter. Below 8 weeks the business is fragile. Below 4 weeks you are running on fumes and a single missed invoice or unexpected expense puts you in a payroll crisis.

5. Top customer concentration. Revenue from the largest single customer divided by trailing 12-month revenue. The risk threshold is 25 percent. Above 25 percent, the loss of that customer would materially damage the business. Above 40 percent, the business has a structural vulnerability that lenders and investors will discount when valuing the business. Most service businesses run between 8 and 18 percent. We see concentration above 25 percent most often at agencies that grew through one big anchor client and at consulting firms that landed a long-term retainer they have not yet diversified away from. The chart should be a bar showing the top five customers as percent of revenue, with a red line at 25 percent.

6. Operating expense growth versus revenue growth. Year-over-year operating expense growth rate compared against year-over-year revenue growth rate. The dashboard chart shows two lines: revenue growth percentage and operating expense growth percentage, both rolling year-over-year. A healthy business runs expense growth at 60 to 80 percent of the revenue growth rate. If expenses are growing at 110 to 130 percent of revenue growth for two quarters running, your operating use is eroding. This usually shows up as a margin compression two to three quarters out, by which point you are looking at layoffs or aggressive cost cuts. The chart is the leading indicator that gets you to the conversation 90 days earlier.

7. Billable utilization (for billable-hour businesses). Billable hours divided by total hours worked, by team or by employee. The target depends on the business model. Pure billable consulting firms target 70 to 80 percent. Accounting firms (with billable client work mixed with internal time) target 65 to 75 percent during normal season and 75 to 85 percent during tax season. Below 60 percent and the business has either too much capacity or a sales problem. The chart should show utilization by team for the trailing 12 weeks, with a target line. We see this metric drive more management conversations than any other dashboard component at billable-hour clients.

8. Net revenue retention (for subscription or retainer businesses). This month’s revenue from customers who existed 12 months ago, divided by their revenue 12 months ago. Above 100 percent means existing customers are growing faster than they are churning, which is the best operating signal a subscription business can produce. SaaS targets 110 to 130 percent. Retainer-based services target 95 to 110 percent. Below 90 percent and the business has either a churn problem or a downgrade problem that the new-customer acquisition machine has to outrun.

What is deliberately not on this list. Net income as a percentage of revenue. Why? Because for most small services businesses, net income is heavily influenced by owner compensation decisions, distributions, and one-off expenses that obscure the underlying operating health. Gross margin tells you more, more quickly. We track net income at month-end close, not on the weekly dashboard.

Also not on the list: total expenses by category. Most owners think they need to see “marketing spend, salaries, rent, software”. On the dashboard. They do not. They need to see that operating expense growth is in line with revenue growth (KPI 6 above). The category-level detail belongs in the close package, not the dashboard.

What changes by industry. Law firms add realization rate (billed-and-collected as a percent of standard rate). Healthcare practices add revenue per visit and visits per day. Construction firms add work-in-progress and billings versus costs. Real estate brokerages add agents per office and transactions per agent. The principle stays the same: six to eight metrics that drive the business, color-coded against targets, refreshed weekly.

How to know your dashboard is working. The owner can read it in under two minutes. The owner can articulate what changed since last week without opening a report. The team can predict what the owner will ask about based on the dashboard before the meeting. If those three things are not true, the dashboard has too many metrics, the targets are wrong, or the visualization is muddled. For more on building this out for your specific business, that is part of what we do as a client accounting services engagement.

Short answer: partially. The Performance Centre handles dashboards and visual KPI tracking well enough to replace Fathom for many early-stage businesses. It does not handle three-statement forecasting, multi-entity consolidations, or board-ready PDF packs, which means Fathom and Jirav still own those workloads. The right answer depends on what stage your business is in and what your FP&A function actually needs to produce.

What the Performance Centre does that competes with Fathom. Visual dashboards. KPI tracking with targets. Trend lines on revenue, margin, AR, cash. Customer concentration views. Operating expense versus revenue comparisons. For a single-entity business that needs a daily-driver dashboard the owner and CFO check weekly, the Performance Centre covers 80 percent of what Fathom does at zero incremental cost (it is included in your Advanced subscription). Fathom’s free trial is fine but at $44 per entity per month starting price, the cost-benefit only works once you need things the Performance Centre cannot do.

What the Performance Centre cannot do that Fathom can. Multi-entity consolidations. If you have three QBO files for three legal entities and you need a consolidated view, the Performance Centre cannot help. Fathom can pull from multiple files and produce a clean consolidated set of statements and KPIs. Narrated board packs. Fathom produces a PDF board pack with commentary fields and a structured layout that is meeting-ready. The Performance Centre’s PDF export is a screen capture of the dashboard. Industry benchmarking. Fathom includes benchmarking against peer industries, which is useful if you want to know whether your 58 percent gross margin is good for your category. The Performance Centre has no benchmarking. KPI definitions matched to common frameworks (Goldratt, Kaplan-Norton, EOS) without setup work.

What the Performance Centre cannot do that Jirav does. This is where the gap is widest. Jirav is a planning and forecasting tool. It lets you build a driver-based forecast that flows through P&L, balance sheet, and cash flow with consistent assumptions. You change a headcount assumption and it propagates through compensation, benefits, payroll taxes, revenue (if revenue is driver-linked), and cash. The Performance Centre has no forecasting capability whatsoever. It is a historical view only. Scenario modeling. Jirav lets you run base and pessimistic cases side by side. The Performance Centre cannot. Headcount and capacity planning. Jirav has specific modules for headcount planning, hire dates, ramp times, and capacity calculations. The Performance Centre has none of that.

The honest verdict by stage. Stage 1 (under $2M revenue, single entity, no board): the Performance Centre is enough. Anything you add at this stage costs money for marginal benefit and slows down your team. Stage 2 ($2M to $10M, single entity, monthly board pack or lender cadence): keep the Performance Centre for daily dashboarding. Add Fathom for the monthly board pack. The combination costs roughly $44 to $200 a month depending on entities and tier, and the time savings on producing the board pack alone justify it. Stage 3 ($10M to $50M, possibly multi-entity, forecasting is part of the planning cadence): Performance Centre for daily use, Fathom for consolidations and board packs, Jirav for forecasting and planning. Now you are spending $500 to $1,500 a month on FP&A tooling but the volume and complexity of the planning work makes it worth it. Stage 4 ($50M+ or formal FP&A function): you are likely outgrowing QBO entirely and moving to NetSuite, Sage Intacct, or a similar mid-market ERP. At that point the discussion shifts to whether you need a real BI tool (Looker, Tableau, Power BI) on top of a finance data warehouse, and Fathom and Jirav often get replaced or supplemented.

The misuse we see most often. Clients at Stage 1 who bought Jirav because someone recommended it. They pay $500 to $1,000 a month for a forecasting tool they barely use because their business does not yet have a forecasting cadence. The money would have been better spent on cleaning up the bookkeeping, building a good Performance Centre dashboard, and waiting for the business to grow into the next stage. Forecasting tools work when there is a forecasting habit to support. Without the habit, the tool sits unused.

A specific scenario where the Performance Centre is enough. A $1.5M services firm with one entity, one owner, no outside investors. The owner wants to see weekly revenue trend, gross margin, AR days, cash position, top customer concentration, and operating expense growth. Six metrics. The Performance Centre handles all six natively, refreshes live, costs nothing extra, and lives inside the system the bookkeeper already uses. Adding Fathom would add $44 a month for a 5 percent improvement in dashboard quality. Adding Jirav would add $500 a month for forecasting capability the business does not need yet. The right answer is the Performance Centre, full stop.

A specific scenario where the Performance Centre is not enough. A $12M agency with three legal entities, an active board, a lender requiring quarterly covenant reporting, and a CFO who runs a 13-week cash forecast plus a rolling 12-month plan. The Performance Centre can show the entity-level dashboards but cannot consolidate, cannot forecast, and cannot produce the board pack format the board wants. The right setup here is Performance Centre for daily and weekly views per entity, Fathom for monthly consolidated reporting and the board pack, and Jirav for the rolling forecast and scenario work. Total tooling cost is about $300 to $600 a month, which is trivial against the business’s revenue and replaces several days of CFO and controller time per month.

Where Looker Studio fits. Worth mentioning because it gets overlooked. Looker Studio (Google’s free BI tool) can pull from a QBO sync via Google Sheets and produce dashboards that are shareable via URL to anyone with a Google account. For external sharing, Looker beats both the Performance Centre and Fathom. For internal use, the Performance Centre wins on simplicity. We use Looker as the “external dashboard”. Layer for several clients while keeping the Performance Centre as the internal daily dashboard. The cost is the setup time (4 to 12 hours depending on complexity) plus a small monthly fee for the sync tool. Once set up, it runs hands-off.

One operational point. If you do upgrade to Fathom or Jirav, do not delete the Performance Centre setup. The dashboards in QBO remain useful for the bookkeeping team and the day-to-day operating questions. We have seen clients turn off Performance Centre dashboards after buying Fathom and regret it three months later when they want a quick chart without opening a separate tool. Run both. The Performance Centre is paid for. There is no reason to leave it unused.

The AICPA management accounting frameworks. Worth a separate note. The AICPA publishes management accounting standards, the Global Management Accounting Principles, and the Statement on Management Accounting series that define what good FP&A looks like across decision support, performance measurement, and risk management. Whichever tools you use, building the practice to those standards is worth the time. The frameworks are vendor-neutral and apply equally whether you are using the Performance Centre, Fathom, Jirav, or a custom solution. For a longer treatment of how FP&A intersects with the books, see our client accounting services page.

The short version: you cannot, not natively. QBO does not have a public-link viewer for the Performance Centre, no read-only external mode, no embed-in-a-website feature. Every direct viewer of a dashboard needs a QBO user account on the company file. This is one of the Performance Centre’s biggest gaps, and being clear about it saves clients from a frustrating discovery later.

What you can do is work around the limitation. Four patterns cover the cases we see most often.

1. Manual PDF export. Inside the Performance Centre, the export-to-PDF function captures the current dashboard view as a static PDF, sized for letter-page printing. You can email this PDF to anyone. The downsides: it is a snapshot, so the recipient sees the dashboard as of the moment you exported it. The formatting is dashboard-shaped, not board-pack-shaped. And you have to remember to do the export each time. We use this pattern for monthly investor updates and occasional one-offs. Time to produce: 60 seconds.

2. Scheduled PDF delivery. The Performance Centre does not have a true scheduling function for dashboards (it does for individual reports, but not for the dashboard view). Workarounds: set up a Make or Zapier scenario that runs on a schedule, opens the QBO page via headless browser, captures the screenshot, and emails it. This is finicky to set up and we only do it for clients with a hard recurring obligation, like a monthly board update. For most clients, a calendar reminder to do the export manually is cheaper and more reliable than the automation.

3. Pipe data to an external dashboard tool with public sharing. This is the right answer for clients who need recurring external sharing with non-QBO users. The architecture: a sync tool (we use Make most often, also have set up Coefficient and G-Accon for some clients) pulls a defined set of QBO data into a Google Sheet on a schedule (daily or weekly). Google Looker Studio reads the Sheet and renders a dashboard. The Looker dashboard has a public share URL or can be shared with specific Google accounts. The end result: the people who need to see the data get a clean, shareable URL. The underlying data is fresh. And you have not had to give anyone a QBO login.

The Looker setup takes 4 to 12 hours of work depending on how many metrics you want and how complex the underlying calculations are. Once set up, it runs hands-off. The monthly cost is the sync tool ($10 to $40 a month for Make, depending on volume). Looker itself is free. For a client with a board, an investor cadence, or a lender that requires recurring reporting, this is the path we set up most often.

4. Buy Fathom or Jirav and use their sharing. Both Fathom and Jirav have native sharing functions that work for non-QBO users. Fathom can share board packs via PDF or a hosted viewer. Jirav has a viewer-tier license for non-editing users. If you already need Fathom or Jirav for the consolidation or forecasting features, the sharing capability is a bonus. If you only need them for sharing, the Make-plus-Looker stack is cheaper. The decision usually comes down to whether you need the other Fathom and Jirav features.

What about a shared QBO login? Sometimes asked. We strongly recommend against it. Sharing a login violates the QBO terms of service, breaks audit-log integrity (every action shows up as the shared user), and creates a security risk if the credentials leak. Pay for an extra user seat or use one of the patterns above. The cost of an extra user is trivial against the audit and security risk of a shared account.

What about read-only QBO access via custom roles? Yes, this works for internal sharing. You can create a custom role that has access to the Performance Centre and selected reports but cannot edit transactions. Assign that role to the people who need view access (a board observer, an outside CFO, an investor with full access rights). The downside: each viewer still needs a QBO user seat, which costs incremental money on the Advanced plan. The upside: audit log integrity is preserved, security is appropriate, and the viewer sees live data. For a small number of trusted internal or quasi-internal viewers, this is the cleanest answer. See our custom roles guide for the setup mechanics.

What about screen sharing in a meeting? Often the right answer for ad-hoc situations. If you have a quarterly board meeting and the board does not need ongoing access between meetings, share your screen during the meeting and walk through the dashboard live. Faster than setting up Looker, more interactive than a static PDF, and avoids the licensing question. We do this with most of our outside-CFO clients for monthly meetings. The handoff is a PDF export of the dashboard plus a one-page narrative.

The scoping question. Before you build any external sharing, think about what the external viewer needs to see. The dashboard you look at internally probably has more detail than your board or your investors should see. Strip out internal-only metrics. Mask customer names if customer concentration is a sensitive number. Aggregate where possible. Most clients build a “share dashboard”. That is a subset of their internal dashboard, with the sensitive or internal-only items removed. This is good hygiene regardless of which sharing pattern you use.

The compliance angle. If you are sharing dashboards with lenders or investors, your data sharing should comply with whatever NDA, side letter, or covenant agreement governs the relationship. Most institutional investors have specific clauses about confidentiality and use of financial data. Quick check before you send: does the recipient have an active NDA, are they entitled to see this data per your agreements, and is the data in a format they can use without re-disclosing it inappropriately. This is rarely an issue in practice but worth thinking about for the first share to a new party.

What we predict will change. Intuit has shipped incremental improvements to the Performance Centre roughly every 6 to 9 months for the last two years. Public sharing or embeddable dashboards is the most requested feature in their plan discussions, based on the user-community feedback we have seen. We expect some form of read-only external sharing to ship in the next 12 to 18 months. Until then, the workarounds above are the working answer. If and when Intuit ships native external sharing, this section gets shorter.

The simplest answer for most clients. If you only need to share occasionally, do the manual PDF export. It is fast and good enough. If you need recurring external sharing, set up the Make plus Looker Studio stack or buy Fathom. If you need internal sharing only, use custom roles inside QBO. Most clients can pick one of those three answers and move on. Over-engineering the sharing layer is one of the more common ways small finance teams waste time on tooling that does not pay back.

Short answer: continuously. There is no separate refresh cycle for the Performance Centre. Charts read from the same live QBO data that the standard reports read from, and that data updates the moment a transaction is entered, edited, or deleted. The lag people notice in their dashboards is almost never from the Performance Centre itself. It is from upstream data sources, most often bank feeds and third-party app syncs.

What is actually live. When you create an invoice, receive a payment, enter a bill, or post a journal entry in QBO, the change is immediately visible to any chart or report that references that data. There is no nightly batch, no cache to refresh, no separate ETL step. The chart you reload at 9:01 AM will show the invoice you entered at 9:00 AM.

What can be delayed. Bank feeds. Most banks update their QBO feed once per day, usually overnight. So a deposit that hit your bank account at 2 PM yesterday may not show up in QBO until the next morning when the bank feed runs. The dashboard chart will accurately reflect what is in QBO. The question is whether QBO has caught up with reality. If your dashboard says cash on hand is $180,000 and your bank app says $215,000, the difference is almost always pending feed activity, not a Performance Centre bug.

Third-party app syncs. Apps like Stripe, Shopify and Bill.com sync transactions into QBO on their own schedules. Stripe pushes daily or hourly depending on configuration. Shopify can be daily or twice daily. Bill.com syncs approved bills in near real time but with a few minutes of lag. Each app has its own cadence. If your dashboard relies on data from these apps, the dashboard freshness is bottlenecked by the slowest sync in the chain. For most clients, this is not a problem because daily-cadence syncs are good enough for daily-cadence dashboard reviews. It becomes a problem when an owner expects intraday refresh and the underlying app only pushes data nightly.

What you can do to verify freshness. Every chart on the Performance Centre has a “last updated”. Timestamp accessible in the chart info menu. If a chart looks stale, check the timestamp. If the timestamp is recent but the data looks wrong, the issue is usually with the underlying source (bank feed, third-party sync, or recent unposted transactions). If the timestamp is also stale, the dashboard may need a manual reload, though we have rarely seen this in practice.

What happens during high-volume periods. Around month-end, when bookkeepers are posting reclassifications, journal entries, and adjustments, the dashboard can render slowly for a few seconds because the underlying data is changing as you watch. This is normal. The data is fresh. The chart is just doing the calculation against a moving target. We tell clients to do their dashboard review either before the bookkeeper starts month-end work or after it finishes, not during the active reclassification window. For more on the close process itself, see our reclassify transactions guide.

The audit-log impact. Every change to a transaction shows up in the audit log immediately, and changes that affect dashboard charts are reflected at the same time. If a bookkeeper voids an invoice at 11:30 AM, the revenue chart updates the next time it renders. This is generally a feature, not a bug. The transparency of the underlying data flow is one of the things that makes the dashboard trustworthy. The downside is that the dashboard can move during the workday as transactions are entered, which sometimes confuses owners who expect a static daily snapshot. For owners who want the static snapshot, the answer is the scheduled PDF export described in the previous FAQ.

Performance versus data freshness. Worth separating two questions. How fresh is the data (continuous, see above). How fast does the chart render (a few hundred milliseconds for native metrics, 2 to 8 seconds for complex custom-report-driven charts on large files). The two are independent. Slow render does not mean stale data. We mention this because some clients assume a 4-second chart render means the chart is fetching old data, when actually it means the chart is recalculating against fresh data on a complex query.

What about caching. QBO does not cache dashboard data on the client side in a way that would create freshness issues. The browser caches static assets (CSS, JavaScript) but the data layer is fetched on every page load. So a hard refresh is not necessary. A normal page reload pulls the current data. If you suspect a caching issue (rare), close the tab and reopen the dashboard from scratch. We have seen this need arise maybe twice in three years across hundreds of client files.

What happens on the mobile app. The QBO mobile app has a stripped-down dashboard view that pulls from the same data but is not the full Performance Centre. Refresh behavior is the same: live data, fetched on app open or pull-to-refresh. Some chart types from the desktop Performance Centre do not render on mobile. If a chart is critical for mobile review, test it on the mobile app before assuming it will be there.

What about API rate limits. The QBO API has rate limits, but the Performance Centre is not subject to them because it runs inside Intuit’s own infrastructure rather than through the API. External tools that pull data through the API (Fathom, Jirav, Looker Studio via Make) are subject to rate limits and can hit them at scale. If you see freshness lag on an external dashboard but not on the Performance Centre, the API rate limit on the external tool is the likely culprit, not anything on the Intuit side.

One specific scenario clients ask about. “I want a dashboard that updates the moment a credit card transaction posts.” That is not possible with current bank feed cadences for most cards. Some cards push to QBO once a day. Some push every few hours. Very few push in true real time. For real-time card transaction visibility, the credit card issuer’s own app or a tool like Ramp or Brex (which have native QBO integrations and push transactions close to real time) is the right answer. The Performance Centre will reflect whatever the bank feed has pushed. It cannot make the bank feed push faster.

The summary. Performance Centre dashboards are as fresh as the data underneath them, and the data underneath them updates as transactions hit QBO. When the dashboard looks stale, the cause is almost always upstream of QBO (bank feed lag, third-party sync schedule, or unposted transactions in someone’s drafts). Fix the upstream issue and the dashboard updates automatically. There is no “refresh the dashboard”. Step. For most clients, this is the freshest financial reporting they have ever had. The novelty of seeing yesterday’s deposits, this morning’s invoice, and last week’s expenses on a single screen, all current, is one of the reasons the Advanced tier earns its price step-up.