KRA eTIMS error codes
TaxID embeds fiscal operations in existing invoicing, POS and ERP software. This reference covers raw control-unit codes, not TaxID transaction statuses. A signed receipt does not establish central KRA acceptance.
OSCU/VSCU resultCd reference, including reported codes outside the cited KRA specification.
Multiple success-code variants exist
KRA returns
"000" (OSCU spec §4.18, also confirmed live from the VSDC 2.0.6 JAR), "0000" (observed live from GavaConnect), and "00" has been reported for the VSCU JAR. Never hardcode a single string. Always check membership in {"0", "00", "000", "0000"}.
/
000
Success
Official spec
Documented success code.
00
Success (Reported VSCU JAR Variant)
Reported
Reported VSCU success variant; not confirmed by the retained VSDC 2.0.6 campaign.
0000
Success (GavaConnect Variant)
Reported
Reported GavaConnect success variant; not the documented VSCU success code.
001
No Search Result
Official spec
No matching search results.
891
URL Construction Error
Client-side
Request URL construction error.
892
Header Construction Error
Client-side
The specification describes an error while creating request header data.
893
Request Body Serialization Error
Client-side
The SCU library could not serialize the request payload.
894
Server Communication Error
Client-side
Communication with the server failed.
895
Unallowed Request Method
Client-side
The wrong HTTP verb was used for this endpoint.
896
Request Status Error
Client-side
Request status error.
899
Client Catch-All
Client-side
Generic client error; the code alone does not identify the cause.
900
No Header Information
Official spec
The specification describes missing header information.
901
Not a Valid Device
Official spec
The device is not valid for this environment.
902
Device Already Installed
Official spec
Documented installed-device condition (OSCU v2.0 §4.18; VSCU v2.0 §4.14).
903
Device Type Mismatch
Official spec
The device type does not match the verification path.
905
Only OSCU Device Can Be Verified
Reported
Reported device-type mismatch outside the cited v2.0 response-code table.
910
Request Parameter Error
Official spec
Request parameter validation failed.
911
Empty Request Body
Official spec
Request body is missing.
912
Request Method Error
Official spec
Request method error.
913
Code Value Error Among Request Parameters
Observed
Code-value validation failed.
921
Sales Data Rejected
Official spec
Declared sales or invoice data could not be received.
922
Sales Data Sequence Error
Official spec
The response-code table describes invoice data received before sales data.
990
Rate Limit Exceeded
Official spec
Request limit exceeded.
991
Error During Registration
Official spec
Registration failed.
992
Error During Modification
Official spec
Modification failed.
993
Error During Deletion
Official spec
Deletion failed.
994
Duplicate Record
Official spec
Duplicate data was reported.
995
No Downloaded File
Official spec
File retrieval failure in document or notice flows.
999
Unknown Error
Official spec
Unclassified server error.
E04
Device / Branch Not Found
Reported
Reported device or branch lookup failure outside the cited v2.0 response-code table.
E11
VSCU Memory Full
Reported
Reported runtime capacity failure outside the cited v2.0 response-code table.
No matching codes found. Open an issue to add this code.
Data sourced from KRA OSCU Specification v2.0 §4.18 and retained sandbox observations and separately labelled reports.