Data & Analytics
Airbyte Amazon settlement sync can hide missing posted dates
A successful Amazon Seller Partner sync can null localized posted-date fields; audit _airbyte_meta before finance uses them.
November 17, 2026
A complete settlement table can still be incomplete in the columns finance uses. In Airbyte issue #90175, a self-hosted Amazon Seller Partner 7.0.1 stream loads posted-date and posted-date-time as NULL into ClickHouse, with _airbyte_meta.changes recording destination serialization errors. Other date fields in that same stream load. The reporter suspects localized V2 report dates do not match the declared ISO date formats.
Inspect row-level errors before the dashboard
Count rows where either posted-date field is NULL and inspect _airbyte_meta.changes by sync ID. Airbyte's Destinations V2 guidance explains that typing errors can be recorded in metadata instead of failing the sync. A successful sync status therefore cannot certify every typed field.
Compare raw and normalized values
Sample raw Amazon report values from the affected V2 stream and compare them with the connector schema and destination output. Preserve marketplace locale and timezone in the sample. Check whether V1 and V2 streams normalize the same field differently. The connector documentation gives the supported stream and version context; do not infer that every marketplace has the same date representation.
Protect finance reconciliation
Gate settlement reporting on a non-null posted-date rate and a zero unexpected serialization-error count, with exceptions for legitimately absent source values. If a parser correction or connector upgrade is tested, backfill the affected settlement window and reconcile row totals and amounts before removing the alert.
Adovo’s view
An ingestion job succeeds when the business fields survive, not when the connector reaches its final state. Error metadata is part of the data contract. Finance should see a failure before a missing date becomes an incorrect reporting period.
