Counterparty Risk Signals

Counterparty Risk Signals

Detect financial stress across your supplier and client base — with confidence scoring and recommended actions.

Detect financial stress across your supplier and client base — with confidence scoring and recommended actions.

Why this matters

Why this matters

CFOs and Treasurers face constant pressure to protect cashflow while keeping relationships balanced. Traditional credit bureaus like Dun & Bradstreet, Coface, or Creditsafe provide valuable data, but often in black-box form and at portfolio-wide cost. Internal spreadsheets and ERP exports capture fragments but lack comparability or early warning.

This dashboard brings suppliers and customers together in one view. Each counterparty is matched, enriched, and scored across solvency, liquidity, leverage, payment behavior, filings, and news. A composite stress score and plain-language comment highlight where to maintain terms, tighten exposure, or diversify. For finance leaders, it means protecting working capital and optimizing the portfolio with explainable, action-ready insights.

How Starzdata solves this

How Starzdata solves this

  • Client provides counterparty name, country, and relationship type (customer or supplier).

  • Curated APIs verify company identity, legal name, and registry mapping.

  • Financial KPIs collected: revenue, solvency, liquidity, debt-to-equity, payment terms, filings.

  • Stress score (0–100) built from weighted drivers, with explainable contributions.

  • Each record comes with a plain-language comment and suggested action.

This segment is activated with a blend of trusted sources and your own inputs

Curated APIs

AI reasoning

Web intelligence

User Input

What you get:

What you get:

  • Verified company identity with financial and behavioral KPIs.

  • Composite stress score with weighted drivers for transparency.

  • Plain-language risk summary and suggested action.

  • Customer and supplier risks shown in one standardized table.

  • Ready-to-use exports via API, CSV, or Sheets.

Sample data for this segment

