Partner data intake

How Data Entry & Validation is set up for you

The steward agrees on incoming field names and target meanings with the receiving team. The operator retains the source identifiers and checks rejected rows by source record. A returned decision gives the partner correction request a precise reason.

Start with a partner submission that contains an amount field and a source record identifier on each row. The Validation Steward confirms the target field, type and transformation. The Import Operator records the partner organization, batch owner, source hash and chosen definition. Include one row whose amount cannot be mapped so the rejected result shows the rule and failed field.

The Independent Reviewer returns that revision with a reason the Import Operator can send to the partner. When corrected data arrives, compare the source hash and row outcome with the earlier version. Validate the successor revision and request a new decision. The earlier return remains part of the decision trail.

After approval, the Execution Operator checks the accepted partition against the receiving target. Record its operation key, step output and receipt. If the partner asks whether a row landed, the team can answer from the source record identifier, reviewed revision and target reference rather than from the file name alone.