Skip to content

Lesson 28 of 34 · Module 9 · Sector lenses

Power lens: tariff and receivables

Dated tariff evidence - watch receivables vs PAT.

Power tips love tariff talk, but a power company's money story is about who pays, how fast, and under what agreement. Your map wants a dated tariff or capacity notice and an honest cash line, because power names are a classic case where pretty PAT and weak cash can sit side by side. Use HUBC as the teaching name.

About 16 min · desk walk + key terms · Shark methodology

Do now: Practice on HUBC Study Mode →

Power tips love tariff talk, but a power company's money story is about who pays, how fast, and under what agreement. Your map wants a dated tariff or capacity notice and an honest cash line, because power names are a classic case where pretty PAT and weak cash can sit side by side. Use HUBC as the teaching name.

After this lesson, you can…

  • ✓Explain power lens: tariff and receivables in plain words
  • ✓Apply the idea to one real PSX company
  • ✓Recognise the most common beginner mistake

Visual mental model

A calm learning loop

  1. 1

    Understand

    Dated tariff evidence - watch receivables vs PAT.

  2. 2

    Check

    What did this lesson train?

  3. 3

    Apply

    Use one real desk or calculator

Move from explanation to evidence, then practice.

Key knowledge

Terms you will use on the desk

Tariff / receivables
Common power-desk homework themes — confirm in Filings.

power sector — study, not tip

This lab trains power sector on a live desk. Write dated evidence, refuse undated tip calendars, and keep scenario weights as business-path opinion — never as % chance the price moves.

In-depth teaching

5 sections

01

How a power company earns

Many independent power producers sell electricity under long-term agreements with a government-linked buyer. Revenue often includes a capacity payment for being available and an energy payment for power delivered, with tariff terms set by regulators and contracts. Fuel costs may be passed through under the agreement, which changes how input cost swings affect margins.

So the first power questions are: what is the contract structure in plain words, which parts of revenue are capacity versus energy, and how are fuel and exchange rate changes treated? Notes and Filings often describe this. If the desk is thin, write unknown rather than guessing the structure.

02

Receivables: the circular-debt trap

A central issue in Pakistan's power sector is the chain of payments: consumers pay distribution companies, which pay the central buyer, which pays the producers, and delays anywhere along the chain can leave producers owed large receivables. When receivables grow, profit may be recognised while cash is delayed, which is exactly the PAT versus OCF scar.

On the desk, compare receivables in Books and notes across periods and look at operating cash relative to profit. Producers with long delays may borrow to cover working capital, which raises interest costs and leverage. Write the receivables trend in one line, and write what you do not know about the timing of settlements.

Pause and predict · free

Getting check ready…

A forward map is…

03

Tariff and capacity notices: dated or unknown

Tariff revisions, capacity payment adjustments, and regulatory decisions can change the economics. Tip messages often claim 'tariff increase coming' without a source. In your map, a tariff or capacity event enters only when a dated official notice or regulator decision exists, and even then you write what it covers and what it does not.

Also watch for dividend and settlement news, which can appear after government payments. A dividend depends on cash actually received, not on accounting profit. If a Filings notice mentions settlement of dues, write the date and amount in the notice, then check Books for the effect on receivables and cash in later periods.

04

Worked mini-example: HUBC on the same SOP

Open HUBC and run the full standard map. Then add power extras: contract structure in a line, receivables trend, PAT versus OCF for the same three periods, debt trend, and the latest dated regulatory or settlement notice. Suppose a teaching base path reads: 'payments continue broadly on schedule, receivables stable, profit converts to cash.'

A teaching bear path: 'payment delays lengthen, receivables grow, the company borrows to cover working capital, and cash conversion weakens.' Falsifier examples: 'operating cash falls below profit for two periods while receivables rise' or 'a Filings notice of new short-term borrowing for working capital'. The line tying the story together is cash, not tariff headlines.

05

Tip-culture trap, and the fork

The power tip trap is the tariff headline and the profit screenshot with no receivables line. 'Record profit, dividend soon' sounds strong but says nothing about when cash arrives. Another trap is assuming a government announcement means immediate payment; announcements and actual transfers are separate events.

Wait means you cannot describe the contract structure or find receivables and cash lines. Need evidence means the structure is clear but cash conversion data or a dated notice is missing. Broker talk requires a complete map where cash conversion has been checked and written. The sector lens adds cash questions; it never replaces the SOP.

Check your understanding · free

Getting check ready…

Scenario weights mean…

Common slip

Skipping the lab and calling the lesson done.

Required lab

Do this on the desk now

  • Open HUBC. Write as_of.

    Done when: as_of written

    Open →
  • Open HUBC Books or note empty.

    Done when: Books checked

    Open →

