Cost and cross-record consistency issues
Fix linked record mismatches by checking contract cost, currency, function, provider, signing entity, service-user ID code, and branch fields against the same contract reference.
What this issue group covers
These issues usually happen when linked records do not match. The same contract, function, provider, amount, or entity using the service appears across connected records, but one of the linked values is different.
This page covers the quick checks for duplicated cost, currency mismatches across linked records, function-to-contract inconsistencies, and cases where the signer, the entity using the service, and branch details have been entered into the wrong fields.
Related
Issues covered on this page
I am duplicating cost
What this usually means
The same cost has been reported more than once across linked contractual arrangements. This usually happens when an overarching arrangement and its subsequent or associated arrangements all carry the same amount, or when extra detail rows are treated like extra cost rows.
What to check and how to fix it
Check the Contractual arrangement type for the records you are comparing.
If one record is really an overarching / master contractual arrangement and another is a subsequent or associated arrangement, fix that first before you review any cost values.
Check whether the same amount has been entered in Annual Contract expense amount on both the overarching arrangement and the linked subsequent or associated arrangements.
If it has, remove the repeated amount so the total is reported once across the arrangement structure.
Check whether costs are available only at child-arrangement level or only at overarching level.
If the cost is not determined at overarching level, keep the overarching amount at 0 and report the cost on the child arrangements. If child-level costs are not available, report the total on the overarching arrangement only.
Check whether you added extra detailed rows because the same contract supports more than one ICT service or more than one function.
If you did, keep the extra detail rows, but do not create extra values in Annual Contract expense amount just because the same contract appears more than once in the detailed contract information.
Check that the same Contract reference ID is being used consistently for the same arrangement.
If the same arrangement has been split across different reference IDs, fix the reference IDs first and then recheck the cost totals.
My currency values do not match
What this usually means
The amounts may be correct, but the linked records are not using the same reporting currency. This usually shows up when the contract-level amount and the provider-level amount are being compared in different currencies.
What to check and how to fix it
Check that you are comparing records at the same reporting level.
Compare entity-level records with entity-level records, sub-consolidated records with sub-consolidated records, and consolidated records with consolidated records before you compare any amounts.
Check the Financial reporting currency used for the relevant financial statements at that same reporting level.
If the currency on the linked cost records does not match that reporting currency, update the currency and amount before you compare totals.
Check Financial reporting currency against Annual Contract expense amount on the contractual arrangement record.
If the currency code and the amount do not belong together, fix them as a pair.
Check Financial reporting currency against Annual ICT provider cost on the provider record.
If the provider-level amount is being expressed in a different reporting currency from the contract-level amount, align it first.
Check whether you are comparing Annual Contract expense amount with Annual ICT provider cost.
If you are, make sure the first amount is only one contractual arrangement and the second amount is the provider total for the entities making use of the ICT services. If the scopes are different, do not force the values to match. Compare like with like instead.
My function and contract details do not match
What this usually means
A contract row is linked to the wrong function, provider, or entity using the service. This is usually an identifier problem rather than a wording problem.
What to check and how to fix it
Check that the Contract reference ID in the detailed contract row matches a real contract in the general contract record.
If it does not, correct the contract reference before checking anything else.
Check that the Function ID used in the detailed contract row exists in the functions record.
If it does not, add or correct the function first.
Check that the Function ID matches the right combination of the service user ID code, licensed activity, and function.
If the same Function ID has been reused for a different combination, assign the correct one and update the linked rows.
Check whether the same Contract reference ID and the provider ID code support more than one function or more than one ICT service.
If they do, use separate rows for each valid combination instead of forcing different functions into one row.
Check that the service user ID code, the provider ID code, and the Function ID point to the same real relationship across the linked rows.
If one of those values points somewhere else, correct the identifier and then review the other rows for the same contract.
My role-related details do not match
What this usually means
The wrong party has been entered into one of the linked fields. Most often, the signer has been copied into the field for the entity using the service, or a branch has not been identified correctly.
What to check and how to fix it
Check Signing entity LEI against who actually signed the contract.
If that field is wrong, correct it there and do not assume it must always match the service user ID code.
Check the service user ID code against the entity that actually uses the ICT service.
If that value is wrong, fix that field before you review branch details.
Check Is service user a branch? If the answer should be yes, the service user must also have a valid Branch ID code from Branches.
If the answer should be no, do not leave branch-specific detail attached to that row.
Check Branch ID code against the branch listed in Branches.
If the code does not match a real branch for that financial entity, correct the branch entry first and then return to the service-user row.
Check the same Contract reference ID on the row where Signing entity LEI is recorded and on the row where the service user ID code is recorded.
If the contract is correct in both places, Signing entity LEI and the service user ID code can be different. Only change them if the wrong value has been entered into the wrong field.
What to do next
After you fix one mismatch, review the other rows that use the same contract, provider, and entity using the service. These issues often repeat across linked records, so one clean pass across the full set is usually faster than fixing them one by one.