Portal invoice
The supplier generates the invoice in ESS Hub from the acknowledged shipment and sees its status afterwards.
WebEDISupplier Invoicing & AP
From supplier invoice to Accounts Payable.
Give suppliers a structured invoice process while connecting portal, EDI, API and document-based invoices to the same enterprise AP workflow.
Portal invoiceEDI · INVOICPDF / documentAPI
Different invoice channels. One AP process.ESS Hub is the supplier-facing invoice layer. Behind it, the enterprise runs one Accounts Payable process, connected to SAP and other ERP systems.
SAP ECCSAP S/4HANAPortal invoiceEDIFACT INVOICPDF / documentAPIFI / APLogistics Invoice VerificationDocument intelligence
The supplier invoice journey
Create the invoice from the transaction that came before it.
Suppliers should not rebuild information that already exists in the purchasing and logistics process. The invoice follows the order and the shipment; submission and status stay in the same workspace.
01Purchase orderOrder · call-off
02Delivery / ASNDESADV acknowledged by the customer
03Generate invoicePer acknowledged shipment
04Supplier reviewReferences and amount
05SubmitElectronic INVOIC sent
06StatusPosted · paid · expected payment
Supplier invoice generation
The invoice is created from the shipment, not typed in.
Once the customer has acknowledged the DESADV, the shipment becomes invoiceable. The supplier generates the electronic INVOIC for that shipment in ESS Hub; the message carries the order and delivery references the customer already knows.
Invoice per acknowledged shipment
Invoicing follows the acknowledged DESADV; shipments not yet acknowledged wait in a separate list.
Order and delivery references
Transport order and ASN number on every invoice.
Invoice number
Generated with the invoice, visible to both sides.
Electronic INVOIC
Sent to the customer as a structured EDI message.
View EDI
The supplier can open the message the customer received.
Same workspace
Invoicing sits next to shipments, labels and documents, not in a separate tool.
Invoicing: electronic INVOIC per acknowledged shipmentSupplier view · real product UI
Invoice generation
Generated from transaction data, as part of the supplier workflow.
Invoice generation is a step in the supplier's process, not a separate accounting application.
Existing transaction dataOrder · acknowledged shipment
ESS HubBuilds the invoice
Structured invoiceINVOIC
Electronic representationMessage the customer can process
SubmissionSent · visible in the invoice list
Multiple invoice channels
Different invoice channels. One AP process.
ESS Hub supports supplier invoice collaboration through the portal, and the ESS technology ecosystem brings EDI, API and document-based invoices into the same enterprise AP process.
Supplier portalStructured invoiceGenerated in ESS Hub from the acknowledged shipment.→ ESS Hub
EDIINVOIC · structured EDI invoiceMature EDI suppliers keep sending invoices electronically; no portal required.→ ESS Hub / integration
PDF / documentInvoice documentDocument invoices are read into structured invoice data.→ Document intelligence
APIStructured invoiceSystem-to-system from the supplier's own system.→ ESS Hub / integration
One invoice processESS Hub · integration · document intelligence
ValidationPO / delivery contextMatchingExceptionsApproval
SAP / ERP · Accounts PayableSAP ECC · SAP S/4HANA · other ERP systems
The invoice channel changes.
The enterprise AP process does not.
Channels
EDI suppliers stay on EDI. Document suppliers stay on documents.
No supplier is forced into the portal. The channel is chosen by the supplier's maturity; the enterprise receives structured invoice data either way.
EDI invoice · INVOIC
Established EDI relationships exchange EDIFACT INVOIC messages directly; ESS Hub validates the structure during onboarding.
EDIFACTPDF / document invoice
Document invoices (PDF) are captured and turned into structured invoice data before they enter the AP process. The supplier sees the same invoice status as for any other channel.
PDF / documentOne AP process
After the channels converge, one enterprise process.
The stages every invoice passes through on the enterprise side, whatever channel it arrived by. Which stages run automatically depends on your AP setup and ERP.
01Invoice receivedFrom any channel
02ValidationStructure and references
03PO / delivery contextOrder and shipment known
04MatchingAgainst order and receipt
05ExceptionsBlocked invoices
06ApprovalYour AP rules
07ERP / AP postingSAP FI / AP
08StatusBack to the supplier
Purchase order / delivery context
The invoice does not arrive alone.
ESS Hub already knows the supplier process that came before the invoice: the order, the shipment and the acknowledged DESADV. The enterprise sees each invoice with its purchase order and delivery note, its amount, its status and the expected payment.
Purchase order
Every invoice carries the order or transport order it belongs to.
Delivery note / ASN
The shipment the invoice was generated from.
Acknowledged DESADV
Invoicing only starts once the customer has acknowledged the shipment.
Amount and dates
Received date and expected payment date per invoice.
One list for finance
Open, blocked and paid invoices with export for the finance team.
Same status on both sides
What the enterprise sees is what the supplier sees.
Invoices with purchase order and delivery note contextEnterprise view · real product UI
Invoice status for suppliers
No more “have you received my invoice?”
The supplier sees the status of each invoice and the expected payment in ESS Hub, instead of asking Accounts Payable by e-mail.
Open · blocked · paid
Open invoices, blocked invoices and invoices paid in the last 30 days at a glance.
Status per invoice
Posted or paid, with the date received.
Expected payment date
Per invoice, next to the amount.
Upcoming and paid payments
What is due, what was paid and when.
Remittance advice
Downloadable per paid invoice.
Payment terms
Payment dates projected from the agreed terms.
Payments: upcoming and paid, with remittance adviceSupplier view · real product UI
SAP / ERP integration
Connected to Accounts Payable behind the process.
Invoices that enter through ESS Hub, EDI, API or document processing end up in the same ERP. The integration layer exchanges structured invoice data with SAP FI / AP and logistics invoice verification, or with other ERP environments.
Deep SAP expertise. Open ERP architecture.
ESS Hub is developed by EDI & SAP Solutions SRL, an enterprise integration company working with SAP and EDI landscapes since 2013. SAP is the primary integration expertise; the architecture is ERP-agnostic and connects through EDI, IDoc, API, files and integration middleware.
Explore SAP IntegrationPrimary
SAP ECCSAP S/4HANA
Also
Other ERP environments
Integration concepts
FI / APMM · Logistics Invoice VerificationIDocAPIEDIFilesIntegration middleware
Real product UI
Invoice screens, shown as they are.
Screens from ESS Hub. Demo data, real application.
ESS ecosystem
One integration company. Specialized products.
ESS Hub is the supplier collaboration product of EDI & SAP Solutions. The other ESS products come from the same enterprise integration practice and cover other parts of the enterprise process.
ESS Hub
Supplier portal, WebEDI and structured supplier processes: orders, shipments, quality, invoices.
Supplier collaborationDrelo.ai
Document intelligence and Accounts Payable automation — a separate product of the ESS ecosystem.
Document intelligence · AP automationDrelo.aiEDI & SAP Solutions
SAP, EDI and middleware integration since 2013; the team behind ESS Hub and Drelo.ai.
Enterprise integrationedisapsolutions.comRequest a demo
See the invoice journey with your own suppliers.
A live walkthrough from acknowledged shipment to INVOIC, AP status and payment visibility, connected to your SAP landscape.