Chapter 01
The Audit
We spent four weeks inside your finance group. We interviewed 14 of your 16 finance team members, in effect your entire finance organization, reviewed 7 core systems, and traced every routine, edge case, and breakdown end to end. Nothing was estimated from a distance. We watched each workflow in motion, catalogued each exception, and measured each gap. Every number in this report stands on evidence, not assumption.
This is a complete demo of the audit deliverable, populated with a composite, illustrative client, not a client of record. Your version is built from your team, your systems, your numbers.
14
Team members interviewed
7
Systems accessed
23
Workflows documented
20
Automation opportunities
4-Week Engagement Timeline
Week 1
DC
Kickoff + Scope Alignment
Feb 3
David Chen, CFO · Sarah Mitchell, Controller
In the room
David Chen, CFO · Sarah Mitchell, Controller
What was covered
Settled the review's boundaries, verified system credentials, and named the go-to people in AP, AR, Close, Treasury, and FP&A. The CFO called the close timeline his single biggest headache.
Key finding
By the CFO's own reckoning, the first week of each close goes to untangling roughly three weeks of leftover exceptions from the prior period.
MR
AP Invoice Intake: Full Process Shadow
Feb 4
Maria Rodriguez, AP Team Lead
In the room
Maria Rodriguez, AP Team Lead
What was covered
Observed intake end to end, from invoice landing in email to entry in NetSuite. Our FDE spent three hours alongside the lead, logging each click, tab change, and message.
Key finding
Invoices arrive by four routes: email, the vendor portal, Ramp, and admin-scanned paper mail. There is no unified entry point, so the lead sweeps all four every morning.
AP
AP Exception Handling Workflow
Feb 5
Aleksandra Pymont, AP Analyst
In the room
Aleksandra Pymont, AP Analyst
What was covered
Traced how items are pulled off the queue and sorted: the categories, the reasoning behind each disposition, escalation paths, and typical time per type.
Key finding
12 exception categories drive about 70% of the monthly load, each resolved by the same repeatable decision path. The analyst can recite the logic for all 12 without notes.
JT
Procure-to-Pay Flow Mapping
Feb 6
James Thompson, Procurement Coordinator
In the room
James Thompson, Procurement Coordinator
What was covered
Walked the P2P chain: requisition, PO creation, goods receipt, invoice matching. Captured each point where work passes between procurement and AP.
Key finding
Where the SOP lists four P2P steps, the live process runs 13 with six manual handoffs; the nine extra steps exist only because NetSuite won't link cleanly to the procurement approval chain, forcing everything through email.
LP
AR Collections + Cash Application
Feb 7
Lisa Park, AR Team Lead
In the room
Lisa Park, AR Team Lead
What was covered
Reviewed how collections get ranked, the rhythm of customer outreach, and the way receipts are matched to open invoices, plus a live look at applying incoming wires.
Key finding
Collections are ordered solely by aging bucket, ignoring how customers actually pay; the record shows some clients reliably run late above $50K yet stay current below it, but both get identical treatment.
Week 2
RF
Intercompany Reconciliation Shadow
Feb 10
Rachel Foster, Senior Accountant
In the room
Rachel Foster, Senior Accountant
What was covered
Shadowed intercompany matching across NetSuite for corporate and the two acquired entities, which still run their own QuickBooks files: how items get spotted, paired, and how mismatches are cleared.
Key finding
Matching is done entirely by hand because the same vendor carries different names in each system; the senior accountant keeps her own private map linking those names across all three systems, and when she is away the whole reconciliation grinds to a halt.
MW
Treasury: Daily Cash Position Assembly
Feb 11
Michael Wu, Treasury Analyst
In the room
Michael Wu, Treasury Analyst
What was covered
Stepped through the daily opening routine: gathering balances from four bank accounts in two currencies, stitching them together in Excel, and formatting the result for the CFO.
Key finding
The two-hour morning build is already outdated by the 10:30am handoff because overnight settlements have moved the numbers; the analyst admits it is never quite right by the time anyone looks at it.
KO
FP&A Variance Analysis Process
Feb 12
Katherine Okafor, FP&A Lead
In the room
Katherine Okafor, FP&A Lead
What was covered
Unpacked how the monthly variance package comes together: data sources, number of feeds, effort involved, and why it slips.
Key finding
Variance work cannot begin until close wraps, and close runs 18 to 22 days; the package lands on day 28 to 30, by which point the month is gone and the next has begun, leaving leadership perpetually reading old numbers.
BN
Ramp + NetSuite Integration Review
Feb 13
Brian Nakamura, AP Specialist · Sarah Mitchell, Controller
In the room
Brian Nakamura, AP Specialist · Sarah Mitchell, Controller
What was covered
Examined how spend data travels from Ramp into NetSuite: where the sync runs on its own, where it stalls, and what gets keyed in again by hand.
Key finding
Ramp's spend categories have no match to NetSuite GL codes, so every close an analyst re-tags 150 to 220 Ramp transactions by hand: two full days of work.
SM
Close Management: Full Entity View
Feb 14
Sarah Mitchell, Controller
In the room
Sarah Mitchell, Controller
What was covered
Mapped the close from start to finish across all 4 entities: which land on time, which don't, where the bottlenecks sit, and how tasks are tracked.
Key finding
Close lives in 4 standalone Excel checklists, so the controller can't see who is on track without inspecting each one by hand; the two acquired entities routinely run late because upstream AP exceptions aren't cleared in time.
Week 3
Exception Pattern Analysis
Feb 17
What was covered
Sorted all 47 exception types spanning AP, AR, and intercompany into resolution decision trees, and pinned down the 12 types responsible for 70% of the volume.
Key finding
Each of the leading 12 exception types resolves along a fixed decision tree that the AP analyst knows by heart, yet not one of them is written down anywhere.
Cross-System Data Flow Mapping
Feb 18
What was covered
Followed every data handoff among the seven systems, noting which moves are automated, which are manual, and which are broken, and drew up the complete integration dependency map.
Key finding
Three of the seven system links depend on moving data by hand, and the Ramp-to-NetSuite re-tagging by itself eats two full days out of every close.
Time Allocation Study
Feb 19
What was covered
Measured how the 16-person finance organization truly spends its hours, sorting each one into coordination, data gathering, review, exception handling, or strategic work.
Key finding
Roughly 60% of the department's hours go to work that agents could take on, while only 8% reaches the strategic analysis and planning these people were actually hired for.
Process Map Construction
Feb 20
What was covered
Drew side-by-side maps for each of the six sub-functions, setting the documented SOP against the workflow we actually observed and flagging every gap, manual handoff, and undocumented step.
Key finding
In every one of the six sub-functions the real work is three to four times as involved as the documentation suggests. AP alone runs 13 actual steps against the four in its SOP.
Conformance Gap Analysis
Feb 21
What was covered
Held documented policy up against observed practice to surface compliance exposure, single points of failure, and undocumented tribal knowledge.
Key finding
Five critical risk items surfaced, among them a 4% intercompany error rate that slips through unnoticed until the external audit and a reconciliation process that rests entirely on one individual.
Week 4
Automation Opportunity Identification
Feb 24
What was covered
Paired each manual workflow with a candidate automation and rated them on ROI potential, build difficulty, and how tangled their dependencies are.
Key finding
A total of 20 automation opportunities emerged across the six sub-functions, worth a projected $1.2M a year, with AP contributing $600K of that on its own.
Implementation Roadmap Design
Feb 25
What was covered
Laid the opportunities out over a four-month build schedule, wiring up dependencies, singling out Month 1 quick wins, and shaping the accuracy ramp.
Key finding
Month 1 goes after the busiest workflows first: AP exception triage alone handles 179 exceptions a month, starting at 88% accuracy in week one and climbing past 97% by go-live.
ROI Modeling + Business Case
Feb 26
What was covered
Assembled a bottom-up ROI model covering labor redeployment ($680K), discount capture ($240K), DSO improvement ($180K), and error reduction ($140K), checking every assumption against what we observed.
Key finding
The model stays deliberately conservative, drawing only on observed volumes and measured cycle times with no stretch projections, so every dollar ties back to a specific workflow and a measured inefficiency.
Internal QA + Deliverable Assembly
Feb 27
What was covered
Reconciled every finding against its source data, peer-reviewed each process map, exception grouping, and ROI figure, and put together this interactive deliverable.
Final Review + Handoff Prep
Feb 28
What was covered
Ran a last QA sweep over the deliverable, readied the scope materials for the Phase 2 conversation, and wrote down the system access and staffing commitments implementation will require.
Team Members Interviewed
DC
David Chen
CFO · Executive
SM
Sarah Mitchell
Controller · Financial Control
MR
Maria Rodriguez
AP Team Lead · Accounts Payable
AP
Aleksandra Pymont
AP Analyst · Accounts Payable
JT
James Thompson
Procurement Coordinator · Procurement
LP
Lisa Park
AR Team Lead · Accounts Receivable
RF
Rachel Foster
Senior Accountant · Accounting
MW
Michael Wu
Treasury Analyst · Treasury
KO
Katherine Okafor
FP&A Lead · Financial Planning
BN
Brian Nakamura
AP Specialist · Accounts Payable
DK
Diana Kovacs
AR Analyst · Accounts Receivable
TB
Tom Brennan
Staff Accountant · Accounting
PS
Priya Sharma
Expense Manager · Expense Management
CM
Carlos Medina
Tax Analyst · Tax
Systems Accessed
NetSuite
Primary ERP
The hub the whole org runs on: 6 systems feed into it, but 3 of those links are currently broken.
Power BI
Reporting & BI
Pulls from NetSuite on a hands-off schedule. The one integration that works.
QuickBooks Action needed
Accounting (2 acquired entities)
The two acquired entities still run their own QuickBooks files; every intercompany match is done by hand, and the whole thing hinges on a single staffer's private crib notes.
Ramp Action needed
Corporate Spend
Each close, someone hand-remaps 150 to 220 charges onto the right NetSuite GL codes.
Bank Portals Action needed
4 accounts, 2 currencies
The daily cash picture is rebuilt by hand in a spreadsheet each morning and is already out of date once it lands.
Concur
Travel expenses at the two acquired entities
Runs on a separate track from NetSuite, doubling up on the work Ramp already handles.
Excel
Used everywhere
The default glue for close checklists, aging, cash positions, FX tracking, and variance work alike.
AutomaticManualBroken
Next chapter
The Findings