Comments
Moreover, lots of customers want to add indirect component costs due to logistic handling. Often, the weight is an entry point to manage this surcharge. Unfortunately, the Weight option in the Costing sheet refers to the net weight, although logistics cost are based on the gross weight, that can be very different than the net weight.
Currently, the code is locked and we cannot even add an extension, although it seems to be easy to add new options in the costing sheet framework.
The standard output unit based subtype list should definitively be extended.
This becomes very urgent. A belgian customer may have a VAT registration no in another country. Now BC applies a check based on the country/region code on the customer/vendor card and you have to enter a VAT Registration No or an Enterprise No (for belgian customer/vendor). To "solve" this, we have to create additional virtual country codes like BE (LU), BE (NL), etc...
If a belgian customer with country code "BE", we can only entry the enterprise no. field with a BE no. but if the customer has a VAT registration in the Netherlands or Luxembourg or France, impossible to enter a VAT registration no. This is a very big limitation and requires an urgent solution.
More customizability would be great in general, in addition to filters I'd like to change the details/information shown under each case in the inbox - this does not seem to honour the case card settings which other views do so the default pieces of information shown (priority, status, modified) are irrelevant for us.
To the administrator... what an idea to ask more votes. The non-deductible VAT is not applicable in all countries. I know this is applicable in IT and BE so only IT / BE partners will vote on this issue.
There are a lot of problems with the non-deductible VAT (eg post purchase invoice with non-deductible VAT on a job and check the job ledger entry => cost price is incorrect). I sent already multiple cases regarding the non-deductible VAT to Microsoft (see helpdesk tickets).
Of course the issue above is also a good one...