-
Allow Deactivation of Sales Order and Purchase Order deletion on complete
It should be an option to NOT delete Purchase Orders and Sales Orders when these documents have been completely shipped/received and invoiced. So much information and related data links are lost in the archive then it would be much preferable if they remained in the main Sales Order or Purchase Order list page with a status of "Complete" or similar.
The current process of pushing to the Archive and then deleting is unwelcome - the Archive becomes a hybrid of version control and audit trail and is pretty impossible to use for any meaningful purpose - e.g. there is no way to extract "last version" of each document. For the majority of customers the database overhead of having these in the main enquiry is negligible. They would then have the option to delete them (using the existing report jobs) after a time period of their choosing.
I know that this behavioud can be modified out of the software but we should be making these easy toggles available as standard
-
Add field length to Configuration Package Excel Export
Add field length to Configuration Package UI and also Excel export. This will help clients fill the templates properly as they'll know how many characters they have to work with in each field,.
-
MTD should be able to handle Company Information VAT Registration No. prefixed with GB
MTD module errors with "the provided Vrn is invalid" if the VAT Registration No. in Company information is prefixed with the Country code. Prefix with GB is good practice for multi national companies and the MTD program logic should really be able to handle either GBnnnnnnnnn on Company Information - hidden logic can detect and strip the GB off if need be. This is frustrating for clients as it means they have to choose between MTD working v Customer Facing Documentation showing the GB v hard coded documentation layout modification to insert the GB.
Realise not a catastrophic problem but really a niggle the client shouldn't have to deal with.
-
Customer/Vendor Document Layouts should not need ReportID
When adding Document Layouts to Customers and Vendors the user is forced to specify the ReportID. Yes this can be copied from the Report selections but this Object ID reference is confusing for the users. In most cases there is only a single report layout id for a company and this is specified as the default on Report Selections. It would be good if the Document Layouts screen allowed the user to leave the ReportID as zero in which case the system would revert to the Report selections to retrieve the reportID it needs. This also makes it easier that if the company default design is changed then a single update to Report Selections impacts all "Normal" customer/vendors rather than having to update all the individual Document Layout records.
-
Deferral from PO should be picked up by Get Receipt Lines
If user adds deferral template to Purchase Order line but then amends deferral schedule to change start date and/or value split, these changes are not picked up on a purchase invoice created using Get Receipt Lines. PO deferral schedule detail should be picked up to ensure schedule dates are respected. Any difference in value between PI and PO (part receipt or price change) could be resolved by calculating necessary ratio for each deferral schedule line as per PO values.
-
Add ability to re-sequence Sales Order/Posted Sales Invoice lines
Sometimes a Sales order can be created/part shipped and the sequence of line items on the order may result in a Sales Invoice that looks a bit unprofessional. For example, if a Sales Order was for 5 different server chassis, 5 sets of memory modules, 5 sets of software licenses and 5 power cords then it could be entered by the user in that sequence. When shipping and invoicing the user might want to see the "assemblies" listed together so the invoice reads as Chassis, Memory, License, Power, Chassis, memory, License, Power..
Provide the ability to input a Print Sequence number on Quote, Order and Posted Invoice lines allowing the documentation to use this table key.