Is SAP suitable for auditing medical claims in Colombia?
SAP is strong ERP software, but Colombian medical-claims audit requires regulatory and clinical adjudication under the Manual Único de Devoluciones, Glosas y Respuestas of Resolución 2284 de 2023.
SAP is suitable for enterprise finance, procurement and operations, but it was not designed to adjudicate medical-claims audit in Colombia. Arkangel AI fills that gap by running 98 administrative, clinical and financial rules and consolidating a proposed glosa causal per invoice line for the auditor to review.
What SAP does well
SAP is a strong enterprise platform for accounting, procurement, inventory, payments, reporting and configurable workflows. In healthcare organizations, that matters: payer operations need reliable financial records, transaction history, contract data and integration with enterprise systems.
That strength should be framed honestly. SAP can be the financial system of record, but a financial system of record is not the same as a Colombian medical-audit adjudication engine.
What Colombian medical audit requires
In Colombia, a defensible objection to a medical claim needs more than a generic risk score. An auditor has to determine whether an invoice line fails under one of the seven general glosa concepts of the Manual Único de Devoluciones, Glosas y Respuestas in Resolución 2284 de 2023: FA (billing), TA (rates), SO (supporting documents), AU (authorizations), CO (coverage), CL (quality, which includes clinical pertinence) and SA (contract follow-up). That manual replaced the numeric coding of Anexo Técnico 6 of Resolución 3047 de 2008, which has been repealed since 1 April 2026.
That requires three separate reviews:
- Administrative review: identity, RIPS structure, authorization, support documents and filing timeliness.
- Clinical review: pertinence, clinical-record justification and consistency with Colombian Ministry of Health practice guidelines.
- Financial review: billed value vs contract, tariff, benefit plan and patterns such as upcoding, unbundling or double billing.
Where SAP was not designed to fit
SAP was not designed to run those three layers independently, assign the manual's glosa concepts, or evaluate clinical pertinence against Colombian clinical practice guidelines. That does not make SAP weak. It means the problem is outside the design target of a general-purpose ERP.
Arkangel AI was built for the regulatory and clinical decision layer. It uses 27 administrative rules, 29 clinical rules and 42 financial rules, then consolidates findings per invoice line so the human auditor can review traceable evidence before any communication reaches the provider.
A complementary architecture
For most payers, the right framing is not "Arkangel AI vs SAP" as a replacement decision. The clean architecture is complementary:
- SAP or another ERP handles enterprise finance and operations.
- Arkangel AI handles Colombian medical-claims adjudication under the glosa manual that applies to each claim.
- The human auditor keeps the final decision and audit trail.
That separation lets the finance stack stay stable while the audit layer applies Colombian healthcare-specific rules.