Checks at entry, in the system that already holds the controls.
SAP has the control framework. What it does not have is something running every control on every document at the moment it arrives, which is why the exceptions surface at the close instead.
What OHM reads, what it writes back
Reads from SAP
- Vendor line items and open payables (FBL1N)
- Purchase orders and their history (ME2N)
- Goods receipts and material documents (MIGO, MB51)
- Invoice verification documents (MIRO) and the vendor master
Writes back into SAP
- Findings against the document, with the clause or rule they were tested on
- Blocks and holds through the same statuses your team already works with
- The audit trail, immutable and re-readable months later
SAP remains authoritative. OHM does not re-post your ledger elsewhere, and there is no shadow book to reconcile.
Where you start
An export, not a project.Standard extracts from the reports above, for a 90-day window. Nothing needs to be built, and no basis work is required to find out whether there is money in it.
Three-way match tolerance in SAP is configured once and applied uniformly. Most of what leaks sits in what tolerance permits — a rate above contract inside tolerance still clears.
What runs against it
The same team, whichever system holds the books. The checks depend on the contract, the PO and the receipt — not on one ERP’s schema.
Run it on 90 days of your own SAP data.
One export. No connector, and nothing to install.
$Check your savings→