Field Note
Ledger Field Mapping Pitfalls in Korean ERP Exports
Date format splits, beneficiary ID inconsistencies, and currency column duplicates that delay chart production when exports arrive without documentation.
Chart production cannot begin until ledger fields map cleanly to our intake schema. Most delays trace to export quirks rather than missing data. Three patterns appear repeatedly in Korean client exports:
Split date columns. Some ERP systems export year, month, and day in separate columns while others use YYYY-MM-DD strings. When a client sends both formats across subsidiary exports, we must reconcile before velocity calculations run. Include a one-row data dictionary with your export showing which column holds the authoritative transaction date.
Beneficiary identifier drift. The same vendor may appear as a business registration number in one subsidiary export and a truncated name string in another. Concentration charts treat these as separate beneficiaries unless mapped. Provide a vendor master crosswalk when available, even if incomplete.
Duplicate amount columns. Exports sometimes include both KRW amount and USD equivalent. Chart passes must target one column consistently. If your committee reviews in KRW, confirm which column reflects the approved ledger entry rather than a reporting conversion.
We return a field mapping validation report within two business days of data receipt. The report lists mismatches with row counts—"847 rows with unparseable date in column D"—so your IT team can fix the export before we spend time on charts that will require rebuilding.
Sending a 1,000-row sample export during scoping, before the full ledger transfer, catches most mapping issues early. The sample costs nothing on your side and typically saves four to six days on the production timeline.
