Skip to content
Request a demonstration

Financial Intelligence · Expanded Financial Intelligence

Financial Anomaly Investigations

Connect unusual financial records with the invoices, payments, vendors, contracts and evidence around them, and support investigation, human decisions and a documented o…

Demonstration: Quillfeather Retail Group (fictional) · Retail. Fictional data and a scripted answer.

The situation

Organisation
Quillfeather Retail Group (fictional)
Who is asking
Internal audit manager
Industry
Retail
What happened
An ordinary payments review flagged patterns that deserve a closer look before the year-end audit.

The question asked

Which payments look unusual enough to investigate, and which have an ordinary explanation?

What it reads, and who can see the result

  • Payments ledger, Q3 exportPayments with payee, date and approver.
  • Approval limits documentDelegated authority by role.
Reads
Payment lines, payee names, dates and approval records.
Does not read
Supplier bank account numbers or personal data of employees.
Permission
Internal audit's standing read access.
Who sees it
The internal audit manager and the audit committee chair.

Try it

Review each flagged record: confirm it or dismiss it. The totals and the answer below follow your decisions.

DatePayeeNarrationPayment (USD)FindingDecision
04 JulCalder PalletsMonthly pallets8,420MatchedNone needed
13 JulStudio VerityConsulting24,950Just under the 25,000 approval limit
13 JulStudio VerityConsulting, part 224,900Second payment to the same payee on the same day, also just under the limit
20 JulHale CleaningQuarterly6,100MatchedNone needed
27 JulBrightwater ITLicences11,800Posted on a Saturday outside normal processing
02 AugNorthgate PrintMarketing5,200MatchedNone needed
16 AugR. ThorneRefund3,000Round-number refund to an individual with no linked sale
29 AugFenwick EnergyUtilities14,230MatchedNone needed
Flagged
4 of 8 · USD 64,650
Investigate
0 · USD 0
Ordinary
0 · USD 0
Undecided
4 · USD 64,650

The answer

Simulated answer. Written for this fictional case, not produced by a live model. Only the figures in it are computed, from what you decided above.

4 of 8 payments match a pattern worth a look, USD 64,650 in all.

Three of the patterns are the ones audit teams commonly test: payments just below an approval limit, a split into two payments on the same day, and a round-number refund with no sale behind it [S1][S2]. A weekend posting is the weakest signal; there may be a legitimate batch.

A pattern is a reason to ask, not a finding. You have marked 0 to investigate (USD 0) and 0 as ordinary (USD 0); 4 are undecided.

Relies on: S1 · Payments ledger, Q3 sampleS2 · Delegated authority table

Review and approval

The internal audit manager decides. Approving the investigation list opens a case for each payment marked to investigate. It does not accuse anyone or stop a payment.

Not ready to approve. 4 flagged payments are still undecided. Confirm or dismiss each one first.

In the product this is a different person with the right permission. Here you play that role to see the rule.

What it produces

registerDraft, not approved

Investigation register

  • 0 payments opened for enquiry, USD 0.
  • 0 payments recorded as ordinary, with the reason.
evidenceDraft, not approved

Pattern evidence

  • Each case lists the pattern, the approval limit and the payments involved.

Limits of this example

  • Detecting a pattern does not show intent; every flagged payment has a person to ask first.
  • The sample is illustrative and the patterns are examples of common tests.
  • This is a scripted demonstration on fictional data. No model was called and no real organisation, person or result is shown.