Connect Timewriter via the legacy SOAP API (v3.1) with connection keys to send outgoing invoices via Peppol.
You connect Timewriter with eConnect in 2026 via the legacy SOAP API (version 3.1). The integration uses connection keys for authentication. After configuration, outgoing invoices are sent via eConnect over Peppol. There is no incoming route via this integration: receiving does not go through the Timewriter connector.
Make sure you have the following:
Follow the general steps in Creating connection keys where needed.
Upon successful delivery, the integration returns an ExternalId (the XCNIN number of the document). Save this as an internal reference to find documents later.
You can track the status of outgoing documents in two ways:
GetOutboxDocumentStatus on the legacy API (status only, without full document)See SOAP API: sending invoices for context on sending and status tracking on the SOAP API.
No, the Timewriter integration is exclusively focused on sending outgoing invoices via Peppol. There is no incoming route via the Timewriter connector.
The OrganisationID is the XCNL, XCBE or XC number of your organisation in eConnect. You can find this in the eConnect platform under Organisations. This number is required for the integration in addition to the connection keys.
You can track the status in two ways: via the eConnect platform (Outbox and document overviews) or via the SOAP method GetOutboxDocumentStatus. Upon successful sending, you receive an ExternalId (XCNIN number) as a reference.
Need help with the integration? Contact support.
Go to the platform