How to Survive Your First Month-End Close on a New ERP

Go-live gets the cake in the break room.

Your first month-end close is where you find out whether you had anything to celebrate.

To survive your first month-end close on a new ERP, prove your opening balances tie out by fund before go-live, give the first close roughly twice its normal calendar, and reconcile cash and payroll daily during hypercare.

Then close your subledgers in order, run a soft close before the hard close, and keep implementation support in the room until the books are signed off.

Most first-close advice online is written for a company on NetSuite with one entity and no council meeting. Cities and counties have a harder job. You’ve got dozens of funds that each have to balance, encumbrances that have to survive the conversion, and a budget-to-actual report council expects on schedule.

And eventually, an auditor will ask how you tested the data migration.

So in this guide I’m laying out a day-by-day first-close timeline, the 8 steps I’d hand any finance director heading into one, the reconciliations that break most often, and the mistakes that turn into audit findings. If you’d rather have senior people in the room for it, KCT’s implementation team stays through the first fiscal close and payroll cycles.

Let’s get into it.

What is the first month-end close on a new ERP?

The first month-end close on a new ERP is the first accounting period your finance team closes entirely inside the new system. Converted legacy balances meet live transactions for the first time, so the close is the first real proof that data migration, configuration, integrations, and training work together under deadline.

On go-live day, you find out whether transactions post. At close, you find out whether a utility deposit landed in the water fund or the general fund, and whether a converted PO is still reserving budget the department already used.

Why the first close is the real ERP go-live test

Houseblend’s guide to NetSuite’s first close makes a point that applies just as well to a city on Tyler, Workday, Oracle, or any other public-sector ERP platform: treat the first close as an acceptance decision, not a routine month. Two accounting histories are being stitched together, and the close is where the seams show.

Set expectations with real numbers. APQC benchmarking across more than 10,000 organizations puts the median monthly close at 6 calendar days, with bottom performers at 10 or more. Your first close on a new system will probably land in that bottom group, and that’s fine if you planned for it.

Public-sector teams on established systems aren’t racing to five days either. McLean County, Illinois, which went live on its new financials in mid-February 2026, told its board in July that a soft close usually wraps within a few days to a week after month-end.

Rule of thumb: Schedule the go-live celebration for after close #1 is signed off.

Plan the ERP go-live financial close as its own workstream, separate from the cutover plan. Before go-live, tell your city manager or county administrator what “done” looks like for close #1 and roughly how long it will take. Then a late first report is something council heard about months ago, and nobody gets surprised on the agenda.

Why a government’s first close is harder than a company’s

A government ERP first close is harder because fund accounting, encumbrances, council reporting, and outside subledgers all have to land correctly at once, usually with a team that’s also running daily operations. A private company converting to a new ERP has one balance sheet to prove. A city with 40 funds has 40.

The details shift with the type of government. Cities usually juggle enterprise funds and utility billing, while counties often have elected officials whose offices run their own subledgers.

Every fund has to balance on its own

Each fund is its own self-balancing set of books, so the conversion has to land assets, liabilities, and fund balance correctly in every one of them. Due-to and due-from accounts also have to net to zero across funds. If the crosswalk from your old fund-department-object string to the new chart of accounts split or merged anything, the first close is where it surfaces.

The new chart of accounts pays off long term. APQC data shows that organizations with wide adoption of a standard chart of accounts close about two days faster. But at close #1, that chart is brand new, and nobody has muscle memory with it yet.

Run a trial balance by fund on go-live day and again at month-end. Check that every fund balances and that interfund balances net to zero before anyone touches an accrual.

Encumbrances and open POs have to cross systems intact

Open purchase orders become encumbrances in the new system, and their remaining balances have to come across exactly. Convert them at full value instead of remaining value, and you’ve double-reserved budget. Drop them and departments suddenly look like they have money they’ve already committed.

The problem gets worse with a mid-year go-live. Year-to-date budget, actuals, and encumbrances all have to agree, or the first budget-to-actual report council sees will be wrong in ways that are hard to explain from the dais.

Pull the legacy open-PO listing on cutover day and reconcile it line by line to the new system’s encumbrance report. Treat any variance as a blocker, not a cleanup item.

Council still expects its budget-to-actual report on time

