How Line-Item Fields Map to the Invoice Data Model

Map each invoice line as a related set of facts about one billed supply. Description, quantity, unit, price basis, adjustment and net amount must remain connected. A correct numeric value assigned to the wrong line or unit can change the transaction even when the document total remains plausible.

The mapping preparation workflow defines those relationships before target syntax. The current creator supports ordinary lines with editable descriptions, free-text units, quantities, prices, percentage discounts and manual tax information. It does not implement every formal line field a destination may require.

Identify what the line represents

Use the accepted order or approved service record to identify the supplied scope. Preserve the product variant or service distinction needed for review. Do not let a generic description conceal several different quantities or charging bases.

Keep formal line identity distinct from its current screen position. Adding or deleting a row changes positions without establishing an external order-line reference. The final profile may require identifiers or links the application does not collect as typed fields.

A source-to-term record should identify the line’s source evidence and target context. A mapper should not infer a stable business relationship from whichever row happened to be second when a screenshot was taken.

Preserve quantity and unit together

A quantity only becomes understandable with its unit. Three hours, three boxes and three individual items describe different supplies. Confirm that the unit price applies to the same basis before mapping either value.

A free-text unit label is not automatically a formal unit code. Record the target list and confirmed mapping where required. Do not guess a code from the label’s first letters or copy one from an unrelated example.

If conversion is necessary, preserve the commercial meaning and calculation evidence. Changing a label alone performs no conversion. The current creator accepts supported numeric values but does not determine pack sizes or contractual hours per day.

Check the price basis explicitly

A price can apply to one unit or a defined base quantity in a target model. The current app has no separate price-base quantity field. A contract priced per hundred items therefore needs a deliberate representation decision, not a mechanical copy.

OpenPeppol’s price group illustrates distinct item price and base-quantity roles. This is a documented profile example, not a feature added to the creator by mentioning it in guidance. The final software must actually implement the required relationship.

Preserve source precision too. The creator’s unit prices use two decimals and quantities up to four. If the required rate cannot be represented faithfully, use an appropriate system rather than altering the supplied quantity to compensate.

Map adjustments and net amounts coherently

Identify whether a reduction is already included in the source price or is a separate line adjustment. Applying it twice changes the charge. Keep percentage, fixed amount and adjustment level distinct in the working record.

Use the allowance and charge mapping guide for those roles. The current creator supports percentage line discounts only, with its documented rounding sequence. It does not provide document allowances, fixed adjustment fields or every formal price-discount structure.

The target net amount must reflect the implemented model and applicable rules. A mapper cannot assume a matching document total proves every intermediate value is correct. Review the line calculation and the source agreement separately.

Preserve additional line facts

A service period, product identifier, buyer order-line reference or line note may need its own target field. Text embedded in a description remains text unless the final adapter implements a verified mapping from confirmed components.

Do not invent a product identifier or period to satisfy a required target value. Collect the actual fact and preserve its role. The creator’s lack of a dedicated control is a capability gap to record, not an invitation to misuse another field.

Keep tax determination separate from line mapping. The adapter expresses confirmed category, rate and reason; it does not establish their legal applicability simply by assigning them to target fields.

Test the complete line relationship

Use two fictional lines with different units, quantities, references and prices. Trace their facts into the actual target groups. Check that the adapter does not exchange values while preserving the total sum.

Add a price-base or period requirement the source model cannot represent and verify that the final workflow reports the gap. A silent default can create a structurally valid but commercially changed document.

Retain the source records, mapping decisions, output and required validation evidence together. The current printable output, application JSON and line-item CSV support preparation within their scope. Formal line mapping and conformance require an implemented final adapter, accurate source facts and the checks appropriate to the recipient’s actual profile.

For a price-basis test, prepare a fictional agreement stating a price per hundred items and a distinct physical quantity. Record the intended calculation before choosing the target representation. If the current source cannot preserve the required basis or precision, require the workflow to report that limit rather than silently treating the quoted price as a per-item rate. Compare the resulting line scope as well as its amount.