OFD field mapping
This table shows how Tungsten AP Essentials maps internal fields with OFD (Open Fixed-layout Document) XML. Currently, AP Essentials does not support OFD files that contain more than one document.
| Tungsten AP Essentials internal field name | OFD field from Doc_0/Attachs/original_invoice.xml |
|---|---|
| Buyer fields | |
| Name | /eInvoice/fp:Buyer/fp:BuyerName |
| BuyerVATRegistrationNumber | /eInvoice/fp:Buyer/fp:BuyerTaxID |
| Supplier fields | |
| Name | /eInvoice/fp:Seller/fp:SellerName |
| SupplierVATRegistrationNumber | /eInvoice/fp:Seller/fp:SellerTaxID |
| SupplierBankDetails1 | /eInvoice/fp:Seller/fp:SellerFinancialAccount |
| Invoice fields | |
| InvoiceCode | /eInvoice/fp:InvoiceCode |
| InvoiceNumber | /eInvoice/fp:InvoiceNo |
| InvoiceCredit | /eInvoice/fp:TypeCode
If TypeCode = 0, it is considered a debit invoice. |
| InvoiceDate | /eInvoice/fp:IssueDate |
| InvoiceCurrency | Currently, this value is set to CNY. |
| InvoiceTotalVatExcludedAmount | /eInvoice/fp:TaxExclusiveTotalAmount |
| InvoiceTotalVATAmount | /eInvoice/fp:TaxTotalAmount |
| InvoiceTotalVatIncludedAmount | /eInvoice/fp:TaxInclusiveTotalAmount |
| Line-item fields | |
| LIT_ArticleName | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:Item |
| LIT_ArticleIdentifier | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:Specification |
| LIT_DeliveredQuantityUnitCode | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:MeasurementDimension |
| LIT_UnitPriceAmount | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:Price |
| LIT_DeliveredQuantity | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:Quantity |
| LIT_VatExcludedAmount | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:Amount |
| LIT_VatRate | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:TaxScheme |
| LIT_VatAmount | /eInvoice/fp:GoodsInfos/fp:GoodsInfo/fp:TaxAmount |
Field mappings from incoming XML formats only map to standard fields. They do not map to custom fields. Consider using the XML document type if your current document type does not support the field mappings you require.