Frequently asked questions about DataSnipper's Financial Statement Suite module.

These checks apply to an FSS project file being opened through Import Project. For a project that will not import, including a corrupt-file error, the next step depends on whether you created it or received it from someone else. An error affecting an individual supporting document inside an Excel workbook is a different troubleshooting context.

If you received it, ask its creator to export the project again from the FSS Homepage project menu and share the unchanged exported file through an approved file-sharing location, such as OneDrive or SharePoint. Use Import Project to open that file. Exporting a marked-up financial-statement PDF is a different operation.

Preserve the original project. If a self-created project or fresh export still fails, contact DataSnipper Technical Support with the exact error and available export/import versions and transfer details.

Prior Period Consistency (formerly Prior Year Consistency) can miss prior-period values in statements of changes, net-assets-attributable tables and other horizontal or complex layouts. This is a known detection limitation under active improvement, even when the same layout is used across funds. It does not establish that your formatting caused the problem, and reformatting all your funds is not a reliable fix.

An explicit numeric year header is one factor worth checking, but it does not establish the cause of missed matches. Check the FSS version against the latest release, whether Server-Side Processing is enabled and, where relevant after a Prior Period Consistency rollout, whether the project has been recreated or rerun.

For affected items, use manual tickmarks and comments, or a manual reference where that control is available, to complete and document the audit check.

DataSnipper Technical Support can investigate in your current support conversation using a sanitized example, the affected page and table, the FSS version and whether Server-Side Processing is enabled. Share the information available; broad formatting changes do not need to be repeated before asking for help.

These checks and workarounds do not guarantee automatic detection, and no fix date is promised.

Financial Statement Suite only performs tests on numerical values, excluding numbers within a paragraph of text. To check consistency in disclosures, use Version Comparison outside of Financial Statement Suite, which highlights all changes rather than numeric ones only.

Yes. Selecting the calculator icon (top right) lets you manually add up numbers. Click the calculator, then drag to select the amounts you want to verify.

DataSnipper flags items as inaccurate only when it is reasonably certain they should have summed together. If the difference is too large, DataSnipper assumes the amounts were not intended to sum, so no flag appears. Use the calculator icon (bottom right) to manually check those cases.

Yes. Select any applied tickmark and choose Custom tickmarks. From there, update it to an existing custom tickmark or create a new one.

No, this is not supported within Financial Statement Suite. Use Document Matching instead: the trial balance data can be used as input to match against figures in the financial statement report.

Yes. DataSnipper recognizes numbers as negative if they are in brackets or have a minus sign before or after them. If a number is not immediately recognized as negative, use the Recognize Text feature to overwrite the previous text layer with DataSnipper's OCR technology.