I need to streamline how our SAP system produces Peppol-compliant eInvoices. At the moment, we are using the standard SAP eDocument tools—Electronic Document Framework (EDF) / Electronic Document Service (EDS)—but I have no firm confirmation yet whether the underlying system will ultimately be SAP HANA or SAP B1, so the solution must cope with either environment. Scope of work We already have the Peppol XML schema and a mapping guide. Your task is to extract every required field from the SAP sales-invoice record, build the XML exactly to that template, convert it to Base64, and then push it through a REST-based POST call. The service will return success or error codes; those responses need to be captured, logged and surfaced clearly so we can reconcile invoices that fail. Key expectations • End-to-end code or configuration that runs inside, or callable from, SAP eDocument (EDF/EDS) • Accurate field mapping to the provided Peppol XML structure • Reliable Base64 encoding and transmission over HTTPS (no password should be used) • Response handling that distinguishes success from failure and stores the returned messages for audit purposes • Clear, concise technical documentation and one short hand-over session Acceptance criteria The solution will be considered complete when a sample batch of invoices is automatically: 1. extracted from our test SAP client, 2. transformed into valid Peppol XML that passes online validation, (format details will be discussed when selected). 3. encoded, transmitted via the supplied POST endpoint, and 4. logged with verifiable response messages. Please centre your proposal on your direct experience with SAP eDocument, SAP HANA or SAP B1 integrations, Peppol XML generation, and API work; examples of similar projects will help me choose quickly.