Float Integration: Feed Cash-Flow Forecasts
Connect Float to DualEntry so your actuals, open receivables, and open payables flow into Float’s cash-flow forecasting and planning platform automatically. The connection is delivered by APIWorx, a managed integration platform that sits between DualEntry and Float. The connector reads posted ledger activity, open invoices, and open bills from DualEntry and pushes them to Float, keeping your cash-flow projections grounded in current ledger data instead of static spreadsheet exports.
The flow is outbound only: DualEntry data moves into Float, and Float does not write back to your ledger. The connector syncs on a schedule (typically daily, configurable) with event-based updates when transactions post in DualEntry, so Float’s forecast inputs stay current without manual export and import.
Prerequisites
Confirm the following before APIWorx provisions the connector. Each item maps to a configuration step that cannot be completed without it, so a gap here stops setup partway through rather than at first sync.
- Admin access to your DualEntry company, used to authorize read access to the general ledger, AR, and AP.
- Admin access to your Float account or workspace, used to authorize the Float connection.
- Your chart of accounts finalized in DualEntry. Each GL account is mapped to a Float account or cash-flow category, so the accounts must be stable before mapping.
- Your Float cash-flow categories set up, so the connector has a target for each DualEntry account that should feed a forecast line.
- An APIWorx engagement for the DualEntry + Float connector. APIWorx hosts and operates the connector; the setup steps below are completed with your APIWorx implementation contact.
How the connector works
The connector moves accounting data from DualEntry into Float in a single direction through APIWorx. On the configured schedule, and when transactions post in DualEntry, APIWorx reads posted ledger activity, account balances, open invoices, and open bills, maps them to Float’s accounts and cash-flow categories, and pushes them to Float as forecast inputs. Float consumes this data to build its projections; it never writes back to DualEntry.
APIWorx runs the connector as a managed service on its own infrastructure, with continuous monitoring and logging. You do not host or run anything yourself, and there is no Float connector tile inside the DualEntry application. The account-to-category mapping and sync schedule are maintained through APIWorx rather than in DualEntry.
The connector performs five jobs on each sync:
- Actuals export. Reads posted transactions, account balances, and GL activity from DualEntry and pushes them to Float as actuals.
- Receivables feed. Sends open invoices, due dates, and amounts so Float can project expected inflows.
- Payables feed. Sends open bills, due dates, and amounts so Float can project expected outflows.
- Account mapping. Maps DualEntry GL accounts to Float’s accounts and cash-flow categories so data lands on the correct forecast lines.
- Continuous refresh. Re-syncs on the configured schedule so Float’s forecast inputs always reflect the latest DualEntry data.
What DualEntry pushes to Float
The connector sends three kinds of data from DualEntry to Float: actuals, projected inflows from receivables, and projected outflows from payables. Together these give Float a starting position (actuals and balances) plus the expected near-term movements (open AR and AP), which is what a cash-flow forecast is built from.
The table below summarizes what flows from DualEntry into Float on each sync:
| DualEntry data | Float input | Notes |
|---|
| Posted transactions and GL activity | Actuals | Mapped to the Float account or category for the originating GL account. |
| Account balances | Opening / running balance | Sets the starting cash position for the forecast. |
| Open invoices (AR) | Projected inflow | Amount and due date drive the expected-inflow timing. |
| Open bills (AP) | Projected outflow | Amount and due date drive the expected-outflow timing. |
Field mapping
The connector maps each DualEntry field to a Float field on every sync. The mapping below is representative; your APIWorx configuration sets the exact account-to-category rules for your chart of accounts and Float workspace.
| DualEntry field | Float field |
|---|
| GL account | Float account / category |
| Posted transaction amount | Actuals entry |
| Open invoice (AR) amount and due date | Projected inflow |
| Open bill (AP) amount and due date | Projected outflow |
| Account balance | Opening / running balance |
| Transaction date / due date | Forecast period |
- Authorize the DualEntry company connection. Grant APIWorx read access to the general ledger, AR, and AP for the company whose data feeds Float.
- Authorize the Float connection. Connect APIWorx to your Float account or workspace.
- Map accounts to Float categories. For each DualEntry GL account, choose the Float account or cash-flow category it feeds. Accounts with no mapping are excluded until mapped, so map every account you want represented in the forecast.
- Set the sync schedule and date range. Choose the sync frequency (for example, daily) and the date range or period settings that control how much history and how far forward the connector pushes.
After these steps, the connector pushes DualEntry actuals, receivables, and payables to Float automatically on the schedule you selected.
Monitor sync health and exceptions
The connector surfaces every exception through the APIWorx portal and does not fail silently, so the portal is where you confirm that data is flowing to Float and find records that need attention. Each sync writes a log entry recording the source record ID, the action taken, and the result; APIWorx retains these logs for troubleshooting and audit.
The connector raises three kinds of exception:
| Exception | Cause | Resolution |
|---|
| Unmapped account | A DualEntry GL account has no Float account or category mapping. | The account is flagged and excluded from the push until mapped. Add the mapping in APIWorx, then it syncs on the next cycle. |
| Sync failure | A sync cycle could not complete for a record set. | The affected records are logged and retried on the next cycle automatically. |
| Balance discrepancy | The DualEntry balance differs from the last value pushed to Float. | The discrepancy is reported for review so you can confirm the forecast starting position is correct. |
An unmapped account is excluded from the forecast rather than posted to a default, so a missing mapping shows up as data absent from Float, not as a wrong number. Review the unmapped list in the APIWorx portal after the first sync to confirm every account you expect to forecast is mapped.
Result
After setup, DualEntry actuals, open receivables, and open payables flow into Float automatically on your chosen schedule, so cash-flow forecasts reflect current ledger data without manual exports. As bills are paid and invoices collected in DualEntry, the projected outflows and inflows in Float update on the next sync.
To confirm the integration is healthy, check that recent DualEntry activity appears in Float under the expected categories, that the opening balance in Float matches your DualEntry cash position, and that the APIWorx exception list is empty or every entry (especially unmapped accounts) is a known exception.
To connect more systems, return to Integrations. For where this forecast data originates in DualEntry, see Cash management, Invoicing and dunning, and Bill management. For the connector’s own technical reference, see the APIWorx DualEntry + Float connector page.