The most common challenge in SME lending in Mexico is not risk appetite. It is visibility. A large share of Mexican businesses — particularly micro and small enterprises — have no audited financials, no credit bureau history, and no formal reporting structure that a traditional underwriter can work from.
What they do have is SAT data.
Since electronic invoicing became mandatory for most Mexican businesses, the SAT database holds years of granular transaction data: who sold what, to whom, in what amounts, and whether the tax obligations behind those transactions were fulfilled. For an underwriter, this is an income statement, a customer concentration report, a compliance check, and a payment behavior signal — all accessible through a single API integration.
What you can derive from SAT data through the CRiskCo API
Revenue proxy (AR invoices): The `/ar-transactions/invoices` endpoint returns sales invoices over any date range. Sum of invoice totals over a trailing 12 months provides a revenue proxy more reliable than self-reported revenue because it comes directly from SAT.
Cost and expense structure (AP transactions): The `/ap-transactions/invoices` and `/ap-transactions/expenses` endpoints show what the business is spending and on whom. Gross margin can be approximated by comparing AR and AP invoice volumes.
Standardized financial reports: `/financialreports/standard/profitandloss` and `/financialreports/standard/balancesheet` return CRiskCo-normalized financial statements mapped to a consistent schema — regardless of which ERP or accounting system the applicant uses. Key ratios (DSO, Quick Ratio, Debt Ratio) are derived from these.
Customer concentration: The distribution of receiver RFCs in AR invoices reveals whether a business is dependent on a small number of clients. High concentration in a single buyer increases credit risk if that relationship ends.
SAT compliance status: `/GetCompanyTaxStatus` returns the Opinión de Cumplimiento — POSITIVO or NEGATIVO. A NEGATIVO opinion lists the specific outstanding obligations by period. Any negative status should be a mandatory review trigger in your underwriting workflow.
Historical FinScore: `/GetHistoricalFinscore` provides CRiskCo's proprietary risk score over time. A declining trend in the 3 months before application is a meaningful signal even if the latest score appears acceptable.
A practical underwriting workflow
A typical integration with the CRiskCo API looks like this:
The full workflow runs in under 60 seconds from RFC submission. No manual document review. No waiting for the applicant to upload bank statements.
What the data doesn't cover — and how to compensate
SAT data is powerful but not complete. Three limitations worth noting for underwriters:
CRiskCo provides direct SAT data access, standardized financial reports, and historical risk scoring through a single API. Read the full technical integration guide → or contact our team →.