0013·Sale type is empty or invalid
Product classificationCommon
What this means
The sale type field takes a specific descriptive string from FBR's vocabulary. It is not an identifier you choose — a system that stores sale types as short internal keys must translate them before submission.
Why it happens
- An internal enum value was submitted directly, for example a lowercase key rather than the full descriptive label.
- The label is close but not exact — wording, capitalisation, or a missing parenthetical qualifier.
- The field was omitted entirely on lines where the type seemed obvious.
- The sale type was left null on a draft that was then submitted without classification.
How to fix it
- 1Map every internal sale-type key to the exact FBR label and translate at the API boundary.
- 2Treat the label as opaque — do not normalise case or trim punctuation.
- 3Reject submission in your own validation when sale type is unset, rather than sending null and letting FBR catch it.
How Ordyoo handles this
Sale types are stored as internal keys for database sanity and mapped to FBR's exact labels in a single translation layer, so the label text lives in one place and cannot drift line by line.
Scenarios where this appears
Sandbox scenarios that commonly produce 0013.
Related errors
Stop debugging FBR payloads by hand
Ordyoo builds and submits compliant invoices so most of these rejections never reach you. Start free.