REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Financials AI / Financial Reports / Salesforce Reports / Standard Reports

Standard Reports

REDA Financials' reporting comes in two complementary layers. The Financial Center carries the accounting statements — trial balance, income statement, balance sheet, cash flow, plus year-end close — purpose-built, ledger-accurate, export-ready. And for everything else you'd ever want to count, group or chart, the package ships report types that put its data into Salesforce's native report builder. Statements you run; reports you build.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials AI → the Financial Center tab for the statements; the packaged report types live in Salesforce's report builder under the standard Reports tab.
Access you'll need. Any REDA Financials permission set can open the Financial Center tab and run all four statements; what you see is limited to the records your role can read. Building reports on the packaged report types uses your org's normal Salesforce reporting permissions.

Layer 1 — The Financial Center statements

One tab, four statements, one filter panel (details): multi-entity, multi-period, framework-aware, dimension-filterable, drillable to source documents, exportable to PDF/CSV/Excel. These are computed live from the ledger — no report maintenance, no stale copies.

Finding it

In the REDA Financials AI app navigation, open the Financial Center tab (it sits between Aging Snapshot and Audit Log). The page announces itself — title "Financial Center", subtitle "Financial reports, year-end close, and accounting operations" — and offers two inner tabs:

Inner tabWhat lives there
ReportsThe four statements. The Report Type picker offers exactly Trial Balance, Income Statement, Balance Sheet and Cash Flow Statement; switching type clears the previous result.
Year-End CloseThe fiscal-year closing ceremony — preview, execute, reopen. Its own article: Year-End Close.

The life of a run

A fresh Reports tab greets you with "Configure your report parameters and click Run Report". The Run Report button stays disabled until you've given it the two things every statement needs — at least one entity and at least one date range. While computing, you'll see "Generating report..."; if the run finds nothing in scope, "No data found for the selected parameters" (usually a date range before the books began, or a filter excluding everything). Running a report is read-only by design — the statements aggregate the ledger without writing anything, so nobody breaks the books by reporting on them.

Layer 2 — Packaged report types for the report builder

Seven report types cover the operational data:

Report typeBuild things like…
GL Account TransactionsLedger extracts, account activity by month, posting-source analyses
Sales Invoices with LinesRevenue by product, tenant billing summaries, overdue lists your way
Purchase Invoices with LinesSpend by vendor/GL/cost center, invoice cycle analyses
Purchase Orders with LinesOpen commitments, receiving status, PO pipelines
Budget with LinesUtilization tables, over-budget flags across entities
Fixed AssetsAsset registers, NBV summaries, disposals in period
Aging Snapshots with LinesAging trends over months, DSO tracking

Anything built on these behaves like any Salesforce report: filters, charts, dashboards, scheduled subscriptions to inboxes. Your admin can also add filtered list views on any tab for the everyday operational lists (overdue invoices, draft journals, unmatched receipts).

The report types are joined for you. Each "…with Lines" type pairs headers with their line detail, and GL Account Transactions carries the account, entity, ledger and period on every row — so the joins that make ledger analysis painful elsewhere are already done. Start from the packaged type, not the raw object.
Which layer for which question? "What's our P&L?" → Financial Center. "Which tenants generate the most CAM income?" → a report on Sales Invoices with Lines. "Is the ledger balanced?" → trial balance. "Chart spend by vendor for the ops meeting" → report + dashboard. When the question is accounting, use the statements; when it's operational analytics, build a report.

Who sees what

All five REDA Financials roles — Accounting Admin, Accounting Controller, Accounts Payable, Accounts Receivable and Read Only — get the Financial Center tab and can run and export all four statements. The reports respect each user's data visibility, so what a user can see in records is what their statements aggregate. The one gated operation in the Financial Center is executing a year-end close, which posts journals and therefore needs journal rights.

Common mistakes to avoid

MistakeWhy it hurtsDo this instead
Hunting the Salesforce Reports tab for a packaged "P&L report"The package deliberately ships no prebuilt Salesforce reports — the statements live in the Financial Center, so the search ends in confusionAccounting statements → Financial Center; the Reports tab is where you build analytics on the packaged report types
Rebuilding the income statement in the report builderHand-built P&Ls drift from the ledger's rules (opening balances, sign conventions, currency handling) and become a maintenance debtUse the statement; reserve the report builder for the operational questions it's good at
Answering an accounting question from an operational reportAn invoice-based "revenue" report counts documents, not postings — journals, and corrections live only in the ledgerWhen the number must tie to the books, run the statement and drill from there
Expecting dashboards out of the boxThe home-page dashboard slots stay hidden until your admin creates the dashboards — waiting for them to "appear" wastes weeksStand them up once on the packaged report types — the dashboards article has the recipe
Statements are computed, not stored. Every run reads the ledger as it stands that second. That's why there's nothing to refresh, and also why a re-run after new postings can differ from last week's — which is exactly what the export-and-file habit at month-end is for.

Where to go next

  1. Executive / AR / AP Dashboards — putting reports on the home pages.
  2. GL Account Ledger — the GL report type in anger.
  3. Report Filters & Dimensions — the statements' controls.

Frequently asked questions

Every REDA role sees the Financial Center and can run statements (data visibility follows your permissions). Building Salesforce reports uses your org's normal reporting permissions — most orgs let everyone build, admins manage folders.

They read the same ledger, so scoped identically they tie. Differences always come from scope — dates, entities, filters. The statements' badge-and-total discipline makes them the arbiter for accounting questions.

Statement exports are on-demand. For scheduled delivery, build the closest Salesforce report (e.g., GL Account Transactions grouped for P&L accounts) and subscribe — or make the monthly Financial Center export part of the close checklist, which is what Meridian does.

Open the REDA Financials AI app from the App Launcher; the tab sits in its navigation bar (between Aging Snapshot and Audit Log). If a role-based navigation trims the bar, the App Launcher's search finds "Financial Center" directly.

That's the resting state — "Configure your report parameters and click Run Report". Statements compute on demand rather than pre-loading a default, so you always know a displayed report reflects parameters you chose.

No — the statements are read-only aggregations of the ledger. Run, re-run, export and drill freely; the only Financial Center operation that writes anything is executing a year-end close.

Was this article helpful?