Lab · Forward map

Build your map: drivers, catalysts, BBB, falsifiers, exit, decision.

Practice on HUBC Study Mode →

Loading forward map lab…

Or practice on live desk with Study ModeOpen HUBC Study Mode

Failed map examples — learn from scars

Real mistakes that fail the validator. See the error, understand the fix.

These are real beginner mistakes that the MapValidator catches. Study them so you don't repeat them.

PROPHECY

Prophecy Language in Rationale

HBL · 5 error(s)

▼

❌ Failed map — 5 validation errors

drivers: [ "Net interest margin", "Asset quality" ]
catalysts: [ { "event": "Q3 results", "whenOrUnknown": "2024-10-24" } ]
scenarios: { "bull": "Stock will go up 20% after clean results", "base": "Price will stay range-bound", "bear": "Will drop 15% if provisions spike" }
scenarioWeights: { "bull": 60, "base": 30, "bear": 10 }
weightsRationale: HBL will go up because provisions are normalizing and NIM is strong. Target 200.
falsifiers: [ "Market crashes", "Bad news" ]
liquidityExit: HBL is liquid
decision: broker_talk
  • Rationale contains prophecy: 'will go up', 'target 200'
  • Scenarios describe price targets, not business paths
  • Weights reflect price odds (60/30/10), not business path opinions
  • Falsifiers are vague ('market crashes')
  • Decision 'broker_talk' without completing evidence steps
💡 Teaching note

Prophecy veto is automatic. Every field must describe business paths, not price predictions. Weights are your opinion on business outcomes — not % chance price moves.

VAGUE-FALSIFIER

Vague Falsifiers

FFC · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Gas cost", "Volumes" ]
catalysts: [ { "event": "Gas price notification", "whenOrUnknown": "unknown" } ]
scenarios: { "bull": "Gas manageable, volumes hold", "base": "Normal agri cycle", "bear": "Things go wrong" }
scenarioWeights: { "bull": 30, "base": 50, "bear": 20 }
weightsRationale: Base case until something changes
falsifiers: [ "Market crashes", "Economy gets bad", "Bad news" ]
liquidityExit: FFC is liquid
decision: need_evidence
  • Falsifiers are generic ('market crashes', 'economy gets bad') — not checkable
  • Bear scenario 'things go wrong' is not a business path
  • Weights rationale 'until something changes' is not a working case explanation
  • Catalyst 'unknown' without falsifier for 'no gas notification in 90 days'
💡 Teaching note

Falsifiers must be specific, dated, and checkable: filing events, book lines, governance signals. 'Market crashes' is lazy — name the filing or book line that kills your base case.

WEIGHT-ERROR

Weights Don't Sum to 100

LUCK · 3 error(s)

▼

❌ Failed map — 3 validation errors

drivers: [ "Cement demand", "Coal cost" ]
catalysts: [ { "event": "APCMA dispatch data", "whenOrUnknown": "monthly" } ]
scenarios: { "bull": "Demand up, coal stable", "base": "Normal cycle", "bear": "Cost shock" }
scenarioWeights: { "bull": 40, "base": 40, "bear": 30 }
weightsRationale: Bullish on demand
falsifiers: [ "Coal spike", "Demand drop" ]
liquidityExit: LUCK liquid
decision: broker_talk
  • Weights sum to 110 (40+40+30), not 100
  • Decision 'broker_talk' with invalid weights
  • Rationale 'bullish on demand' doesn't explain base/bear weights
💡 Teaching note

Weights must sum to exactly 100. The validator catches this automatically. Your rationale must explain why base is the working case, not just 'bullish on X'.

MISSING-DRIVER

Missing Key Driver (Circular Debt)

OGDC · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Oil price", "Production volumes" ]
catalysts: [ { "event": "Monthly production data", "whenOrUnknown": "monthly" } ]
scenarios: { "bull": "Oil up, production up", "base": "Stable", "bear": "Oil down" }
scenarioWeights: { "bull": 30, "base": 50, "bear": 20 }
weightsRationale: Oil price drives everything
falsifiers: [ "Oil crash", "Production drop" ]
liquidityExit: OGDC liquid
decision: need_evidence
  • Missing critical driver: circular debt receivables / cash collection
  • OGDC is an E&P — cash collection from refineries is the real driver, not just oil price
  • Falsifiers don't mention receivables aging or government payment delays
  • Liquidity exit ignores that OGDC shares can be thin in panic
💡 Teaching note

Every sector has hidden drivers. For E&P: cash collection = production × price × collection rate. Missing receivables driver = incomplete map. Always ask: 'What kills cash flow even if price is good?'

