Why reconcile
A submit that answered with a Workday ID proves the record was accepted at that moment. Reconciliation proves it is still there, carries the status you expect, and holds the lines you sent, after Workday's business process has run and after anyone has touched it. It turns the question "did everything land?" into a query.
Record by Workday ID
Every submit is paired with the extract that reads its business object back; the pairing is made when the business object is switched on. For each pair the app builds a view, RECON_<PREFIX>, that matches each succeeded record to the record the extract read back by Workday ID, and classifies it:
| Class | Meaning |
|---|---|
| confirmed | the extract holds the record and its status is the one expected |
| not yet extracted | the record succeeded after the extract's last window; the next run will pick it up |
| missing | the extract's window covered the record and it is not there |
| drift | the record is there with a different status, such as cancelled after posting |
The expected status comes from the submit's result lookup on its Configure form, where you also say which status field to read and whether the status is optional for the object.
Line by line
Because a line has the same table name on both sides, RECON_<PREFIX>_<LINE> goes one level deeper. Each line sent under a confirmed record is matched by position to the line read back, and every column both tables share is compared after converting the text that was sent to the extract's type, so 100 equals 100.000000 and 2026-03-31 equals the date Workday returned. DRIFT_COLUMNS names the columns that differ.
The Lines tab on Reconcile lists only the lines that were not found or differ; the views are there for SQL.
-- submitted journals the extract has not read back
SELECT SRC_REF_ID, OUT_STATUS, IN_LOADED_AT
FROM DATA.RECON_JOURNAL
WHERE NOT FOUND;
Keeping it fresh
An extract can list submits in Run after, so it runs once a batch for any of them completes. With that set, Reconcile confirms a morning's submit within minutes rather than after the nightly extract. Verification per wave already reads each accepted record back the moment it is accepted; reconciliation is the second, independent look that survives everything that happens afterwards.
After an import
Records sent through Workday's bulk import have no Workday ID in the answer; they are read back by their source key, which the app writes into the record's own ID field. From there, reconciliation is the same.