Deltek and Adyen integration

What moves between them

The flow runs from Adyen into Deltek. ml-connector consumes Adyen settlement and reconciliation reports and posts the resulting entries into Deltek Vantagepoint's general ledger as journal entries: captured payments, refunds, processing fees, and chargebacks, each mapped to the matching Deltek GL account and organization. Capture, refund, and report-available webhooks trigger the work as soon as activity settles, and a scheduled poll backfills anything a webhook missed. Adyen is treated as a read-only accounting source, so ml-connector never writes payment instructions or financial entries back into Adyen.

How ml-connector handles it

ml-connector stores both credential sets encrypted and sends the Adyen X-API-Key on every request, switching to the merchant-specific live URL prefix when the environment is live, because Adyen has no generic live hostname. On the Deltek side it requests an OAuth2 token with the password grant against the tenant deltekfirst.com URL and refreshes it before the hour expires, and the API user must hold the accounting role with full field visibility or fee and amount values come back as zero. Adyen webhooks arrive signed with HMAC-SHA256, so each notification is verified before processing and the pspReference is used as an idempotency key, since Adyen can deliver the same notification more than once. On REPORT_AVAILABLE, the settlement report is downloaded from the signed URL, parsed, and its lines mapped to Deltek GL accounts and organizations, which are aligned first so every journal line lands on a valid dimension. Because Deltek Vantagepoint has no usable inbound webhook and offers no idempotency header, ml-connector polls it on a schedule and checks for an existing journal entry before posting to avoid duplicates. Adyen rate limits return a too-many-requests error, so ml-connector backs off and retries, and every record carries a full audit trail and can be replayed if a Deltek post fails.

A real-world example

A mid-sized architecture and engineering firm runs Deltek Vantagepoint for project accounting and bills clients for retainers and deposits that it collects online through Adyen. Before the integration, the accounting team downloaded Adyen settlement reports each day and manually entered the gross receipts, refunds, and processing fees into Deltek as journal entries and cash receipts, then spent month-end close reconciling the bank deposit against the payments it was supposed to cover. With Deltek and Adyen connected, each settlement report posts into Deltek automatically, split into the right GL accounts and organizations, so the processing fees are recognized and the deposits already tie out. The daily re-keying step is gone and close starts from reconciled numbers.

What you can do

• •Post Adyen settlement and reconciliation reports into Deltek Vantagepoint's general ledger after every payout.
• •Record captured payments, refunds, processing fees, and chargebacks against the correct Deltek GL accounts and organizations.
• •Receive Adyen capture, refund, and report-available webhooks, verified by HMAC-SHA256, and act on them as activity settles.
• •Authenticate Adyen with its API key and live URL prefix, and Deltek with its OAuth2 tenant token.
• •Poll Deltek on a schedule with retries and a full audit trail on every record, because Deltek cloud cannot be pushed to.

Questions

Which direction does data move between Deltek and Adyen?

The flow is Adyen into Deltek. Settlement reports, captures, refunds, fees, and chargebacks move from Adyen into Deltek Vantagepoint's general ledger as journal entries. Adyen is treated as a read-only accounting source, so ml-connector does not write payment instructions or financial entries back into Adyen.

Does Adyen post invoices or purchase orders into Deltek?

No. Adyen is a payments platform and has no native invoice, purchase order, or vendor objects. What it provides is payment, refund, payout, dispute, and reconciliation report data, and ml-connector maps that activity into Deltek's general ledger as journal entries rather than as AP documents.

How does the integration handle Adyen webhooks and Deltek's lack of webhooks?

Adyen pushes HMAC-SHA256 signed webhooks such as CAPTURE, REFUND, and REPORT_AVAILABLE, which ml-connector verifies and acts on as activity settles. Deltek Vantagepoint offers only workflow-driven outbound webhooks with no usable inbound event API, so ml-connector polls Deltek on a schedule and checks for an existing entry before posting, since Deltek has no idempotency header.