Why Reckon is on the roadmap, not in production
Reckon One is a common choice among Australian micro-businesses and the bookkeepers who serve them, particularly practices that took on long-running Reckon clients before the wider Xero / QuickBooks Online migration wave. ExpenseFlow does not yet ship a native Reckon integration. We prioritise integrations by request volume rather than guessing, and Reckon is currently in the queue: real but not yet active.
A native Reckon One integration has to cover the BAS-specific GST treatments Australian bookkeepers rely on (GST on income, GST on expenses, GST-free, input-taxed, and the FBT-relevant variants) and behave consistently with how the Xero and QuickBooks Online integrations already work. We would rather ship that properly than rush a partial sync that creates a quarter-end mess.
What ships when Reckon lands
When the Reckon integration lands, it matches the mechanics of the existing integrations: continuous two-way sync, GST codes preserved per line, the original receipt image attached to the underlying Reckon transaction, and supplier records auto-created on first sight. Per-client rules will default jobs and tracking where the client uses them.
If your practice runs on Reckon today and an ExpenseFlow rollout depends on it, request access with Reckon flagged. The founder follows up personally on integration-request entries and will give an honest read on timing.