How to Improve Financial Reporting in Tyler Munis (2026 Guide)
Tyler Munis financial reporting guide for 2026: fix your GL string, tighten month-end close, move Crystal reports to SSRS, clean up roles, and map the ACFR.
On this page
- Key takeaways
- Why Tyler Munis financial reporting goes wrong
- How to improve financial reporting in Tyler Munis in 2026: 8 steps
- Which Munis reporting tool should you use for which job?
- What better Munis reporting looks like after 90 days and after a year
- When to get outside help with Munis reporting
- Tyler Munis financial reporting: frequently asked questions
- Better Munis reports start with a better ledger
To improve Tyler Munis financial reporting, fix the foundation before the reports. Clean up the general ledger string, enforce posting and reconciliation discipline, then rebuild your key reports in SSRS and use Hub dashboards or ACFR Statement Builder only for the jobs they do best.
The timing matters. Tyler’s own knowledge base says support for Crystal Reports in Enterprise ERP (Munis) was set to end on October 31, 2026. That date has now passed, and your council and auditors still expect a clean budget-to-actual every month and an ACFR on time every year.
Our guide is for finance teams already live on Munis whose reports are slow, untrusted, or rebuilt in Excel every cycle. If you are still implementing, start with our post on Tyler Munis implementation mistakes instead.
Key takeaways
In KCT’s experience, many Munis reporting problems trace back to the GL structure, posting discipline and reconciliations, not the report writer.
Tyler recommends SQL Server Reporting Services (SSRS) for custom Munis reports. Crystal Reports support was scheduled to end October 31, 2026.
On SaaS, writing custom SSRS reports requires Tyler Reporting Services, which Tyler offers at an additional cost. Canned SSRS reports cannot be modified.
Inventory and triage the reports you already rebuild in Excel before you build anything new.
Role hygiene matters. Tyler Reporting Services views check Munis permissions, and roles drift over time.
Use the right tool for each job: standard reports, SSRS, Hub, ACFR Statement Builder, or Excel.
Why Tyler Munis financial reporting goes wrong
Bad Munis reports are usually a symptom, not the disease. When the budget-to-actual gets rebuilt in Excel or the ACFR schedules get built by hand, the cause is usually upstream: the account structure, late postings, or unreconciled sub-ledgers.
Public records back this up. Lehigh County Authority, a Pennsylvania water and sewer utility, set out to “streamline financial reporting” and ran a needs assessment first. The key takeaway in its January 2026 board project review was blunt: “Munis itself is not the problem!” The fix was re-implementing Finance with a new general ledger string.
The City of Santa Fe, New Mexico, shows the discipline side. Its fiscal year 2021 audit, released in July 2023, reported a material weakness after the city fell behind on entering cash transactions in Munis and reconciling the books to the bank. Journal entries lacked attached support, and the GL needed multiple correcting entries.
Neither problem is a reporting tool problem. Use the table below to match what you see to where the fix lives.
Swipe to see all columns →
| Symptom | Likely cause | Where to fix it |
|---|---|---|
| Budget-to-actual rebuilt in Excel every month | GL string does not match how council reads the budget | Step 2 |
| Reports do not tie to the trial balance | Late postings, unreconciled sub-ledgers | Step 3 |
| “Which report is the right one?” | Duplicate, unowned custom reports | Steps 1 and 4 |
| Crystal reports breaking after upgrades | Unsupported report platform | Step 5 |
| Users see data they should not, or cannot see what they need | Role drift | Step 6 |
| ACFR schedules built by hand | Accounts not mapped to statement groups | Step 7 |
How to improve financial reporting in Tyler Munis in 2026: 8 steps
To improve Tyler Munis financial reporting in 2026, inventory your current reports, fix the GL string, make the month-end close report-ready, standardize report definitions, move custom reports from Crystal to SSRS, clean up roles, map accounts for the ACFR, and build Hub dashboards last. Work through the steps in order: each one makes the next easier.
Inventory and triage the reports you have today.
Assess the general ledger string against the reports you must produce.
Tighten posting and reconciliation discipline so the GL is report-ready every month.
Standardize report definitions, parameters and owners.
Move custom reports off Crystal Reports and onto SSRS.
Fix roles and access before you publish reports widely.
Map accounts for the ACFR before year-end.
Build dashboards on trusted data, then review the catalog quarterly.
Step 1: Inventory and triage your current Munis reports
You cannot fix reports nobody owns. Start with a full list of every report finance, budget, departments, council and auditors rely on, including the spreadsheets built from Munis exports.
Those spreadsheets are where the time goes. Our Close-Time Calculator lists “reports rebuilt every cycle because the ERP will not produce them clean” as one of the common places close days disappear.
For each report, capture:
Then sort every line into one of four buckets: retire, keep, rebuild, or replace with a standard report. Flag every Crystal report as you go. That list drives Step 5.
KCT rule of thumb: many agencies find that a good share of their custom reports have not been run in a year. Retiring those is usually the fastest win.
Step 2: Assess your Munis chart of accounts and GL string against required reports
If your account structure does not reflect how council reads the budget, every report becomes a workaround. Fixing the string is what lets Munis produce the report directly instead of finance staff assembling it.
Two agencies show how this plays out. The City of Madison, Wisconsin, updated its Munis Chart of Accounts in 2024 to reflect new budgeted services, and its 2025 Adopted Budget reflects the new structure. Lehigh County Authority’s re-implementation with a new GL string lists department-level budgeting and financial reporting among its improvements.
Test your current string against five outputs you cannot skip:
The adopted budget book.
Budget-to-actual by department and fund.
Grant reimbursement and compliance reports.
Required state reporting.
ACFR fund statements.
If Munis can produce all five without spreadsheet surgery, you only need targeted fixes, such as new segment values or roll-ups. If it cannot, plan a restructure tied to a fiscal-year boundary.
Be honest about the scope. Restructuring a live GL touches budgets, history, interfaces and every sub-ledger, including Utility Billing and Asset Management. Treat it as a project, with your external auditor reviewing the design.
For GL design principles, see our post on Tyler Munis implementation mistakes.
Step 3: Make the general ledger report-ready at every month-end close
A report can only be as accurate as what has been posted and reconciled. If cash, payables and sub-ledgers lag, no report writer can make the numbers right.
Santa Fe’s FY2021 audit is the cautionary example: cash entries fell behind in Munis, bank reconciliations lagged, and the city needed multiple correcting entries. According to the city’s announcement, it put a monthly close process in place in FY23.
The cost of slow reconciliation reaches past the finance office, whatever system you run. In June 2026, Good Morning Wilton reported that Wilton, Connecticut, would miss its state audit deadline because key reconciliations were unfinished, and the town’s bond advisor said that after June 30 it could not issue new bonds until the FY2025 audit was released.
A report-ready close in Munis usually includes:
A close calendar with sub-ledger cut-offs for AP, AR, payroll, Utility Billing, cash receipts and Asset Management.
Reconciliation deadlines for bank and sub-ledger-to-GL reconciliations. KCT rule of thumb: aim for a fixed number of business days after month-end, and keep it the same every month.
Required attachments on every journal entry, so auditors never chase support.
One close checklist owner who signs off before reports go out.
Want to see what a slow close is costing you? Run your numbers through the Close-Time Calculator.
The page shows a KCT pattern of roughly two weeks down to about four days. Treat that as a KCT rule of thumb: your result depends on configuration and how clean your reconciliations are.
Step 4: Standardize report definitions, parameters and owners
Two versions of “budget-to-actual” erode trust faster than one wrong number. Every key report needs one definition, one owner and one home.
KCT rule of thumb: when department heads stop trusting Munis reports, the cause is often two reports with the same name and different logic, not a data error. Your Step 1 inventory will usually surface them.
For each key report, write down:
Which accounts and funds it includes.
Whether encumbrances are in or out.
Which period and which budget version (original, amended, revised).
Where it lives: one Munis menu location or one SSRS folder.
A naming convention and a simple version log.
Then publish a short report catalog for department heads. One page is enough. People use the right report when they can find it.
If your reports still will not tie out because the GL string, posting rules or reconciliations are broken, that is structural work, and it is what our ERP Recovery & Optimization service is built for. KCT is not a Tyler partner or reseller and takes no referral fees from Tyler, so our recommendations follow your data, not a product list.
Step 5: Move Munis custom reports off Crystal Reports and onto SSRS
SSRS is where Munis custom reporting is headed, and Crystal is where it has been. Tyler’s knowledge base states that “SQL Server Reporting Services (SSRS) is the recommended platform for custom reporting in Enterprise ERP (MUNIS),” and that Crystal support was set to end on October 31, 2026. Check Tyler’s current announcement for any extension that applies to you.
Tyler also says SSRS will remain in place for all versions of Enterprise ERP into the future, so reports you rebuild now will carry forward through upgrades.
A few facts from Tyler’s documentation shape the plan:
Here is how to turn that into a migration:
Confirm with your Tyler account team whether you own Tyler Reporting Services and what your contract includes.
Plan access and setup before anyone starts building.
Prioritize the Crystal reports from Step 1 by audience: council and auditor reports first.
Build from Tyler Reporting Services views rather than base tables.
Need a canned report changed? Build a custom version alongside it instead of editing it.
Test every rebuilt report against the trial balance before you retire the Crystal version.
Still running Crystal reports today?
Identify which ones run at month-end and year-end, freeze changes to them, and rebuild the five most critical first. Everything else can follow in priority order.
Step 6: Fix roles and access before you publish reports widely
Your reports are only as safe and as useful as the roles behind them. Tyler Reporting Services views verify permissions per ERP module, so a messy role structure produces reports that either leak data or show users nothing.
Roles drift quietly. The City of College Station, Texas, implemented Munis in 2015. Its September 2024 internal audit of ERP role-based access found no audit of user privileges since implementation, 128 users and 44 roles with at least one segregation of duties conflict, and an average of 32 days to deactivate access after an employee left.
Before you roll out new reports:
Review report-related roles: who can view, and who can author or publish SSRS reports.
Strip privilege creep, such as staff who kept old roles after changing jobs.
Align roles with segregation of duties.
Automate termination notices from HR to IT so access ends on the last day.
Re-review every year, not once a decade.
Step 7: Map accounts for the ACFR before year-end, not during it
Much of the ACFR pain we see is a mapping problem, and you can solve it in the spring. If every account is mapped to a statement line and fund type before year-end, the statements come together. If not, someone builds schedules by hand in October.
Tyler sells ACFR Statement Builder as a separate product. Tyler describes it as embedded with GASB rules, with statement and schedule templates and the ability to drill into any number to see the values behind it.
Tyler’s own knowledge base on ACFR account groups shows why mapping comes first. It covers accounts imported without fund types or placed in the wrong group, and notes that saving a group with accounts that do not belong there returns an error.
Whatever tool you use, ACFR Statement Builder, another product, or spreadsheets:
Map every account to a statement line and fund type.
Keep a crosswalk that your auditor can read.
Run an interim trial balance through the mapping at mid-year.
Log each new GASB pronouncement you adopt and what it changed.
Step 8: Build dashboards on trusted data, then review quarterly
Dashboards come last, not first. A dashboard on top of an unreconciled GL just shows the wrong number faster.
Tyler’s Enterprise ERP product page describes Hub as giving role-based, out-of-the-box views of key information, alongside Interactive Reporting accessed from Hub, analytics and reporting tools, and export to Excel.
One limit matters: according to Tyler’s knowledge base, Hub custom data feeds can be based on existing Tyler feeds with fields removed, but fields cannot be added. Custom data belongs in SSRS.
Start small. Pick three to five measures department heads already ask for:
Budget vs actual by department.
Open encumbrances.
Cash by fund.
Utility Billing receivables.
Then review the report catalog every quarter. Check usage, log any accuracy issues, and retire anything nobody opened.
Which Munis reporting tool should you use for which job?
Tyler Enterprise ERP reporting spans several tools. Use standard reports for routine lists, SSRS for anything council or auditors see, Hub for quick role-based views, ACFR Statement Builder for the annual report, and Excel only for one-off analysis. Tool names and licensing change, so confirm with Tyler which of these are in your contract.
Swipe to see all columns →
| Tool | Best for | Watch out for |
|---|---|---|
| Standard (canned) Munis reports | Routine operational lists, out of the box | Canned SSRS reports cannot be modified |
| Custom SSRS via Tyler Reporting Services | Council packets, auditor schedules, custom budget-to-actual | Additional cost on SaaS; needs roles, accounts and setup first |
| Crystal Reports | Legacy only | Support set to end October 31, 2026 |
| Tyler Hub and Interactive Reporting | Role-based quick views and dashboards | Hub feeds cannot add fields |
| ACFR Statement Builder | ACFR statements and schedules with GASB templates and drill-down | Separate product; only as good as your account mapping |
| Excel export | Ad hoc analysis | Not a system of record; avoid monthly rebuilds |
What better Munis reporting looks like after 90 days and after a year
Better reporting is visible: reports tie out, nobody rebuilds them, and the ACFR stops being a fire drill. You do not need a benchmark to know you got there. You need a checklist.
KCT rule of thumb: within about 90 days, a focused team can usually finish the inventory, publish a report catalog, and rebuild its most critical Crystal reports. Within a year, the structural items should be done:
Report catalog published and owned.
Crystal reports retired.
Close calendar met three months running.
Budget-to-actual produced from Munis with no Excel rework.
ACFR mapping tested at mid-year.
Annual role review completed.
Steady, documented support gets you there. At the City of Richardson, Texas, KCT has been embedded since December 2023, supporting live Finance and HCM with configuration, reporting and integrations, all documented for the city’s team.
When to get outside help with Munis reporting
Bring in help when the problem is structural or when nobody in-house can write SSRS. A few clear signs:
Reports have not tied to the trial balance for several months.
Your GL string needs a restructure, not a tweak.
No one on staff writes SSRS reports.
Crystal reports are still running month-end or year-end.
Your auditor has issued findings on close or reconciliation.
Start with an assessment. Lehigh County Authority’s needs assessment is what told it the software was not the problem, which pointed the work at the GL string instead of a new system.
Munis reporting draws on more than the core ledger. Utility Billing and Asset Management sub-ledgers feed the GL, so any assessment should include them.
The cost of help depends on the modules, departments and stakeholders involved, and KCT can support at any point, from diagnosis to ongoing report builds.
If you are procuring help, check whether other agencies, your state or your associations have cooperative contracts you can use.
If you want to know what independent Munis support should look like and how to verify it, read our guide to choosing a vendor-neutral Tyler Munis consultant.
Tyler Munis financial reporting: frequently asked questions
What reporting tool does Tyler Munis use?
Tyler Munis uses SQL Server Reporting Services (SSRS) as its recommended platform for custom reporting, and Tyler says SSRS will remain in place for all future versions of Enterprise ERP. Munis also offers standard menu reports, Hub dashboards with Interactive Reporting, and export to Excel for ad hoc analysis.
Is Crystal Reports still supported in Munis?
Crystal Reports support for Enterprise ERP (Munis) was set to end on October 31, 2026, according to Tyler’s knowledge base, and Tyler recommends SSRS instead. Check Tyler’s current announcement for any extension that applies to your agency, and rebuild your critical month-end and year-end Crystal reports in SSRS now.
Do you need Tyler Reporting Services to write custom Munis reports?
Tyler Reporting Services is required to write custom SSRS reports on SaaS-hosted Enterprise ERP. Tyler provides default reports in the menu, but custom report writing requires Tyler Reporting Services, offered at an additional cost. Its views give report authors readable, permission-checked data. Confirm what your contract includes with your Tyler account team.
Can you modify the canned SSRS reports in Munis?
Canned SSRS reports in Munis cannot be modified. Tyler states that they have a fixed structure and modifications are not supported, so changes go through a formal enhancement request. The practical workaround is to build a custom SSRS version alongside the canned report, using Tyler Reporting Services views, and test it against the trial balance.
Can Munis produce the ACFR?
Munis can support ACFR production through ACFR Statement Builder, a separate Tyler product with GASB-based statement and schedule templates and drill-down to the values behind any number. It is sold separately from core Munis. Whatever tool you use, results depend on mapping every account to the right fund type and statement group.
Why don’t your Munis reports match the general ledger?
Munis reports that do not match the general ledger usually trace to late postings, unreconciled sub-ledgers, or two reports using different definitions (a KCT rule of thumb). Santa Fe’s FY2021 audit tied its problems to cash entries falling behind in Munis. Fix the close and the report definitions before you rebuild a single report.
Better Munis reports start with a better ledger
Good reporting is an outcome, not a feature you buy. It comes from a GL string that matches how your council reads the budget, a close that runs on schedule, and one trusted definition for every key report.
The Crystal Reports deadline is a useful forcing function. You have to touch your custom reports anyway, so fix the ledger and the close underneath them while you are there.
If you need a one-time fix to the structure, posting rules or reconciliations, talk to us about ERP Recovery & Optimization.
If you need ongoing SSRS report builds, Crystal migration and month-end support, our Managed Services & Support team can carry that load. Not sure where to start? Take the free ERP Health Check.