Developer Resources

Technical Factsheets

Comprehensive technical documentation covering e-invoicing standards, API specifications, and integration guides for developers and system integrators.

E-Invoicing Standards

Download detailed specifications and implementation guides for global e-invoicing standards.

Peppol BIS 3.0

Complete specification for Peppol Business Interoperability Specifications including message types, validation rules, and transport protocols.

  • Invoice & Credit Note specs
  • Order & Catalogue formats
  • AS4 transport profile
View Documentation

UBL 2.1 Standard

Universal Business Language specification for electronic business documents including schema definitions and implementation guidelines.

  • XML Schema definitions
  • Code list specifications
  • Sample documents
View Documentation

EN16931 European Standard

EU electronic invoicing semantic data model and syntax bindings for cross-border B2G and B2B transactions.

  • Core invoice model
  • Syntax bindings (UBL/CII)
  • Validation artefacts
View Documentation

PINT Specifications

Peppol International Invoicing specifications for global e-invoicing including regional extensions and country-specific requirements.

  • A-NZ, JP, MY extensions
  • Singapore InvoiceNow
  • Cross-border rules
View Documentation

GoRoute.ai API Reference

Complete REST API documentation for GoRoute.ai e-invoicing platform including authentication, endpoints, and code samples. See the full API reference.

  • OpenAPI 3.0 spec
  • Code examples (Python, JS)
  • Webhook integration
View API Docs

Validation & Schematron

Comprehensive validation rules and Schematron artefacts for ensuring e-invoice compliance across all supported networks.

  • Schematron rules
  • Error code reference
  • Compliance testing
View Validation Guide

Country-Specific Requirements

Technical specifications for national e-invoicing mandates and local global e-invoicing compliance requirements.

Need Help With Integration?

Our technical team can help you navigate e-invoicing standards and implement compliant solutions for your business. Browse our whitepapers for detailed guidance.

Ready to Get Started?

Book a demo with our team to see how GoRoute can simplify your e-invoicing compliance.

Frequently asked questions

These answers are also published as structured data for search and answer engines.

What is Peppol BIS 3.0? +
Peppol BIS (Business Interoperability Specifications) 3.0 is the standard that defines how business documents like invoices and credit notes are structured and exchanged on the Peppol network. It uses UBL 2.1 XML syntax with EN16931 as the underlying semantic model.
What format does GoRoute use for e-invoices? +
GoRoute uses UBL 2.1 (Universal Business Language) XML format as specified by Peppol BIS 3.0. This is the standard syntax for invoices, credit notes, orders, and catalogues exchanged on the Peppol network and mandated across the EU.
What is the AS4 transport protocol? +
AS4 (Applicability Statement 4) is the secure messaging protocol used by Peppol for document transport between Access Points. It provides reliable delivery with digital signatures, encryption, message receipts, and non-repudiation built into the protocol.
What is PINT and how is it different from BIS? +
PINT (Peppol International) is the next-generation invoice specification designed for non-European markets. While BIS 3.0 is based on EU standards (EN16931), PINT extends support for Asia-Pacific (A-NZ, JP, MY, SG) and other regions with country-specific extensions.
Where can I find UBL XML sample files? +
Sample UBL XML files for invoices, credit notes, and other document types are available in the Peppol BIS 3.0 release package on OpenPeppol's GitHub repository. GoRoute's API documentation at docs.goroute.ai also includes working examples.