Inconsistency in Tax-reporting

The disadvantage of using a linked Supplier/Customer to determine if a tax code applies to the Sales or Purchase component is:

  • A Manager user must enable the “Customer” and “Supplier” tabs and at least create a dummy customer and supplier before they can specify if a Journal entry or Receipt/Payment is a sale or purchase.

  • When a selecting a Customer/Supplier, the user would need to select a contact from a database combining all customers and all suppliers (a longer list). The combined database would need to show which entries are for customers and which are for suppliers (as an entity can be both a supplier and customer of a business). In practice a Manager user will know if they are looking for a customer or supplier entry so specifying this first may make data entry more efficient.

  • Correction of this thread’s topic “Inconsistency in Tax-reporting” must wait until Improvement to payment and receipt forms is implemented, which is probably a larger task.

  • An alternative would be to add a drop down Sale/Purchase to journal entries (at what ever level was thought to be optimal). For Receipts/Payments, instead of using line item credit/debit status to determine line item Sale/Purchase; a transaction level Sale/Purchase drop down could be added or use the existing Receipt/Payment drop down. A change which would only effect the “Tax Summary” Report and only for negative Receipt/Payment line items. In both cases these changes would only be an incremental improvement in Managers functionality if they corresponded to the vision of where Manager is going, something I’m not privy to.