← All workflows

Workflow run

7/8/2026, 1:00:54 PMDrafting from research 2026-07-08Voices: dror
Draft 1 / 1 · Brief #2 · Dror
BlackLine publishes seven benchmarks for 'agentic financial close readiness'
gate: passapprove

Final post

A new framework is going around: seven benchmarks to measure whether your finance team is "agentic close ready." Journal automation coverage. Reconciliation maturity. Exception handling. AI risk controls.

It's a well-built scorecard. It's also solving the wrong problem.

The premise is that finance close will be run by agents within 12–24 months, and the readiness gap is in your process maturity. What the premise skips: agents can only automate what lives inside the system they can reach. And SAP finance close doesn't live inside SAP anymore.

Look at a real close cycle in an ECC or S/4HANA shop:

- Balance-sheet reconciliations run in a third-party tool that pulls FAGLB03 nightly and never writes back
- Manual accruals get proposed in a shared Excel that three people edit at once
- Intercompany matching happens in email threads with attachments named FINAL_v7_use_this
- Exception workflows are Teams chats
- Approvals are forwarded PDFs

SAP holds the general ledger. Everything that makes the close actually take two weeks — the adjustments, the chasing, the reconciling of things that shouldn't need reconciling — happens outside it.

Put agents on top of this and you get faster fragmentation. The agent reconciles what the spreadsheet says with what the third-party tool says, and neither of them is what SAP shows in F.01. You've automated the mismatch.

The real readiness gap isn't AI maturity. It's execution maturity — whether close activities happen inside SAP or around it. Bring the adjustments, exceptions, intercompany work, and approvals back into SAP, on live data, under existing authorizations. Now an agent has something governed to act on.

Close the month in 2 days, not 2 weeks. That was the SAP investment thesis. It's still available — but not via agents layered on top of a fragmented close.

Comment "GAP" and I'll send the diagnostic we use to map where close actually happens in an SAP shop vs. where the org chart says it does.

Would appreciate your POV on this — Joshua Greenbaum, Jon Reed, Timo Elliott
338 words · CTA GAP · tagging Joshua Greenbaum, Jon Reed, Timo Elliott