Watch
Avalara E-Invoicing & Live Reporting in action.
See how the ELR Connector works with SAP: how an invoice leaves your SAP system, is converted to what each country’s tax authority expects, and comes back accepted.
1. Avalara ELR Connector for SAP S/4HANA
An overview of the ELR Connector on SAP S/4HANA: how invoices are extracted from SAP, mapped to each mandate, submitted through Avalara and written back with their acceptance status and government ID.
Need a specific scenario covered? Send it to support and we will walk you through it.
What we cover
Everything between your SAP system and the tax authority.
Technical and functional support for the ELR Connector, the Avalara platform and the e-invoicing and live reporting obligations your SAP documents must meet, country by country.
Country mandates and onboarding
Activation and setup per mandate: Italy, Malaysia, India, France, Belgium, Germany, Poland, Portugal, Spain, Saudi Arabia and the Peppol network. Registrations, government connections and credentials.
Document mapping and dataset issues
Missing or wrong fields in your invoice data (customers, lines, taxes, totals), format mapping per mandate, and the special business cases each country handles differently.
Rejected or failed submissions
Documents rejected by the tax authority or the network, format and business rule failures, duplicates, and submissions that never reached the Avalara platform.
SAP integration layer
SAP Business One, SAP Business ByDesign, SAP S/4HANA and SAP ECC: OData and Gateway services, the ELR Connector, outbound invoice extraction, inbound supplier e-invoices posted as drafts, and the status write-back into SAP.
Monitoring and status reconciliation
Documents stuck in pending, acceptance status or government ID not written back to SAP, differences between the Avalara platform and your ERP, and periodic checks that no document is left behind.
Configuration changes
New legal entities, new countries, new document types, routing rules and changes in how invoices are selected and sent from your SAP system.
How it works
Send us the case, we take it from there.
The faster we can reproduce the issue, the faster it gets solved. Include the SAP document number, the country, the mandate and the status shown in the Avalara platform.
Email info@tax-bridge.ioFAQ
Common ELR support questions.
Usually a mandate rule the invoice does not meet: a missing or invalid identifier (VAT number, Peppol endpoint, registration code), a tax category or rate the country does not accept, a date or reference outside the allowed range, or a duplicate document number. We read the rejection returned by the authority, locate the field in your SAP data or in the mapping, correct it and resubmit.
Pending means the authority has not answered yet or the status has not been written back to SAP; error means the submission failed before or at the Avalara platform. We check the connector log and the Avalara platform, find where the document stopped and either resubmit it, correct the data or escalate to Avalara if the delay is on their side.
The entity is set up in the Avalara platform under the mandate, your SAP system is extended so its invoices are selected and extracted, the field mapping is reviewed against the country’s rules and real test transmissions are run through the Avalara sandbox before go-live.
We cover configuration inside the Avalara platform (entities, mandates, routing, credentials, Peppol identifiers) and escalate to Avalara Support or your Account Manager when the issue is on their side. The Avalara licence and billing stay with Avalara.
Yes. We recommend keeping an SAP test system connected to the Avalara sandbox so every mapping and configuration change is validated with real test transmissions before it reaches production.
Need help now?
Open an ELR support request.
Include the SAP document number, the country and mandate, and the status shown in the Avalara platform, and we will come back with a diagnosis.
Email info@tax-bridge.io