Your monthly or quarterly financial report to council doesn’t pause for an ERP project. The report probably has to be rebuilt in a new report writer, against a budget that may have been loaded at a different level of detail than before.

Rebuild that report in the new system before go-live and test it against a month you already reported from the legacy system. If the new version can’t reproduce a month you already presented, find out why before council sees one you haven’t.

Utility billing, tax, court, and pension subledgers live outside the GL

Most cities and counties run separate systems for utility billing, property tax, municipal court, permits and recreation, and those systems post into the GL through interfaces. Each interface is a new place for cash to land in the wrong fund or not land at all.

The Washington State Auditor’s report on the City of Puyallup shows how this goes. The city converted its general ledger in April 2023 and changed utility billing systems in the same audit period. The new billing system recorded activity differently from the old one, and the auditor said that made it hard for the city to determine proper financial reporting.

Pension reporting belongs on the same list. Retirement systems like TMRS, TCDRS, CalPERS, and state-level plans expect deposits and files in a specific shape, and payroll liability accounts that don’t clear after remittance are an early warning sign.

Make a one-page interface inventory before go-live listing each source system, what it posts, how often, which GL accounts it hits, and who checks it each morning.

The same lean team is running the city and the cutover

Your accountants didn’t get a sabbatical for the implementation. The people closing the books are also paying vendors and fielding calls from every department that can’t find its report.

Staffing gaps alone can derail a close. The City of Dover’s controller-treasurer told council that a short-staffed finance department meant reconciliations couldn’t be completed, which fed into audit findings and a late report. Add a system conversion on top and the margin disappears.

Budget for backfill. Temporary accounting help for AP and cash receipts during the first two closes is cheap compared to a qualified audit opinion.

The 2026 public-sector ERP first-close timeline (T-30 to close +10)

A government’s first close really starts 30 days before go-live and ends about 10 business days after the first month-end. Here’s how I’d lay out that window, with an owner on every line.

Treat those day counts as a starting point, not a promise. A small town with a handful of funds may move faster. A county with elected-official offices running their own subledgers may need the full window and then some.

Print the table, put names in the owner column, and walk it through with your team two weeks before go-live.

How to survive your first month-end close on a new ERP: 8 steps

You survive your first month-end close on a new ERP by doing most of the work before the month ends. Six of these eight steps happen before close day 1.

Step 1: Prove opening balances tie out by fund before the first live transaction

Your opening trial balance in the new system has to match the legacy closing trial balance, fund by fund, before anyone posts a live invoice. Once live activity mixes in, every variance could be a conversion error or a bad entry, and you'll burn days figuring out which.

Puyallup's audit report says its April 2023 general ledger conversion complicated the audit, on top of staff turnover that left new employees in key roles. Auditors won't take "the consultant said it tied" as evidence.

Build a conversion evidence file with four things: the legacy trial balance, the new opening trial balance, the account crosswalk, and a written explanation for every variance. Have the controller sign it. You'll hand that file to your auditor at year-end.

Step 2: Set the go-live date by your fiscal calendar, not the vendor's

Going live at the start of a fiscal year means you carry balances, not a half-year of activity. Going live mid-year means converting year-to-date actuals, budgets, and encumbrances, then running year-end in a system holding mixed history.

Neither choice is automatically right. McLean County went live on financials in mid-February 2026 and scheduled payroll for October, staggering the two biggest risks. The City of Everett, Washington, is targeting a June 30, 2027 Phase 1 go-live and told bidders that budget cycles, year-end close, and audit activity may affect scheduling.

Whatever date you pick, make sure your first close isn't also your fiscal year-end close, your budget adoption month, or your first payroll on the new system. Each of those deserves its own month.

Step 3: Build a first-close calendar with buffer days

If your legacy close takes 8 business days, plan 15 for the first one. Map every task to a day and a person, the same way the timeline above does.

You'll use the extra days. Staff will look up screens they used twice in training, reports will need tweaks, and at least one interface will post something strange.

Tell council and your manager now that the first monthly financial report might run a week behind. Then try to beat that date.

Step 4: Reconcile daily during hypercare, not at month-end

Reconcile bank activity, payroll clearing accounts, and interface postings every morning during the first month. A difference you catch the next morning usually has one cause and a fresh memory behind it. Leave it for three weeks, and it's tangled up with everything that posted since.

