Invoices and customs forms: numeric fields first
Route `invoice-ocr-translate` (translate_image.invoice) targets customs paperwork, pro-forma invoices, and foreign bills. Tax IDs, IBANs, and date formats are high risk. Machine translation is not a substitute for filings—keep original scans adjacent to translations. When a vector PDF exists, prefer its text layer for numbers before relying on a raster pipeline.
Invoice image translation workflow
- Capture glare-free corners; photograph header blocks separately from line-item tables if needed.
- Lock amounts, tax lines, party names, and dates before translating narrative notes.
- Attach a field-by-field comparison sheet for finance sign-off with the reimbursement packet.
Image translation FAQ (invoice)
Which fields break most often in `invoice-ocr-translate`?
Amounts, VAT numbers, date formats, currencies, and addresses—always human-verify against contract references.
Decimal vs. thousands separators clash—how?
Normalize to the source country format, then cross-check numeric and written amounts.
Is MT enough for customs filing?
No—licensed brokers must certify; MT is internal draft only.
Vector PDF vs. phone photo?
Prefer selectable PDF text, then OCR only the raster portions.
Multiple currencies in one frame?
Lock symbols, capture rate dates, and keep original numerals beside translations.