The project \u201cA&K Project ERP Software Testing\u201d<\/strong> aimed to systematically test comparatively evaluate ERP and accounting software<\/strong> for commercial processes in micro-enterprises (SOHO), self-employed professionals, and freelancers.<\/strong> The focus was not on the functional completeness of the tools, but on the quality of input validation,<\/strong>, die the stability of typical use cases<\/strong> and usability<\/strong> in day-to-day work.<\/p>\n\n\n\n Six solutions were examined: Sage 50 Connected, SevDesk, Papierkram, Zoho Books, Buchhaltungsbutler and MonKey Office 2022.<\/strong>.<\/p>\n\n\n\n ERP and accounting solutions form the basis for key commercial processes such as invoice creation, quotation management, master data maintenance, document management and payment processing.<\/strong>The demand is particularly high among SOHO users and micro-enterprises, while resources such as time, budget, and IT expertise are often limited.<\/p>\n\n\n\n In practice, this leads to typical challenges such as:<\/p>\n\n\n\n The project therefore addressed the question of how robust and user-friendly<\/strong> commercially available solutions actually are when handling standard business processes.<\/p>\n\n\n\n The project was organized as a team effort, with each team member testing one software solution and documenting the results in a structured manner.<\/p>\n\n\n\n Methodologically, a black-box testing approach<\/strong> was used, meaning there was no access to the underlying code base. This was combined with tests based on equivalence classes.<\/strong>Standardized input values included:<\/p>\n\n\n\n These test values were applied to input fields in key use cases<\/strong> and compared with the expected system behavior. The tests clearly showed that even established systems exhibit recurring weaknesses, particularly in input validation and plausibility checks.<\/strong>Typical issues included:<\/p>\n\n\n\n At the same time, the analysis confirmed that:<\/p>\n\n\n\n The results were consolidated in a comparison matrix and presented as an overall evaluation. The following solutions received particularly strong ratings:<\/p>\n\n\n\n A recurring finding across almost all solutions: The project demonstrates how methods from business informatics, including testing methodology, comparative evaluation, and quality criteria, can be applied to real-world software selection and implementation decisions. The specific added value lies in:<\/p>\n\n\n\n The project therefore contributes to the quality assurance of digital commercial processes<\/strong> and supports small organizations in selecting suitable systems for their day-to-day operations.<\/p>","protected":false},"excerpt":{"rendered":" Projekt\u00fcberblick Das Projekt \u201eA&K Projekt ERP-Softwaretests\u201c hatte das Ziel, ERP- und Buchhaltungssoftware f\u00fcr kaufm\u00e4nnische Vorg\u00e4nge in Kleinstunternehmen (SOHO), bei Selbstst\u00e4ndigen und Freiberuflern systematisch zu testen und vergleichbar zu bewerten. Im Mittelpunkt stand dabei nicht die funktionale Vollst\u00e4ndigkeit der Tools, sondern die Qualit\u00e4t der Eingabevalidierung, die Stabilit\u00e4t typischer Use Cases sowie die Benutzerfreundlichkeit im Arbeitsalltag. Untersucht wurden sechs L\u00f6sungen: Sage 50 Connected, SevDesk, Papierkram, Zoho Books, Buchhaltungsbutler und […]<\/p>\n","protected":false},"author":6,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-744","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/pages\/744","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/comments?post=744"}],"version-history":[{"count":3,"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/pages\/744\/revisions"}],"predecessor-version":[{"id":1205,"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/pages\/744\/revisions\/1205"}],"wp:attachment":[{"href":"https:\/\/www.widg.de\/en\/wp-json\/wp\/v2\/media?parent=744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n\n\n\nInitial Situation<\/h2>\n\n\n\n
\n
\n\n\n\nApproach & Methodology<\/h2>\n\n\n\n
\n
The approach included:<\/p>\n\n\n\n\n
\n
\n\n\n\nKey Findings<\/h2>\n\n\n\n
\n
\n
\n\n\n\nResults & Comparison<\/h2>\n\n\n\n
\n
The functionality of input fields<\/strong> (validation, plausibility checks, restrictions) performed weakest compared with UX and basic functionality and therefore represents the greatest potential for quality improvement.<\/p>\n\n\n\n
\n\n\n\nAdded Value & Knowledge Transfer<\/h2>\n\n\n\n
\n