Field order change for XML invoices

You can rearrange the field order for buyer, supplier and invoice sections in the PDF generated from XML invoices based on your preferences. This preference can be set in the XMLInvoiceFieldOrderConfiguration.xml file located in the GlobalPath folder.

The configuration file has a default field order for buyer, supplier, and invoice sections as shown below.

<Buyer>
Name,Identifier,BuyerVATRegistrationNumber,CorporateGroupNumber,Description,CountryCode,
CountryName,BuyerAddressPostalCode,Street,StreetSupplement,POBox,City,TelephoneNumber,
FaxNumberBuyerTaxNumber1,BuyerTaxNumber2,Email
</Buyer>
<Supplier>
Name,Identifier,Description,POBox,Street,StreetSupplement,SupplierAddressPostalCode,City,
CountryCode,CountryName,TelephoneNumber,FaxNumber,SupplierVATRegistrationNumber,SupplierTaxNumber1,
SupplierTaxNumber2,CorporateGroupNumber,Email
</Supplier>
<Fields>
InvoiceCredit,InvoiceNumber,InvoiceDate,InvoiceDueDate,InvoiceTotalVatExcludedAmount,
InvoiceTotalVatRatePercent,InvoiceTotalVATAmount,InvoiceTaxAmount1,InvoiceTaxAmount2,
InvoiceTaxAmount3,InvoiceTaxAmount4,InvoiceTotalVatIncludedAmount,
InvoiceTotalVatIncludedAmountSpelled,InvoiceCurrency,InvoiceOrderNumber,SupplierAccountNumber1,
SupplierAccountNumber2,SupplierAccountNumber3,SupplierAccountNumber4,SupplierIBAN1,SupplierIBAN2,
SupplierIBAN3,SupplierIBAN4,SupplierSWIFT1,SupplierSWIFT2,SupplierSWIFT3,SupplierSWIFT4,
SupplierBankCodeNumber1,SupplierBankCodeNumber2,SupplierBankCodeNumber3,SupplierBankCodeNumber4,
SupplierBankClearingNumber,PaymentReferenceNumber,PaymentType,DeliveryDate,DeliveryTerms,
DeliveryNote,DeliveryCost,DeliveryCostPackaging,DeliveryCostInsurance,DeliveryCostToll,
DeliveryCostPostage,PaymentTerms,PaymentTermsInterest,InvoiceDiscountAmount,InvoiceDiscountPercent,
BuyerContactPersonName,BuyerContactReference,BuyerVATRegistrationNumber,BuyerTaxNumber1,
BuyerTaxNumber2,BuyerAddressPostalCode,SupplierVATRegistrationNumber,SupplierTaxNumber1,
SupplierTaxNumber2,SupplierAddressPostalCode,InvoiceBaselineDate,InvoicePostingDate,
InvoicingPeriodStart,InvoicingPeriodEnd,Barcode,AddressName,AddressOptionalName,AddressStreet,
AddressPostalCity,AddressPostalCode,EsrAmount,EsrNumber,EsrReference,LIT_RowIdentifier,
LIT_ArticleIdentifier,LIT_ArticleName,LIT_OrderNumber,LIT_DeliveredQuantity,
LIT_DeliveredQuantityUnitCode,LIT_UnitPriceAmount,LIT_VatRate,LIT_VatAmount,LIT_DiscountPercent,
LIT_DiscountAmount,LIT_VatExcludedAmount,LIT_VatIncludedAmount,VAT_BaseAmount,VAT_RatePercent,
VAT_RateAmount,VAT_TotalAmount,VAT_Currency,BAT_SupplierBankCodeNumber,BAT_SupplierIBAN,
BAT_SupplierAccountNumber,BAT_SupplierAccountNumberType,BAT_SupplierBankClearingNumber,InvoiceNote,
AmountRounding
</Fields>

You can change this order as per your preferences.

For example, in the following configuration file, the field orders for buyer, supplier, and invoice sections are set based on preferences.

