Float
Actuals, open receivables, and open payables from your ledger, pushed into Float on a schedule so your cash-flow forecast stops depending on a spreadsheet export.
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.
Posted transactions and GL activity
Account balances
Open invoices (accounts receivable)
Open bills (accounts payable)
Transaction dates and due dates
GL account to Float category mappings
Data synced
The integration syncs the following data types:
- Posted transactions and GL activity are read from DualEntry and pushed to Float as actuals on every sync cycle
- Each posted transaction lands on the Float account or cash-flow category mapped to its originating GL account
- The transaction date maps to the Float forecast period, so actuals fall into the correct forecast window
- New postings in DualEntry trigger event-based updates between scheduled runs rather than waiting for the next cycle
- Float consumes actuals as forecast input only and never writes an adjusted figure back to the DualEntry ledger
- DualEntry account balances push to Float as the opening and running balance for the forecast
- The opening balance sets the starting cash position against which every projected inflow and outflow is applied
- Balances are refreshed on each sync, so the forecast starting position tracks the ledger rather than a point-in-time export
- If a DualEntry balance differs from the last value pushed to Float, the connector raises a balance discrepancy exception for review instead of resolving it silently
- Open invoices in DualEntry are sent to Float as projected inflows on every sync
- Invoice amount and due date drive the timing of the expected inflow across Float's forecast periods
- Once an invoice is collected and no longer open in DualEntry, it stops appearing as a projected inflow on the next cycle
- Invoices feed the Float account or cash-flow category mapped to their GL account, so AR lands on the intended forecast line
- Open bills in DualEntry are sent to Float as projected outflows on every sync
- Bill amount and due date drive the timing of the expected outflow across Float's forecast periods
- Paying a bill in DualEntry removes it from Float's projected outflows on the next sync cycle
- Bills feed the Float account or cash-flow category mapped to the originating GL account
- Each DualEntry GL account maps to one Float account or cash-flow category, and the connector applies that mapping on every push
- Mappings are configured and maintained in the APIWorx portal, not in DualEntry, and there is no Float connector tile inside the DualEntry application
- A GL account with no mapping is flagged as an unmapped-account exception and excluded from the push rather than posted to a default category
- Because unmapped accounts are excluded, a missing mapping appears as data absent from Float rather than as an incorrect forecast figure
- When you add or restructure GL accounts in DualEntry, add the matching entry in APIWorx and the account begins syncing on the next cycle
- The connector re-syncs on the schedule you configure, typically daily, with event-based updates when transactions post in DualEntry
- You set the date range and period settings that control how much history and how far forward the connector pushes
- Every sync writes a log entry recording the source record ID, the action taken, and the result, retained by APIWorx for troubleshooting and audit
- A sync cycle that cannot complete for a record set logs the affected records and retries them automatically on the next cycle
- All exceptions surface in the APIWorx portal, so the connector reports failures rather than failing silently
Key Features
- 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. - 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. - 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. - 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. - 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. - 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. - 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. - 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
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.
Because of this, there is no Float connector tile inside the DualEntry application. The account-to-category mapping, the sync schedule, and the exception log are all maintained through APIWorx, and setup requires an APIWorx engagement for the DualEntry and Float connector.
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.
Because the sync re-runs on a schedule, the forecast stays grounded in current ledger data. As bills are paid and invoices collected in DualEntry, the projected outflows and inflows in Float update on the next cycle rather than waiting for someone to rebuild the spreadsheet.
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.
That keeps the source of truth unambiguous. DualEntry owns actuals, balances, open invoices, and open bills, and Float owns the forecast built from them. Changing a forecast assumption in Float has no effect on your DualEntry records.
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 as a wrong number in the forecast.
Review the unmapped list in the APIWorx portal after the first sync to confirm every account you expect to forecast is mapped. Add the mapping in APIWorx and the account syncs on the next cycle. The same applies when you add or restructure GL accounts later.
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.
Between cycles, Float reflects the last push. A bill paid or an invoice settled in DualEntry is reflected in the forecast on the next sync, and a receivable that has been collected stops appearing as a projected inflow once it is no longer open in DualEntry.
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.
Each sync also writes a log entry recording the source record ID, the action taken, and the result, and APIWorx retains those logs for troubleshooting and audit. To confirm the integration is healthy, check that recent DualEntry activity appears in Float under the expected categories, that the opening balance matches your DualEntry cash position, and that the exception list is empty or every entry is a known exception.
.avif)