How Planful works

Requirement evaluated: Multi-currency translation using period-appropriate rates with the translation adjustment calculated, not entered

For your five entities (US, UK, Germany) rolling up from NetSuite, Planful's Consolidation module translates local-currency books into common and reporting currencies. Admins load exchange rates by type (for example EOM and Avg) in Currency Setup and assign them to accounts. Planful's documentation describes closing rate for balance sheet accounts, weighted average for P&L, and historical rates for historical accounts and retained earnings (Using the closing exchange rate for all Balance Sheet accounts; the weighted average exchange rate for the Profit and Loss Account; historical exchange rates for Historical Accounts and Retained Earnings). The consolidation run does the CTA calculation. …

Limitations: Rate tables must still be maintained or loaded (the consolidation prerequisites include updating foreign currency exchange rates), so the rates are inputs but the CTA is not keyed. The setup (rate types per account, historical rate handling for equity, CTA Sets and target accounts) …

Requirement evaluated: Documented API or scheduled file interface for systems with no native connector

For a multi-entity software company like yours running NetSuite as the GL with a mix of source systems, Planful provides two documented pathways to connect any system that lacks a native connector. First, Planful exposes a REST API library that covers data import and export across GL data, segment hierarchies, entity hierarchies, currency exchange rates, and workforce planning data; the Transfer Data REST API accepts payloads in JSON format and supports both single-transfer and batch-transfer modes, secured via basic authentication (Planful help center: Transfer Data REST API). …

Limitations: The SFTP-based file path requires Planful's Integration Team to initially review file formatting and configure the Boomi process, so new source system connections involve a setup engagement rather than purely self-serve configuration. …

Requirement evaluated: Variance explanations captured in the system against the variance they explain, not in a separate document

For your two-person FP&A team preparing quarterly board variance packs, Planful's Dynamic Commentary stores the explanation inside the platform, attached to the data cell it explains, rather than in a separate Word or PowerPoint file. Users add cell-level comments in Dynamic Reports, Spotlight Web or SpotlightXL. Comments can be posted for combinations of dimensions at leaf level, rollup level and calculated members, and can include @mentions, #tags and hyperlinks (Planful help: Using Dynamic Commentary in Excel Reports). …

Limitations: Comments attach to a data intersection (scenario, time and dimension members), so the explanation sits against the variance cell only when the variance is a calculated member or formula line in the report. …

Requirement evaluated: Self-service access for department leaders limited to their own cost centers

For a company like yours with 60 cost centers across 7 departments, Planful handles this through its native Dimension Security framework. An administrator navigates to Maintenance > Reports > Dimension Security, selects the Financial reporting area, marks the Cost Center dimension as secured, then uses the Dimension Security Setup page to assign each department leader access only to their specific cost center members from the hierarchy. …

Limitations: Initial configuration requires admin effort to map each of your 60 cost centers to the correct department leaders; there is no automated sync from your NetSuite org chart, so any cost center additions or user changes must be maintained manually in Planful's User & Role Management.

Requirement evaluated: Rolling 12-month or 18-month forecast that re-extends automatically as each month closes

For your NetSuite-fed, 60-cost-center model with quarterly reforecasts and a board that wants a rolling 12-month view, Planful's Structured Planning uses Forecast or Plan scenarios with a Projection Start Date. Months before that date are treated as closed periods and filled from the Actual scenario, which is loaded from your ERP. When the Projection Start moves, an administrator runs 'Refresh Closed Period Data' from Scenario Setup to pull in the newly closed month. Planful's own FAQ says it does not automatically roll time periods forward in templates, scenarios or reports unless they are configured to. …

Limitations: The roll is achievable but is not automatic out of the box. Someone has to advance the Projection Start and refresh closed-period actuals each month, or an admin has to build Process Flow and substitution-variable automation. …

Requirement evaluated: Audit trail on assumption changes recording the prior value, the new value, the user, and the timestamp

For your rolling 12-month forecast, where the board expects assumption changes to be traceable, Planful's Data History feature is an opt-in, cell-level audit trail across the web application and the Excel plug-in (SpotlightXL). For each data change it records the user, the exact timestamp, the previous value, the updated value, the action type and the source (web or Excel Spotlight) (Planful Help: Opt-in Features). Users can double-click a cell in Dynamic Planning Web, or click Data History in SpotlightXL, to see recent edits. The audit trail is also presented in a filterable view by user, date, action type and source. …

Limitations: Data History is documented for Dynamic Planning Analytical and Master Models, and the cell view shows only the last 10 changes per cell. Confirm the retention depth, export options and enablement steps for your tenant. …

Requirement evaluated: Time-to-fill and vacancy assumptions by role that phase cost correctly when a start date slips

For your 480-person, five-entity planning model, Planful's Workforce Planning module (also marketed as Workforce Pro) is position-driven. The expense of an employee is always driven by Position Start Date, and new compensation items are calculated on a position-start basis, so an employee who starts June 3rd is counted as .93 rather than 1 for that month. When a start date slips, the planner edits the position start date, either in Advanced Planning or by a budget manager in MyPlan. As the start date changes, the variance is updated and displayed, so cost re-phases without manual overrides. Benefits can also be set to begin based on position start month, which helps with delayed start dates.

Limitations: I found no documentation of a role-level time-to-fill or vacancy-lag assumption table that derives an expected start date from a requisition open date. Your FP&A team would probably enter or adjust start dates position by position, or build custom logic with Custom Compensation date functions. …

Requirement evaluated: Each planned position carries department, role, level, location, start date, and compensation band

For a software and services company managing 60 cost centers and 480 employees across five entities, Planful's Workforce Planning module (within Structured Planning) creates a discrete position record for every employee or planned hire. Each record carries system-defined fields for Position Description (role/job title), FROM_DATE, a system-defined attribute that captures the employee position start date, and Position Budget Entity, the home budget entity that ties the position to its department and drives allocation columns. Location is also a recognized updatable attribute on the employee record, alongside Department and Employee Type, and can be changed via a Data Load Rule. …

Limitations: Planful does not offer native out-of-the-box connectors to HRIS systems such as Workday, ADP, or BambooHR: Planful does not offer native integrations with external payroll or HRIS systems, and supports importing data using Data Load Rules that require data to be formatted according to Planful's specifications. …