How to Create Opening Balances in the G/L in Business Central

Let’s Be Honest — Even Experts Need a Cheat Sheet Sometimes

I was recently helping a client load their opening G/L balances in Microsoft Dynamics 365 Business Central — something I’ve done at least a hundred times. But halfway through, I caught myself second-guessing myself.

Wait… do we use ending balance or net change? Should that go in the description or the document number?

So I took a breath and thought: Let me write this up — once and for all.
Because whether you’re doing this for the first time or the fiftieth, it’s easy to forget the little things when you’re knee-deep in journal lines and dimension mappings.

This post is your go-to guide to keep your G/L openings clean, accurate, and audit-friendly — and to save Future You from hours of head-scratching.

---

Why Opening G/L Balances Matter

Your general ledger is the financial backbone of your Business Central environment. It’s the first major accounting step in your ERP go-live process. Get it right, and you have a solid foundation for everything else — subledgers, reporting, budgeting, and compliance.

Get it wrong… and you’ll be chasing reconciliation differences for weeks.

---

Summary G/L Balances vs. Detailed History

Once your go-live date is set, the next question is: how much detail do you really need?

Option 1: Monthly Summary G/L Balances (Highly Recommended)

This is the cleanest, simplest way to migrate your G/L. You bring in monthly net change journal entries for each account, for 2–3 prior fiscal years.

Why it works:

• Keeps your new chart of accounts clean
• Supports year-over-year comparison reporting
• Avoids dragging in obsolete or inactive accounts
• Saves time, effort, and consulting dollars
• Easy to reconcile and explain later

One journal entry per month. Balance it. Post it. Move on. Trust us — your auditors will thank you.

Option 2: Full Transactional History

Yes, it’s technically possible to bring in all historical entries, but unless your audit committee specifically asked for it… don’t.

Why it’s risky:

• Requires significantly more mapping and validation
• Often means reactivating accounts you intentionally left behind
• Requires a lot more reconciliation and therefore time
• Costs more — sometimes a lot more

Best Practice: Bring in monthly net change entries for 2–3 prior years and keep the legacy system available as a read-only archive if needed.

---

How Many Years Should You Bring?

Let your business needs guide you:

Question	Recommendation
Do you need comparative reports in Business Central?	Bring 2–3 years of monthly summaries
Do your auditors expect prior-year balances?	Bring at least one full fiscal year
Is your legacy system still accessible post-go-live?	Keep it light — YTD and one prior year
Has your company changed significantly?	Only bring in periods that are still relevant
Would anyone actually use the older data?	Be honest. If not, skip it.

Best Practice: Stick with monthly net-change entries for 2–3 years. Enough to support reporting — not so much that it clutters your clean start.

---

Step-by-Step: Loading Opening G/L Balances in Business Central

---

1. Start with a Mapping File

Before you touch Business Central, build a spreadsheet that maps:

• Your old G/L accounts
• To your new Business Central accounts
• With appropriate dimensions (e.g., department, project, business unit)

Business Central relies heavily on dimensions, and it’s likely your chart of accounts structure has changed during implementation. Mapping helps you:

• Post accurately to the right accounts
• Avoid recreating unnecessary legacy codes
• Make your trial balance actually make sense when you’re done

Think of this as your accounting GPS — skip it, and you’re going to get lost.

---

2. Prepare Monthly Net Change Trial Balances

From your legacy system, export monthly trial balances for each year you’re bringing in (e.g., Jan 2022–Dec 2024).

For each month:

• Calculate the net change (not ending balance) for each G/L account
• Confirm that each journal entry balances to zero
• Prepare separate journal lines for each account per month

Don’t post cumulative balances. Business Central calculates running totals — posting an ending balance each month will stack values incorrectly.

---

3. Use a Configuration Package + Text Codes (Your Secret Weapon)

Skip the manual entry. Use configuration packages to load your journal entries — and Business Central’s text codes to auto-generate Document Nos. and Descriptions.

Example Fields to Populate:

Field	Example
Document No.	BEGBAL-%5 → BEGBAL-JAN-24
Posting Date	01/31/2024
Account Type	G/L Account
Account No.	10200
Amount	5000
Description	Opening Balance – %5→ Opening Balance – Jan 2024
Dimensions	DEPARTMENT = SALES

---

Common Business Central Text Codes:

Code	Meaning	Example
%1	Day number	31
%2	Week number	05
%3	Month number	01
%4	Month name	January
%5	Accounting period name	JAN-24

We’ll cover even more advanced text code strategies in an upcoming post. Stay tuned.

---

4. Import, Validate, and Post

• Import one month’s journal at a time using your config package
• Validate for missing dimensions, invalid accounts, or formatting errors
• Post monthly journals in order — oldest to newest
• Make sure every entry balances before moving forward

---

5. Run Trial Balance Reports and Archive Them

After all entries are posted:

• Run the Trial Balance report in Business Central for each fiscal year
• Compare to legacy reports to confirm accuracy
• Save PDF copies as part of your cutover documentation

Your auditors will appreciate it. So will Future You when questions come up in 6 months.

---

Final Thoughts

Opening balances may not be the flashiest part of your ERP project — but they’re one of the most important.

• Map your accounts and dimensions
• Use monthly net-change entries
• Leverage config packages and text codes
• Post with confidence
• Document it all for the audit trail

Get it right once, and you’ll never have to second-guess it again.

Wrapping Up

Getting your G/L opening balances right in Business Central isn’t flashy, but it’s one of the most critical setup steps for a smooth go-live. Take your time. Reconcile everything. And test before you post.

Want more smart, battle-tested Business Central tips?
Subscribe to Dynamics Power Play – the no-BS blog for consultants, controllers, and anyone building a better ERP experience.