Try the sample free

Methodology note · for the audit file

How Journalscope selects and scores journals

Method as of 30 October 2026 · applies to the engine published on this site (SHA-256 checksums)

Run it on the sample

Journalscope is a set of fixed, documented rules applied to the ledger export you load. It does not use machine learning, it does not decide what is inappropriate and it does not replace your testing: it gives you a complete, reproducible population, a risk-ranked list and a selection you can explain to a reviewer or an inspector.

1. The journal population

2. Completeness check: trial balance roll-forward

With a trial balance, every account is rolled forward: opening balance + ledger movement in the period = expected closing balance, compared with the closing balance in the trial balance. An account agrees when the difference is within 0.01 (settable).

StatusMeaning
agreesOpening + movement equals closing within the tolerance.
does not agreeThe difference is larger than the tolerance: the extract may be incomplete, or the trial balance is from a different date.
in ledger, not in trial balanceThe ledger has movement on an account the trial balance does not list.
TB closing balance is blank or not a numberThe closing figure could not be read, so the account is never reported as agreeing.
TB opening balance is not a numberThe opening figure could not be read. A blank opening balance counts as zero (a new account).

The conclusion is written on the Summary sheet: either every account rolls forward ("the journal population is complete for these accounts") or the number of accounts that do not. Without a trial balance the workpaper says completeness was not tested by roll-forward. Two further checks: journal numbering gaps (for each number prefix with at least five numbered journals, every missing number range is listed) and population debits = credits.

Journalscope completeness panel for the fictional sample: debits equal credits, two accounts do not roll forward and one numbering gap.
The completeness panel for the fictional Larkfield Components sample (real app output).

3. Criteria and risk score

Each journal is tested against 19 criteria drawn from the characteristics of inappropriate journal entries in ISA 240 (32(a) and its application material), AU-C 240 and PCAOB AS 2401. A criterion is applied only when the export has the field it needs; the Criteria sheet says which were applied and which were not, and why. The risk score of a journal is the sum of the weights of the criteria it meets.

IdCriterion and rule (defaults)WeightCharacteristic it targetsNeeds in the export
C01Posted at a weekend
Posting date (or entry date) falls on a Saturday or Sunday.
1Entries made outside normal working patterns, when review is less likely.Posting date (entry date too, when present)
C02Posted on a public holiday
Posting or entry date is a public holiday in the chosen calendar or one of your own non-working days.
1Entries made outside normal working patterns, when review is less likely.A holiday calendar or your own non-working days
C03Round amount
A line amount is a multiple of 1,000 and at least 1,000 (both settable).
1Round numbers are a recognised characteristic of estimates and manipulated entries.Amount
C04Amount ending in 999
A whole line amount of 999 or more ends in 999.
1Consistent ending numbers just below an authorisation limit.Amount
C05Large journal (at or above your threshold)
Total debits of the journal are at or above the threshold you set (off until you set one).
1Entries large enough to be material on their own.A large-journal threshold you set
C06Entered after period end, dated in the period
Entered after the period end but dated inside the period.
3Post-closing entries made in preparing the financial statements.Entry date
C07Entered long after its effective date
Entered more than 30 days after its posting date (settable).
2Back-dated entries that change a period already reported internally.Entry date
C08Posted by a user who seldom posts journals
The user posted 5 journals or fewer in the period (settable).
2Entries made by individuals who typically do not make journal entries.User
C09No user recorded
The user field is empty while other journals have one.
2Entries that cannot be traced to a person.User
C10Hits a seldom-used account
An account used on 3 lines or fewer in the period (settable).
2Entries to unrelated, unusual or seldom-used accounts.Account
C11Keyword in the narrative
A line narrative contains one of your keywords.
1Narratives that point to adjustments, corrections or instructions from management.Narrative and a keyword list
C12No narrative on any line
Every line of the journal has an empty narrative.
1Entries with little or no explanation or description.Narrative
C13Debits and credits do not balance
Debits and credits of the journal differ by more than 0.01.
3One-sided entries: the ledger or the extract is incomplete or altered.Amount
C14Suspense or clearing account
An account whose name reads like suspense, clearing, unallocated, unreconciled, mispostings, holding, wash, plug, difference or rounding.
1Accounts used to park amounts without a clear counter-entry.Account names (ledger or trial balance)
C15Posted outside working hours
Entered between 22:00 and 06:00 (settable).
1Entries made late at night or early in the morning.Entry or posting time
C16Same person posted and approved
The same person posted and approved the journal.
2No segregation of duties between preparer and approver.User and approver
C17Manual journal
Source or journal type reads like a manual or general journal, an adjustment or a top-side entry.
1Manual entries bypass the controls built into the accounting system.Source or journal type
C18Possible duplicate of another journal
Another journal has the same posting date, total debits and set of accounts.
1Duplicated entries that inflate balances.Posting date, amount, accounts
C19Near period end
Dated in the last 5 days of the period (settable).
1Entries recorded at the end of the reporting period (ISA 240.32(a)(ii)).Posting date and period end

Default keyword list: adjust, adjustment, correct, correction, error, reverse, reversal, reclass, plug, suspense, write off, write-off, writeoff, misc, sundry, per md, per ceo, per cfo, per fd, director, top side, topside, override, bonus, per director, do not. Holiday calendars: UK: England and Wales bank holidays; Ireland public holidays; US federal holidays; No public holidays (weekends only); you can add your own non-working days. Every threshold, the calendar and the keyword list are recorded on the Summary sheet of the workpaper.

4. Selection: key items plus an unpredictable element

5. What Journalscope does not do

6. How to document reliance (ISA 240, ISA 500, ISA 230)

ISA 240.32(a) requires procedures to test the appropriateness of journal entries recorded in the general ledger and other adjustments made in preparing the financial statements, including entries at the end of the reporting period. ISA 500.9 requires you to evaluate whether information produced by the entity is sufficiently reliable for your purposes, including its accuracy and completeness. ISA 230 requires the file to show what was done, by whom and the evidence obtained. (Paragraph references are to ISA 240 and ISA 500 before their latest revisions, which take effect for later periods; check them against the versions you apply.) A file that relies on Journalscope usually holds:

  1. Source of the data (ISA 500.9): who extracted the ledger and trial balance, from which system, entity and period, on what date; the file names and SHA-256 values shown on the Summary sheet.
  2. Completeness: the roll-forward conclusion and its exceptions (Completeness sheet), the numbering gaps and the debits = credits check, with your follow-up of any exception.
  3. Criteria and parameters: the Criteria sheet (applied or not, and why), each threshold and your reason for it, for example a large-journal threshold set at performance materiality.
  4. Selection: the Sample sheet with the key-item rule, the random seed and your completed evidence columns.
  5. The tool: this page saved as a PDF with the date of your run, and the engine checksums from the security page, so a reviewer knows exactly which rules were applied.
  6. Conclusion: section 5 of the Summary sheet, completed and reviewed.

Questions about the method: support@atesensoftware.com. Changes to criteria or defaults are dated on this page.