# 1. Reconciliation Hell: The Paper Chase That Never Ends
Your purchase order says one thing. The invoice says another. The receiving report tells a third story.
Welcome to **reconciliation hell**—the endless process of matching documents, investigating discrepancies, and resolving conflicts between systems that should agree but don't.
### The Numbers Don't Lie
According to McKinsey & Company, **procurement accounts for 50-80% of a company's cost base** ([Source: McKinsey via Precoro, 2025](https://precoro.com/blog/procurement-cost-reduction/)).
Administrative overhead—including reconciliation processes—represents a **hidden drain** on these resources. Companies report dedicating significant staff time to invoice matching, exception handling, and payment dispute resolution.
For a company with $100M in annual procurement, even a conservative estimate of **10-15% consumed by administrative overhead** represents **$10-15M in hidden costs**.
### What This Cost Actually Includes
The hidden expenses add up quickly:
* **Salaries** for reconciliation teams
* **Time spent** investigating exceptions
* **Delayed payments** due to unresolved disputes
* **Opportunity cost** of talented professionals performing manual data matching instead of strategic work
### The Root Cause
The problem is simple: **multiple systems of record** with no authoritative source of truth.
Your ERP contains one version of an order. Your supplier's system contains another. The logistics provider has a third version. The payment system has yet another.
Each transaction requires **extensive cross-referencing**. Every discrepancy triggers investigation that can take days or weeks to resolve.
### The Compound Effect
These costs compound across thousands or millions of transactions annually. They create a **massive drag on operational efficiency**.
The reconciliation burden doesn't appear as a distinct line item. It hides across multiple departments and budget categories.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/the-business-case-for-blockchain-in-supply-chain/the-hidden-costs-in-supply-chain/1.-reconciliation-hell-the-paper-chase-that-never-ends.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.