This article addresses frequently asked questions and provides solutions for issues related to ERP integrations with the Payhawk system.
Why my mark as reviewed expense hasn't been exported to the ERP system yet?
If you check the expense history and see the status Expense export into X integration scheduled, it means the expense was marked as reviewed as part of a bulk action. When many expenses are processed at once, the export can be delayed. It may take up to 7 hours for the expense to be fully exported to your ERP system.
Can Payhawk receive purchase orders from external systems?
Yes, Payhawk can receive purchase orders from external systems, for example, Omnea.
Payhawk has dedicated purchase order API endpoints, which allow you to perform all CRUD operations with purchase orders.
If you're considering integrating an external system with Payhawk for purchase order management, contact Payhawk Support to get assistance if needed.
Can Payhawk operate in a fully outbound model where the ERP only pushes and pulls data via API?
Yes, if you build custom logic using Payhawk's Developer API, your ERP can push data to Payhawk and pull data from Payhawk's API without requiring inbound connectivity from Payhawk to your ERP. Payhawk supports API keys for authentication.
What happens to a third-party connector when my ERP is upgraded?
When a third-party connector moves your data into an external system through Payhawk's Developer API, upgrading your ERP does not require changes in Payhawk. Payhawk's API stays stable, so the data it provides is unaffected.
The connector vendor maintains compatibility with the upgraded ERP version. It’s recommended to confirm with your connector vendor that it supports the new version before the upgrade date.
Note that Payhawk can make changes to its API, but those changes are always tied to the new API version. The current version remains stable, and any changes apply only to future versions.