Airbyte Amazon settlement dates arrive as null

A connector can complete a sync while two fields needed for settlement reconciliation become null. An Airbyte Amazon Seller Partner report describes posted-date and posted-date-time null in the V2 flat-file settlement stream, with _airbyte_meta.changes citing DESTINATION_SERIALIZATION_ERROR. The reporter used source connector 7.0.1, ClickHouse destination 2.1.33, and a self-hosted platform. Treat that stack as the observed scope.

Compare raw values with the declared type

Preserve a small redacted source report and inspect the raw date strings. The issue notes localized values in an EU account while the stream schema declares ISO-style date and date-time formats. Compare the parsed record, destination raw table, final typed table, and _airbyte_meta.changes. The Airbyte connector guide identifies the source and report streams; it does not prove this particular conversion is fixed.

Reconcile before a close

Count settlement rows with missing posted dates by report and currency, then reconcile amounts and identifiers against the raw Amazon report. Do not fill missing posted dates with settlement start or deposit dates merely to satisfy a dashboard. Those fields answer different finance questions. If a controlled transformation is used temporarily, retain raw values and document locale parsing and timezone rules.

Set an acceptance gate

A successful sync should be followed by field-level checks for null rates, serialization changes, and representative dates across locales. Ask the connector owner for a version-specific conversion fix and a test covering V2 settlement reports, then reprocess affected periods if the ledger requires it.

Adovo’s view

A green pipeline is not a balanced ledger. Dates that vanish during serialization change the story finance sees. Reconcile the raw report first; only then trust the typed destination.