Reconciliations

  • Updated on Oct 17, 2025
  • Published on Oct 1, 2025
  • 3 minute(s) read
Prev Next

Cint offers a reconciliation process that allows buyers to remove completes that do not meet quality standards.

The following provides information on when it is acceptable to reconcile, the process for doing so, and the responsibilities of buyers who choose to use this ability.

Cint reserves the right to request supporting documentation for reconciliations and may overturn any reconciliation that does not have a valid reason or adhere to the below.

Dashboard overview

The reconciliations page allows you to submit reconciliation requests and track their status.

See submit a reconciliation for information on submitting a reconciliation.

Dashboard.png

The following fields display for submitted reversals:

  • Filename: Lists the reconciliation files that have been submitted.

  • Submitted on: The date when the request was uploaded.

  • Status: Shows either pending or complete.

    • Pending: requests are still being reviewed by the SINT audit team

    • Complete: indicates a final decision on accepting individual RIDs.

  • Submitted: The number of RIDs submitted.

  • Positive: The number of RIDs positively reconciled to a complete.

  • Negative: The number of RIDs negatively reconciled from a complete to a termination.

  • Expired: RIDs that were outside the reconciliation window when submitted and cannot be reconciled. Remember, SEND policy states that individual RIDs have until the 25th of the following month to be submitted.

  • Invalid IDs: The number of RIDs that were unable to be submitted for reconciliation.

  • Submitted by: Lists the project manager who submitted the RIDs.

See submit a reconciliation for information on submitting a reconciliation.

Acceptable reasons for a reconciliation

The following fraudulent behaviors are acceptable reasons to disqualify a respondent:

  1. Straight-lining: (Reason code to provide while submitting recon: 932)

    • Definition: respondent selects all answers on questions in a straight line, demonstrating the respondent was not reasonably paying attention to the survey question

    • Supporting data: RIDs, questionnaire and answers, reason code, survey id/target group id

  2. Speeding: (Reason code to be provided while submitting recon: 933)

    • Definition: respondent’s length of interview (LOI) was outside of the reasonable LOI for the survey

    • Supporting data: RIDs, respondent’s LOI, as calculated by entry and exit time, compared to other respondents’ LOIs reason code, survey id/target group id

  3. Marketplace complete not on client side: (Per new policy, it is called ghost complete, reason code: 935)

    • Definition: Marketplace registers a complete for a respondent, but there is no evidence of that respondent in the client survey

    • Supporting data: RIDs with associated response codes and/or complete status. Reason code, survey ID/target group ID

      In order to remove respondents for this reason, the survey must be using one of the link security methods provided by Lucid.

  4. Inappropriate open ends: (Including repetitive, vulgar, and nonsensical) (new name is poor quality open-end and reason code: 934)

    • Definition: open-ended responses in the client-side survey are repetitive (i.e. the same answers for all open-ended, or the same answers for multiple responses), contain vulgar language, are nonsensical, not pertaining to the questions, or include random strings of letters, words, or sentences

    • Supporting data: RIDs, questionnaire and answers reason code, survey id/target group id

  5. Mismatched responses: (new name is: inconsistent answers and reason code: 936)

    • Definition: respondent answers differ from the Marketplace and client survey; example: age mismatch

    • Supporting data: RIDs, Marketplace qualifications, and client-side questions and answers. Reason code, survey ID/target group ID

  6. Duplicate responses: ( This is not acceptable reason as per new policy.)

    • Definition: identical open-ended responses seen across multiple respondents.

    • Supporting data: RIDs, questionnaire and answers

  7. Adjusted complete: the respondent was adjusted from another status to complete via reconciliation reason code: 11

  8. No reason provided: the respondent was adjusted from another status to terminate. Reason code: 26

Unacceptable reasons for a reconciliation

The following behaviors are unacceptable reasons to disqualify a respondent:

  1. Duplicate respondent.
    Reason code: 931

  2. Disqualifying a respondent due to survey side setup errors, new name: set up error.
    Reason code: 940

  3. Inaccurate CPI.
    Reason code: 941 - launching a project with the incorrect CPI

  4. Incorrect qualifications and quotas, new name: incorrect quals & quotas.
    Reason code: 942 - improper setup of targeting and/or quotas within the Marketplace

  5. Project overfilling.
    Reason code: 943 - failure to use the proper quota calculation type

  6. Bulk termination.
    Reason code: 944

Reconciling to complete

If a technical error prevents the recording of a complete status in Marketplace, buyers must reconcile sessions. This ensures the respondent and supplier are properly compensated for their effort.

To do this, include the IDs of these valid sessions RID, reason code, survey/target group ID and select completes and adjusted termination when submitting the reconciliation.

Reconciliation timeline

Refer to the policy for the new reconciliation window and example.

Customers are encouraged to complete the reconciliation process as soon as possible. Reconciliations can be completed until the 25th of end of the following month after the individual RID timestamp to adjust the status. It is important to note that the timeline is based on the time of completion of each ID and not the completion of the project overall.

In order to receive optimal support, best practice is to reconcile as soon as you have the final IDs.

See submit a reconciliation for more information.

Related articles