The customer needs purchase orders (POs) to display part pricing based on the pre-tax amount rather than the price including tax. Currently, when adding a part to a PO, the system automatically pulls the price, including tax. This issue arose after a previous change where the system was updated to use the last PO price for parts. While including tax may be acceptable in general stock pricing, it is not appropriate for POs.
Current Limitations
- Incorrect Pricing on POs: The system is pulling tax-inclusive prices into POs instead of pre-tax values.
- Regression from Previous Fix: The behavior began after a prior enhancement that updated part pricing logic.
- Mismatch with Business Needs: Customers need tax to be applied at the PO level, not baked into individual part prices.
General Example
A user creates a PO and adds a part. Instead of showing the pre-tax cost, the PO reflects the total including tax, from the last order. This inflates the part price on the PO and creates confusion in financial records, since tax should only appear in the designated tax field of the PO.
Requested Enhancements
- Pre-Tax Pricing on POs
Ensure that POs always display part prices as pre-tax amounts, regardless of how prices are stored in general stock. - Separate GS and PO Price Handling
Allow general stock to retain tax-inclusive pricing if desired, while POs consistently use pre-tax values. - Validation for Consistency
Add logic to prevent tax-inclusive prices from populating into POs, reducing the risk of overpaying or misreporting.
Business Value
- Accuracy: Ensures POs reflect the correct pre-tax values, aligning with accounting and procurement standards.
- Compliance: Keeps tax handling consistent with financial reporting requirements.
- Clarity: Reduces confusion for staff and prevents errors when reconciling costs.
- Trust: Builds confidence that Limble’s PO system is reliable and aligned with business practices.
