Map Header And Line Fields
The most important structural choice in field mapping is whether a value belongs on the document header or on repeating lines.
Header values
Section titled “Header values”Header values appear once per document.
Examples:
- invoice number
- document date
- due date
- currency code
- vendor or customer number
For header values:
- leave Is Line Field off
- map the row to the header table
Example:
- Extracted field:
documentDate - Destination: purchase header -> document date
Line values
Section titled “Line values”Line values repeat for each item or charge on the document.
Examples:
- item number
- description
- quantity
- unit cost
- amount
For line values:
- turn on Is Line Field
- set the destination to the line table
- set Line Table ID if needed
- treat repeating values as line-item data
Example:
- Extracted field:
lineItems.quantity - Destination: purchase line -> quantity
If one line field is set up correctly, the system can create one line record per extracted line-item group.
Practical examples
Section titled “Practical examples”Basic purchase header setup
Section titled “Basic purchase header setup”You want to fill these header fields:
- invoice number
- document date
- vendor number
Suggested setup:
vendorInvoiceNo-> purchase header -> vendor invoice no.documentDate-> purchase header -> document datevendorNo-> purchase header -> buy-from vendor no.
Purchase lines
Section titled “Purchase lines”You want one line per extracted item with quantity and cost.
Suggested setup:
lineItems.itemNo-> purchase line -> no.lineItems.quantity-> purchase line -> quantitylineItems.unitCost-> purchase line -> direct unit cost
For all three rows:
- turn on Is Line Field
- make sure the line table is the purchase line table
Common mistakes
Section titled “Common mistakes”- Do not mix header fields and line fields on the same row. A field that repeats per line should be marked as a line field.
- Do not leave line mappings without the correct line table. If the line table is wrong, line creation will fail or write to the wrong place.
- Do not skip sample-data review. If the extracted field name is wrong, the mapping will not apply.
Once the structure is correct, finish the setup in Defaults, keys, and review.