NO-EXIT

No Exit Plan for Thin Name

THIN · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Unknown — need filings" ]
catalysts: [ { "event": "None known", "whenOrUnknown": "unknown" } ]
scenarios: { "bull": "Could be anything", "base": "Wait and see", "bear": "Risks everywhere" }
scenarioWeights: { "bull": 10, "base": 20, "bear": 70 }
weightsRationale: Too many unknowns
falsifiers: [ "Any bad news" ]
liquidityExit: Will figure out later
decision: broker_talk
  • Liquidity exit 'will figure out later' is not a plan
  • Decision 'broker_talk' on thin data with no exit = dangerous
  • Drivers 'unknown' but decision not 'wait'
  • No lot size, volume, or free float analysis
💡 Teaching note

Thin data → Wait is the only valid decision. If you don't know lot size, volume, and free float, you cannot size a position. 'Broker talk' on unknown liquidity = gambling.

THIN-DATA-INVENTED

Inventing Numbers on Thin Coverage

THIN · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Revenue growth 15%", "Margins expanding" ]
catalysts: [ { "event": "Next quarter results", "whenOrUnknown": "2024-12-15" } ]
scenarios: { "bull": "Growth continues", "base": "Stable", "bear": "Slowdown" }
scenarioWeights: { "bull": 40, "base": 40, "bear": 20 }
weightsRationale: Management guided growth
falsifiers: [ "Results miss" ]
liquidityExit: Assume liquid
decision: need_evidence
  • Drivers invented ('Revenue growth 15%') — Books are empty, no data to support
  • Catalyst date invented — no filing confirms Dec 15
  • Weights reflect optimism, not evidence
  • Liquidity exit 'assume liquid' on unknown name = dangerous
💡 Teaching note

Thin coverage → Wait. Honesty beats invented drivers. If Books are empty, write 'unknown — need filings/books'. Never invent numbers to make a map look complete.

What you can say now

Evaluation language — not a price call.

  • →I can brief this name: drivers, catalysts, business paths, falsifiers, exit, decision.
  • →I can evaluate a prediction claim: where is the evidence, and what would prove it wrong?
  • →I still refuse price targets and up/down odds — judgment, not prophecy.

Worth keeping

  • Veterans keep scars next to every step.
  • A complete map still is not a price call.
  • Capacity payments reward availability, so a plant can earn even when it is not running at full output.
  • A dividend from a power company depends on cash received, which can lag accounting profit.

Write Wait when evidence is thin — that is skill, not weakness.

Try it on a live desk

Practice · support fades as you go

Practice with support

Write Wait when evidence is thin — that is skill, not weakness.

Need a hint?

A scar-backed habit on the live desk — not a tip.

Done when: You can explain what you checked and what remains uncertain.

Now without hints

Try it independently

What did this lesson train?

A strong answer: A scar-backed habit on the live desk — not a tip.

Lesson FAQ

What did this lesson train?

A scar-backed habit on the live desk — not a tip.

Does a strong map mean buy?

No. It means homework. Decision may still be Wait.

Are weights price odds?

No. They are opinion on business paths only.

Why do receivables matter so much for power companies?

Because profit may be recognised while payment is delayed. Growing receivables can tie up cash and raise borrowing, even when profit looks healthy.

Can I trust a tariff rumour?

Only when a dated official notice or regulator decision exists. Until then, write it as unverified and keep the decision at Wait or Need evidence.

Mark this lesson complete

What did this lesson train?

Show calm answer

A scar-backed habit on the live desk — not a tip.

A scar-backed habit on the live desk — not a tip.

Tick every required lab step above before you mark complete.

Sign in before completing lessons if you want them counted toward the certificate.

Optional: graded test (sign-in)

Member lesson tools

Full lesson test & member tools

Checking sign-in…

Ask coach

Locked

Ask: review my map gaps

Share drivers and falsifiers — coach checks process.

Sign in to unlock →

Stay on the course path

Follow the Shark Methodology path. How-tos and metrics are optional reference.

  • Shark Methodology course

    Main beginner path: evidence, forward maps, and evaluating claims — not competing starts.

  • Learn PSX hub

    Start Lesson 1, then optional guides and tools when you need them.

  • PSX today

    Pakistan stock market today in plain words - breadth, gainers, losers.

  • PSX companies list

    Browse all Pakistan Stock Exchange listed companies by name or sector.

  • KSE 100 index today

    Educational constituent board - not the official index level on psx.com.pk.

  • PSX gainers today

    Biggest % rises among ordinary listed shares - homework, not a buy list.