Use case · Scaling without headcount
Four people on reconciliation. Does the fifth one fix it?
“That is why a bigger team often produces a bigger close, not a faster one. The problem sits upstream, and headcount does not reach upstream.”
- From
- Your controller
- Role
- Reconciliation specialist, full time
- Reason
- “Volumes are up again. Matching the PSP reports takes the whole team, every month.”
Approve the request and see what changes for the team.
Illustrative request.
Checking by hand
At high volume, checks turn into samples. Samples miss the difference that matters.
“At 150,000 transactions a month, spread across two or three payment providers, a marketplace feed, an order system and manual corrections, that clean line becomes impossible to keep. No single person can watch it.” From the Actuals blog
Check a sample first, then match every transaction. Three differences are hidden in this month.
Illustrative month of 150,000 transactions. Each block holds 1,000 of them. The sample checks 8 blocks, about 5 percent.
The week of the fifth hire
What would the fifth person do all week? The same as the other four.
“Before Actuals, Recharge relied heavily on spreadsheets and tools like Power BI, dedicating extensive manpower solely to managing reconciliation tasks.”
From the Recharge.com story

“Now that Actuals automates reconciliation, our team can focus on resolving issues instead of getting bogged down in the process itself.”
Freddy Dijkman, CFO, Recharge.comSwitch to see where the same week goes when matching runs every day.
- Downloading reports
- Matching in spreadsheets
- Chasing differences
- Resolving real exceptions
- Analysis
Illustrative week of one person. “Finance teams report saving multiple hours per week per team member on reconciliation, redirecting that time to analysis.” From the Actuals FAQ.
From the customer files
Ask our customers what it would take without Actuals. The answer is people.
Switch Actuals off to see what each team says it would need.

Processes that previously required multiple people are now handled in a structured and scalable way. As shared internally at Grover.
“If Actuals were to break down, we would need two to three additional full-time employees to handle reconciliation manually.” Payments Associate Manager, Grover

Scaling into new countries does not require workarounds or additional headcount.
“Without Actuals, reconciliation would be extremely labour-intensive and simply not scalable.” CFO, Flowbird

Actuals automates high-level reconciliations. The team resolves the outstanding issues.
Spreadsheets, Power BI and extensive manpower, dedicated solely to managing reconciliation.

Every order, payment, refund and settlement matched at transaction level. From monthly firefighting to daily control.
Reconciliation in Excel, with month-end checks taking almost two weeks across two million orders a year.
How Actuals takes it on
Match every transaction upstream, every day. Your team works on the exceptions.
Press the button to split bulk issues from true exceptions.
Illustrative day.
- Found the same day
“Immediate mismatch detection, explanation, and resolution on a daily basis.”
- Bulk apart from exceptions
“Clear separation between bulk issues and true exceptions.”
- Investigated together
“Structured workflows for collaborative investigation.”
- 10 to 20%
“Finance team time required is approximately 10 to 20 percent during the project, focused on accounting decisions rather than technical work.”
- Several days off the close
“Across the customer base, month-end close is typically shortened by several days. In some cases from one to two weeks down to two to three days.” Customer results vary.
Quotes and figures from the Actuals product page and FAQ.

“Nobody hires the person who owns the match between the payment provider and the ledger. Across more than fifty open finance roles, not one. In most teams that work is nobody’s job and everybody’s evening.” Peter Engel, Founder & CEO, Actuals
Your next finance hireBefore you post the job ad. The 15-minute Actuals scan shows where your numbers first stop matching, upstream of your team.


