Skip to content
English
  • There are no suggestions because the search field is empty.

My contract reference is being rejected 

Fix invalid or inconsistent contract references by checking the right source document, keeping one reference per arrangement, and matching that reference across linked records.

What this usually means

This usually means the contract reference in the record does not match the contractual arrangement you are reporting, or the same arrangement is using different references across related records.

In the register, the contract reference is one of the key fields used to link contract data across templates. If that value is wrong, reused inconsistently, or taken from the wrong document, the contract structure becomes unreliable.

Why this happens

  • The reference comes from the wrong document, such as an SLA or supporting document instead of the contract or arrangement being reported.

  • The same arrangement has been entered more than once under different references.

  • A master contract and its linked order forms or subscriptions are using references inconsistently.

  • The reference used in one part of the register does not match the reference used in related records.

  • Group-level records and underlying entity records are not using the same reference for the same arrangement.

What to check and how to fix it

Check the Contract reference ID field on the contract record.

If the value comes from an SLA, appendix, service schedule, or other supporting document, replace it with the reference for the actual contract or arrangement you are reporting.

Check the contract stack for that provider.

If you have a master agreement, order forms, subscriptions, or implementing arrangements, make sure each reportable arrangement has its own reference and that you are not using one reference for different arrangements.

Check the other records for the same provider and contract stack.

If the same arrangement already appears under a different reference, keep one reference for that arrangement and update the other records to match it.

Check linked records that depend on the same contract reference.

If a related record points to the same arrangement but uses a different reference, correct the mismatch before you save or validate again.

Check whether the arrangement should point to a main contract.

If the record is a subsequent or associated arrangement and the structure is correct but the link to the main contract is wrong, fix the Main contract reference ID field as well.

Check group and entity records together if this contract is reported in a consolidation.

If the same arrangement uses different references at different levels, standardise the value so the same arrangement keeps the same reference everywhere.

What happens next

Once the reference is corrected, the contract should align properly with its related records. Re-save the record, then revalidate or re-export your register so the corrected reference is used consistently across the reporting set.

Related issues