Skip to main content

Financial Assessment Type conflicts between source and target person

In this article, we explain an error when merging two people: Person 630478 has a conflicting Non Residential Financial Assessment.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

If you see an error while trying to merge two people in Mosaic, it likely means the system's validation code has flagged a conflict. Specifically, both people have assessment results of the same type with overlapping or clashing date ranges, which Mosaic can't unify during a merge.

Why This Happens

Mosaic doesn’t allow a merged person to have two active results of the same assessment type covering the same time period. For example:

  • Person 123456 might have an active result starting 08/04/2024 (ongoing).

  • Person 654321 might have another starting 10/04/2023 (also ongoing).

If you merge them, the new person will have two active assessment results overlapping in time—this could make them liable for duplicate charges, which Mosaic prevents.

How the System Validates This

Mosaic checks if both people have an active assessment of the same type with overlapping dates. If they do, it blocks the merge.

Possible Workarounds

You have a couple of options to resolve the clash:

  1. Cancel the clashing assessment result for one of the people.

    1. This removes the active status and avoids the overlap.

  2. Adjust the dates of the assessment result for one person so they no longer overlap.

    1. Then try the merge again.

⚠️Important: These changes can affect billing. For example, if you cancel an assessment result that’s already been part of certified billing cycles, Mosaic might treat it as if you owe the service user a refund for that period. Always test any workaround thoroughly in your test environment before applying it to live data.

Need Further Help?

If you're unsure or need financial guidance on the implications, we can arrange help from a finance consultant. Just raise a new case and request finance consultant support.

Did this answer your question?