Connecting an API Verifactu to Perfex CRM requires deciding how CRM invoicing relates to the external service. The goal is a workflow staff can understand and an integration that remains maintainable as the CRM, PHP or API changes. This article describes an integration architecture; it does not announce a ready-to-install module.
Organise the integration as a module
Perfex CRM documentation describes modules and an action and filter system. Check which extension points exist in the installed version before selecting the invoicing event. Keeping the connector in a module helps locate its configuration and responsibilities, and limits scattered changes throughout the application.
Define when the connector acts
Not every invoice change represents a new issue. Distinguish drafts, administrative actions and operations that require processing. Document the selected event and check that one action cannot trigger two submissions. If a task can repeat, protect processing with status and concurrency controls tied to the invoice.
Provide visibility without exposing secrets
Staff need to know whether an operation is pending, has a result or needs attention. Store the API reference alongside the invoice relationship and display a concise event history. Restrict connector configuration and sensitive actions through permissions. Authentication secrets should remain on the server and outside CRM views.
- Check isolation between businesses or installations.
- Link each external operation to a local invoice.
- Separate commercial status from integration status.
- Describe an incident review procedure.
Validate the versions you will maintain
Prepare a test copy with the actual Perfex CRM and PHP versions. Check installation, upgrades and the complete workflow before deployment. If your project requires PHP 7.4 and 8.x, define the specific supported versions and run them in your test matrix; do not infer compatibility of the entire CRM from a single script.