Completeness Check for Trial Balance Upload

Overview

The In-App Completeness Report lets Admins and Managers identify and resolve missing General Ledger (GL) accounts directly within FloQast.

Supported Setups and User Roles

Who can use this feature:

• User Roles: Admin and Manager users.
• Supported Configurations: Entities using Trial Balance Upload (including Cloud Connect and TB API).
• Not Supported: Direct ERP integrations (e.g., NetSuite, Sage Intacct, QuickBooks Online). Support for additional ERP types will be introduced in future releases.

What You Can Do

The in-app Completeness Report supports three primary actions for missing accounts:

• Create Individual Reconciliations: Turn a single missing account into a standalone reconciliation.
• Add to Existing Groups: Map one or more missing accounts into an existing Grouped Account reconciliation.
• Create New Groups: Bundle multiple missing accounts into a brand-new Grouped Account reconciliation.

You can perform all three actions in bulk, creating multiple reconciliations at once without switching between tools or files.

How to Run the In-App Completeness Report

1. Navigate to the Report

Go to the Reconciliations tab and open the Completeness dropdown. Select the General Ledger Group you want to investigate.

If you are running the completeness report for the first time in a given period, the report generates asynchronously in the background—you can continue working elsewhere in FloQast while it loads. If you have already run completeness for this period, you will be taken directly to the in-app report.

2. Filter and Organize Accounts

Use the grid tools to isolate related accounts. You can drag, drop, and pin columns, or apply filters to cluster accounts together. For example, filter for accounts beginning with 1015 and 1016 to group fixed assets alongside their depreciation accounts.

3. Select Accounts

Check the boxes next to the accounts you want to reconcile. Use Shift + Click to select a range of accounts, or use Select All to grab every account in your current filtered view.

4. Edit Settings

Click the Edit Settings button to open the configuration panel for your selected accounts.

5. Assign Reconciliation Attributes

Fill out the required fields, just as you would when setting up an individual reconciliation:

• Entity: You will only see entities you have access to.
• Folders: Use the keyword search to find and select existing folders without needing to match exact spelling.
• Assignees: Add Preparers and Reviewers as needed.

6. Apply and Create Reconciliations

Click Apply to populate the grid with your new settings. Review the details, then click Create Reconciliations to push the updates to the reconciliation template.

7. Verify the Results

The report will process your changes asynchronously. Once finished, the Accounts Not Included in FloQast counter will decrease to reflect the newly created reconciliations.

Asynchronous Report Generation

When you run the Completeness Report for the first time in a close period, the report generates asynchronously. This means you do not need to stay on the page while the report loads—you can navigate to other areas of FloQast and return when the report is ready.

If you have already run completeness for the current period, subsequent visits will load the previously generated results immediately. You can re-run the report at any time to capture changes made since the last run.

Read-Only Completeness Reports

Completeness reports that are more than three months older than the current close period are automatically set to read-only. This prevents accidental modifications to historical data while still allowing you to reference past reports for auditing and review purposes.

Current Limitations

• This feature is available for Trial Balance Upload entities only. Direct ERP integrations (NetSuite, Sage Intacct, QuickBooks Online, etc.) are not supported in this release.
• Income Statement accounts are not currently captured in the Completeness Report.
• There is no option to permanently ignore or exclude accounts from the report. All missing accounts are surfaced each time the report runs.
• The report does not consolidate multiple completeness checks. If you currently run separate reports for different GL Groups, you will continue to run them individually—they are now managed inside the app rather than in separate files.
• Asynchronous loading allows you to work elsewhere while the report generates, but it does not resolve underlying performance issues for extremely large data volumes.

Frequently Asked Questions

Q: Does this change how the Completeness Check works?

A: No. The underlying logic is identical to the previous workflow. The comparison between your Trial Balance accounts and the reconciliation template is unchanged. The update streamlines the process by moving everything into the app, eliminating the need to export, edit, and re-upload spreadsheets.

Q: Can I use this for entities connected via a direct ERP integration?

A: Not at this time. This release supports Trial Balance Upload setups only, including Cloud Connect and TB API. Support for additional ERP types will be added in a future release.

Q: What happens if someone else updates the reconciliation template while I’m working?

A: FloQast will detect the change and invalidate your current completeness results to prevent duplicate account entries. You will be prompted to refresh the report before you can continue making changes.

Q: Can I ignore accounts that I don’t plan to reconcile?

A: The current version surfaces all missing accounts. There is no option to permanently exclude specific accounts from the report. This capability may be introduced in a future update.

Q: Why don’t I see my Income Statement accounts in the report?

A: Income Statement accounts are not currently included in the Completeness Report. The report focuses on accounts that typically require balance sheet reconciliation.

Q: I run 10 separate completeness reports today. Will they be consolidated into one?

A: No. If you run multiple completeness reports across different GL Groups, you will continue to manage them separately. The difference is that each report is now handled inside the app rather than in individual spreadsheet files.