Mayday vs FloQast

At a glance

1. Through Easy Month End, Mayday's close product. It's a separate application with its own login.
2. FloQast's Workday page is the only one claiming transaction-level data. NetSuite and Sage Intacct mention balances and transactions in the variance analysis context. Xero, Dynamics and SAP are described in terms of balances.
3. FloQast's journal entry product says journals can be created and posted to your ERP, but names no ERP. The only named write-back anywhere on their site is Workday.
4. Prepayments, deferred revenue and amortisation appear as things FloQast reconciles, and accruals appear as AI agent use cases. No evidence found of building a schedule and posting it.
5. Balancer maps loan account relationships across the group, shows a matrix of which balances disagree, matches AR and AP, and posts FX and interest journals.
6. FloQast's pricing page claims intercompany reconciliation under its reporting package. There is no product page behind it, and the link from their own glossary entry leads to a page that doesn't exist.
7. FloQast has an AI agent that posts expenses across departments, projects and cost centres. No evidence found of recharging between entities.
8. Claimed on the pricing page. The consolidation link in FloQast's own navigation leads to a page that doesn't exist.
9. Through AI transaction matching and a bank connector covering hundreds of banks.
10. Workday, NetSuite, Sage Intacct, SAP, Dynamics and Xero have dedicated pages. Oracle, QuickBooks and Yardi appear as logos only, with no supporting detail.
11. FloQast's Xero page describes bringing in general ledger trial balances and refreshing account balances. No transaction-level or write-back claim appears on it.

Checked against both companies' public pages in September 2026. FloQast ships frequently, so confirm anything that will decide it for you.

What both products do

Both products run a month-end close and hold the review around it:

• Close checklists with owners, due dates, rollover and progress tracking
• Balance sheet reconciliation review with preparer and reviewer separation
• Variance analysis against materiality thresholds, with AI-drafted explanations
• An audit trail of who prepared what and who signed it off
• Visibility across multiple entities

The difference isn't whether the close gets tracked. It's whether the accounting inside it gets done, and on which ledger.

Where FloQast is stronger

ERP coverage. Nine accounting systems, including SAP, Oracle, Workday and Dynamics 365. Mayday supports three cloud ledgers. If your books are on an enterprise ERP, this comparison is over before it starts.

SOX and compliance. A full compliance pillar: 404a management, 404b testing, embedded controls, automated evidence collection, enterprise risk management with risk scoring and heatmaps, and AI-assisted controls testing in beta. Mayday has none of this. For a public company or one preparing to list, it's decisive.

Scale and track record. More than 3,500 companies, $200M in annual recurring revenue, and customers including Shopify, Zoom, DoorDash and Lululemon. FloQast has been doing this since 2013 and is the category leader by most analyst measures. Mayday is a much smaller company serving a different end of the market.

Transaction matching at volume. AI matching rules written in plain language, exception workflows, and a bank connector covering hundreds of banks worldwide. If you're matching tens of thousands of lines a month, Mayday has no equivalent.

Close analytics. Progress against a pace line, all-entity views, retrospective trend analysis across closes. Mayday tracks close progress; it doesn't analyse it over time.

Workflow beyond accounting. FloQast extends the same checklist and sign-off model into AP, FP&A and reporting. Mayday stays inside month end.

Where Mayday is stronger

It builds the schedules. Prepayments, deferred revenue and accruals: Mayday identifies the transactions, builds the schedule, posts the journal to Xero, QuickBooks Online or Intuit Enterprise Suite, and keeps it reconciled month to month. FloQast reconciles schedules and posts journals from supporting items and bank files. Nothing in their material builds an amortisation schedule for you. That's the practical difference between a spreadsheet you maintain and one you no longer need.

Depth on Xero. FloQast's Xero page describes bringing in trial balances and refreshing account balances. Mayday reads Xero at transaction level and writes back to it: journals, invoices, bills, contacts and chart of accounts changes. On the same ledger, the two products are doing different amounts of work.

Intercompany. Balancer maps loan account relationships across the group, shows which balances disagree, surfaces the transaction responsible and posts the FX and interest journals. FloQast claims intercompany reconciliation on its pricing page, but there's no product page behind it and the link from its own glossary is broken.

Recharges. Recharger allocates costs and revenue between entities and across departments and cost centres, posting invoices, bills or journals to both sides. FloQast's nearest equivalent posts expenses across departments, projects and cost centres within a ledger.

Cross-entity bank reconciliation. BRAG matches a statement line in one Xero entity to a bill or invoice in another, from inside Xero's own bank rec screen, and creates the intercompany entry as part of the match.

Group master data. Mayday HQ aligns chart of accounts, tracking categories and contacts across every entity and writes changes back into Xero.

