Support Center

How Can We Help You?

Find answers to common questions, troubleshooting guides, and resources to get the most out of GoRoute.ai.

Getting Started

1 Create Your Account

Sign up for a GoRoute.ai account to access the dashboard and API credentials.

  • Visit app.goroute.ai to register
  • Complete your organization profile
  • Verify your email address

2 Configure Your Peppol ID

Set up your Peppol participant identifier to start receiving e-invoices.

  • Choose your identifier scheme (GLN, VAT, etc.)
  • Register your participant ID
  • Configure document types to receive

3 Integrate with Your System

Connect GoRoute.ai to your accounting or ERP system using our API.

  • Generate API keys in the dashboard
  • Review API documentation
  • Test in sandbox environment

4 Send Your First Invoice

Submit your first e-invoice through the Peppol network.

  • Create invoice in UBL format or use our converter
  • Validate against Peppol BIS 3.0 rules
  • Submit and track delivery status

Common Issues & Solutions

Invoice validation failed with Schematron errors

Schematron validation errors indicate business rule violations in your invoice. Common causes include:

  • Missing mandatory fields - Ensure all required elements like buyer/seller details, tax information, and line items are complete.
  • Invalid tax calculations - Verify that line totals, tax amounts, and invoice totals are mathematically consistent.
  • Invalid code values - Check that currency codes, unit codes, and country codes use ISO standards.

Use our validation API to test invoices before sending.

Recipient not found in Peppol network

This error occurs when the recipient's Peppol ID cannot be located in the network. To resolve:

  • Verify the identifier - Confirm the recipient's Peppol ID format and scheme (e.g., 0088:1234567890123).
  • Check document type support - The recipient may not be registered to receive the specific document type you're sending.
  • Contact the recipient - They may need to register with a Peppol Access Point or update their SMP registration.

API authentication errors (401/403)

Authentication issues typically stem from API key configuration:

  • Check API key format - Ensure you're using the correct key in the X-API-Key header.
  • Verify key permissions - Your API key may not have access to the requested resource.
  • Key expiration - API keys may have been rotated. Generate a new key from the dashboard.
  • Rate limiting - You may have exceeded your API quota. Check your usage in the dashboard.

Invoice delivery status shows "pending" for too long

Extended pending status can occur due to network or recipient issues:

  • Recipient Access Point delay - The receiving AP may be experiencing high load or temporary issues.
  • Network connectivity - There may be routing issues between Access Points.
  • Retry mechanism - GoRoute.ai automatically retries failed deliveries. Check the transaction log for detailed status.

If status remains pending beyond 24 hours, contact support with your transaction ID.

Country-specific compliance requirements (XRechnung, FatturaPA, etc.)

Different countries have specific e-invoicing requirements (CIUS):

  • Germany (XRechnung) - Requires Leitweg-ID for B2G invoices.
  • Italy (FatturaPA) - Must be processed through SDI with specific codice destinatario.
  • France (Factur-X) - May require specific profile levels and attachments.

Visit our country compliance pages for specific requirements.

Additional Resources

Still Need Help?

Our support team is ready to assist you with any questions about e-invoicing, integration, or compliance.