Esker is a French enterprise software publisher offering cloud-based AP (Accounts Payable), AR (Accounts Receivable), and procurement automation solutions. It is one of the most established P2P automation platforms in the European market, used primarily by mid-market and large enterprise companies to digitize invoice workflows, manage approval chains, and automate supplier payment processing.
Esker's core value is workflow processing at scale: it handles document capture, OCR extraction, configurable approval routing, ERP integration, and payment execution. Its AP module automates the flow of invoices through the organization, from reception to payment, with strong ERP connectors (SAP, Oracle, Sage, Cegid) and compliance features suited to enterprise environments.
The gap Esker leaves open is financial verification. Esker processes AP flows. It does not verify whether the financial content of those flows is correct before they are committed. An invoice that passes through Esker's workflow and reaches the ERP has been routed, approved, and posted. Whether the invoiced unit price matches the negotiated contract, whether the quantity aligns with the delivery note, or whether the reference has already been paid: none of these are systematically checked. Esker's value proposition is process efficiency; financial accuracy is outside its scope.
This is the precise boundary Phacet occupies. As the competitive framing states: Esker and Basware process AP flows. Phacet controls, between capture and payment, where no one else verifies.
The second difference is addressability. Esker's implementation model targets large organizations with IT teams, integration budgets, and multi-month rollout capacity. Phacet is designed for growth-stage SMEs (30M to 300M€ revenue), with first agents operational in under two weeks, starting at 299€/month. No DSI involvement required, no integration project, no 6-month timeline.
For DAFs evaluating AP tools, the question is not whether Esker processes invoices well. It's whether processing is enough, or whether pre-payment controls, 3-way matching, and financial anomaly detection need to run before the AP flow reaches the ERP at all.
