Understanding individual results in Advanced Reconciliations

An Advanced Reconciliations result is a single reconciled outcome within a result set. This could be a matched pair, a break, or a partial match, depending on what LUSID found when it compared your left and right data.

Types of individual result

Result type	Meaning	Treated as exception?
Match	The left and right core rule values match, and the aggregate rule values agree.
Partial Match	The left and right core rule values match, but there are aggregate value discrepancies.	☑️
Break	LUSID could not match the core rules and their values to the other side.	☑️
Cross	LUSID matched core rule values on both sides by treating two different values as equivalent, as configured in your reconciliation definition.
Partial Cross	The left and right core rule values match as a cross, but there are value discrepancies.	☑️

Understanding what changed between runs

Each time you rerun a reconciliation instance, LUSID compares the new results to the previous run and records what changed in the resultLifecycle field:

Lifecycle status	Meaning
New	This result wasn’t produced by the previous run.
Unchanged	The result is still present, and its values have not changed.
Changed	The result is still present, but one or more values have changed.
Cleared	This result was produced by a previous run, but has not been produced by this run (typically because the underlying data was corrected).

Reviewing a result

Each individual result, including matches, has a review status:

Review status	Meaning
Not Required	Your reconciliation review configuration doesn’t require this result to be reviewed.
Required	A person needs to review this result.
Reviewed	A person has reviewed and recorded a decision for this result.

You can customise which types of result require reviews in your reconciliation definition’s review configuration. By default, open exceptions require review, while matches and closed exceptions do not.

Types of result decision

Leave exception open or close immediately. When you review a result, you record one of the following decisions:

Decision	Meaning
Acknowledge	The reviewer looked at the result but hasn’t committed to a resolution.
Fix at Source	The reviewer requires the underlying data to be corrected upstream; the exception stays open.
Fix as Group	The reviewer suspects two or more results share the same underlying cause, and expects them to be fixed together; the exceptions stay open until the fix takes effect.
Accept	The reviewer accepts the result as a genuine, tolerated difference; the exception closes.
Force Match	The reviewer asserts that the linked results match once specific matching rules are set aside. If setting those rules aside: Doesn’t produce a match, LUSID refuses the decision; the exception stays open. Produces a match, all linked results close.
Tolerate	The result is left open, with no fix required.

Note
Fix as Group and Force Match both apply a single decision across multiple results at once. LUSID keeps track of which results were grouped together under one decision, so undoing the decision on any one of them undoes it for the whole group.

Exceptions

The following result types have exception information:

Partial Match
Partial Cross
Break

An exception has a status of Open or Closed. Once Closed, each exception has a closure type that specifies how it was resolved:

Closure type	Meaning
Cleared	LUSID closed it automatically; the exception is no longer produced.
Accepted	A reviewer accepted the result.
Force Matched	A reviewer force-matched the result against others.