EidralFinance Engine
Chapter 02

The audit: we learn how the work actually moves

4 weeks on site with the finance team. Process owners get shadowed rather than surveyed, because the shadow spreadsheet and the approval that happens in a hallway never come up on a call.

What it produces

A process and time map, a controls register, the exception taxonomy in your team's own wording, a volume baseline pulled from the systems rather than estimated, and a build plan signed by the people who run the work. $15–25k, credited in full against a build signed within 90 days.

Audit input 01 — Interviews

14 sessions with 11 people. Every session transcribed and tagged against the workflow it describes.

RoleSessionsMinutes eachFocus
AP analysts490Invoice intake, coding decisions, and which screen they open first
Controller360Close sequence, approval thresholds, intercompany tie-out
AR and collections360Dunning cadence, dispute handling, cash application
Procurement245PO creation, receipt discipline, vendor master hygiene
CFO245Reporting cadence, cash position, what gets escalated
Audit input 02 — Documentation

38 sources ingested, indexed and made queryable. The working spreadsheets matter most, because they are where the real process lives when the SOP has drifted.

SOPs and desk procedures11
Approval and delegation policy4
Chart of accounts and vendor master6
Close checklists8
Working spreadsheets found in use9
Audit input 03 — Software

9 systems mapped, including the ones nobody lists on an architecture diagram.

Scope
Systems mapped
9
Workflows analysed
12
Exceptions sampled
340
Manual hours per year
18,800

In-scope process work, not total department labour

Where the hours come from
DriverVolumeHours/yr
Supplier invoice intake and coding42,000 invoices at 7 min4,900
Invoice exceptions7,560 at 22 min, 18% of volume2,772
Month-end close12 closes × 5 people × 6 days3,240
Account reconciliation140 accounts monthly at 35 min980
Vendor statements and correspondenceStatement chases and query handling2,100
AR and collectionsDunning, disputes, cash application3,900
Expense report review6,200 reports at 9 min930
Total in scope18,800
Of 18,800 manual hours a year
68% carried
  • Carried by agents12,784 hrs68%
  • Stays with people6,016 hrs32%

6,016 hours a year remain manual, and should: judgement calls, genuine exceptions, and the relationships that need a person on the other end. The two shares are complements of one another, so they sum to 100 by construction.

Priority workflows
P1

Invoice intake and coding

82% automatable$238k

Highest volume and the most repetitive. Ships first because it also proves the connector work.

P2

Invoice exceptions

71% automatable$166k

Roughly seven in ten exceptions fall into twelve recurring types the audit names.

P3

Month-end close

63% automatable$124k

Task tracking, evidence collection and the intercompany tie-out across four entities.

P4

Account reconciliation

74% automatable$102k

Bank, lockbox and clearing accounts, with only genuine variances surfaced.

P5

Vendor statements and correspondence

58% automatable$76k

Lowest value of the five and the most relationship-sensitive, so it ships last.

The five sum to $706k, the same modelled annual value shown in chapter 01. Bars are each workflow's value against the largest of the five.

Implementation timeline
W1
W4
W8
W12
W16
W20
  1. Audit · 4 weeks
  2. P1 Invoice intake and coding
  3. P2 Invoice exceptions
  4. P3 Month-end close
  5. P4 Account reconciliation
  6. P5 Vendor statements and correspondence
  7. Operate · ongoing

Audit 4 weeks, build 12–14 weeks, then continuous operation. Workflows overlap because the connector work for one is usually most of the connector work for the next.

Illustrative

Session counts, document counts and hours are modelled against the basis company, not recorded from an engagement. The method is real; the volumes are what a 24-person finance function at that size would produce.