Executive / AR / AP Dashboards
Each REDA Financials role gets a home page built for its morning: the AR clerk's, the AP clerk's, the controller's and the admin's — recent records, activities, and a dashboard slot wired to a role-appropriate dashboard. The package provides the slots and the data plumbing; your team owns the dashboards themselves, which is what makes them yours.
Access you'll need. Any REDA Financials permission set sees its role's home-page dashboard once it is built (dashboard and folder sharing follow ordinary Salesforce visibility). Creating the dashboards is an administrator task using your org's normal Salesforce reporting permissions.
The four home pages and their dashboards
| Home page | Dashboard it looks for | Natural content |
|---|---|---|
| AR Home | Accounts Receivable Dashboard | Open AR by aging bucket, collections this month, top overdue customers, unapplied cash |
| AP Home | Accounts Payable Dashboard | Due this week, open POs and commitments, spend by vendor, discounts captured |
| Controller Home and Admin Home | Executive Financial Overview | Revenue and net income trend, cash position, AR/AP totals, budget utilization |
The slot renders the dashboard when one exists under the expected name — and simply stays hidden until then, so a fresh org shows clean home pages rather than errors.
The slots key on the dashboard's developer name (the unique name set when the dashboard is created), not its display label:
| Home page | Expected developer name |
|---|---|
| AR Home | Accounts_Receivable_Dashboard |
| AP Home | Accounts_Payable_Dashboard |
| Controller Home & Admin Home (shared) | Executive_Financial_Overview |
Beyond the dashboard slot, each home page also carries the working furniture of its role's morning: activities and upcoming events, recent records, and the Chatter feed — so the dashboard is the headline over a page that's already useful without it.
They ship — check before you build
Accounts_Receivable_Dashboard,
Accounts_Payable_Dashboard and Executive_Financial_Overview —
and appear in the dashboard list under their display titles, Revenue & Collections,
Payables & Procurement and Executive Intelligence. Look there first: if a
home-page slot is empty the usual cause is folder visibility, not a missing dashboard.
Confirm what you already have
Open the Dashboards tab and look in the REDA Financials: Dashboard folder. If the three are there, you have nothing to build — share the folder with the roles that need it and you are done.
Adapt rather than replace
The packaged dashboards are a starting point. Clone one to add your own components rather than editing the packaged record, and keep the developer name of whatever the home page should render.
Refresh policy
Dashboards show their last refresh; set a daily schedule (or refresh on open) so the morning glance is the morning’s truth.
What you build with
The package ships no dashboards or reports of its own — deliberately, since every finance team's KPIs differ — but it ships the plumbing: seven report types that expose the module's data to the report builder (GL Account Transactions, Sales Invoices with Lines, Purchase Invoices with Lines, Purchase Orders with Lines, Budget with Lines, Fixed Assets, Aging Snapshots with Lines — the full tour is in Standard Reports). Every dashboard component is a report on one of these; the aging-snapshot type in particular turns monthly snapshots into trend charts (outstanding by bucket over time, DSO month over month) that no live view can give you. The Financial Center's statements remain the package's own "financial dashboards" — computed, not charted — and the two layers complement rather than compete.
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Creating the dashboard with the right label but a different developer name | The slot keys on the developer name — the dashboard exists, the home page stays blank, and everyone concludes it's broken | Set the developer name exactly as the table above shows when creating each dashboard |
| Building components on raw object reports instead of the packaged report types | You lose the joined context (lines with headers, GL with entity and period) the types were designed to provide | Start every source report from one of the seven packaged types |
| No refresh schedule | The morning glance shows last Tuesday's truth and quietly erodes trust in the numbers | Schedule a daily refresh (or refresh-on-open) and keep the last-refreshed stamp visible |
| Making decisions from a tile | Dashboards summarize; they can't show the invoice behind a spike | Treat tiles as triggers — the statement, aging or ledger is where the decision gets made |
Where to go next
- Standard Reports — the report types beneath the tiles.
- Report Filters & Dimensions — the deep-dive layer.
- Your Setup Roadmap — where dashboard setup fits.
Frequently asked questions
No — the slot hides until a dashboard exists under the expected name. Ask your admin to create it (recipe above); it appears on next load.
Depends how the admin configures the dashboard's running user — fixed (everyone sees the same) or per-viewer (each sees their own visibility). For finance KPIs, fixed-user with a broad-visibility running user is the common choice.
Fully — they're ordinary Salesforce dashboards. Any report on the packaged types (or your own data) can become a component; the home pages simply display them.
Yes — both home pages look for Executive Financial Overview. That's usually right (both audiences want the whole-business view); if the admin needs different tiles, the shared dashboard can simply grow, or the admin's home page layout can be adjusted by your Salesforce administrator.
The slots look for the expected developer names. The lightest path is to recreate (or clone) your dashboard under the expected developer name; the components carry over and the home page picks it up on next load.
Dashboard and folder sharing are ordinary Salesforce visibility: if you can't access the dashboard, the slot hides rather than erroring. Ask your admin to share the dashboard's folder with your role.
Was this article helpful?