In the latest version (21.6.78) it is now possible to set division on transaction level when making entries to custom balance sheet accounts.
When you edit custom balance sheet account
And division is selected, then all transactions in this account will belong to the selected division.
And division field on transaction-level will be disabled.
However if Division is not set on custom balance sheet account level, then you will be able to select division on transaction-level
This new functionality works well, however is it possible to also provide this type of functionality for Suppliers, Customers, Expense payers, etc.
Often one supplier, customer, etc will have dealings across more than one division and the only way to account for this, currently, is by having 2 instances of the supplier, customer, etc.
A field could be placed in the transaction header next to selection of the client for those suppliers, customers, etc that do not have a division set. e.g.
You are suggesting having contacts which interact with Manager in more than one way.
For example “John Smith”
could interact with Manager business division “A”, “B”, or “C”. Reports for John Smith overall and probably specific dealings with division “A”, “B”, or “C” maybe reasonably requested. Ideally Manager would only request clarification of which division when it was ambiguous.
the program requirements are similar to John Smith interaction with Manager as a customer, supplier employee and expense claim payer. So while I can see value in supporting this, I suspect it is not as easy as it may appear.
To support this perhaps when creating a contact, which of several divisions the contact interacts with could be specified.
In the short term it maybe necessary to have a different contact for each division they interact with.
This was contained in my post:
I don’t see it this way. It would be easier to have all divisions available at transaction level, (if a division isn’t nominated in the client set up).
It has been done with custom balance sheet accounts I believe that it could be possible for contacts.
@AJD what problem are you trying to solve? Can we start with the report? How would this address your reporting requirements?
The following screen shot shows an overall AP balance of $127.34 all of which is shown in one division. It is 2 purchase invoices for the same supplier, 1 invoice for $27.34 which is correctly shown in the first division, but the 2nd invoice for $100.00 should be shown in the second division.
The only way to achieve this currently is to have a separate instance of the supplier set up for the second division.
Why is it important to split this supplier by division? If you say that it’s because so liabilities are properly reflected per division, they still are.
If supplier belongs to division A but the supplier invoice comes for expenses incurred by division B, what happens is that interdivisional loan will hold the balance for those expenses.
So division A will look like it owes $100 to supplier but at the same time it will show division B owes $100 to division A thus total liabilities of division A will be zero.
The reason why I do not support suppliers, customers, bank accounts, cash accounts etc. to have division set on transaction-level is because divisional ledger for these accounts would be meaningless.
If you are reconciling your account with supplier, the supplier will send you one statement for the account… not per division - they do not know how you split your transactions by division nor do they care as from their point of view - you have one account with them.
If you want them to send you statements per division, then you’d have two accounts with them - and you would create each account as separate supplier.
At the end of the day, Manager is to reflect what is really happening in real world. In real world, this supplier is one account.
Absolutely, this was not for supplier reference at all.
I mistakenly thought that the interdivisional loan was only for bank account adjustments, but now I see that it applies to clients (AP, AR, etc).
The comment I would make is that the interdivisional loan will become very unweildy and difficult to fathom in a full year report.
I agree. The figure will be clickable and you will be able to drill-down into which division owes which one and why.
Interdivisional loan comes into play when you have a transaction which spans across multiple divisions. The less such transactions you have, the less entries in interdivisional loan.
Thanks.
Yeah, after further testing I also now see that my suggestion would run into problems for multiple line invoices split across divisions.
This is a fantastic addition to Manager and whilst I haven’t read all the threads I would like to offer the following:-
My understanding is that is how it currently works
It works that way for custom Balance Sheet accounts, but not for P&L accounts.
This is what I’m trying to discourage. It’s hard to get side-by-side report by division when each division is using different set of accounts.
If you don’t need divisions, don’t create them. Then, they (and the field itself) will not appear. If you have divisions, you need the field to appear so you can select the correct division.
This should not have been done for P&L accounts, if that is what you are referring to. Previously, tracking codes should have been used; these would have been converted automatically to divisions.
No. All editions are the same except for multiple user capabilities in the server and cloud editions. There are no differences for divisions.
I have divisions created
I do not see division selection on any of the Balance Sheet Accounts. I have download 27.7.15 but still do not see the Division Selection when trying yo edit a Balance Sheet Account the Chart of Accounts?
Hi Lubos
Sorry to trouble you.
I have just worked out the error of my ways. I didn’t look beyond the Bank Accounts… which of course can only belong to one division. …Very dumb
Thanks for the consideration and intro of division code/tracking code at balance sheet account level
i think tracking code has been changed to Division Code. Following are the current statement of facts
If this could be consistent at txn level, you could draw down division/ tracking code level trial balance and balance sheet.
Please consider
