900
Official spec
No Header Information
What does KRA eTIMS error 900 mean?
The specification describes missing header information. The code alone does not identify which field is absent or where the interface expects it.
Raw control-unit codes differ from TaxID HTTP errors and transaction statuses. A code alone neither authorizes fiscal replay nor proves central KRA acceptance.
Resolution
Verify the headers, device identity and authentication fields required by the exact endpoint and runtime. Retain the HTTP status, resultCd and redacted resultMsg to distinguish a client-side validation error from a control-unit response.
Notes
OSCU v2.0 §3.3.2.1 lists cmcKey as required for code search, but the adjacent JSON sample omits it. That discrepancy does not establish that omitting the key returns 900, 901, 910 or 892. Earlier project notes associated 900 with an empty local VSCU cmcKey file; treat that as a reported runtime-specific observation, not a universal OSCU cause.
Related codes