Rules and mappings

The validation steward maintains a definition for each organization and reviews the field mappings associated with that definition. A mapping names the source field, target field, their types, a transform rule and a version. The definition carries its effective dates and policy reference. Choose the definition before a batch is parsed so reviewers can trace a result to the rules applied.

• Definition. Choose the organization, effective dates and policy reference for the rule set.
• Field mapping. Record the source field, target field, types and transformation for each mapping.
• Version. Preserve the mapping version and batch rule version used for a reviewed result.

The Validation Steward checks that the definition selected by the Import Operator belongs to the sending organization. A mapping has its own version and effective date, while the batch records a rule version. Those values let a reviewer understand which interpretation of an incoming field produced a row outcome. When a sender changes a layout, the steward reviews the affected mapping before the next parse. A later investigation can then compare the older and newer meanings without silently changing the reviewed result.

When a sender renames a field or changes a value type, the steward compares the incoming layout with the active mapping. They agree on the target meaning with the receiving system owner and record a new mapping version when the meaning changes. A batch retains its selected definition and rule version for later investigation.

Agree who owns the receiving target field names and which transformation is expected for each source field. Choose how the steward records a mapping change and how the operator selects the effective definition. Test a row whose source type conflicts with the target type. The resulting failure should identify the rule and field that need attention, so the steward can decide whether the source or mapping needs correction.

Suppose a sender changes a source field from an amount to a text value. The steward checks the target field and transformation before the operator processes the next submission. If the rule rejects rows, the result identifies the failed field and the reviewer can see which rule was used.

Use the sender’s changed amount field as the sample. Show the old mapping version beside the new one, then trace the rejected row to its failed field and rule. Ask the Import Operator to identify which rule version was used on the batch before the Independent Reviewer considers its accepted partition.

• Validation Queue — Find parsed batches whose rule results need review.
• Incoming Batches — Check the organization and definition selected at intake.

See the related process and the data model to rehearse this handoff with a real submission.