<XMLProfile name = "Faktura_Tax">
<Buyer>
Identifier,BuyerVATRegistrationNumber,CorporateGroupNumber,Description,CountryCode,CountryName,
BuyerAddressPostalCode,Street,StreetSupplement,POBox,City,TelephoneNumber,FaxNumber,
BuyerTaxNumber1,BuyerTaxNumber2,Email,Name
</Buyer>
<Supplier>
Name,Identifier,Description,POBox,Street,StreetSupplement,SupplierAddressPostalCode,City,
CountryCode,CountryName,TelephoneNumber,FaxNumber,SupplierVATRegistrationNumber,
SupplierTaxNumber1,SupplierTaxNumber2,CorporateGroupNumber,EMail
</Supplier>
<Fields>
InvoiceCredit,InvoiceNumber,InvoiceDate,InvoiceDueDate,InvoiceTotalVatExcludedAmount,
InvoiceTotalVatRatePercent,InvoiceTotalVATAmount,InvoiceTaxAmount1,InvoiceTaxAmount2,
InvoiceTaxAmount3,InvoiceTaxAmount4,InvoiceTotalVatIncludedAmount,
InvoiceTotalVatIncludedAmountSpelled,InvoiceCurrency,InvoiceOrderNumber,SupplierAccountNumber1,
SupplierAccountNumber2,SupplierAccountNumber3,SupplierAccountNumber4,SupplierIBAN1,SupplierIBAN2,
SupplierIBAN3,SupplierIBAN4,SupplierSWIFT1,SupplierSWIFT2,SupplierSWIFT3,SupplierSWIFT4,
SupplierBankCodeNumber1,SupplierBankCodeNumber2,SupplierBankCodeNumber3,SupplierBankCodeNumber4,
SupplierBankClearingNumber,PaymentReferenceNumber,PaymentType,DeliveryDate,DeliveryTerms,
DeliveryNote,DeliveryCost,DeliveryCostPackaging,DeliveryCostInsurance,DeliveryCostToll,
DeliveryCostPostage,PaymentTerms,PaymentTermsInterest,InvoiceDiscountAmount,InvoiceDiscountPercent,
BuyerContactPersonName,BuyerContactReference,BuyerVATRegistrationNumber,BuyerTaxNumber1,
BuyerTaxNumber2,BuyerAddressPostalCode,SupplierVATRegistrationNumber,SupplierTaxNumber1,
SupplierTaxNumber2,SupplierAddressPostalCode,InvoiceBaselineDate,InvoicePostingDate,
InvoicingPeriodStart,InvoicingPeriodEnd,Barcode,AddressName,AddressOptionalName,AddressStreet,
AddressPostalCity,AddressPostalCode,EsrAmount,EsrNumber,EsrReference,LIT_RowIdentifier,
LIT_ArticleIdentifier,LIT_ArticleName,LIT_OrderNumber,LIT_DeliveredQuantity,
LIT_DeliveredQuantityUnitCode,LIT_UnitPriceAmount,LIT_VatRate,LIT_VatAmount,LIT_DiscountPercent,
LIT_DiscountAmount,LIT_VatExcludedAmount,LIT_VatIncludedAmount,VAT_BaseAmount,VAT_RatePercent,
VAT_RateAmount,VAT_TotalAmount,VAT_Currency,BAT_SupplierBankCodeNumber,BAT_SupplierIBAN,
BAT_SupplierAccountNumber,BAT_SupplierAccountNumberType,BAT_SupplierBankClearingNumber,InvoiceNote,
AmountRounding
</Fields>
</XMLProfile>

In the PDF generated by the Collector, the field order for buyer, supplier, and invoice sections is displayed as configured in the configuration file. Any fields not included in the configuration file are added at the end section of the generated PDF.

  • If the configuration file is not in the GlobalPath folder, or unresponsive messages are found during processing, the default order is used in the PDF.

  • If multiple entries are found within the same profile in the configuration file, the Collector only considers the first entry and ignores the others.

  • If multiple buyer, supplier, and invoice sections are found in the same profile in the configuration file, the Collector prioritizes the first section and ignores the others.

  • If the fields are not in proper tags, such as, <Buyer></Buyer>, the default buyer order is used from the configuration file.

  • If duplicate entries of the same field exist under the same profile, they are not considered.