Energy Credit Risk Management Webinar | Paragon CRM

How much credit is available for a counterparty, and what supports that number? Answering that question can mean checking an agreement, confirming a limit allocation, reviewing exposure, and reconciling collateral. When those records are scattered, even a routine review becomes harder to complete and explain.

This practical guide looks at five connected credit workflows and the questions worth asking about each. You can also watch our energy credit risk management webinar with Damon Walker, Energy Product Analyst for Paragon CRM.

Recorded October 22, 2026 · 45 minutes · Product overview and Q&A

Go directly to a video topic: Counterparties (09:10)  |  Agreements and limits (17:10)  |  Collateral and credit support (21:57)  |  Margin calls (27:30)  |  Reporting (35:15)

Download the Paragon CRM brochure

Start with a counterparty record your team can rely on

Before an analyst can assess a credit position, the team needs to know which legal entity it is reviewing and whether the supporting information is current. A rating on file may have changed. A review may be due. An agreement may belong to a related entity rather than the counterparty on the transaction.

A useful counterparty record brings together contacts, credit ratings and effective dates, supporting documents, related entities, and review dates. Comments should sit with the relevant record so another analyst can understand the background without searching an email chain.

Paragon CRM provides a shared place to maintain that information. External ratings can also be brought into the system when the relevant subscriptions and integrations are in place. The operational benefit is easier access to the information behind the credit decision, including the items that still need follow-up.

Make agreement terms and limit allocations visible

A credit limit needs context. If a parent-level line is allocated across subsidiaries, the reviewer needs to see the total line and the allocation to the entity being assessed. Looking only at the parent figure does not explain how much has been assigned to a particular subsidiary.

Agreement terms matter as well. Credit support annexes, margin thresholds, minimum transfer amounts, and rounding rules affect how a credit relationship is managed. Those terms should be easy to locate alongside the agreement they belong to.

In Paragon CRM, teams can maintain agreement details and assign or allocate credit limits across related entities. A practical review is to trace one active counterparty from its agreement to its applicable limit and confirm that the relationship is clear to someone outside the original approval process.

Make sure credit support is counted once

Recording a letter of credit is only part of the job. The calculation also needs to reflect how that support applies to the relationship. Eligible credit support might reduce exposure or affect limit availability, according to the configured approach.

Consider this simplified example, where eligible collateral reduces exposure:

Illustrative credit position
Item Illustrative amount
Credit limit $20 million
Gross exposure $12 million
Eligible collateral applied against exposure $3 million
Adjusted exposure $9 million
Available credit $11 million
Simplified example. Eligibility and treatment depend on credit policy and agreement terms.

If the same $3 million were also added to the credit limit, reported available credit would rise to $14 million. The same support would have been counted twice.

The useful review questions are which support is eligible, which entity or agreement it covers, and where it enters the calculation. Eligibility and treatment depend on your credit policy and agreement terms.

Paragon CRM allows teams to configure how credit support affects exposure or limit availability. The webinar walks through that treatment and the importance of applying it consistently.

Check the inputs before preparing a margin call

A margin notice depends on several connected pieces of information. A reusable template helps, but the request still needs to reflect the relevant agreement and credit position. Before issuing a notice, review:

  • The applicable agreement, margin threshold, minimum transfer amount, and rounding terms.
  • The exposure and credit support used in the calculation, including any support already applied.
  • The amount requested and the counterparty contact information.
  • The completed notice before it is sent.

Paragon CRM supports configurable notice templates that pull in relevant exposure, collateral, and counterparty information. The demonstration follows a collateral request through review and into Outlook for sending. A consistent template gives the team a common starting point while keeping the review step visible.

Build reports around the exceptions that need action

A report is more useful when the reader can quickly identify what needs attention. A portfolio summary may show total exposure, while an analyst needs the counterparties that have exceeded their limits and the detail behind each position.

Saved layouts and filters let teams work from a consistent view. Formula columns and conditional formatting can highlight exceptions, and drill-down views help reviewers investigate the underlying exposure. Paragon CRM also supports subscriptions to alerts, including credit limit breaches.

It helps to decide who owns each exception and what follow-up is expected. A notification tells the team that something changed; a clear process determines who investigates it. Upcoming counterparty reviews deserve the same attention so that overdue information does not disappear into a separate spreadsheet.

Five questions to ask about your current credit workflow

Use these questions to identify where information or follow-up is difficult to manage:

  1. Can an analyst find the current agreement, rating, and next review date in one place?
  2. Can the team trace the credit limit and allocation that apply to a specific legal entity?
  3. Can a reviewer explain exactly how collateral and other credit support affect available credit?
  4. Can the team prepare and check a margin notice without re-entering the same information in several files?
  5. Can the person responsible identify limit breaches and upcoming reviews without manually assembling a separate list?

Discuss your credit workflow with our team

If one of these workflows is creating extra work for your team, tell us where the process gets difficult. Use the form below to ask a question or discuss how Paragon CRM could support your credit operations.

Explore Paragon CRM

About the speaker

Damon Walker, Energy Product Analyst for Paragon Credit Risk Management System Damon Walker is the Energy Product Analyst for Paragon CRM at MCG Energy Solutions. He brings more than 20 years of experience across the technology and practitioner sides of energy credit risk, including roles as a Credit Risk Manager in the energy and banking industries.