Float Integration | DualEntry

Float

Overview

Cash-flow forecasting usually runs on data that goes stale the moment it is exported. Someone pulls balances, an AR aging, and an AP aging out of the ledger, pastes them into the forecast, and the numbers hold until the next bill is paid. Float builds the forecast. DualEntry holds the ledger. The connector in between keeps the inputs current.

On each sync, the connector reads posted transactions, GL activity, account balances, open invoices, and open bills from DualEntry, maps every GL account to a Float account or cash-flow category, and pushes the result into Float as forecast inputs. Account balances set the opening and running cash position. Open invoices become projected inflows and open bills become projected outflows, with amount and due date driving the timing on both, and transaction and due dates mapping to Float forecast periods.

The flow is outbound only. DualEntry is the source of truth for every figure that moves across, and Float owns the forecast built on top of it. Float does not write back to your ledger. Syncs run on the schedule you configure, typically daily, with event-based updates when transactions post in DualEntry, so a collected invoice or a paid bill drops out of the projection on the next cycle.

This is not a native DualEntry integration. The connector is built and hosted by APIWorx, a managed integration platform that runs it as a managed service on its own infrastructure. There is no Float connector tile inside the DualEntry application, and the account mapping, sync schedule, and exception log are maintained in the APIWorx portal.

Data synced

The integration syncs the following data types:

Actuals Export

DualEntry → Float

Account Balances

DualEntry → Float

Receivables (AR)

DualEntry → Float

Payables (AP)

DualEntry → Float

Account Mapping

DualEntry → Float

Continuous Refresh

DualEntry → Float

Key Features

  1. Actuals straight from the ledger Posted transactions and GL activity export to Float as actuals on every sync, landing on the Float account or category mapped to the originating GL account. Transaction dates map to Float forecast periods.
  2. Opening position from real balances DualEntry account balances push across as Float's opening and running balance, so the forecast starts from your actual cash position rather than a manually entered figure.
  3. Receivables become projected inflows Open invoices go across with amount and due date, and the due date drives when Float expects the cash. An invoice that is no longer open in DualEntry stops appearing as a projected inflow.
  4. Payables become projected outflows Open bills go across the same way, with amount and due date setting expected-outflow timing. Paying a bill in DualEntry removes it from the projection on the next cycle.
  5. Mapped once, applied every sync Each DualEntry GL account maps to one Float account or cash-flow category, and the connector reuses that mapping on every push so data lands on the intended forecast line.
  6. Unmapped accounts excluded, never guessed A GL account with no mapping is flagged and held out of the push rather than posted to a default. A missing mapping shows up as data absent from Float, not as a wrong number.
  7. Scheduled and event-based refresh Syncs run on the frequency you choose, typically daily, with event-based updates when transactions post in DualEntry. You also set the date range controlling how much history and how far forward gets pushed.
  8. Delivered and hosted by APIWorx Authorization runs through APIWorx: admin access to your DualEntry company grants read access to the GL, AR, and AP, and admin access to your Float workspace authorizes the other side. APIWorx operates the connector as a managed service with continuous monitoring and logging, and every exception surfaces in its portal.

FAQ

Is this integration handled by third parties?
Yes. The DualEntry and Float connection is delivered by APIWorx, a managed integration platform that sits between the two systems. APIWorx hosts and operates the connector as a managed service on its own infrastructure, with continuous monitoring and logging, so you do not host or run anything yourself.

How does integrating DualEntry with Float help my business?
A cash-flow forecast is only as good as the data behind it, and that data is usually assembled by hand: balances, an AR aging, and an AP aging exported from the ledger and pasted into the forecast. The connector removes that step by pushing posted activity and balances into Float as actuals and opening position, open invoices as projected inflows, and open bills as projected outflows.

Does data flow back from Float to DualEntry?
No. The flow is outbound only: DualEntry data moves into Float, and Float does not write back to your ledger. Float consumes the data as forecast input and builds its projections on top of it.

What happens to a GL account that is not mapped to a Float category?
Each DualEntry GL account is mapped to a Float account or cash-flow category, and an account with no mapping is flagged as an unmapped-account exception and excluded from the push until you map it. It is not posted to a default category, so a missing mapping shows up as data absent from Float rather than a wrong number in the forecast.

How often does the integration sync?
The connector syncs on the schedule you configure during setup, typically daily, with event-based updates when transactions post in DualEntry. You also choose the date range and period settings that control how much history and how far forward the connector pushes.

What happens if something fails to sync?
The connector surfaces every exception through the APIWorx portal and does not fail silently. It raises three kinds: an unmapped account, which is flagged and excluded until mapped; a sync failure, where the affected records are logged and retried automatically on the next cycle; and a balance discrepancy, reported for review so you can confirm the forecast starting position is correct.