#counterparty name input(input)country input(input)relationship type input(input)client payment terms input(input)year referenceyear reference confidencecompany id externalcompany id external confidencewebsite domainwebsite domain confidencecounterparty namecounterparty name confidencerelationship typerelationship type confidencerevenue latestrevenue latest confidencesolvency scoresolvency score confidenceliquidity ratioliquidity ratio confidencedebt to equitydebt to equity confidencerevenue trend yoyrevenue trend yoy confidencelate payment dayslate payment days confidenceinsolvency filings 12minsolvency filings 12m confidencenegative news mentions 12mnegative news mentions 12m confidencestress scorestress score confidencestress driver solvency wtstress driver solvency wt confidencestress driver liquidity wtstress driver liquidity wt confidencestress driver debt wtstress driver debt wt confidencestress driver payments wtstress driver payments wt confidencestress driver filings wtstress driver filings wt confidencestress driver news wtstress driver news wt confidencecomment
1NordSteel ComponentsSESupplierNet 452024100%CO_52011100%nordsteel.se96%NordSteel Components AB100%Supplier100%148000000100%84100%1.48100%0.62100%6.3100%7100%100%180%2195%0.25100%0.2100%0.15100%0.2100%0.1100%0.190%Stable supplier: strong solvency and liquidity; mi...
2AgriChain FranceFRCustomerNet 302024100%CO_52027100%agrichain.fr98%AgriChain France SA100%Customer100%94000000100%61100%0.98100%1.25100%-3.4100%18100%100%380%6392%0.3100%0.2100%0.15100%0.2100%0.05100%0.190%Rising risk: weak liquidity, leverage up, late pay...
3MedLife DiagnosticsDECustomerNet 302024100%CO_52044100%medlife-diagnostics.de97%MedLife Diagnostics GmbH100%Customer100%152000000100%86100%1.6100%0.55100%4.2100%2100%100%85%1295%0.25100%0.2100%0.15100%0.2100%0.1100%0.190%Low risk: strong solvency and liquidity; on-time p...
4ChemPro PolskaPLSupplierNet 602024100%CO_52061100%chempro.pl99%ChemPro Polska Sp. z o.o.100%Supplier100%118000000100%54100%0.92100%1.6100%-5.9100%24100%1100%480%8190%0.3100%0.2100%0.15100%0.2100%0.1100%0.0590%High risk: weak liquidity, leverage, late payments...
5BuildSmart ItaliaITSupplierNet 302024100%CO_52075100%buildsmart.it99%BuildSmart Italia SRL100%Supplier100%87000000100%73100%1.12100%0.95100%1.9100%9100%100%280%3493%0.25100%0.2100%0.15100%0.2100%0.1100%0.190%Moderate risk: acceptable solvency; minor delays (...
Showing 1 to 5 of 5 entries • Click row for details

Each row represents one counterparty (customer or supplier). Inputs are the client’s name, country, relationship type, and optional payment terms. The enriched outputs include verified identity, financial KPIs, payment behavior, insolvency filings, and negative news mentions. A composite stress score (0–100) is broken down by driver weights. Each row closes with a plain-language risk comment and a suggested action (e.g., keep terms, tighten, move to prepay).

Your questions on this segment, answered

Can the outputs be integrated into ERP, treasury, or CRM systems?

Can the outputs be integrated into ERP, treasury, or CRM systems?

Can the outputs be integrated into ERP, treasury, or CRM systems?

How can this dashboard complement existing bureau subscriptions?

How can this dashboard complement existing bureau subscriptions?

How can this dashboard complement existing bureau subscriptions?

How do you handle counterparties without published financials?

How do you handle counterparties without published financials?

How do you handle counterparties without published financials?

Can I see the driver weights behind each stress score?

Can I see the driver weights behind each stress score?

Can I see the driver weights behind each stress score?

How does web intelligence add value beyond bureau data?

How does web intelligence add value beyond bureau data?

How does web intelligence add value beyond bureau data?

What data sources are combined (registries, bureaus, web signals)?

What data sources are combined (registries, bureaus, web signals)?

What data sources are combined (registries, bureaus, web signals)?

How is the stress score different from a credit bureau rating?

How is the stress score different from a credit bureau rating?

How is the stress score different from a credit bureau rating?

How often are company financials and stress scores refreshed?

How often are company financials and stress scores refreshed?

How often are company financials and stress scores refreshed?

Your questions on this segment, answered

Can the outputs be integrated into ERP, treasury, or CRM systems?

Yes. Exports are workflow-ready in CSV, Sheets, JSON, or via API for seamless integration with ERP, treasury, and CRM.

How can this dashboard complement existing bureau subscriptions?

It does not replace them — it enriches them. Bureau data feeds in via curated APIs, but Starzdata adds structured web signals, explainability, and plain-language actions.

How do you handle counterparties without published financials?

In such cases, the model relies more heavily on payment patterns, filings, and news, while transparently showing confidence levels.

Can I see the driver weights behind each stress score?

Yes. Each score shows the contribution of solvency, liquidity, debt, payment behavior, filings, and news so you can interpret results clearly.

How does web intelligence add value beyond bureau data?

Web signals bring freshness — negative news, payment slippage, or new filings appear before annual accounts, giving earlier warnings.

What data sources are combined (registries, bureaus, web signals)?

We merge company registries and curated bureau feeds (Coface, Creditsafe, D&B) with structured web intelligence, all reconciled under one taxonomy.

How is the stress score different from a credit bureau rating?

Bureau ratings are useful but opaque. The stress score is fully explainable, with weights for solvency, liquidity, leverage, payments, filings, and news.

How often are company financials and stress scores refreshed?

Core financials are refreshed annually from registries and bureau feeds, while payment, filings, and news signals update monthly or on demand.

{ "_meta": { "dictionaryColumns": ["Variable", "Data_Type", "Sample_Value", "Description"] }, "data": [ { "Variable": "counterparty_name_input", "Description": "Client-provided counterparty name", "Business_Rules": "Exact or fuzzy match accepted", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "NordSteel Components" }, { "Variable": "country_input", "Description": "Client-provided country for disambiguation", "Business_Rules": "Two-letter ISO code preferred", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "SE" }, { "Variable": "relationship_type_input", "Description": "Client-provided relationship type", "Business_Rules": "ENUM: Supplier|Customer", "Source_System": "Client Data", "Data_Type": "ENUM", "Sample_Value": "Supplier" }, { "Variable": "client_payment_terms_input", "Description": "Optional client payment terms used for actioning", "Business_Rules": "Free text (e.g., Net 30, Net 45)", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "Net 30" }, { "Variable": "year_reference", "Description": "Year of reference for KPIs", "Business_Rules": "Fiscal year ending YYYY", "Source_System": "Curated APIs", "Data_Type": "INTEGER", "Sample_Value": 2024 }, { "Variable": "company_id_external", "Description": "Verified external company identifier", "Business_Rules": "Stable mapping across systems", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "CO_52011" }, { "Variable": "website_domain", "Description": "Verified company website/domain", "Business_Rules": "Active, resolvable domain", "Source_System": "Web Intelligence", "Data_Type": "VARCHAR", "Sample_Value": "nordsteel.se" }, { "Variable": "counterparty_name", "Description": "Canonical legal name of counterparty", "Business_Rules": "Normalized form", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "NordSteel Components AB" }, { "Variable": "relationship_type", "Description": "Resolved relationship type", "Business_Rules": "ENUM: Supplier|Customer", "Source_System": "Web+AI Reasoning", "Data_Type": "ENUM", "Sample_Value": "Supplier" }, { "Variable": "revenue_latest", "Description": "Latest available revenue (EUR)", "Business_Rules": "Currency normalized to EUR", "Source_System": "Curated APIs", "Data_Type": "DECIMAL", "Sample_Value": 148000000.0 }, { "Variable": "solvency_score", "Description": "Solvency/credit score (0–100)", "Business_Rules": "Higher is better", "Source_System": "Curated APIs", "Data_Type": "INTEGER", "Sample_Value": 84 }, { "Variable": "liquidity_ratio", "Description": "Current assets / current liabilities", "Business_Rules": "Rounded to 2 decimals", "Source_System": "Curated APIs", "Data_Type": "DECIMAL", "Sample_Value": 1.48 }, { "Variable": "debt_to_equity", "Description": "Total debt divided by equity", "Business_Rules": "Rounded to 2 decimals", "Source_System": "Curated APIs", "Data_Type": "DECIMAL", "Sample_Value": 0.62 }, { "Variable": "revenue_trend_yoy", "Description": "Revenue change vs prior year (%)", "Business_Rules": "Positive or negative decimal", "Source_System": "Curated APIs", "Data_Type": "DECIMAL", "Sample_Value": 6.3 }, { "Variable": "late_payment_days", "Description": "Average days beyond terms (DBT)", "Business_Rules": "Non-negative integer", "Source_System": "Curated APIs", "Data_Type": "INTEGER", "Sample_Value": 7 }, { "Variable": "insolvency_filings_12m", "Description": "Count of insolvency-related filings in last 12 months", "Business_Rules": "Integer", "Source_System": "Curated APIs", "Data_Type": "INTEGER", "Sample_Value": 0 }, { "Variable": "negative_news_mentions_12m", "Description": "Negative news items (retrieved) in last 12 months", "Business_Rules": "Integer; soft signal", "Source_System": "Web Intelligence", "Data_Type": "INTEGER", "Sample_Value": 1 }, { "Variable": "stress_score", "Description": "Composite stress score (0–100)", "Business_Rules": "Weighted sum of drivers; explainable, not black-box", "Source_System": "Web+AI Reasoning", "Data_Type": "INTEGER", "Sample_Value": 21 }, { "Variable": "stress_driver_solvency_wt", "Description": "Weight of solvency in stress score", "Business_Rules": "0–1; weights sum to 1", "Source_System": "Web+AI Reasoning", "Data_Type": "DECIMAL", "Sample_Value": 0.25 }, { "Variable": "stress_driver_liquidity_wt", "Description": "Weight of liquidity in stress score", "Business_Rules": "0–1", "Source_System": "Web+AI Reasoning", "Data_Type": "DECIMAL", "Sample_Value": 0.20 }, { "Variable": "stress_driver_debt_wt", "Description": "Weight of leverage in stress score", "Business_Rules": "0–1", "Source_System": "Web+AI Reasoning", "Data_Type": "DECIMAL", "Sample_Value": 0.15 }, { "Variable": "stress_driver_payments_wt", "Description": "Weight of payment behavior in stress score", "Business_Rules": "0–1", "Source_System": "Web+AI Reasoning", "Data_Type": "DECIMAL", "Sample_Value": 0.20 }, { "Variable": "stress_driver_filings_wt", "Description": "Weight of insolvency filings in stress score", "Business_Rules": "0–1", "Source_System": "Web+AI Reasoning", "Data_Type": "DECIMAL", "Sample_Value": 0.10 }, { "Variable": "stress_driver_news_wt", "Description": "Weight of negative news in stress score", "Business_Rules": "0–1", "Source_System": "Web+AI Reasoning", "Data_Type": "DECIMAL", "Sample_Value": 0.10 }, { "Variable": "comment", "Description": "Plain-language risk summary with suggested action", "Business_Rules": "≤300 chars", "Source_System": "Web+AI Reasoning", "Data_Type": "TEXT", "Sample_Value": "Stable supplier: strong solvency and liquidity; mild payment slippage. Keep terms; monitor news." } ] }