Living Between SAP and a Hundred Excel Workarounds

This is another composite, not a specific company — but it's an unusually consistent one, because it shows up at nearly every mid-sized or larger business running SAP. SAP is the system of record. It is almost never where the actual day-to-day work happens.

The gap between "in SAP" and "actually done"

An invoice or exception being "in SAP" doesn't mean anyone's acting on it. SAP is excellent at being the ledger of record — it's not built to be a friendly, fast interface for the person triaging a hundred exceptions a day. So a shadow system grows up around it, almost always in Excel, because that's where the actual triage, prioritization, and communication happens.

Every department has its own version of the workaround

AP has a spreadsheet tracking exceptions SAP flagged but nobody's resolved yet. AR has a separate one tracking follow-up status that SAP doesn't represent well. Approvals often happen over email because routing something through SAP's own workflow feels heavier than the decision warrants. None of these spreadsheets talk to each other, and none of them talk back to SAP until someone manually re-enters the outcome.

The reconciliation between systems becomes its own job

At some point, someone has to make sure the shadow spreadsheet and SAP actually agree — and they usually don't, perfectly, because updates happen in the spreadsheet first and get pushed back to SAP later, sometimes in a batch, sometimes when someone remembers. That reconciliation is quiet, recurring work that doesn't show up on anyone's job description but consumes real hours every week.

Audit season turns the gap into a real problem

SAP's own audit trail is solid for what happened inside SAP. It has nothing to say about the decision made in a spreadsheet, or the approval that happened over email before someone updated the record. Reconstructing the real story of how a transaction moved from flagged to resolved means piecing together SAP exports, spreadsheet history, and email threads — for every item an auditor wants to trace.

This isn't a SAP problem, exactly

SAP is doing what it was built to do — being a rigorous, comprehensive system of record. The gap isn't a flaw in SAP; it's that the fast-moving, exception-heavy operational work around AP, AR, and approvals needs a different kind of tool than a ledger, and without one, that tool ends up being whatever's on hand, which is usually a spreadsheet.