Birmingham City Council in the UK is the cautionary tale here. The council went live on Oracle Fusion in April 2022, and an external auditor later said the bank reconciliation setup posted transactions all over the place. The council then struggled for years to produce auditable accounts. A daily bank match won't fix a broken configuration, but it will tell you it's broken in week one instead of year two.

Flip side: back in 2014, the City of Richmond, Virginia credited its smooth Oracle go-live to organizational change management that kept going through and beyond go-live, with fewer than 100 service desk tickets in the first two weeks.

Hold a 30-minute standup every morning of the first month with the controller, a cash person, a payroll person, and whoever owns the interfaces. Review yesterday's differences, assign each one, move on.

Where go-live support usually runs thin: Hypercare is the point where many implementation contracts get light. The vendor's consultants roll off to their next go-live right as your first close begins. KCT is a vendor-neutral public-sector ERP consulting firm that already leads programs for cities like Richardson, Farmers Branch and Little Elm, Texas. Its implementation team runs cutover and stays through the first fiscal close and payroll cycles, working for your government rather than the vendor. If you're already live and the close won't reconcile, KCT's ERP recovery and stabilization work is built for exactly that.

Step 5: Close the subledgers in the right order

The general ledger closes last, and every subledger that feeds it has to close first, in an order where nothing upstream changes after something downstream locks.

My starting sequence:

1. Cash receipts and the interfaces that post to cash: utility billing, property tax, court, permits, recreation
2. Accounts payable and purchasing, including encumbrance adjustments
3. Payroll, benefits, and pension liabilities
4. Grants and project accounting
5. Capital assets and depreciation, if you run them monthly
6. Interfund transfers and cost allocations
7. General ledger review and adjusting entries

Adjust the order to how your system posts. The rule that matters: once a subledger is locked for the month, nobody reopens it without the controller's sign-off.

Step 6: Run a soft close before the hard close

A soft close locks the period for departmental users but leaves it open for finance to post adjustments. A hard close locks it for everyone. On a first close, you want the soft close early and the hard close only after every reconciliation is reviewed.

The risk on the other side is leaving periods open forever. Stamford, Connecticut's ERP governance committee noted in October 2024 that Period 13 for FY23 was still open, months after that fiscal year ended. Open periods invite back-dated entries and make every later report less reliable.

Put both dates on the close calendar: soft close on close day 1, hard close on a fixed day after review. Move the hard-close date only with a documented reason.

Step 7: Decide on a parallel run on purpose

A full parallel run means entering every transaction in both systems for a month. That doubles the workload for the same lean team you're already worried about.

A targeted parallel usually gives better value. Run payroll in both systems for one or two cycles, since a wrong paycheck is the error employees and unions notice first. If utility billing changed too, compare a billing cycle side by side.

Write down what you're running in parallel, for how long, and what result ends it. Don't let a parallel run quietly turn into permanent double entry.

Step 8: Treat the first close as an acceptance test

The first close is the best evidence you'll get that the system works, so package it like evidence. Your sign-off package should include:

• Trial balance by fund, tied to the opening balances plus the month's activity
• Bank reconciliations for every account
• Subledger-to-GL reconciliations for AR, AP, payroll liabilities, grants and capital assets
• An interfund check showing due-to and due-from net to zero
• The council budget-to-actual report, reviewed for reasonableness
• An open-issues log with owners and target dates
• A workaround log listing every manual step that isn't how the system should run

Then look at your contract. If the vendor's final acceptance or holdback payment is tied to the go-live date, push to tie it to a clean first close, or better, the first two. That keeps the vendor engaged while their people still remember how they configured it.

The reconciliations that break most often in a government's first close

The reconciliations most likely to break in a public-sector first close are the ones riding on brand-new mapping rules, starting with pooled cash, interfund balances, and payroll liabilities. The table covers those plus four more, with the first thing to check on each.

Capital assets deserve a special mention. Philadelphia's controller has flagged for years that the city lacked a modern capital asset system, which is being addressed as part of its OPAL ERP project, and that gaps in financial reporting systems contributed to delays in preparing the ACFR. If your asset module goes live later than core financials, write down how the GL will be kept in sync until then.

Pick one person to own each row of this table for the first three closes, and put their name in the close calendar next to it.

First-close mistakes that turn into audit findings

