Integration Engineer

Overview

The Integration Engineer owns all data pipeline delivery between the client s ERP systems and the Flick e-invoicing platform. This is a specialist role that requires both ERP functional knowledge and structured invoice schema expertise. The candidate must understand why an ERP generates a particular field value and exactly how that value must be transformed to satisfy UBL 2.1, PINT, or a regional e‑invoicing schema.

This is not a general API integration role.

In the implementation phase this engineer performs field‑level ERP‑to‑schema mapping, configures Flick s integration endpoints, builds the test data library for SIT and UAT, and drives integration testing through to production sign‑off. Post go‑live they handle new integration scope—additional ERP instances, new business units, new invoice flow types—and support the Senior Platform Engineer with any application‑level integration issues.

Has mapped ERP invoice data to a UBL 2.1, PINT, or EDIFACT schema in a production e‑invoicing deployment—not just worked with XML generally. Knows what mandatory, conditional, and optional mean in a compliance schema and has debugged validation failures at field level. Understands ERP invoice data structures—knows where SAP, Oracle, or Dynamics stores supplier identifiers, tax codes, line amounts, and document references, and how to extract and transform them correctly.

Experienced with Peppol Participant  and party identifier standards (GLN, VAT number, DUNS, Peppol —0192, 0088, etc.) and has resolved party lookup failures in a production Peppol context. Has delivered end‑to‑end API or SFTP integrations connecting an ERP to a Peppol Access Point or national e‑invoicing platform—owns the full flow from authentication through to invoice acknowledgement handling. Detail‑oriented data mapper: produces clean, accurate mapping documents that both engineers and finance stakeholders can follow, and works systematically through large ERP field catalogues without losing accuracy.

Comes from an environment where e‑invoicing compliance failures had real consequences—mandate deadlines, tax authority rejections, or live billing disruptions.