← All error codes Developer FAQ

KRA eTIMS integration FAQ

TaxID integration contracts and control-unit evidence.

What does TaxID provide?

TaxID connects fiscal operations to partners’ existing invoicing, accounting, POS and ERP software. Its API retains source references, branch-scoped results and evidence for safe recovery. Current invited access is simulated; production access requires separate KRA and operational acceptance.

How do application requests authenticate?

Use the assigned branch API key on your server with Authorization: Bearer. Configure the exact TaxID API origin. Workspace invitations authenticate browser access and are separate from application keys. Never embed keys in browser code.

Is resultCd the TaxID receipt status?

No. resultCd belongs to the underlying KRA endpoint. TaxID returns HTTP errors and transaction statuses such as SIGNED and OUTCOME_UNKNOWN. Inspect the contract for the API you called; HTTP 200 alone does not establish signing.

Does SIGNED mean KRA accepted the invoice centrally?

SIGNED means TaxID persisted a control-unit receipt. It does not independently establish central KRA acceptance. SIMULATED responses issue no fiscal invoice and make no KRA submission.

How should an application handle a timeout?

Keep the original clientReference, idempotency key and exact submitted body. Retrieve GET /v2/etims/sales/search?clientReference= with the URL-encoded reference. OUTCOME_UNKNOWN or RECONCILIATION_REQUIRED requires operator investigation. Do not generate a replacement reference or blindly resubmit.

Does a duplicate result recover the original receipt?

No. A duplicate code does not provide the original signature or prove that identical contents were signed. Investigate the original transaction and retained receipt evidence. Counters alone are insufficient.

Does VSCU signing require a second saveInvoice call?

The implemented TaxID VSCU signing flow calls /trnsSales/saveSales. The cited VSCU v2.0 specification documents that sale endpoint. The wording of codes 921 and 922 does not establish an additional saveInvoice API contract.

How should an operator handle initialization code 902?

902 is the documented installed-device condition. For OSCU, verify matching identity and an issued or retained communication key; for VSCU, verify retained device state and the application checkpoint. Missing state or credentials require operator/KRA recovery. The code alone proves neither recovered credentials nor transaction readiness.

Where do tax rates and unit codes come from?

Use the endpoint’s current reference data and merchant tax classification. Packaging-unit and quantity-unit code tables differ. Historical specification samples and SDK defaults are not current tax advice.

Data sourced from KRA OSCU Specification v2.0 §4.18 and retained sandbox observations and separately labelled reports. Add a missing question.