FloQast incident

Issue Fetching GL Balances from Quickbooks Online

Critical Resolved View vendor source →

FloQast experienced a critical incident on October 28, 2025 affecting QBO API, lasting 6h 22m. The incident has been resolved; the full update timeline is below.

Started
Oct 28, 2025, 01:23 PM UTC
Resolved
Oct 28, 2025, 07:45 PM UTC
Duration
6h 22m
Detected by Pingoru
Oct 28, 2025, 01:23 PM UTC

Affected components

QBO API

Update timeline

  1. investigating Oct 28, 2025, 01:23 PM UTC

    We are investigating issues capturing balances in the per-GL column for entities connected to QBO.

  2. monitoring Oct 28, 2025, 03:57 PM UTC

    The source of the GL balances from Quickbooks Online failing to pull in has been identified and resolved. We are actively monitoring to ensure that the issue is fully mitigated.

  3. resolved Oct 28, 2025, 07:45 PM UTC

    This incident has been resolved.

  4. postmortem Oct 30, 2025, 12:03 AM UTC

    **Summary:** Customers who have integrated their QuickBooks Online instance with FloQast began to see their Per GL balances in the Close module fail to correctly reflect balances from QuickBooks Online, and instead showed a zero balance. **Root Cause:** A monthly limitation of available API request credits was exceeded, and this resulted in all requests made to QuickBooks Online being rejected. The rejected requests caused a failure to obtain correct balance data, ultimately ending in the zero balance being displayed for reconciliations. **Immediate Resolution:** Proper functionality was restored by working to increase the available API request credits allocated from QuickBooks Online, allowing for the requests to return accurate data once again. **Follow-up Actions:** Additional monitoring will be put in place to more specifically measure third-party request quota limitations and usage, alerting FloQast in advanced of any potential conflicts.