An Indonesian address import can fail even when the postcode survives: the source province may end up in the city column. Treat labels from each source as a mapping task. The current generator offers Jakarta-area fixtures, so it should not be described as a complete Indonesian address directory.

Set up a focused test

Create a two-row fixture with distinct IDs. In one row, put the generated city into locality and the generated region into administrativeArea. In the other, deliberately swap those values. Define whether your importer checks geography or only accepts strings; otherwise the swapped row may pass while the test incorrectly expects rejection.

Run the checks

  1. Inspect the import preview before committing rows.
  2. Keep province, locality and postal code in separate columns.
  3. Verify field names in the resulting API response.
  4. Add district details manually when your destination schema requires them.

Interpret the result

Do not infer missing administrative levels from an arbitrary street string. A better import error identifies the missing destination field and retains the original row for correction. Save the mapping configuration beside the fixture so the same file can be imported consistently after a schema change.

Open the related address tool to prepare synthetic examples for your test.