What an ERP export cleanup delivers

This is an actual run of the delivery toolkit, not a manually prepared before/after example. All names, suppliers and descriptions are fictional. The original stays untouched. The cleaned review file keeps unresolved values so you can inspect them; the separate cleared-only file holds back every row with an exception.

What was sent and what came back

One item-master export with item number, description, base unit, inventory, unit cost, lead-time text, outstanding quantity and vendor name. It includes formatting drift, damaged IDs, blanks and a report total. There is no monthly usage or inventory-health assessment in this cleanup scope; see the sample inventory checkup report for that service.

40 input rows = 30 cleaned and cleared + 10 rows in exceptions. These groups are disjoint. The review CSV retains all 40 rows, including the total and conflicting duplicates; the cleared-only CSV contains 30. Held rows may still have approved formatting edits, all in the log.

The rules a client would confirm

These are the explicit approvals for this invented export, recorded in the downloadable rules file. They are not defaults to apply to other exports.

• Six transformations are agreed for this sample; confirm scope and price before work starts.
• The semicolon export is UTF-8 with a BOM; its first row is the header.
• Trim only surrounding whitespace. Item identifiers are case-insensitive and should be uppercase.
• EA, each and Each all mean one each here. No pack-size conversions are approved.
• Unit Cost uses European notation and two decimal places. Currency is not inferred.
• Inventory notation is mixed: normalize only unambiguous numbers to two decimals; flag 1,234.
• Only identical duplicates may be removed. Conflicting duplicate rows must both be held.
• Valid identifiers are six digits beginning 000 or FX- plus three digits. Do not reconstruct lost zeros or scientific IDs.
• No., Description, Base Unit of Measure, Inventory and Unit Cost are required; stock and cost cannot be negative.
• Hold any row with an exception from the cleared-only file. Keep it unchanged except for logged approved transformations in the review file.
• Lead times such as 2W and open-order quantities are passed through, not converted or checked in this cleanup scope.

Before and after

Source rows refer to the original CSV, including its header. Each excerpt below is read from the generated files. Values are quoted; ␠ marks a space and empty quotes mean a blank. A held row is excluded from the cleared-only download.

Every change has a receipt

The 111 edits above count operations, not unique cells: a field trimmed and then uppercased has a log entry for each change. Every entry records the source row, item key, field, old value, new value and rule. Case normalization identifies conflicting duplicates; it does not decide which stock balance is correct.

Exceptions: what needs your decision

No missing digits are reconstructed. A mixed-format quantity needs its notation confirmed; a blank balance is not assumed to be zero. Conflicting duplicates need a source-system decision, and a total is held for confirmation rather than silently deleted. Negative stock is held because this sample's approved rule forbids it; a different business might legitimately allow it.

There are 12 issue entries across these 10 rows. An identifier can trigger more than one check. Values shown in the exceptions list reflect the rule stage that raised the issue; approved formatting changes remain visible in the change log.

Independent QA: PASS

The separate QA script replays the change log against the original and compares every retained cell with the review output: 0 row-accounting or unlogged-change errors. It checks required fields and duplicate keys, with known unresolved issues disclosed as informational findings. It records SHA-256 checksums for the original, review CSV, change log and exceptions. PASS confirms the delivery's traceability; it does not certify held rows for import or prove the source stock is correct.

The QA report's run timestamp is omitted for reproducible public files. The checks, results and checksums are the actual tool output.

Download the delivery

• Original ERP export (semicolon CSV, UTF-8 BOM)
• Full cleaned review file (includes held rows)
• Cleared-only rows (derived from the review file)
• Cell-by-cell change log
• Exceptions and source row references
• Independent QA report
• QA checks and SHA-256 receipts (JSON)
• Rules and client confirmations (JSON)
• Initial data profile (JSON)
• Toolkit cleanup summary

CSV does not enforce text types. When opening in Excel, import item numbers as text so leading zeros survive; do not double-click and resave the original. The cleared subset is a reviewable starting point, not a destination-specific ERP upload format.

For your own export, agree the rules, required fields and handling of exceptions before processing. Nothing is changed in your ERP. See cleanup scope and order through Upwork.