An accountant turns a payroll register into journal entries every pay period. The arithmetic is repetitive. The awkward part comes when a new department appears in the register, an employee moves between entities or the general ledger has closed for the month. FloQast’s Transform software can use a finished close to build an agent for recurring work. A controller assessing it should follow one entry through the exceptions and approvals that made the original process trustworthy.
- 01The platform FloQast combines close management, reconciliations, journal work and controls for accounting teams.
- 02The agent Transform can start from an existing close or reusable skills, then check a proposed workflow against the team’s own numbers.
- 03The distinction An assistant can answer a question about a balance. An agent that prepares recurring entries needs inputs, a repeatable calculation and an approval path.
01 / ProductWhere an agent fits into the financial close
FloQast’s accounting platform connects tasks, reconciliations and journal preparation with the people responsible for reviewing them. The business case starts with the overlap between evidence and execution. The preparer needs the source payroll report, the mapping of payroll categories to ledger accounts and a method of reconciling the control total. The reviewer needs those same things after the entry is prepared to understand exactly what will reach the books.
Its Transform AI Agents page describes three ways into that work. Builder can start with a finished close or a description of the desired inputs and outputs. Skills package smaller actions, such as fetching a trial balance or creating a journal entry. The Library supplies existing agents which a team can tailor. FloQast also describes an AI Assistant that answers questions from accounting records. Being able to ask why a balance changed is useful even when the team has no intention of delegating any part of the preparation.
There is evidence of scale, although it should be read with care. In its January 2026 announcement, the company reported more than US$200 million in annual recurring revenue across the business. Its September product release describes Transform learning from an already completed close and the AI Assistant reviewing entries before approval. The revenue number concerns the whole business. The more pertinent evidence for an agent purchase will be how a team’s own work appears to its reviewer.
02 / AudienceWhich accountant can describe what must be preserved?
Start with a preparer who has done the payroll entry often enough to explain which files arrive, why they occasionally change and where the final figure is posted. Pair that person with a reviewer who has previously sent an entry back. The second person will often remember a distinction missing from the standard instructions, such as the difference between the pay date and the period to which an expense belongs. That distinction belongs in the demonstration.
A controller consolidating several entities may face the same file format and a different accounting policy at each subsidiary. One ledger might accept the payroll summary directly. Another may require allocations to departments or a separate approval for intercompany entries. A reusable skill is valuable when its input and output are stable. It can create extra work when teams assume that identical column headings mean the same entries are authorized everywhere.
A team that cannot yet determine who owns a reconciliation has an earlier problem. FloQast’s pricing and package page describes Close Management as including checklists, reconciliations, an assistant and ERP integration. For some organizations the sensible first purchase is the ability to see who has finished their work and what remains unresolved. An AI agent becomes easier to evaluate after those responsibilities are visible.
03 / WorkflowRebuild a completed payroll entry with the controller watching
For a proposed evaluation, use approved historical payroll material the team is permitted to share, minimizing personal fields. Preserve the source export, the department mapping used that month, the balancing worksheet and the journal the reviewer signed. Keep a second completed pay period back for evaluation. If both the inputs and final answer for every period are handed to the builder, the exercise has little to say about the next unfamiliar file.
Ask the preparer to show where a currency, account or entity first enters the process. Trace a gross amount, a deduction and the cash settlement from the source report into the proposed lines. A journal can balance perfectly and still charge the wrong subsidiary. A reviewer should be able to select one line and explain the source amount, mapping decision and reason for its destination. Write down where the output requires an ordinary arithmetic check and where it requires an accountant’s judgment.
Introduce the held-back pay period, including a changed department code or a previously unseen category if one exists in the approved records. Watch what the proposed agent does with the unmapped item. A visible exception with a useful explanation gives the preparer something to resolve. Quietly routing it to a familiar suspense account might move the process along while increasing the reviewer’s work later. Trace the corrected output back to the specific mapping change and preserve the original evidence.
Finally simulate the ledger boundary. An entry may be prepared correctly just as someone closes the period, rejects the approval or changes a control total. Ask which system records the approval, what the next reviewer sees and how a duplicate posting would be identified if someone repeats the request. Keep the test within an isolated or non-posting workflow until those responsibilities are understood. The evaluation should end with a file the auditor could reopen and a ledger owner who knows which action actually took place.
04 / PricingPrice the close package and the integration together
| Package | Stated scope | Commercial basis |
|---|---|---|
| Close Management | Close checklist, reconciliations, AI assistant and ERP integration | Request a quote. FloQast says it charges no per-user fees. |
| Close AI | Adds AI agents and matching, automated reconciliations and journal posting | Request the scope and price for the entities and workflows in the evaluation. |
| Risk & Compliance | Controls, audit readiness, enterprise risk and operational audits | Offered on its own or with a Close package. |
Offer shown on 21 November 2026 in the FloQast pricing and packaging guide.
The current pricing page gives package boundaries and a quote route, without a standard dollar tariff. An insurer and a software business might have the same number of accounting staff and entirely different requirements for ledger connections, approval chains and supporting evidence. Send the vendor a description of the entities, transaction sources, posting permissions and control environment. Ask for implementation work, recurring charges and ongoing responsibilities to be identified separately.
For the payroll example, estimate the time spent preparing the register, researching unmapped items, reviewing the proposed entry and reconciling it after posting. Calculate that for a normal cycle and for one with a material exception. A time saving that occurs only in a clean routine cycle can still be worth buying. The estimate is more credible if the controller also knows what happens in the month a reorganization changes a large portion of the mapping.
05 / DistinctionsCompare one journal across close platforms
BlackLine’s Blueprint gives an accounting team an adjacent platform to consider for financial close and reconciliation. Use the same journal, entity structure and approval sequence in both evaluations. Ask the reviewer to find the source for a particular line and identify which rule produced it. The elapsed time to a first draft matters less if the documentation is so thin that the reviewer ends up rebuilding the entry.
Numeric’s Blueprint is particularly relevant when close automation sits alongside a broader decision about the accounting system. A company planning to change ERP may wish to reconsider which system should own journal generation. A group keeping its existing ERP can focus instead on whether the integration preserves dimensions, posting status and durable identifiers. Write those assumptions down before interpreting a comparison between two very different demonstrations.
06 / QuestionsCan a later reviewer reproduce the earlier close?
Suppose payroll corrects a department code after the original journal has been approved. Running an agent against the corrected source may now produce a perfectly reasonable new result, while obscuring why the old entry was reasonable at the time. In the evaluation, have someone retrieve the original source, mapping and approval as they stood on the posting date. Then show the separately approved correction. The ability to explain the difference is part of the product’s value to the controller.
A second uncertainty concerns authority. FloQast describes automatic posting in its Close AI package and emphasizes human approval on its platform page. Those claims can fit together if a system delivers an approved entry to an ERP automatically. Ask the vendor to demonstrate where approval occurs for this workflow, whether a changed input invalidates it and which person can authorize another posting. A quarterly audit should not have to reconstruct a critical permission from someone's memory of the setup call.
07 / DecisionWhich part of the close should move first?
The close depends on one experienced preparer
Document a recurring journal from the last completed period and ask a second accountant to reconstruct it from the evidence.
The team already has an orderly close
Compare agent-prepared and current journals on a held-back period, including changed mappings and rejected approvals.
Several entities want to share a payroll agent
Identify common skills and local accounting exceptions, then price and demonstrate each required ledger connection.
A business worth understanding.
Suggest your business or one you find interesting. Tell us what you want to understand about its product, positioning, design or workflows.
Suggestions are free. Selection and publication stay with the desk.
- FloQast accounting workflow automation platformConsulted
- FloQast current pricing and package comparisonConsulted
- FloQast Transform AI Agents, Builder, Skills and LibraryConsulted
- FloQast September 2026 accounting product announcementsConsulted
- FloQast January 2026 company revenue announcementConsulted


