Skip to content
MirrorFirm

Which elements should we ask for when specifying a mismatch release?

Provides a request checklist covering cause types, record structure, policy variation, labels and environment state so a buyer's specification is concrete from the first conversation.

Use this list when describing what you want generated, so the request can be scoped in a pilot.

- The domain and the two systems in conflict, such as a warehouse system and a carrier invoice. - The cause types to cover, for example timing, duplicate, partial settlement, amendment, unit mismatch or missing link. - The related record types the agent must follow to find the cause. - The policies and approval limits that should govern the fix, with some variation between cases. - The labels you need: root cause, correct action, acceptable alternatives and expected final state. - Cases where the right action is to escalate or take no action. - The range of difficulty, from single-hop evidence to evidence spread across several records. - The format and reset behaviour you need, whether static files or a stateful environment.

Not every item will suit every buyer. Listing the ones you do not need is as useful as listing the ones you do.

A specific request avoids a release that looks plausible but cannot be scored against your own questions.

Audience:
Evaluation teams
Content type:
Checklist
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Reconciliation mismatch