Each application response contains one Sovos response code and several status reason codes that provide document status and help determine when further action is required.

The following response code and status reason codes can appear in the application response:

A sample application response shows how status codes appear together in a single XML response.

<ApplicationResponse>
  <cac:DocumentResponse>
    <cac:Response>
      <!-- PRIMARY: Overall status -->
      <cbc:ResponseCode listID="SCIResponseCode">AP</cbc:ResponseCode>
      
      <!-- DETAILED: Sovos processing status -->
      <cac:Status>
        <cbc:StatusReasonCode listID="SCICloudStatusCode">200</cbc:StatusReasonCode>
        <cbc:StatusReason>Authorized by the tax authority</cbc:StatusReason>
      </cac:Status>
      
      <!-- TAX AUTHORITY: Government response -->
      <cac:Status>
        <cbc:StatusReasonCode listID="SCIGovtStatusCode">S100</cbc:StatusReasonCode>
        <cbc:StatusReason>Invoice authorized. Number: 278754</cbc:StatusReason>
        <cbc:SequenceID>278754</cbc:SequenceID>
      </cac:Status>
      
      <!-- ACTION: What to do -->
      <cac:Status>
        <cbc:StatusReasonCode listID="SCIStatusAction">NOA</cbc:StatusReasonCode>
        <cbc:StatusReason>No action required</cbc:StatusReason>
      </cac:Status>
    </cac:Response>
  </cac:DocumentResponse>
</ApplicationResponse>

You receive all of these status codes in a single response. Check them in order to understand the complete status.

Status codes work together to tell the complete story of your document's processing status.

Application responses for authorized and completed documents typically include attachments such as cleared invoices and PDF renderings.

Application responses for status 200 (document.authorized) and 209 (workflow complete) typically include the following document attachments:

• LegalCleared - Country-specific format with tax authority clearance metadata.
• PDF - PDF rendering (if configured).

These attachments provide the cleared invoice and proof of authorization.

You may receive multiple notifications for a single document as it progresses through processing stages. Each notification represents an event or milestone.

Use documentId to correlate notifications.

Processing order

Use timestamps to process in chronological order. Notifications may arrive out of sequence. Use the createdAt timestamp to order notifications chronologically and track progression.

Track progression using SCICloudStatusCode:

• 100 > 101 > 104 > 105 > 200 (successful authorization)
• 100 > 101 > 400 (rejected)

Implement idempotent processing. Each notification has a unique notificationId. Track which notifications you have processed to avoid duplicate handling.

Determining final document status

The most important status element is the SCIResponseCode. A document is complete when you receive one of the final SCI response codes (AP, RE, or CA).

When you have multiple notifications, apply the following status code priority for final determination:

1. Highest priority: document.cancelled (201) — If a document was authorized then cancelled, the cancellation takes precedence.
2. Next: document.authorized (200) — Authorization status indicates tax authority approval.
3. Then: Rejection codes (400-404) — If no authorization or cancellation, check for rejection status.
4. Finally: In Process (IP) — If none of the previous conditions apply, the document is still processing.

Not all status code combinations are valid. Understanding which combinations can occur helps you implement correct response handling logic.

Valid combinations

SCICloudStatusCode	SCIResponseCode	Scenario
100-105	IP	Processing stages
200	AP or CA	Authorization (standard or conditional)
201	AP	Cancellation successful
202	RE	Use denied
207	AP	PDF created
208	AB	Archived
209	AP	Workflow completed (check other status codes for outcome)
400	RE	Rejected
401	RE	Processing error
500-504	RE	System or network errors

Invalid combinations

If you observe any of the following combinations, it indicates a problem that you should report to Sovos:

SCICloudStatusCode	SCIResponseCode	Why invalid
200	RE	Authorization cannot be rejected.
400	AP	Rejection cannot be accepted.
201	RE	Cancellation cannot be rejected.

If you see invalid combinations in your application responses, flag them as problems. This helps Sovos identify and fix system problems.

SCIResponseCode is a two-letter response code that provides the overall compliance status of a document.

Terminal codes (AP, RE, CA) indicate final status. Non-terminal codes (IP, AB, UQ) mean continue polling.

The following table provides the complete reference for all status codes across all markets. Only a subset of these status codes are used in each country or region. Your country-specific implementation guide covers which status codes apply to your market.

SCIStatusAction is a three-letter status code that identifies any additional required action.