0090·Fixed notified value or retail price is required
Product classificationCommon
What this means
For sale types taxed on notified or printed prices, the retail price field is the taxable base. FBR cannot validate the line without it, so an empty or zero value is rejected outright — a distinct failure from submitting a value that produces the wrong tax.
Why it happens
- The item was classified as Third Schedule but no MRP was recorded against it.
- MRP exists on the supplier's record but was not inherited into the distributor's catalogue.
- The field was populated only when it seemed relevant, and defaulted to zero otherwise.
- MRP was stored as a display string and failed to parse into a number.
How to fix it
- 1Make MRP mandatory in your own data model for any item classified under a notified-price sale type.
- 2Block invoice finalisation when a Third Schedule line has no retail price, rather than submitting a zero.
- 3Remember the field is a line total — MRP multiplied by quantity.
How Ordyoo handles this
Third Schedule items always inherit MRP from the supplier's registration, with no editable override at distributor level. That prevents a stale local MRP from silently diverging from the price the manufacturer printed on the pack.
Scenarios where this appears
Sandbox scenarios that commonly produce 0090.
Related errors
Stop debugging FBR payloads by hand
Ordyoo builds and submits compliant invoices so most of these rejections never reach you. Start free.
