[et_pb_section fb_built=\u201e1\u201c admin_label=\u201eSuccess Storie\u201c _builder_version=\u201e4.16\u201c custom_padding=\u201e0px||0px||true\u201c da_disable_devices=\u201eoff|off|off\u201c locked=\u201eoff\u201c global_colors_info=\u201c{}\u201c da_is_popup=\u201eoff\u201c da_exit_intent=\u201eoff\u201c da_has_close=\u201eon\u201c da_alt_close=\u201eoff\u201c da_dark_close=\u201eoff\u201c da_not_modal=\u201eon\u201c da_is_singular=\u201eoff\u201c da_with_loader=\u201eoff\u201c da_has_shadow=\u201eon\u201c][et_pb_row admin_label=\u201eLine\u201c _builder_version=\u201e4.18.0\u201c custom_padding=\u201e0px||||false|false\u201c global_colors_info=\u201c{}\u201c][et_pb_column type=\u201e4_4\u201c _builder_version=\u201e4.16\u201c custom_padding=\u201c|||\u201c global_colors_info=\u201c{}\u201c custom_padding__hover=\u201c|||\u201c][et_pb_post_title _builder_version=\u201e4.27.4\u201c _module_preset=\u201e41fe5663-30f3-436a-bb9f-42fabe888181\u201c global_colors_info=\u201c{}\u201c][\/et_pb_post_title][et_pb_text admin_label=\u201eKurze Zusam\u00admen\u00adfas\u00adsung\u201c _builder_version=\u201e4.27.4\u201c header_font=\u201c|700|||||||\u201c header_4_letter_spacing=\u201e12px\u201c module_alignment=\u201ecenter\u201c hover_enabled=\u201e0\u201c saved_tabs=\u201eall\u201c locked=\u201eoff\u201c global_colors_info=\u201c{}\u201c sticky_enabled=\u201e0\u201c]<\/p>\n
Currently, hardly any other topic in the field of com\u00admer\u00adcial processes is stirring up as much exci\u00adte\u00adment as the mandatory accep\u00adtance of e\u2011invoice formats, which will come into effect at the beginning of 2025. Even though the focus of e\u2011invoicing is on process auto\u00adma\u00adtion, one element in the process chain for pro\u00adces\u00adsing e\u2011invoices is often neglected: user-fri\u00adend\u00adli\u00adness. This is because where dark pro\u00adces\u00adsing is unde\u00adsi\u00adrable or impos\u00adsible, invoices still have to be checked and approved manually by humans in practice.<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=\u201e4.27.4\u201c header_font=\u201c|700|||||||\u201c header_4_letter_spacing=\u201e12px\u201c module_alignment=\u201ecenter\u201c saved_tabs=\u201eall\u201c locked=\u201eoff\u201c global_colors_info=\u201c{}\u201c]<\/p>\n
Unfort\u00adu\u00adna\u00adtely, the multitude of e\u2011invoicing standards in national and inter\u00adna\u00adtional invoicing also causes problems when it comes to visual receipts. Some of the different e\u2011invoice formats\u2014such as ZUGFeRD\u2014come with a classic paper-based repre\u00adsen\u00adta\u00adtion of the invoice as a PDF, while others\u2014such as the German XRechnung or the Italian Fattura PA\u2014do not.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=\u201e1_2,1_2\u201c _builder_version=\u201e4.18.0\u201c custom_padding=\u201e0px||||false|false\u201c global_colors_info=\u201c{}\u201c][et_pb_column type=\u201e1_2\u201c _builder_version=\u201e4.16\u201c custom_padding=\u201c|||\u201c global_colors_info=\u201c{}\u201c custom_padding__hover=\u201c|||\u201c][et_pb_text _builder_version=\u201e4.27.4\u201c header_font=\u201c|700|||||||\u201c header_4_letter_spacing=\u201e12px\u201c module_alignment=\u201ecenter\u201c saved_tabs=\u201eall\u201c locked=\u201eoff\u201c global_colors_info=\u201c{}\u201c]<\/p>\n
The machine-readable XML format of e\u2011invoices is not par\u00adti\u00adcu\u00adlarly suitable for employees in companies to check the content and technical details of invoices. People want to receive invoice documents in a format they are familiar with for checking purposes. The lack of a visible document signi\u00adfi\u00adcantly disrupts the approval process.<\/p>\n
<\/p>\n
Even if visual receipts are included with the e\u2011invoice, they usually differ signi\u00adfi\u00adcantly in terms of pre\u00adpa\u00adra\u00adtion, design, and layout and are often confusing. Users therefore have to repea\u00adtedly under\u00adstand the respec\u00adtive invoice layout and search for the relevant infor\u00adma\u00adtion for checking \u2013 an effort that should not be unde\u00adre\u00adsti\u00admated.<\/p>\n
<\/p>\n
In addition, the visual receipt that may be supplied is not legally binding and, as practice shows \u2013 espe\u00adci\u00adally with ZUGFeRD \u2013 is often incorrect. Only the digital data record is relevant for pro\u00adces\u00adsing an e\u2011invoice and thus also for manual veri\u00adfi\u00adca\u00adtion and approval.<\/p>\n
<\/p>\n