Home

⌘K
  2. Home
  4. Docs
  6. Home
  8. Client Profile
  10. PEPPOL e-documents

PEPPOL e-documents

Purpose

Use the PEPPOL page to configure the client’s PEPPOL / XML e-invoice integration in Resico ERP. This page controls whether PEPPOL is enabled, stores the API environment and authorization values, defines the XML address scheme, and maintains unit and VAT mappings between Resico and PEPPOL.

Roles involved

  • System administrator
  • Finance manager
  • E-invoicing / integration specialist

Preconditions

  • You need permission to edit Client profile.
  • The client must already know whether the test or production PEPPOL environment should be used.
  • The PEPPOL username, API key and address scheme must be available before setup.
  • Resico units of measure and VAT groups should already exist because this page maps them to PEPPOL values.

Navigation path

Client profile → PEPPOL

Step-by-step procedure

  1. Open Client profile → PEPPOL.
  2. Enable the integration using Enable PEPPOL.
  3. In the Authorization settings section, select the PEPPOL API environment.
    • Test
    • Production
  4. Enter the authorization values:
    • Username
    • API key
  5. In the XML settings section, select the Address scheme.
  6. In the Mapping settings section, review all Resico Units listed on the left side and map each one to the corresponding PEPPOL unit value.
  7. Review all Resico VAT rows listed on the page and map each VAT to the corresponding PEPPOL VAT value.
  8. For VAT rows where the Resico VAT percentage is 0, review the additional exception mapping field that appears below the main VAT mapping and select the appropriate extra PEPPOL VAT value if required.
  9. In the Other settings section, enable XML mail if XML-based mail delivery should be used in the e-invoice process.
  10. Click Save to apply the configuration.
  11. Use Cancel to leave the page without saving.

Required fields

  • PEPPOL API environment
  • Username
  • API key
  • Address scheme
  • Unit mapping for each listed Resico unit
  • VAT mapping for each listed Resico VAT row

Additional required mapping when applicable:

  • Extra VAT mapping for zero-VAT rows that require the second PEPPOL VAT selector

Validation rules

  • PEPPOL API environment must be selected from the available list.
  • Address scheme is mandatory.
  • Each listed Resico unit should be mapped to one PEPPOL unit value.
  • Each listed Resico VAT row should be mapped to one PEPPOL VAT value.
  • For VAT rows with 0% VAT, the additional PEPPOL VAT selector may also need to be completed depending on the e-invoice scenario.
  • The page uses dynamic PEPPOL value lists for address scheme, units and VAT mappings.

Exceptions

  • The available PEPPOL values for address scheme, units and VAT mappings are loaded dynamically and can vary by environment.
  • The additional VAT exception field appears only for Resico VAT rows where the VAT percentage is zero.
  • The page contains some commented legacy fields in code for username, password, port and export frequency, but those are not part of the active page workflow.

Common errors

  • The wrong API environment is selected, causing the client to point to the wrong PEPPOL endpoint.
  • Username or API key is entered incorrectly, preventing authorization.
  • Unit mappings are incomplete, causing XML export problems for products that use unmapped units.
  • VAT mappings are incomplete or incorrect, causing invoice XML validation errors.
  • The zero-VAT exception mapping is missed for a VAT row that requires it.

Troubleshooting

  • If PEPPOL export fails, first verify the selected PEPPOL API environment, Username and API key.
  • If XML validation errors occur, review the Address scheme and check all unit and VAT mappings carefully.
  • If issues affect only zero-VAT transactions, confirm whether the additional VAT exception field was completed for the relevant VAT row.
  • After any mapping change, test the configuration with one controlled e-invoice before using it broadly.

Questions / Gaps

  • The PEPPOL value lists are loaded dynamically, so the exact selectable values for address scheme, units and VATs should be confirmed directly in the live tenant.
  • The exact business meaning of the second VAT selector for zero-VAT rows should be confirmed with a real PEPPOL export scenario.
  • It should also be confirmed whether enabling XML mail affects only delivery method or also changes XML generation behavior.