API & Data
Data Integrity
One command runs automated checks across your entire revenue chain and tells you exactly what's healthy — and what needs attention.
Why it matters
Muntri validates every record as it's created — but a data-quality report gives you a single, trustworthy view of your whole revenue chain: are opportunities linked to accounts, do won deals have contracts, do the amounts line up from deal to contract to revenue?
Run the check
Admins can run the full report on demand and read a clear pass/fail summary.
{
"summary": {
"total_checks": 16,
"passed": 16,
"failed": 0,
"critical_failures": 0,
"health": "healthy"
},
"checks": [
{ "check": "Opportunities without account", "count": 0, "status": "pass", "severity": "critical" }
]
}
Reading the result
Each check carries a severity, and the summary rolls them into an overall health status:
| Health | Meaning |
|---|---|
| healthy | No critical failures |
| degraded | Some failures, but none critical |
| critical | One or more critical failures — act now |
What gets checked
The report groups checks by how much they matter.
These break the revenue chain and should always be zero:
- Opportunities without an account
- Orders without an opportunity
- Contracts without an account
- Won opportunities without a contract
- Won opportunities without a revenue schedule
- Negative amounts on opportunities, orders or contracts
Real data-quality problems worth fixing soon:
- Opportunities without a stage
- Orders without an account
- Contracts without an opportunity
- Won deals where the amount doesn't match the contract total
- Contracts ending before they start
- Converted leads with no linked contact
Improvement opportunities:
- Contacts without an account
- Won opportunities missing contact roles
- Revenue schedules with no linked contract
- Revenue schedules where the value doesn't match the opportunity
How to act on it
flowchart LR
A[Run the check] --> B{Failures?}
B -->|none| C[Healthy — done]
B -->|critical| D[Fix chain gaps first]
B -->|high / warning| E[Clean up data quality]
D --> A
E --> A
classDef n fill:#ffffff,stroke:#2563eb,stroke-width:1.5px,color:#0B1024;
class A,B,C,D,E n;Run it after a big change
A CSV import, a CRM migration, or a large bulk edit are perfect moments to run the check — confirm the chain is intact before you rely on the numbers.