Architecture sanity-check — 55-account CoA + 2-segment sub-account key for a single-entity distribution/light-manufacturing build. Anything obviously missing before we lock the segment layout?

Hello,

It’s most helpful to see a Chart of Accounts that I’m reviewing.  I recommend that your Acumatica Partner and your CPA, who are familiar with your business, review details of your Chart of Accounts and provide the most meaningful feedback.

Most Charts of Accounts that I’ve reviewed are American; if there are different Canadian rules, I don’t know them.

That said, 

1. 55 accounts seems extremely small.  Acumatica has no limit on COA size.   
   • Consider making the 55 accounts your Account Classes for easy summary reports
   • Create 2 sets of Financial reports; the Summary version will not expand the Account Classes and the Detail version will expand the Account Classes by GL Account.
2. Have Acumatica-required accounts like PO Accrual, Landed Cost Accrual, Cash in Transit, Inventory in Transit, Gain/Loss on Currency, etc. been included?
3. Avoid this situation:  “with a handful of accounts carrying their own list”.  Where a subaccount only pertains to a specific account…. use separate Accounts, not subaccounts. 
4. Loans to related parties could be tracked in Accounts Payable and can be reported separately in both AP Aging and GL when you give them a separate AP account.  (‘Due to Related Parties’, for example.)

I hope this helps you.

Really appreciate the detailed read, Laura — a few quick responses:

On the required-accounts check: good prompt to double-check, and it turns out we're already covered on that list — PO Accrual, Landed Cost Accrual (confirmed required under our costing method), Cash in Transit, and a realized/unrealized FX split are all in the 55. Inventory in Transit is the one we deliberately left out — single warehouse, no inter-location transfers, so there's nothing for it to track. The original post just gave the category breakdown rather than the full account list, so that's on us for not being clearer.

On chart size / Account Classes: appreciate the reporting-layer idea. We went the other way deliberately — using the sub-account key to carry the granularity instead of expanding the GL, with Generic Inquiries doing the reporting cut. Different philosophy, but a considered one rather than an oversight.

On the related-party loan — that's genuinely the part we went back and forth on longest. We landed on sub-account detail under the liability account rather than AP, mainly because the AP route seems to force a fabricated purchase document for a balance that isn't a real trade payable, and it still shows up in AP aging either way regardless of which account carries it. Curious if you've seen a shop actually run the AP route cleanly in practice, or if that AP-aging pollution is just accepted as a cost of doing it that way.

Thanks again for taking the time — genuinely useful to get an outside set of eyes on this before it locks in.

Hello,

AP Aging can be modified to add AP Account Parameter - that’s how we exclude some Payables detail (non-trade).