Why FreeAgent is on the roadmap, not in production
FreeAgent is a popular choice for UK sole traders, micro-limited-companies and the practices that serve them. ExpenseFlow does not yet ship a native FreeAgent integration. We prioritise integrations by request volume rather than guessing, and FreeAgent is currently in the queue: real but not yet active.
The FreeAgent API surface is well documented and relatively clean, which makes the build itself manageable. What we need before we commit to it is enough request signal that the practices we end up onboarding actually use FreeAgent at scale, rather than a single client at a single firm. Each new integration adds ongoing maintenance, so the bar for shipping one is higher than the bar for evaluating it.
What ships when FreeAgent lands
When the FreeAgent integration lands, it matches the mechanics of the Xero and QuickBooks Online integrations: continuous two-way sync, UK VAT codes (standard, reduced, zero-rated, exempt, out-of-scope, plus reverse-charge variants for construction and imported services) preserved per line, the original receipt image attached to the FreeAgent bill or expense, and project tags defaulted from per-client rules where the client uses them.
If your practice runs on FreeAgent and an ExpenseFlow rollout depends on it, request access with FreeAgent flagged. The founder follows up personally on integration-request entries.