Field mapping

The field mapping answers the question: where does the value come from that DATEV expects in a given field? It is described declaratively – as an assignment, not as program code. That keeps it traceable and reviewable how a value comes about.

What is this for?

• Map source fields from DocuWare or SAP onto DATEV fields.
• Draw values from an e-invoice where one exists.
• Perform conversions through a fixed function library – deliberately not a free scripting language.

How to set it up

1. Create one mapping per client and document type.
2. For every DATEV field state the source – a field of the source system or a value from the e-invoice.
3. Where needed use a function from the library, for example to reformat a date.
4. Set the selection condition that decides which documents are picked up at all.
5. Type-check errors later point at the source field and mapping line – not at the produced XML. That saves searching inside the file format.