← Iron Core System

Sample findings brief

What your teams receive every week: what Iron Core found in your systems, the records behind each finding and what fixing it might be worth. The company and every figure below are fictitious.

Prepared for
A fictitious manufacturer, 420 staff, three sites
Period
Week 46, 9 to 15 November 2026
Systems read
ERP, CRM, service desk, identity directory, workflow log
Produced
On the customer's own infrastructure
Sent to
Finance, IT security and operations leads
4New findings this week
1Confirmed by the owning team
3Duplicate payments to recover
2Closed since the last brief

New findings

Each finding says what the data shows, the records behind it, what fixing it might be worth and which team owns it.

F-46-01ProcessProposedConfidence: high

Invoices wait about six days for a second approval that nine in ten pass unchanged

What the data shows

412 supplier invoices went through two approvals in September. The second approval took a median of 5.8 working days, and 91% were approved with no change or comment. Most were small, routine purchases from long-standing suppliers.

Suggested next step

Finance could approve once below a threshold it sets, keeping the second approval for new suppliers and large amounts.

Second-approval wait, working daysInvoices
024689+median 5.8
Records
Workflow log, 412 approvals, 1 to 30 Sep 2026
Worth
High: faster supplier payments, more early-payment discounts
Owner
Finance
F-46-02AccessIn progressConfidence: high

37 ERP accounts hold administrator rights they haven't used in six months

What the data shows

Of 52 accounts with ERP administrator rights, 37 have not used them since May. Six of those are linked to directory accounts that are already disabled.

Suggested next step

IT security reviews the rights and removes what isn't needed. The account list is in the Iron Core console for IT security only; this brief does not name accounts.

ERP administrator accounts52 in total
15 used31 unused since May6 disabled users
Records
ERP audit log and identity directory, 1 May to 15 Nov 2026
Worth
Medium: smaller attack surface, cleaner access review
Owner
IT security
F-46-03MoneyConfirmedConfidence: high

Three supplier invoices were paid twice

What the data shows

Three pairs of October payments match on supplier, amount and bank account, four to six days apart, under slightly different invoice numbers. Finance checked them against the paper invoices and confirmed all three.

Suggested next step

Ask the suppliers for refunds or credit notes, and add a check for the same supplier and amount within a few days before payment runs.

Matched payment pairsOctober 2026
SupplierInvoice numbersPaid
Supplier A4471 · 4471/A3 and 7 Oct
Supplier BFV-0932 · FV093210 and 16 Oct
Supplier C2026/10/118 · 2026-10-11821 and 27 Oct
Records
Accounts payable ledger and bank statements
Worth
High: the three payments recovered
Owner
Finance
F-46-04CustomersInvestigatingConfidence: medium

Late-delivery complaints cluster on one warehouse route

What the data shows

Route 7 carries 14% of shipments but drew 41% of late-delivery complaints this quarter. The rise starts in the week the route changed carrier. The pattern is clear; the cause is not yet confirmed.

Suggested next step

Operations compares carrier hand-over times on route 7 with the other routes before deciding anything.

Share of shipments and of complaintsQ4 to date
Route 7Route 3Route 5Others 14%41% of complaints shipmentscomplaints
Records
CRM tickets and warehouse dispatch system
Worth
Rated once the cause is known
Owner
Operations

Closed since the last brief

Iron Core keeps measuring after a fix, so the brief can show whether it worked.

FindingWhat the team didMeasured sinceStatus
The same suppliers recorded several times in the ERPFinance merged 212 duplicate supplier recordsNew duplicates: none in four weeksClosed
Contract renewal reminders sent after the notice deadlineLegal moved the reminder to 60 days before the deadlineRenewals missed: none in six weeksClosed

Asked this week

Anyone with access can ask Iron Core a question in plain language. Answers cite their sources and use only data the person asking is allowed to see.

Why did invoice approvals slow down in September?

The second approval step was extended to all supplier invoices on 1 September; before that it applied only above a set amount.[1] The median wait for the second approval rose from 1.9 to 5.8 working days in the same week.[2]

The number of invoices did not change much over the period, so volume does not explain the delay.[3]

  1. Approval policy, version 4, effective 1 Sep 2026
  2. Workflow log, second-approval steps, 1 Jun to 30 Sep 2026
  3. ERP accounts payable, invoice count per week

How to read a brief

Impact is rated high, medium or low. A real brief also puts it in your currency and hours, calculated from your own records, never from benchmarks. Findings go to teams and processes; a brief never ranks, scores or names individual employees.

Confidence: high

The records match exactly and were checked against their source system.

Confidence: medium

A consistent pattern in the data. The cause still needs a person to find it.

Confidence: low

A weak signal, listed only when it is cheap to check and costly to miss.

Status

Proposed, investigating, in progress, confirmed or closed. The owning team sets it, not Iron Core.

Important information

Read this before relying on a brief like this one. The contract and the data processing agreement govern each deployment.

  1. This brief is fictitious. The company, systems, suppliers, figures and records on this page are invented to show the format. They do not describe a real organisation.
  2. Findings must be checked. Findings are generated automatically from connected data and can be incomplete or wrong. The owning team checks each one before acting.
  3. Estimates are estimates. Impact figures are projections from historical data, not guaranteed savings.
  4. Not an audit. A brief does not replace a financial audit, legal advice or a security assessment.

See inside your company.

Darka Software Darka Software P.S.A. · Księcia Witolda 49/15, 50-202 Wrocław, Poland · KRS 0001015995, District Court for Wrocław-Fabryczna · NIP 8992950274 © 2026 Darka Software P.S.A.
Darka Software

Darka Software P.S.A.
Księcia Witolda 49/15
50-202 Wrocław, Poland

KRS 0001015995, District Court for Wrocław-Fabryczna, VI Commercial Division · NIP 8992950274

PrivacyCookie settings© 2026 Darka Software