Skip to main content
Version: 2025-12-18

How to reconcile respondents for invoice adjustments

This guide explains how to submit respondent IDs to Cint for reconciliation, allowing you to remove poor-quality target group completes from your invoicing.

After a target groups's completion, you may identify respondents whose answers are of poor quality (e.g., fraudulent, inconsistent, or nonsensical). By reconciling these respondents, you can ensure they are not included in your invoice. Additionally, your reconciliation data helps Cint to continuously improve supplier quality and enhance automated security tools across the exchange.

Prerequisites:

  • You have access to the Cint API.
  • You've completed a target group and identified specific respondent IDs (RIDs) that you want to reconcile because of poor quality.
    • You can generate a report to get a CSV file containing all RIDs available for reconciliation.
  • You've reviewed and understood Cint's reconciliation policy.
  • You have the necessary roles assigned to your client.

Steps to reconcile respondents for one or more target groups​

1. Prepare your reconciliation CSV file​

First, you'll need to organize the respondent IDs and their corresponding reason codes into a CSV format.

Example of a reconciliation file: In this example, the first two RIDs are being positively reconciled (code 11), while the third is being negatively reconciled (code 932).

note

What is positive vs. negative reconciliation?

You'll use different reason codes depending on your goal:

  • Negative reconciliation: Use this to remove a poor-quality complete from your invoice. This is the most common scenario.
  • Positive reconciliation: Use this to convert a respondent with a terminated status to a complete status. This is useful if a respondent was incorrectly screened out.

In the example below, we reconcile three RIDs. We positively reconcile two RIDs (convert them from a terminated status to a complete status so they are counted towards the total quota in a target group), while the last RID has a reason code to terminate the RID (this removes the RID from counting towards the total quota for the target group).

30AA2CCB-9668-4E56-94E2-C0E279EFAE6B, 11
923AC8C0-BD60-4236-AAB2-B6E723402400, 11
8445F477-77D3-47F9-A900-CEAEA885BF0E, 932

You can submit up to 100,000 RIDs in a single submission.

info

You can call the reconciliation reason codes endpoint to find Cint's accepted reason codes.

2. Submit your reconciliation request​

After you've prepared your CSV file, you'll need to submit it. To do this, you'll call the submit reconciliations endpoint and include your CSV values in the request body. The name query parameter is required.

curl -L \
  -X POST \
  'https://api.cint.com/v1/demand/accounts/{account_id}/reconciliations?name=myFileForReconciliation' \
  -H 'Content-Type: text/csv' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer <token>' \
  --data-binary "30AA2CCB-9668-4E56-94E2-C0E279EFAE6B, 11\n923AC8C0-BD60-4236-AAB2-B6E723402400, 11\n8445F477-77D3-47F9-A900-CEAEA885BF0E, 932"
  • The API returns a request_id and the name of the CSV data.
{
  "name": "myFileForReconciliation.csv",
  "request_id": "01F8K8P3Z5KNYR5H0GQZAYGQJ9"
}

3. Verify the status of a specific reconciliation request​

You can check the processing status of a particular reconciliation submission by using its unique request ID.

GET https://api.cint.com/v1/demand/accounts/{account_id}/reconciliations/01F8K8P3Z5KNYR5H0GQZAYGQJ9

A successful request will return the following response:

{
  "request_id": "01F8K8P3Z5KNYR5H0GQZAYGQJ9",
  "name": "myFileForReconciliation.csv",
  "status": "complete",
  "submitted_at": "2026-01-01T23:00:00.000Z",
  "submitter_las_id": "4325c214c-2d72-7as2-b498-d6345342ff10b0",
  "submitted_count": 3,
  "expired_count": 0,
  "invalid_count": 0,
  "positive_reversed_count": 2,
  "negative_reversed_count": 1
}

Troubleshooting common issues​

  • Reconciliation deadline: Remember the trailing-month deadline. RIDs achieved in a given month can only be reconciled until the 25th of the following month. Submissions for RIDs past this deadline will be rejected.
  • CSV file formatting: Your RID and reason code must be comma-separated.
  • File size exceeded: If your CSV file exceeds 100,000 IDs, you'll need to split it into multiple smaller CSV groups and submit each one separately.
  • RID or reason code not found or invalid: Verify that the RID you are trying to reconcile is correct, belongs to one of your completes, and falls within the reconciliation policy guidelines. You should also verify that you are using the correct reason codes.