Version 1.0, last updated [DATE]Download as file

Service Description — Audit Scoot

Version 1.0, [DATE]. This document is the “Service Description” referenced by the General Terms and Conditions and the Master Subscription Agreement. It defines the scope against which conformity is measured. It is versioned; the version applicable to an Order Form is the one in force at its Effective Date.

1. Overview

Audit Scoot is a desktop application for audit data analytics. It ingests general ledger data locally, structures it into an analyzable local project file, executes a catalogue of audit analyses, and lets users generate additional analyses through an AI-assisted interface. All Client Audit Data is processed locally on the user’s machine; no transaction data is transmitted to Provider (see GTC §2.2 / MSA §3.2).

2. Ingestion and mapping

  • Input formats: .xlsx and .csv general ledger extracts; trial balance and chart of accounts files where available.
  • Capacity: up to [5] million journal entry lines per Engagement (fair use, GTC §4.8); typical multi-million-row files process locally in [seconds to minutes] depending on hardware.
  • Vertical mapping: assisted alignment of source columns to the canonical schema (e.g., JE ID, posting date, entry date, account number, functional amount, preparer, approver, journal type, descriptions, counterparty, period, entity).
  • Horizontal mapping: assisted classification of the local chart of accounts into a standardized 4-level financial hierarchy, by account number ranges and account-name text.
  • Validation: reconciliation checks between journal entries, trial balance, and chart of accounts, with an exceptions view (e.g., accounts in TB not in JE, unbalanced journals) to be resolved or documented before analysis.

3. Analysis catalogue (v1.0)

The Service includes 30 or more built-in analyses, grouped into modules covering the general ledger and the statements it produces, revenue and receivables, purchases and payables, and audit completion. Each produces on-screen results with drill-down to journal-entry lines.

Analyses are added over time; the number above is a floor, not a fixed scope. The binding list for any given Order Form is the catalogue of the version in force at its Effective Date.

Some analyses require Client Audit Data that does not exist in the general ledger — for example subledgers, asset or vendor registers, or system access logs. Those analyses are identified as such in-application and become available only once Customer supplies the corresponding data. Provider does not warrant that any analysis dependent on such data is operable on a general ledger alone.

The exact list and parameters per analysis are documented in-application. The catalogue is versioned; every Output is stamped with the catalogue version; material methodology changes are documented in release notes (GTC §2.5 / MSA §3.5).

4. AI-assisted analysis generation

The user types a question; the application sends only the Mapping Metadata and the question to Provider’s AI service, which returns a declarative analysis specification (database query plus output configuration). The query executes locally, read-only, and renders through the standard output components. Generated analyses are drafts requiring professional review (GTC §2.4 / MSA §3.4). Fair-use guideline: [500] queries per user per month.

5. Outputs and the Engagement Archive

  • On-screen tables, charts, and KPI views with drill-down to journal lines.
  • Exports to Excel (including drill-down workbook format).
  • Engagement Archive: a machine-readable local export per Engagement containing the analysis parameters, executed queries, result sets, catalogue version, and timestamps, designed for inclusion in the customer’s audit file (retention is the customer’s responsibility, GTC §6.4 / MSA §8.5).

6. Environment and connectivity

  • Platform: Windows [10/11, 64-bit]; [macOS: roadmap]. Recommended: [16] GB RAM for large datasets.
  • Connectivity: internet required for activation, licence checks, and AI features; analysis execution is local; offline usage records are queued and synchronised.

7. Support

Email support on Dutch business days, response target [1] business day. Onboarding assistance for the initial mapping for the first [2] Engagements. In-application documentation.

8. Exclusions

The Service does not: provide audit, accounting, tax, or legal advice; perform audit procedures or provide assurance; guarantee detection of all errors, anomalies, or fraud; act as an archiving or records-retention service; include ERP connectors, continuous monitoring, or multi-user server deployment (roadmap items are not commitments).

Cookie settings

This site sets no analytics or marketing cookies. Strictly necessary storage only: portal cookies (session, CSRF) when you log in, and browser localStorage for your currency preference.

View Cookie Policy