How to choose the right Peppol access point: 11 key criteria + template

Choosing the right Peppol access point might seem like a simple checkbox on your e-invoicing to-do list. 

You need to be Peppol-compliant, so you pick a provider and move on… right? But in practice, this decision has far more impact than many teams realise. 

The access point you choose will shape how well your invoice processes run, how easily you can scale, and how quickly things get resolved when something breaks. Especially in SAP environments, where a misaligned setup can silently disrupt downstream flows. 

Below, you’ll find 11 criteria to help you evaluate any Peppol access point provider, based on real-world experience and projects across different industries.  

👉 Want to structure your evaluation? Download the Peppol Access Point Scoring Template and use it to guide your decision. 

    Peppol Integration Capabilities

    Peppol isn’t only about sending a file, it’s about making sure that file fits within your internal processes.  For SAP users, that means checking whether the provider supports: 

    • company-code or sales-org level activations 
    • async processing
    • reprocessing logic
    • integration possibilities with SAP and modules like SAP VIM 

    Some access points offer prebuilt integrations like SAP DRC or our own Doctis connector, that are built for SAP’s structure. Others require manual development or workarounds for seemingly basic needs.

    Peppol Security Standards

    You’re handling sensitive invoice data. So, security is non-negotiable. 

    Check whether the provider: 

    • Uses end-to-end encryption (TLS, HTTPS, API-level security) 
    • Avoids requiring external access to your SAP system
    • Supports user role segregation and audit logging 

    This becomes even more important if: 

    • You work across multiple countries 
    • You process vendor bank info, VAT numbers, or personal data 
    • You have external consultants or hybrid landscapes 

    Global Reach

    Peppol originated in Europe, but many companies operate beyond one country or one format. 

    Check: 

    • Does the provider support formats like UBL, XRechnung, Factur-X, and country-specific variants? 
    • Are these formats included by default or billed separately? 
    • Can they quickly add support when legal requirements shift? 

    Accounts Payable & Receivable (AP/AR)

    Some access points only support Accounts Receivable (outgoing) or Accounts Payable (incoming) flows, not both. 

    That might seem fine for now. But what if your plans change next year? 

    In SAP, AP and AR follow entirely different processing logic. If you need to manage both but your provider only handles one, you’ll be stuck with multiple integrations and overlapping governance. 

    Make sure the provider supports both flows and allows you to activate them separately. 

    Customer Support

    Even the best technical setup can hit a bump. When that happens, you want more than just a generic helpdesk. You want support that understands: 

    • your ERP environment (e.g. SAP or SAP VIM) 
    • your invoice flow (not just XML) 
    • your internal urgency 

    Check: 

    • How fast do they respond—and escalate if needed? 
    • Do they offer portal access, dashboards, or self-service tools? 
    • Is support included or billed separately? 

    Pricing

    It’s tempting to pick the cheapest access point. But price structures vary wildly. 

    Compare: 

    • Is it a flat monthly fee, or volume-based? 
    • Are support, format updates, retries, and testing environments included? 
    • What happens when you add more entities or volumes? 

    One hidden cost we often see: some Access Points charge per message instead of per document. That means even an acceptance response counts as an extra charge. It looks cheaper at first, but in reality it can cost you more. Always compare the cost per document. 

    Innovation & Updates

    Peppol isn’t static. Formats evolve. Local laws change. New security standards emerge. 

    You want a provider that: 

    • Proactively updates their infrastructure 
    • Communicates clearly about upcoming changes 
    • Gives you time to test before go-live 
    • Doesn’t push format changes as paid upgrades 

     Ask how they handled recent shifts like the move to BIS 3.0 or French Factur-X. 

    Experience

    A provider might claim to support SAP or enterprise systems. But can they prove it? 

    Ask for examples of: 

    • Projects with SAP ECC or S/4HANA 
    • Scenarios involving SAP VIM or multi-entity environments 
    • Handling of complex tax or document logic 

    Reputation

    A glossy website doesn’t equal reliability. Ask for references. Not just any customer, someone in your industry, with a similar ERP stack, or your scale. 

    User Interface

    Even with automation, you’ll occasionally need to step in. Check whether the provider offers: 

    • A user-friendly portal to track documents 
    • Clear delivery statuses (sent, delivered, rejected…) 
    • Access control per team or role 

     If your teams are working in SAP, check whether the portal or connector integrates visually—like our Doctis logging cockpit.  

    Document Quality

    Some access points treat documents like technical payloads. Others know the presentation matters. 

    Look at: 

    • PDF formatting quality (clean, branded, readable) 
    • Attachment handling (merge, separate, compress…) 

    In SAP VIM, bad document quality can delay approvals, break indexing logic, or frustrate users trying to review invoices.
    Pro tip: have your AP team review a few sample invoices during the pilot. If they struggle, your users will too. 

    When you’re comparing access points, it’s easy to get lost in the details. 

    That’s why we created a simple scoring template you can use internally.  It helps align IT and finance, surface risks early, and avoid surprises down the line.  

      Let’s talk