Intuit Enterprise Suite. Mayday supports it. FloQast doesn't mention it, and QuickBooks appears on their site as a logo with no supporting copy at all.

You can try it today. Work out what Mayday costs from the pricing page, then start a 30-day trial without a card. FloQast is a demo, a scoping conversation and an implementation. For a growing finance team, that difference in buying process is often the whole story.

Ledgers and fit

Breadth of integration and depth of integration are different things, and this is the clearest example of it in the category.

FloQast's model is ERP-agnostic by design. It pulls balances from whatever system you run, ties them to Excel workbooks in your cloud storage, and manages the workflow and evidence around them. That's how one product supports SAP and Xero at the same time, and for a team running several ERPs across a group it's a genuine advantage. Workday is the exception, and the only ledger they name for writing journals back.

Mayday's model is the opposite. Three cloud ledgers, read and written at transaction level, with the month-end accounting workflows built for them specifically. Narrower, and deeper where it counts for those three.

So the question isn't which product supports more systems. It's whether yours is one of Mayday's three, and whether you want the spreadsheets managed or removed.

On price

FloQast doesn't publish pricing. Its packages carry a “contact sales” button, and the company is explicit that it doesn't charge per user, pricing instead around scope and scale. Expect a scoping conversation, a quote and an implementation project. Their own material references more than 3,000 implementations and a professional services team.

Mayday's Active plan, covering Balancer, Recharger, BRAG and Mayday HQ, is £34 a month at two entities, £139 at ten and £229 at twenty, billed annually, with unlimited users. Flux, Deferred Revenue and Prepayments are add-ons. There's a free tier and a 30-day trial that doesn't need a card.

Which should you choose

FloQast, if your books are on SAP, Oracle, Workday, Dynamics or another enterprise ERP; if you're SOX-scoped, public or preparing to list; if you need controls testing, evidence collection and risk management alongside the close; if you match bank transactions in very high volume; or if you want one workflow model covering AP and FP&A as well as accounting.

Mayday, if you're on Xero, QuickBooks Online or Intuit Enterprise Suite; if you want the prepayment, deferred revenue and accrual schedules built and posted rather than reconciled; if you run a group and need intercompany reconciled, recharges posted, cross-entity bank recs matched and the chart of accounts kept aligned; or if you want to see what it costs and try it before speaking to anyone.

Most evaluations resolve on the first line of each. The ledger decides it.

Frequently asked questions

Does FloQast work with Xero?

Yes, and it has a dedicated Xero page. What it does there is worth understanding: FloQast describes bringing in general ledger trial balances and refreshing account balances. The reconciliations are performed against Excel workbooks in your cloud storage. There's no transaction-level or write-back claim on the Xero page, and across their whole site Workday is the only ledger named for posting journals back. Mayday reads Xero at transaction level and writes journals, invoices, bills and chart of accounts changes back to it.

Can FloQast create and post prepayment, deferred revenue or accrual schedules?

Not from what's published. FloQast reconciles amortisation and depreciation schedules and posts journals built from supporting items and bank files, and it offers AI agents for things like PO and vacation accruals. Building the schedule itself, then releasing it month by month and keeping it tied to the ledger, isn't described anywhere. That's the part Mayday automates.

Does FloQast handle intercompany reconciliation?

Their pricing page claims it under the reporting package. There's no product page behind that claim, and the link from FloQast's own glossary entry for intercompany reconciliation leads to a page that doesn't exist. Take it as unproven rather than absent, and ask them directly. Mayday's Balancer maps the relationships across the group, shows which balances disagree, surfaces the transaction responsible and posts the FX and interest journals.

FloQast supports far more ERPs. Why would we choose Mayday?

Because breadth of connection and depth of work are different things. FloQast connects to nine systems by pulling balances and managing the spreadsheets around them, which is how one product covers SAP and Xero at once. Mayday supports three cloud ledgers and works inside them at transaction level, building and posting the schedules so there's no spreadsheet to manage. If your ledger is one of Mayday's three, you get more of the work done. If it isn't, FloQast is the answer.

How much does FloQast cost?

They don't publish it. Pricing is quoted per organisation rather than per user, based on scope and scale, and buying involves a demo and an implementation. Mayday's prices are all on the pricing page, with a 30-day trial that doesn't need a card, so you can work out the cost and test the product before talking to anyone.

Can you use both?

There's little reason to. They overlap on close management, reconciliation review and variance analysis, which is the bulk of what either is bought for. A group running an enterprise ERP at the parent and Xero in its subsidiaries is the one case where it could make sense, with FloQast over the group close and Mayday handling the Xero entities' month-end accounting and intercompany.

Last reviewed: September 2026