# Invoice OCR Field Mapping Worksheet

> Source: https://netray.co/tools/invoice-ocr-field-mapping-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Map every invoice field your OCR extracts to its ERP target, set a minimum confidence per field and see which fields fall short of the bar.

## Category

ai-automation

## Audience

- AP manager
- ERP analyst
- Finance systems lead

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Invoice field

**Key:** field

**Type:** text

#### Label seen on document

**Key:** ocr_label

**Type:** text

#### Level

**Key:** level

**Type:** select

**Options:**

- Header
- Line
- Tax
- Footer

#### Data type

**Key:** dtype

**Type:** select

**Options:**

- Text
- Date
- Amount
- Quantity
- Code

#### Required

**Key:** required

**Type:** select

**Options:**

- Yes
- No

#### Validation rule

**Key:** validation

**Type:** text

#### ERP target field

**Key:** erp_target

**Type:** text

#### Sample avg confidence

**Key:** sample_conf

**Type:** number

**Unit:** %

#### Minimum to auto-post

**Key:** min_conf

**Type:** number

**Unit:** %

#### Gap to bar

**Key:** gap

**Type:** number

**Expr:** sample_conf - min_conf

**Format:** decimal

**Rows:**

**Field:** Vendor invoice number

**Ocr label:** Invoice No / Inv #

**Level:** Header

**Dtype:** Text

**Required:** Yes

**Validation:** Unique per vendor, no duplicates

**Erp target:** Reference / vendor invoice number

**Sample conf:** 96

**Min conf:** 95

**Field:** Invoice date

**Ocr label:** Date / Invoice Date

**Level:** Header

**Dtype:** Date

**Required:** Yes

**Validation:** Not future dated, within 12 months

**Erp target:** Invoice date

**Sample conf:** 94

**Min conf:** 90

**Field:** Vendor tax ID

**Ocr label:** GSTIN / VAT No / EIN

**Level:** Header

**Dtype:** Code

**Required:** Yes

**Validation:** Matches vendor master

**Erp target:** Vendor lookup key

**Sample conf:** 89

**Min conf:** 95

**Field:** PO number

**Ocr label:** PO / Order Ref

**Level:** Header

**Dtype:** Code

**Required:** Yes

**Validation:** Open PO exists for vendor

**Erp target:** Purchase order reference

**Sample conf:** 91

**Min conf:** 95

**Field:** Line quantity

**Ocr label:** Qty / Quantity

**Level:** Line

**Dtype:** Quantity

**Required:** Yes

**Validation:** Numeric, within receipt tolerance

**Erp target:** Invoiced quantity

**Sample conf:** 93

**Min conf:** 92

**Field:** Unit price

**Ocr label:** Rate / Unit Price

**Level:** Line

**Dtype:** Amount

**Required:** Yes

**Validation:** Within price tolerance of PO

**Erp target:** Invoiced unit price

**Sample conf:** 92

**Min conf:** 95

**Field:** Tax amount

**Ocr label:** VAT / GST / Sales Tax

**Level:** Tax

**Dtype:** Amount

**Required:** Yes

**Validation:** Rate times base equals amount

**Erp target:** Tax line amount

**Sample conf:** 90

**Min conf:** 90

**Field:** Invoice total

**Ocr label:** Total / Amount Due

**Level:** Footer

**Dtype:** Amount

**Required:** Yes

**Validation:** Equals sum of lines plus tax

**Erp target:** Gross invoice amount

**Sample conf:** 97

**Min conf:** 97

**Totals:**

#### Net gap (sum)

**Key:** gap

**Agg:** sum

**Format:** decimal

**Summary:**

#### Average sample confidence

**Key:** avg_conf

**Expr:** avg_sample_conf

**Format:** decimal

**Primary:** true

#### Fields mapped

**Key:** field_count

**Expr:** count

**Format:** integer

**Notes:** A negative gap means that field is currently below the bar and should be routed to review or the OCR model should be tuned. Replace the example ERP targets with the real table fields or API properties in your system.

## Content

**Intro:** Most invoice automation projects stall on the mapping step: the OCR returns labels like Inv # or Rate, and nobody has written down where each one lands in the ERP. This worksheet makes that mapping explicit, one row per field, with the validation rule and the confidence you require before a value may post without a human look.

**Sections:**

#### How to use the worksheet

**Body:** Start from a sample of 30 to 50 real invoices from your top vendors, not a clean demo set. List every field you need to create a vendor invoice in your ERP: header fields, tax lines and the line fields needed for a match against the purchase order. Record the labels you actually see on the documents, since the same field is called different things by different suppliers. Then fill in the average confidence your OCR tool reported on the sample and set the minimum confidence you will accept for automatic posting. The gap column shows where you fall short.

**Bullets:**

- One row per field, header and line level separated
- Write the label variants suppliers use, not just your own name for the field
- Set stricter bars for money and identifiers than for free text
- Add a validation rule to every required field

#### Choosing minimum confidence per field

**Body:** A single global threshold hides risk. A wrong description costs nothing, while a wrong total or tax ID creates a payment error or a failed vendor lookup. Set the bar by consequence: identifiers and amounts higher, dates and descriptions lower. Where the field can be cross-checked, such as total against line sum plus tax, or PO number against open orders, the validation rule can catch what confidence misses, so you may accept a slightly lower raw confidence. Revisit the bars after each month of production data, since vendor mix changes.

#### Common mistakes

**Body:** Teams often map only header fields and discover at go live that line items, freight and tax breakdowns drive most exceptions. Others map to a display name rather than the real ERP field, which causes rework in the integration layer. A third trap is averaging confidence over the whole sample: always look per field, because a 97 percent average can hide a 80 percent tax ID.

**Bullets:**

- Forgetting freight, discount and rounding lines
- Mapping to a label instead of the actual ERP field or API property
- Ignoring multi currency and multi language invoices
- Not re-measuring after the model or template changes

**Cta:** If you want this mapping turned into a working capture and posting flow against your own ERP, with approval on every write-back, we can review your sample and tell you honestly whether your ERP vendor's own capture tool is enough.

**Faq:**

#### How many invoices should I sample?

**Answer:** Thirty to fifty invoices is enough to build the mapping, provided they cover your top vendors, different layouts and at least a few scans or photographed documents. For measuring accuracy later you need a larger set, a few hundred documents, so the numbers per field are stable.

#### Do I need to map line items?

**Answer:** Yes, if you do a three way match against purchase orders or post to expense lines. Header only capture works for non PO invoices with a single coding, but line level mapping is where most manufacturers lose touchless rate.

#### What confidence score should be the minimum?

**Answer:** There is no universal number, because vendors score confidence differently. Choose by consequence, higher for amounts and identifiers, and calibrate against your own sample by comparing the score with actual correctness, not by trusting the default.

#### Can I import this into my ERP?

**Answer:** The worksheet exports to Excel or CSV, which most integration teams use as the mapping specification. It is documentation, not a loader, so your integration developer still builds the actual interface to the ERP.

## Search terms

invoice ocr field mapping, invoice data extraction fields list, ocr to erp field mapping template, accounts payable ocr fields, invoice capture field mapping excel, invoice header and line fields, ap automation field mapping, invoice ocr confidence by field

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json