Invoice date and currency formats: normalize without guessing

Keep the source value before normalizing it

Normalization makes extracted invoice values consistent enough to compare and import. It should preserve meaning, not conceal uncertainty. Keep a raw value, a reviewed value, and a note when interpretation is required.

In Parzable, use separate schema fields for Invoice date, Due date, Currency, and Total. Add descriptions that identify the printed labels and ask the extractor not to infer absent information. The current prompt asks for missing values as N/A; check those before importing into typed columns.

Do not assume a field’s type selection guarantees a normalized result. Inspect the downloaded data and validate it in a staging sheet before it reaches the destination.

Resolve the date before changing its format

A year-month-day output is a useful convention after you have established what the date means. It does not resolve an ambiguous source by itself. Ask for a clear copy or confirm the supplier’s intended format when necessary; an address or browser locale alone is weak evidence.

If you transform dates in Excel, inspect the import preview and a few reopened values. Excel’s automatic interpretation can change text into dates before you have reviewed it. See Microsoft’s text and CSV import guidance.

Separate currency identity from number formatting

A dollar symbol does not uniquely identify a currency. Preserve the printed symbol if the document does not establish the currency code. Do not silently convert it to USD.

Keep totals separated by currency in reports. Adding EUR and USD values into one total does not create a meaningful combined amount. Currency conversion requires an explicit rate, date, and policy outside this extraction guide.

Use a small normalization log

The blank normalization log includes filename, field, raw value, reviewed value, decision, and reviewer note. Use it for ambiguous dates, separator corrections, or any transformation that would be hard to reconstruct later.

Keep invoice numbers and supplier references as text even when they look numeric. Preserve negative signs, credit-note labels, and parentheses in the raw field until you have confirmed the intended sign. Never change a missing amount to zero just to satisfy an importer.

A simple release rule is useful: each required field must either have a reviewed value or a named exception owner. Anything still ambiguous stays out of the final import. This keeps formatting cleanup from becoming unsupported guesswork.