Connected to SAP, your ERP, and site access control
Verdana integrates with the systems where operations already live, so that third-party management is not an island fed by manual data entry. The most common integration is with the ERP: synchronization of the vendor master, cost centers, purchase orders, receipts, and billing documents, in both directions and with conflict control.
With SAP, the typical use case is this: a vendor is registered and qualified in Verdana—questionnaire, verification, documentation, approval—and only once approved is it created or activated in SAP with its data already validated. From then on, the vendor's risk and document status in Verdana determines how it operates in the ERP, and orders, receipts, and invoices flow without anyone retyping them. The same pattern applies to other ERPs on the market.
The second group of integrations is physical access control: the site's turnstiles, readers, and visitor systems, connected via API so that the authorization issued in Verdana enables actual entry and a document-related suspension blocks it. The third is verification sources—restricted-party lists, public registries, and tax and social security rolls—which feed due diligence and continuous monitoring depending on the country.
Where there is no connector, there is an API. Verdana exposes an API so the customer's IT team can build whatever it needs, and supports file-based integrations for legacy systems that offer no other route.
How the systems connect
How each product family integrates
- Compliance: approval of the third party in Verdana gates its creation or activation in the ERP. Only third parties that have passed due diligence operate in the transactional system, and a change in risk status is reflected in the ERP.
- Procurement: two-way synchronization of the vendor master, cost centers, purchase orders, receipts, and invoices, with conflict control so that there are never two diverging masters.
- Contractor management: the document status of the company and of each person enables or blocks operations, and integrates via API with the site's physical access control: if the documentation lapses, access lapses with it.
- Third-party management: a single third-party record—data, contacts, contracts, external users—that feeds and reconciles with the ERP master data, available to every department that deals with that third party.
ERPs Verdana integrates with
Verdana integrates with the leading ERPs on the market. The pattern is the same with any of them: the third party is verified and approved in Verdana, and only then created or activated in the ERP with data that has already been validated; from then on, its document and risk status determines what the ERP can do with it.
The connection is two-way—vendor master, cost centers, orders, receipts, and invoices. When a system does not offer a native connector, Verdana integrates via API or by file.
Frequently asked questions
What systems does Verdana integrate with?
With ERPs, including SAP, for the vendor master, cost centers, orders, and billing documents; with physical access control systems via API; and with verification sources depending on the country. When no connector is available, there is an API, as well as file-based integration for legacy systems.
How does the SAP integration work in practice?
The vendor is registered, verified, and approved in Verdana, and only once approved is it created or activated in SAP with data that has already been validated. From then on, its document and risk status determines how it operates, and orders, receipts, and invoices flow with no double entry.
Can Verdana connect to turnstiles and site access systems?
Yes, via API, so that the authorization issued in the platform enables actual entry and a document-related suspension blocks it, with no lists emailed to the gatehouse.