The Problem With Epicor Reporting (And Why You’re Reading This)
Epicor is a capable ERP. It handles manufacturing, distribution, financials, inventory, and supply chain for thousands of companies across North America. But the reporting — the built-in tools for actually getting data out of Epicor in a useful format — is where most companies hit a wall.
Not because the tools don’t exist. Epicor has several reporting tools built in. The problem is that most users don’t know which tool to use for which job, the built-in tools have real limitations, and the path to custom reports is genuinely complex if you haven’t done it before.
This guide explains every Epicor reporting option — Kinetic reports, the Financial Report Designer, Advanced Financial Reporting, BAQs, dashboards, custom forms, SSRS — in plain language. What each one does, where each one breaks down, and when you need to bring in outside help.
We build custom Epicor reports and Epicor Kinetic report help for companies across manufacturing, distribution, and automotive industries. Here’s what we’ve actually learned.
Epicor’s Built-In Reporting Tools: What Each One Is For
Epicor is not a single reporting tool — it’s a platform with multiple reporting mechanisms, each designed for different use cases and different user types. Understanding which tool is designed for which job is the starting point.
Epicor Financial Report Designer
The Epicor Financial Report Designer (sometimes called FRD) is Epicor’s built-in tool for creating balance sheets, income statements, trial balances, and other structured financial reports. It uses a row/column design approach — you define which GL accounts appear on which rows, how columns are grouped (actuals, budget, variance), and what time period is shown.
What it does well:
- Standard financial statements — P&L, balance sheet, cash flow
- Multi-period comparisons (month vs. prior month, vs. budget)
- Department and cost center breakdowns
- Designed for finance users who are not technical
Where it breaks down:
- Limited formatting flexibility — you cannot easily produce the exact layout your board or auditor expects
- Does not combine financial data with operational data (inventory levels, job costs, sales activity)
- No automated delivery — someone has to run it manually each period Complex consolidations across multiple entities require workarounds
When you need custom help: When the Financial Report Designer produces roughly what you need but not the exact format, or when you need automatic delivery of financial reports on the first business day of each month without manual effort.
Epicor Advanced Financial Reporting (AFR)
Advanced Financial Reporting is Epicor’s more powerful financial reporting module — available as an add-on, not standard in all versions. AFR provides greater flexibility in financial statement design, multi-entity consolidation, and layout control than the standard Financial Report Designer.
What it does well:
- More layout flexibility than FRD
- Better multi-company/multi-entity financial consolidation
- More control over column and row definitions
- Better handling of complex account structures
Where it breaks down:
- It’s still limited to financial data from the GL — it doesn’t pull operational data
- Setup and maintenance requires someone who understands both the GL account structure and the AFR design tool
- Some layouts still can’t match exactly what a board or auditor expects without custom development
- It costs extra — it’s not included in all Epicor packages
When you need custom help: When AFR produces the right data but you need the output delivered automatically, formatted to a specific professional standard, or combined with data from outside the GL.
Epicor BAQ Reports (Business Activity Queries)
BAQ (Business Activity Query) is one of the most flexible and powerful built-in reporting tools in Epicor. A BAQ is essentially a saved SQL query — you define which tables to pull from, how to join them, what calculated fields to create, and what filters to apply. BAQbased reports can pull data from virtually any part of the Epicor database.
What BAQs do well:
- Pull data from any combination of Epicor tables
- Support complex joins, calculated fields, and filters
- Can be used as the data source for Epicor dashboards
- Available to non-technical users through a guided interface BAQs feed Epicor dashboards and custom SSRS reports
Where BAQs break down:
- Complex BAQs require real SQL knowledge to write correctly
- Performance degrades on large datasets without proper indexing
- BAQ output in the native Epicor grid is functional but not formatted for professional delivery
- No native scheduling — reports still need to be run manually
When you need custom help: When your BAQ is pulling the right data but you need it formatted professionally, delivered automatically, or combined with data from outside Epicor (like a CRM or payroll system).
Epicor Kinetic Reports
Epicor Kinetic is Epicor’s modern UI framework — the current version replacing the older Epicor 10 and classic UI. Epicor Kinetic reports are the reports that run within the Kinetic interface.
The reporting architecture in Kinetic is not fundamentally different from Epicor 10 — BAQs, SSRS-based report styles, and the Financial Report Designer are all still there. What changed is the interface for accessing and configuring reports.
Common Epicor Kinetic reporting challenges:
- Reports that worked in Epicor 10 may have broken or changed behavior after the Kinetic upgrade
- The Kinetic web interface handles some SSRS report interactions differently
- Some legacy Crystal Reports embedded in Epicor 10 are not supported in Kinetic Dashboard widgets may need to be rebuilt in the Kinetic framework
When you need Kinetic-specific help: If you upgraded from Epicor 10 to Kinetic and reports broke, or if you need new reports built from the ground up in the Kinetic environment. See our Epicor Kinetic report help page for what we handle.
Epicor Dashboard and Dashboard Customization
Epicor dashboards are interactive views built inside the Epicor application using BAQ widgets, chart panels, KPI tiles, and grid displays. They are designed for operational monitoring — order status, production throughput, open purchase orders, warehouse activity — where a user needs a real-time view inside the ERP without running individual reports.
What Epicor dashboards do well:
- Real-time data display inside the Epicor interface
- Clickable, drillable — users can click through to source records
- No separate BI tool required
- Works for shop floor, warehouse, and operational management audiences
Epicor dashboard customization — adding new widgets, modifying existing dashboards, adding BAQ-based data panels, creating custom chart types — requires BAQ development skills and familiarity with the Epicor dashboard designer.
Where Epicor dashboards break down:
- Not accessible to people outside the Epicor application (customers, board members, executives without ERP logins)
- Limited visual sophistication compared to Power BI
- Cannot easily combine Epicor data with external data sources (CRM, payroll) Not designed for formatted document output
When you need custom help: When your team needs a dashboard that’s more visually sophisticated, accessible outside the ERP, or combining Epicor data with data from other systems. That’s typically where Power BI connected to the Epicor database becomes the right answer.
Epicor Custom Forms and Custom SSRS Reports
Custom Epicor forms are documents generated from within Epicor — purchase orders, sales orders, invoices, packing slips, shipping labels, work orders, RMAs. These forms are typically built using SSRS Report Designer (RDL files) and deployed through Epicor’s Menu Maintenance and Report Style system.
This is where most companies need the most help. The standard Epicor forms are generic.
Companies need:
- Custom invoices with their specific branding and layout
- Purchase orders formatted to vendor specifications
- Packing slips with barcodes and lot tracking
- Work orders formatted for the shop floor Pick lists sorted by warehouse location
Customizing these forms requires understanding both the Epicor RDD (Report Data Definition) and BAQ structure, and the SSRS report design tool. It’s not impossible for someone technical to learn, but it takes time — and most IT teams at Epicor shops don’t have dedicated report developers.
ReportingGuru builds: Custom Epicor forms and SSRS reports for manufacturing, distribution, building supply, and automotive companies. We handle the BAQ, the RDD, the SSRS design, and the deployment through Menu Maintenance.
Epicor P21 (Prophet 21) Reports: The Distribution Side
Epicor Prophet 21 (P21) is a completely separate product from Epicor Kinetic — it’s Epicor’s ERP designed specifically for wholesale distribution businesses. The database structure, reporting tools, and customization approach are different from Kinetic.
P21 reporting tools:
Epicor Report Studio — P21’s built-in web-based reporting tool for non-technical users. Drag-and-drop interface, filters, automated delivery
Crystal Reports — used extensively in P21 for customer-facing documents, operational reports, and forms
SSRS — for more complex reports requiring paginated output and scheduled delivery Power BI — for analytics dashboards connected to the P21 SQL Server database
What P21 users most commonly need custom help with:
Customer-facing documents — invoices, statements, order confirmations — that need specific branding, layout, and data combinations the standard P21 templates don’t provide.
Sales and inventory reports — sales summaries, inventory aging, and open order backlog reports that require data from multiple P21 tables that Report Studio can’t easily join.
Financial reports — AP aging, AR aging, balance sheets formatted for specific audiences (board, lenders, audit) that don’t match P21’s native output.
Automated delivery — distribution companies need reports in buyer, sales rep, and manager inboxes every morning without anyone manually running them.
ReportingGuru builds: P21 custom reports using Crystal Reports, SSRS, and Power BI — connected directly to the P21 SQL Server database — for distribution companies across the US
When to Go Beyond Built-In Epicor Reporting
Here’s the honest trigger list. If any of these describe your situation, the built-in tools are not going to solve it:
You need data from more than one system. Epicor data + Salesforce data + payroll data in one report. That requires a SQL Server integration layer — not the built-in Epicor reporting tools.
You need formatted professional output. Board-quality financial packages, branded customer invoices, formal LP investor statements — these require SSRS or Crystal Reports development with precise layout control.
You need automatic scheduled delivery. If someone has to log into Epicor and run a report manually, that’s not automated. SSRS subscriptions deliver reports automatically without human involvement.
Your reports broke after the Kinetic upgrade. Legacy Epicor 10 reports don’t always survive the Kinetic migration cleanly. If reports are broken or missing, they need to be assessed and rebuilt.
You need dashboards outside the ERP. Executive dashboards, sales team scorecards, and customer-facing analytics that don’t require an Epicor login need Power BI or a similar tool connected to the Epicor database.
Your IT team doesn’t have Epicor reporting expertise. Knowing general SQL is not the same as knowing Epicor’s database schema, the RDD/BAQ relationship, and the Menu Maintenance deployment process. ERP-specific knowledge cuts the time and the errors significantly.
What We Build for Epicor Users
We’ve been building custom Epicor reports for over 17 years across manufacturing, distribution, building supply, automotive, and job-cost industries. Here’s what we handle:
BAQ development — complex multi-table queries, calculated fields, performance optimization
Custom SSRS reports — built on BAQs or direct SQL, formatted for professional output
Custom forms — invoices, POs, packing slips, pick lists, work orders — deployed through Menu Maintenance
Epicor dashboards — BAQ widget development, dashboard layout, KPI panels
Power BI dashboards — connected to the Epicor or P21 database, for audiences outside the ERP
Epicor Kinetic migration — assessing and rebuilding reports that broke in the Kinetic upgrade
P21 reports — Crystal Reports, SSRS, and Power BI built on the Prophet 21 SQL Server database
Financial Report Designer help — designing or reformatting FRD reports to match board and audit requirements
Automated delivery — SSRS subscriptions, email scheduling, automated report distribution
No minimums. No retainers. No up-front cost. US-based team. Same-day responses.
Custom Epicor reports → Epicor Kinetic report help → Prophet 21 / P21 reports →
FAQ
What is the Epicor Financial Report Designer and what can it do?
The Epicor Financial Report Designer (FRD) is the built-in tool for creating standard GL-based financial reports — balance sheets, income statements, trial balances, and budget-vs-actual comparisons. It uses a row-and-column layout approach where you assign GL accounts to rows and define time periods and scenarios in columns. It’s accessible to finance users without SQL knowledge. Its main limitations are layout inflexibility, no automated delivery, and the inability to pull operational data outside the GL.
What is the difference between Epicor 10 reports and Epicor Kinetic reports?
Epicor 10 and Epicor Kinetic use the same underlying reporting architecture — BAQs, SSRS-based report styles (RDL files), and the Financial Report Designer. The difference is the UI layer.
Kinetic’s web-based interface changed how reports are accessed and deployed through Menu Maintenance. Reports that worked in Epicor 10’s classic UI sometimes behave differently or break in Kinetic, particularly Crystal Reports-based forms that relied on the classic viewer. Migrating from Epicor 10 to Kinetic is often when companies discover that their custom reports need to be assessed and rebuilt.
What are BAQ reports in Epicor and when should I use them?
A BAQ (Business Activity Query) is Epicor’s built-in SQL query tool — it lets you define which Epicor database tables to pull from, how to join them, what fields to include, and what calculations to apply. BAQs are the data engine behind Epicor dashboards and can be used as data sources for custom SSRS reports. Use BAQs when you need to combine data from multiple Epicor tables that no standard report covers. For complex BAQs or for turning BAQ data into formatted professional output with automated delivery, custom SSRS development is typically needed on top.
What is Epicor dashboard customization?
Epicor dashboard customization means adding, modifying, or redesigning the BAQ-driven panels, widgets, charts, and KPI tiles that appear on dashboards within the Epicor application. This requires BAQ development to define the data, and familiarity with the Epicor dashboard designer to build the visual layout. Custom Epicor dashboards are useful for operational teams working inside the ERP daily. For executives, customers, or anyone without an Epicor login, Power BI dashboards connected to the Epicor database are a better fit.
What is the difference between Prophet 21 and Epicor Kinetic?
Prophet 21 (P21) and
Epicor Kinetic are two separate ERP products owned by Epicor Software. Kinetic is Epicor’s ERP for manufacturing, automotive, and job-shop environments. Prophet 21 is Epicor’s ERP designed specifically for wholesale distribution. They have different database schemas, different reporting tools, and different customization approaches. Custom reports built for one cannot be directly used in the other.
Can custom Epicor reports be delivered automatically by email?
Yes. Custom SSRS reports deployed in Epicor can be configured with SSRS subscriptions that generate the report on a defined schedule — daily, weekly, monthly — and email it to a distribution list automatically. This is how you move from “someone runs the report every Monday morning” to “the report shows up in the right inbox at the right time without anyone touching it.” Setting up SSRS subscriptions requires access to the SSRS Report Server, which is separate from the Epicor application itself.
What custom Epicor forms can ReportingGuru build?
We build any transactional form that Epicor generates — custom invoices, purchase orders, packing slips, sales order acknowledgments, work orders, pick lists, RMA forms, shipping labels, and customer statements. These are built as SSRS RDL files connected to Epicor BAQs or direct SQL, deployed through Epicor’s Menu Maintenance and Report Style system. We handle everything from the data query through the visual design and the Epicor deployment.
Related Pages
Epicor Custom Reports — Our Epicor reporting service page — BAQs, SSRS reports, custom forms, dashboards, and Kinetic migration.
Epicor Kinetic Report Help — Specific help for reports broken after a Kinetic upgrade or new reports needed in the Kinetic environment.
Prophet 21 / P21 Reports — Custom reporting for Epicor Prophet 21 distribution ERP — Crystal Reports, SSRS, Power BI, and Report Studio.
Epicor CPQ Reporting — Custom reporting for Epicor CPQ (Configure Price Quote).
SQL Server Reporting Services (SSRS) — The primary tool used to build custom Epicor reports — what SSRS is and what we build with it.
Power BI Development — For Epicor and P21 users who need interactive dashboards outside the ERP.
External Resources
Epicor Official Documentation — Official Epicor product documentation including the Financial Report Designer, BAQ Designer, and Report Style setup.
Epicor Community / EpicCare — The Epicor user community — useful for finding answers to specific BAQ, dashboard, and report configuration questions.
Microsoft SSRS Documentation — The definitive reference for SSRS, which powers custom Epicor report styles and forms.
Need Epicor Reporting Help Right Now?
We work with Epicor Kinetic, Epicor 10, and Prophet 21. We know the database schemas, the BAQ designer, the RDD structure, and how to deploy through Menu Maintenance. We’ve built hundreds of custom Epicor reports for manufacturing and distribution companies across the US.
No minimums. No retainers. No up-front cost. Same-day response.