A lot of the first-close trouble that later shows up in audit letters traces back to five decisions made around go-live. None of them is a software problem.

Releasing support at go-live

The implementation contract ends, the consultants leave, and the first close starts the following month with nobody who knows why a posting rule was configured the way it was. Keep at least one senior functional resource, yours or a third party's, committed through the first two closes and the first payroll quarter.

Letting the prior period linger

A period left open "just in case" becomes a place where corrections pile up with no review. Stamford's FY23 Period 13, still open in October 2024, is what that looks like on a committee agenda. Set a hard-close date for every period, including the last legacy period, and hold it.

Temporary workarounds that become permanent

Every first close has a spreadsheet somebody built because a report wasn't ready. Six months later that spreadsheet is a control nobody designed, and nobody tests. Keep a workaround log with an owner and a retirement date for each entry, and review it at every close.

Nobody owns the government's side

The vendor answers for its software and the integrator answers for its statement of work, but neither answers for whether the city's books are right. In a lot of projects, that falls to a finance director who's already doing two jobs. Name that owner in writing before go-live.

Letting reconciliations slide into audit season

A late reconciliation in month one becomes a late year-end, which becomes a late audit. Late audits carry real costs. In Santa Fe, New Mexico, a string of late audits put the city's access to new state capital outlay grant agreements at risk.

Your first year-end close on a new ERP (and the ACFR)

Your first fiscal year-end on a new ERP is the first close an outside auditor will test in depth, so plan for it the day you finish close #1. Your controller reviews month-end. At year-end, an outside firm gets to ask the questions.

A few things are different at year-end:

• The auditor will ask about the conversion. Expect questions on how balances were migrated, who reviewed them, and what controls existed during cutover. That conversion evidence file from Step 1 becomes audit support.
• Period 13 adjustments land in a new system. Audit adjustments, accrual true-ups, and GASB conversion entries all need a home, and the people posting them need to know the period structure.
• The ACFR has to come out of the system. If your fund structure doesn't map cleanly to the statements, year-end turns into weeks of spreadsheet reconstruction. Mapping the fund structure to the ACFR is something KCT designs for before go-live, not after an audit finding.
• Mid-year go-lives mean mixed history. Part of the year sits in legacy, part in the new system. Decide early how you'll produce full-year reports, and test it before June 30 (or whenever your year ends).

Invite your audit firm to a walkthrough of the new system and the conversion evidence a couple of months before fiscal year-end. If they're going to push back on how something was converted, you want to hear it while there's still time to fix it before year-end.

What "good" looks like by close #3

By your third close on the new ERP, you're looking for direction more than speed. Is each close a little shorter and cleaner than the one before? One rough close doesn't say much, but three in a row will.

I'd track these:

• Close duration. Business days from month-end to hard close, trending down each month toward your pre-go-live number.
• Aged reconciling items. Anything older than 30 days gets a name and a date.
• Workaround count. The log should be getting shorter, not longer.
• Interface corrections. Manual reclassifications of interface postings should be close to zero.
• Council report timing. Back on its normal schedule.

Automation is where the bigger gains come from later. Ventana Research found that 88% of organizations automating all or most of their close finish the quarterly close within six business days, compared with 40% of those using little or no automation. Recurring entries, auto-reconciliation rules, and scheduled reports you didn't have time to set up before go-live belong on the list now.

If close #3 still looks like close #1, stop and find out why. It usually traces back to a posting rule nobody fixed or a reconciliation that still lives in someone's personal spreadsheet. Ongoing month-end and year-end close support is one way to keep that from becoming the new normal.

FAQs

The close is the finish line

A new ERP is done when your team can close a month in it without the consultants on the phone, and your auditor can follow the trail from the old system to the new one.

To survive the financial close on a new ERP, start planning your first close the same week you set your go-live date. That's when you can still change the contract's acceptance terms and line up backfill for your accounting staff. If you want a wider view of how public-sector ERP projects tend to go, [LINK: KCT government ERP statistics post] and the [LINK: Public-Sector ERP Readiness Workbook] are good next reads.

If your go-live is coming up, or you're already live and the first close won't reconcile, KCT can help. Senior, vendor-neutral operators run the cutover and stay through your first fiscal close, or step in to stabilize a close that's gone sideways. Book a 30-minute discovery call to walk through where things stand.