web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

COA. some has 6 digits and some have 10 digits. Seeking for best practice.

(1) ShareShare
ReportReport
Posted on by
Hi All, 
I have COA that looks like this:
 

 
Many accounts share the same first 6 digits, but the last 4digits are different. These final 4 digits distinguish one account from another within their main account type (assets, liabilities, or owner's equity). Since the dots between the digits could cause parsing issues combinations of accounts and dimensions, I am considering removing the dots, resulting in a format with 10 digits instead of 6. Any GL account that has 6 accounts, I'm thinking to add 4 zeros to follow them. Currently, about 60% of the chart of accounts (COA) has 6 digit numbers, while 40% of them has 10 digits including the 2 dots between them. 
 
'

What do you consider best practice for managing this COA? Do you see any issues with my approach? 
D365 supports up to 20 digits.  Thanks so much for your feedback!
 
 
 
Categories:
I have the same question (0)
  • Verified answer
    Syed Haris Shah Profile Picture
    1,666 Super User 2026 Season 1 on at
     
    I recommend keeping the COA simple, clean, and aligned to financial statements by using clear numeric ranges for main accounts, for example:
    • 100000–199999 Assets (Cash, AR, Inventory, Fixed Assets, etc.)
    • 200000–299999 Liabilities (AP, Accruals, Debt, etc.)
    • 300000–399999 Equity
    • 400000–499999 Revenue
    • 500000–599999 COGS
    • 600000–699999 Operating Expenses
    • 700000–799999 Other Income/Expense
    The main account should represent the nature of the account (e.g., Salaries, Rent, Cash).
    Organizational or functional views (Sales, Finance, Location, Business Unit, etc.) should be handled through financial dimensions, not by creating separate main accounts like “Salaries – Sales” and “Salaries – Finance”.
     
    If you decide to continue with a dotted COA structure, then it is important to:
    • Review accounts where segments are missing numbers after the dot,
    • Make them consistent in length/format (e.g., 10 digits total or a consistent segment structure), and
    • Ensure each account is placed within the correct account range that matches its account category (Assets, Liabilities, Revenue, etc.).
     
    While D365 can technically support dotted account numbers, in practice they often cause integration and data handling issues (e.g., Excel, ETL tools, middleware treating “.” as a decimal or separator). For long-term stability, reporting consistency, and easier integrations, it is better to use simple numeric main accounts (e.g., 6 digits) and rely on dimensions for additional detail.
     
    If you find this answer helpful, please consider verifying the answer. 👍
     
    Regards,
    Syed Haris Shah
     
  • André Arnaud de Calavon Profile Picture
    304,708 Super User 2026 Season 1 on at
    Hi,
     
    If you are using a CoA with variable length of the main accounts or not, doesn't really matter. I have seen all variations. 
    Syed had a valid point about the use of dots and Excel. For that reason, you might remove them. 
    Also note that there is a setting for the CoA and dimension delimiter on the General ledger parameters. This is used in a segmented entry control where you can specify main accounts and dimension values in one field. The delimiter should be different from the dot if you keep using it in the main accounts.
  • CU23091914-1 Profile Picture
    on at
    Thanks, Andre', for your respond.  In their legacy system, they used dots to distinguish different cash accounts or different inventory accounts but the first 6 digits are the same.  Now moving to D365, the dots may create a problem as it indicate as financial dimensions; therefore, I don't want to continue the dots. 
    I'm seeking for best practice to prevent future's problems
     
  • CU23091914-1 Profile Picture
    on at
    Thanks, , for your respond.
  • Suggested answer
    Giorgio Bonacorsi Profile Picture
    2,746 on at
    Hello,

    Usually, implementation is the perfect time to clean up the Chart of Accounts.
    You can consult an accounting expert to determine the best accounts to include and how to structure the CoA based on our business needs.

    From a D365FO perspective, the main best practices are:
    - The system treats the account ID as text and sorts it alphabetically. Therefore, it is standard practice to assign beginning numbers according to the structure (example=1xxx = Balance Sheet – Assets, 2xxx = Balance Sheet – Liabilities, etc.).
    - Keep the same number of digits for all accounts.
     
    Thank you,
    Giorgio
     
     
     
  • CU23091914-1 Profile Picture
    on at
    Hi All, 
    Finally, I wanted to ensure if the 10 digits in length will cause any data issues because I normally see 4-6 digits. I don't see the company will create many new COA in the future.  What are the possible issues of having 10 digits COA in terms of over consumption of storage?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 593 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 543

#3
CP04-islander Profile Picture

CP04-islander 430

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans