How are GIB status codes Must read?
The Revenue Administration status code shows the stage at which the e-Invoice envelope is from being placed in the queue to being completed in the receiving system. Not every code means a permanent error; In intermediate cases such as 1000, 1100, 1210 and 1220, the next status response should be waited instead of resending the envelope.
IOP status and error codes table
The table below shows common envelope situations with brief descriptions and the basic action that can be taken. Check the current envelope's current status and recipient label before making a reshipment decision.
| Code | Status | Description / possible why | Recommended action |
|---|---|---|---|
| 1000 | Envelope added to queue | Envelope placed in IOP processing queue. | Wait for the status to update; do not resend. |
| 1100 | Envelope being processed | IOP maintains technical checks on the envelope. | Wait until processing is completed; do not resend. |
| 1110 | Not a ZIP file | The sent package is not in the expected ZIP format. | Prepare the document as a valid ZIP package and resend. |
| 1111 | Invalid Envelope ID length | The envelope ID does not match the expected 32-character structure. | Correct the envelope ID and recreate the package. |
| 1120 | Failed to copy the envelope from the archive | A copy problem occurred while the package was being taken into the processing area. | Recreate the package; If the problem persists, check the integrator logs. |
| 1130 | Failed to open ZIP | The archive is corrupt, unreadable, or there is a temporary system problem. | Verify ZIP integrity, rebuild the package and send. |
| 1131 | ZIP must contain a file | No document to process was found inside the envelope. | Add the invoice, application response, or system response XML to the package. |
| 1132 | Not an data-bym-translation="43">Produce and resend the document in valid XML format. | Paket içindeki belge XML biçiminde değil. | Belgeyi geçerli XML biçiminde üretip yeniden gönderin. |
| 1133 | Envelope ID and XML file name are different | The envelope ID and the name of the XML file inside do not match. | Sync the ID and file name and send again. |
| 1140 | Failed to parse the document | The documents in the envelope could not be parsed for processing. | Verify the XML and package structure and regenerate the envelope. |
| 1141 | No envelope ID | The envelope does not have a document ID field. | Add the required envelope ID and resend. |
| 1142 | Envelope ID and ZIP file name are different | Envelope ID and ZIP file name do not match. | Match envelope ID and ZIP name. |
| 1143 | Invalid version | The document was produced with an unsupported envelope or document version. | Recreate with the current, supported version. |
| 1150 | Schematron check result is incorrect | The document does not meet at least one of the Revenue Administration business rules. | Correct the business rule in the error detail and resubmit. |
| 1160 | Failed XML schema check | XML structure does not comply with the relevant UBL-TR schema. | Validate the data-bym-translation="75">Check the certificate and signer ID and sign again. |
| 1161 | İmza sahibi TCKN/VKN alınamadı | İmza sertifikasındaki kimlik bilgisi okunamadı. | Sertifika ve imzalayan kimliğini kontrol edip yeniden imzalayın. |
| 1162 | Signature could not be saved | An error occurred while processing or saving the electronic signature. | Verify the signature, re-sign and send the document. |
| 1163 | The envelope contains a previously registered invoice | The same invoice ID or ETTN may have been previously registered in the system. | Do not resend; first query the envelope status of the current invoice. |
| 1170 | Authority could not be checked | Sender or recipient authority could not be verified. | Try again after checking the label and authorization information. |
| 1171 | No sender authority | Sender label may not be the sending unit label. | Use current GB label when shipping. |
| 1172 | No mailbox authorization | Recipient label mailbox may not have the tag. | Use the current PK tag for the recipient. |
| 1175 | Signing authority could not be checked | There was a problem verifying the signer's authority. | Check the certificate and authorization record and try again. |
| 1176 | Signer is unauthorized | The document was signed with a certificate that is not authorized for the transaction. | Re-sign and send with the authorized certificate. |
| 1177 | Invalid signature | The electronic signature of the document could not be verified. | Check signature integrity and re-sign the document. |
| 1180 | Failed to check address | Sender or recipient label address could not be verified. | Check the addresses from the current user and tag list. |
| 1181 | Address not found | Turkish ID number and tag information do not match or the tag is out of date. | Update and resend GB/PK labels with party information. |
| 1182 | Failed to add user | There was a technical or data-related problem creating the user record. | Verify the registration information; If the problem persists, open a support ticket. |
| 1183 | Could not delete the user | The operation could not be completed while removing the user record. | Check the current user status; open a support ticket if necessary. |
| 1190 | Failed to prepare system response | The system response could not be generated for the envelope. | Check the transaction logs and try regenerating the response. |
| 1195 | System error | A general technical error has occurred in the IOP or integration layer. | Monitor the situation; If the problem persists, contact the integrator or IOP support. |
| 1200 | The envelope was processed successfully | The envelope was processed successfully in the central system or at the recipient's side. | Do not resend; if necessary, wait for the next status response. |
| 1210 | The document could not be sent to the address | The document could not be delivered to the recipient address on the first attempt; retries are in progress. | Wait until GIB's retries are completed. |
| 1215 | Document sending failed | Resend attempts were completed but the document was sent to the recipient could not be delivered. | Resend the invoice after verifying the latest status. |
| 1220 | No system response from the target | The document has been received by the recipient, but no positive or negative system response has been received. | Do not resend; contact the recipient and wait for status 1230 or 1300. |
| 1230 | Failed system response from the destination | The receiving system reported that it could not process the envelope. | Correct the error in the response and resend after a final status check. |
| 1300 | Completed successfully | The envelope process completed successfully. | No action required; Do not resend the same invoice. |
Check before resending
Record the envelope ID, invoice number, ETTN, shipping time and recipient GB/PK label together. Especially in cases 1163 and 1220, uncontrolled resubmission can lead to the risk of duplicate documents; Based on the last response on the integrator screen.
Bu içerik genel bilgilendirme amaçlıdır. Mevzuat ve teknik sürüm bilgileri uygulama öncesinde resmi, güncel kaynaklardan doğrulanmalıdır.