LoginSign Up
← Back to all sparks
P

Payhawk

FINANCE
Velocity2.5

Payhawk is bolting a travel agency and a payments bank onto its expense platform.

travel-and-expensecross-border-paymentserp-integrationfraud-controlsopen-banking
◆Current state
Payhawk now ships on three fronts at once - corporate travel booking, cross-border payment execution, and ERP-facing accounting hygiene - from a base that was a card-and-expense tool. The May batch built out banking surface (GBP accounts for EU customers on the EMI license, German open-banking top-ups via Yapily, bulk payments covering global FX) alongside a layered set of insider payment fraud controls. The June and July entries turn inward toward accounting mechanics: templated expense notes for consistent ERP exports, and detailed diagnostics for supplier sync failures.
◆Where it's heading
The direction is consolidating the whole spend lifecycle in one platform - book the trip, pay the supplier, hold the currency, export the entry - rather than going deep on any single one. Travel is the most aggressive expansion: in three months it went from bookings to allowances-in-policy, baggage bundles, in-app trip changes, and admin booking on behalf of employees, which is a full travel-and-expense product surface, not a feature. The recent shift to ERP export consistency and supplier error visibility suggests the buildout is now being backfilled with the integration reliability that enterprise finance teams gate purchases on.
◆Prediction
Expect the next releases to keep pairing travel-product depth with accounting-integration hardening - more policy-driven controls on the booking side, more supplier and ERP reconciliation on the back-office side. Nothing in these entries points to AI or agentic work, so any move in that direction is not yet visible from this feed.

◆Recent moves

  1. 19d ago

    Detailed Duplicate Supplier Errors

    Supplier sync failures now report which records broke, why, and how many are affected. It is the diagnostic surface that starts to matter once ERP integration is something customers depend on daily, and it fits the recent turn from feature expansion toward making the accounting pipeline trustworthy.

  2. 1mo ago

    Note builder

    A template for the expense Note field so every ERP export lands in a consistent format. Narrow in scope, but it targets the manual cleanup finance teams do after export - the same accounting-hygiene thread as the supplier error detail.

  3. 1mo ago

    Booking on behalf of others

    Admins can book travel for any employee with that person's policy and approvals applied automatically. This is the delegation layer corporate travel desks actually run on, and it moves Payhawk Travel from a self-serve booking tool toward something an assistant or office manager can operate on someone else's behalf.

  4. 2mo ago

    Five Layers of Payment Fraud Prevention

    ⚡ SPARK

    A layered set of insider payment fraud controls now spans the payment process end to end, shipping in the same batch as bulk global FX payments and multi-currency accounts. Controls and payment volume arriving together is the tell: Payhawk is building the trust surface a platform needs before finance teams route real accounts payable through it.

  5. 2mo ago

    Bulk Payments: Full End-to-End Experience

    Bulk payments now handle global FX transfers and destination-specific requirements, closing the gaps that previously sent finance teams back to their bank for the hard payments. Read next to the GBP accounts and German open-banking top-ups from the same batch, it looks like Payhawk finishing its outbound payments rail.

  6. 2mo ago

    Travel allowance in policy

    Travel allowances can be set in policy and applied to every trip automatically, replacing per-trip manual handling. Another piece of the policy engine that makes Payhawk Travel enforceable rather than merely bookable.