PNGRB Databank Regulations 2026: Reporting Rules

For a company working in the petroleum or natural gas sector, regulatory reporting can involve several teams at the same time. Pipeline data may come from operations, finance may handle cost and revenue figures, safety teams may keep incident records and consumer complaints may be maintained by another department.

The Petroleum and Natural Gas Regulatory Board (PNGRB) has now brought a large part of this information into one formal reporting framework through the Petroleum and Natural Gas Regulatory Board (Databank and Information System) Regulations, 2026.

The notification is dated 2 September 2026. The Regulations state that they come into force from the date of their publication in the Official Gazette.

The real work for businesses lies in Schedules A to H. These schedules deal separately with City Gas Distribution (CGD), natural gas pipelines, petroleum product pipelines, safety information, LNG terminals, other charges, POL-related infrastructure and NHIMS-based data.

PNGRB Databank Regulations 2026 at a Glance

The 2026 Regulations set out how information relating to the petroleum and natural gas sector is to be collected, reported, checked and maintained. The table below covers the main details businesses should know, including the reporting framework, covered sectors, timelines and key compliance points.

The Regulations have been issued under powers drawn from Section 61(2)(x), read with Section 11(h) and Section 51 of the PNGRB Act, 2006.

What Are the PNGRB Databank and Information System Regulations, 2026?

In simple terms, the Regulations set out how PNGRB will collect, organise, review and maintain regulatory information from entities covered by the framework. They also explain how the Board may deal with information that needs to be verified, corrected or updated.

The term “data” has been defined broadly. It covers both structured and unstructured information, whether submitted electronically or in physical form. PNGRB can use this information for processing, analysis, verification, storage and other regulatory purposes allowed under the applicable law.

This is why businesses should look at the Regulations as more than just another reporting requirement. The information submitted may also form part of PNGRB’s wider regulatory and monitoring process.

It also creates a base for:

• regulatory analysis,
• sector-level statistics,
• consumer information,
• price and service monitoring,
• infrastructure tracking,
• operational monitoring, and
• safety oversight.

PNGRB can also prepare statistical reports from the information furnished by entities and host those reports on its website.

Why Has PNGRB Introduced This Data Reporting Framework?

PNGRB has itself listed the reasons for collecting this information.

The Regulations refer to consumer awareness and protection, fair trade, competition, open access, transportation tariffs, technical and safety standards, adequate supply and uninterrupted availability of petroleum, petroleum products and natural gas.

What does this mean in practical terms?

More consistent information can help the regulator see what is actually happening on the ground.

For example, PNGRB can look at:

• whether CGD infrastructure is progressing,
• how much natural gas is being supplied to different sectors,
• how pipelines are being utilised,
• what consumers are paying for CNG or DPNG,
• how many complaints are being received,
• where operational losses are occurring, and
• what type of safety incidents are being reported.

For the business, however, this also means that a regulatory return may depend on information sitting with several different teams.

Who Is Covered Under the PNGRB Databank and Information System Regulations?

Regulation 3 uses wide language. It applies to entities engaged or intending to be engaged in activities connected with:

• refining,
• processing,
• storage,
• transportation,
• distribution,
• marketing,
• import,
• export,
• petroleum,
• petroleum products,
• natural gas,
• pipelines,
• city or local natural gas distribution networks, and
• LNG terminals.

That does not mean every covered entity must fill every form. The relevant reporting requirement depends on the business activity.

Applicability of Schedules A to H

The Schedule mapping comes directly from Regulation 5.

Important Definitions Businesses Should Understand

The Regulations contain a number of definitions, but a few are especially useful from a compliance point of view.

These definitions are set out in Regulation 2.

Schedule-Wise PNGRB Data Reporting Requirements

This is where the notification becomes more operational. The eight schedules do not ask for the same data, and they do not follow the same filing cycle.

Schedule A- City Gas Distribution Reporting

Schedule A is particularly detailed because a CGD business touches consumers, pipelines, CNG stations, gas procurement, pricing and infrastructure at the same time.

CGD-1: PNG Connections and Sales: The monthly CGD-1 report captures district-wise information relating to:

• domestic PNG connections,
• commercial PNG connections,
• industrial PNG connections,
• sales volume,
• cumulative connections,
• domestic connection targets,
• shortfall, and
• pending domestic customer registrations.

The pending connection data is also divided into ageing buckets such as 0-30 days, 31-60 days, 61-90 days and more than 90 days.

For specified non-quarter-end months, the report is to be submitted within 20 days of the following month. For March, June, September and December, the period is 30 days from the following month. The nominated nodal officer is made responsible for correct and timely submission.

CGD-2: CNG Stations and Sales: CGD-2 goes deeper into the CNG network. It captures information such as:

• number of stations,
• compression capacity,
• station code,
• station name,
• commissioning date,
• address,
• latitude and longitude,
• type/model of station,
• operator/OMC information,
• compressors and boosters,
• dispensing units, and
• natural gas sales.

It follows the same 20-day/30-day monthly structure described in the format.

CGD-3: Pipeline Infrastructure and City Gate Stations: This report tracks physical network development. Entities have to report information on:

• steel pipeline, 
• MDPE pipeline, 
• inch-kilometres, 
• current-month additions, 
• cumulative infrastructure, 
• target and shortfall, 
• City Gate Station location, 
• tap-off point, 
• hook-up agreement, 
• commissioning, and 
• CGS capacity. 

The format specifically indicates that both steel and MDPE pipeline information should be collected.

CGD-4: Segment-Wise Cost Sheet: This is one of the more demanding Schedule A returns because it pulls information from finance as well as operations. It asks for segment-wise financial information for areas such as DPNG, CNG, commercial and industrial PNG, LNG and other business segments.

The cost sheet contains information on:

• sales quantity, 
• revenue, 
• cost of gas, 
• APM/NAPM/HPHT/CBG and other sources, 
• compression cost, 
• dispensing charges, 
• power and fuel, 
• maintenance, 
• manpower, 
• insurance, 
• consultancy and legal expenses, 
• depreciation, 
• interest, 
• selling and distribution expenses, and 
• profit/loss. 

Entities operating several GAs are also asked to provide GA-wise cost sheets and reconcile the figures with entity-level profit and loss accounts.

The quarterly submission is to be signed by key managerial personnel such as the CFO, CS or CEO. PNGRB may seek CA/CMA certification where required, while annual submissions are to be certified by the statutory auditor or practising CA/CMA.

CGD-5 and CGD-6: CGD-5 is a monthly report for APM allocation, RLNG, CBG and HPHT.

CGD-6 tracks GA-wise CAPEX and OPEX, including planned and incurred expenditure as well as cumulative expenditure.

CGD-7: Capacity Booking: CGD-7 deals with capacity available and booked within a city or local natural gas distribution network. The form asks for:

• entry-point capacity,
• exit-point capacity,
• technical parameters,
• capacity used for own requirements,
• common/contract carrier capacity already booked, and
• capacity available to shippers.

CGD-8: Consumer Complaints: CGD-8 moves away from infrastructure and focuses on consumers. It covers:

• consumer base, 
• additions,
• disconnections,
• complaints received,
• complaints resolved,
• pending complaints,
• complaints beyond prescribed timelines,
• complaint categories,
• compensation,
• service-quality performance,
• awareness programmes, and
• escalations.

Quarterly data is to be submitted within 30 days after the quarter, and the format requires certification by the Principal Nodal Officer. 

CGD-9: Annual Quality of Service: CGD-9 takes a wider annual view. It asks about:

• consumer growth,
• connection performance,
• average connection time,
• planned and unplanned supply interruptions,
• quality and pressure non-compliance,
• meter complaints,
• defective meters,
• billing accuracy,
• complaint handling,
• compensation,
• consumer satisfaction, and
• Consumer-awareness programmes.

The report is to be submitted by 30 April for the previous financial year.

CGD-10: DPNG and CNG Price Break-Up: This format makes monthly consumer-price reporting much more transparent. For DPNG, businesses report components such as:

• basic APM cost,
• transportation tariff,
• GST on transportation,
• State VAT,
• supply and distribution cost,
• entity margin, and
• final retail selling price.

For CNG, the breakup can include:

• basic gas cost,
• regasification charges,
• marketing margin,
• transportation tariff,
• GST,
• compression charges,
• other charges,
• entity margin,
• excise duty,
• VAT, and
• retail price per kilogram.

Special Point: CBG Data: The Gazette itself says that although CBG data formats have been included, bringing CBG under PNGRB regulation is subject to inclusion of CBG within PNGRB's statutory purview through a proposed amendment to the Act. Until that amendment, the document states that CBG data may be collected on a voluntary basis.

The published Schedule A nevertheless includes:

• CGD-11 for operative CBG plants,
• CGD-14 for pipeline infrastructure connecting CBG plants, and
• CGD-15 for CBG sales and obligations.

This distinction should not be missed when interpreting the notification.

Schedule B- Natural Gas Pipeline Reporting

Schedule B is aimed at natural gas pipelines and combines physical, operational, financial and capacity-related information.

• NGPL-1A: Physical Progress: The quarterly report captures:
  • authorised length,
  • welded length,
  • lowered length,
  • commissioned length,
  • section-wise progress,
  • ROU/ROW status,
  • spur lines,
  • compressors, and
  • terminals.

The report is due within 30 days of the close of the quarter.

• NGPL-1B: Financial Parameters: This report covers:
  • fixed assets, 
  • CWIP, 
  • operating expenses, 
  • financial expenses, 
  • depreciation, 
  • total expenses, 
  • revenue, 
  • tariff, 
  • profit and loss, 
  • term loans, and 
  • working-capital loans. 

It is due within 60 days from the close of the quarter.

A scanned copy signed and stamped by a GM-level or higher authorised person is to be uploaded within 10 days after online submission. The fourth-quarter/year-end report is to be CA-certified. 

• NGPL-2: Monthly Gas Supply: NGPL-2 tracks sector-wise natural gas supply. The categories include areas such as:
  • power,
  • fertilisers,
  • city gas,
  • petrochemicals and refineries,
  • sponge iron and steel, and
  • internal/other consumption.

The report must be submitted by the 20th of the following month.

• NGPL Capacity and Commercial Information: The later NGPL formats deal with pipeline capacity, entry/exit points, common-carrier availability, invoiced amounts, outstanding amounts, escrow-related information and annual capacity determination.

NGPL-6, for example, asks for the software package and flow equation used for capacity determination, entry and exit details, gas composition and maximum achievable capacity. It is to be submitted by 30 April for the previous financial year.

One point deserves caution: parts of the Gazette around NGPL-4 use wording relating to quarterly information while also carrying an annual 30 April submission statement. Businesses should therefore rely on the exact applicable format and any PNGRB clarification rather than generalising the frequency from the heading alone.

Schedule C- Petroleum and Petroleum Product Pipelines

Schedule C follows a similar approach for petroleum and petroleum-product pipelines.

• Physical Progress Reporting: The quarterly physical report looks at:
  • authorised pipeline length,
  • welding,
  • lowering,
  • commissioning,
  • ROU/ROW,
  • spur lines,
  • pump stations,
  • receiving terminals,
  • dispatch terminals, and
  • project completion.

The stated filing period is 30 days from the close of the quarter. 

• Financial Reporting: The financial report collects fixed assets, CWIP, revenue, expenses, profit/loss and loan details.

It is due within 60 days after the quarter. A signed and stamped copy is to be uploaded within 10 days after online submission, and the year-end filing requires CA certification.

• PPPL-2: Pipeline Throughput: PPPL-2 asks for monthly throughput and cumulative capacity utilisation.

The monthly filing must be completed by the 20th of the following month. A signed and stamped scanned copy is to be uploaded within seven days after online submission.

• PPPL-3: Capacity Determination: PPPL-3 deals with the technical basis for determining pipeline capacity, including software, flow equations, pipeline sections, quality specifications and maximum achievable capacity.

It is an annual submission due by 30 April for the previous financial year.

Schedule D- Technical, Safety and Operational Reporting

Schedule D deserves special attention because some deadlines run in hours, not days.

Major, Minor and Near-Miss Incidents: The Technical-1 incident format records:

• date and time,
• incident category,
• fatalities,
• injuries,
• lost man-hours,
• financial loss,
• plant shutdown,
• fire,
• explosion,
• blowout,
• leakage,
• investigation status, and
• probable cause.

For a major incident:

• first information must be given immediately, but not later than 4 hours after occurrence,
• the prescribed major-incident report must be submitted within 48 hours,
• major, minor and near-miss incidents must also appear in quarterly reporting, and
• investigations are required for all three categories.

The form treats an incident as major where specified events occur, including explosion/blowout, fatality, fire lasting more than 15 minutes, loss above Rs 20 lakh, cumulative man-hours lost above 500 or plant shutdown/outage.

Gas Operations and Losses: Technical-2 looks at CGD gas operations. It records sources such as:

• APM,
• non-APM,
• RLNG,
• CBG,
• purchases from other CGD entities, and
• stock received from other GAs.

On the output side, it tracks CNG, PNG, internal consumption and stock transfers.

It then moves into operational losses such as:

• CNG package loss,
• discharge-to-sales difference,
• cascade venting,
• line damage,
• purging,
• commissioning losses, and
• LCV transportation loss.

Technical-3 performs a similar monitoring role for natural gas pipelines and captures receipts, deliveries, self-use gas, accounted gas, unaccounted gas and line pack.

Schedule E- LNG Terminal Reporting

Schedule E contains LNG-1 and cross-refers to the PNGRB LNG Terminal Registration Regulations, 2025.

LNG terminal operators need to report information such as:

• PNGRB registration,
• total regasification capacity,
• long-term committed capacity,
• short-term committed capacity,
• number of cargoes,
• own-use cargo,
• third-party cargo,
• volume handled,
• capacity utilisation,
• regasification charges,
• truck-loading charges,
• handling gas losses, and
• other charges.

The report is biannual, with information referenced to 1 April and 1 October.

Schedule F- Other Charges

Schedule F should not be read as if the 2026 Databank Regulations themselves have created a fresh fee.

The Schedule cross-refers to the PNGRB (Levy of Fee and Other Charges) Regulations, 2007 and asks entities to report charges payable and paid.

It covers information for:

CGD Networks

• GA name,
• population,
• financial year from authorisation, and
• Charges payable/paid.

Pipelines

• pipeline name,
• previous financial-year revenue,
• charges payable/paid, and
• Payment details.

The return is due by 30 April for the previous financial year.

Schedule G- Refining, Transportation and Storage of POL

Schedule G deals with physical infrastructure and movement of petroleum products and LPG.

SP-1: Petroleum Products: SP-1 records:

• depot/terminal,
• storage capacity,
• product coverage,
• refinery/source,
• mode of transportation,
• transportation cost,
• pipeline connectivity, and
• area covered.

Data may be submitted within 15 days after the completion of each quarter.

SP-2: LPG: SP-2 looks at LPG bottling plants, including:

• bottling capacity,
• storage,
• source,
• pipeline/rail/road/coastal connectivity,
• transportation cost, and
• areas served.

This also carries a 15-day post-quarter reporting period.

SP-3 to SP-6: These forms cover subjects such as:

• transportation cost and quantities,
• tank trucks,
• rail wagons, and
• Fractionators with connectivity details.

The relevant formats carry a 30 April annual deadline for the previous financial year.

Schedule H- NHIMS and Digital Data Reporting

Schedule H is quite different from a conventional quarterly compliance return.

It creates data schemas for the National Hydrocarbon Infrastructure Management System (NHIMS).

Master and Infrastructure Data: NHIMS-1 to NHIMS-6 include fields relating to:

• pipeline ID,
• pipeline type,
• authorised and operating length,
• capacity,
• design pressure,
• design temperature,
• compressor stations,
• pumping stations,
• source/entry points,
• storage depots,
• terminals,
• LPG bottling plants,
• clients,
• exit points, and
• geographical location.

Transactional API Data: NHIMS-7 is the transactional NGPL entry schema through API. It includes:

• pipeline ID,
• D+1 date,
• time,
• source,
• capacity,
• actual volume,
• operating pressure,
• temperature, and
• gas-quality parameters.

NHIMS-8 covers transactional NGPL exit information, including D+1 date, time, exit ID, client ID and volume out.

NHIMS-9 to NHIMS-11 cover PPPL movement through storage, entry and exit points. These are also API-oriented transactional datasets with D+1 fields.

The Gazette even gives an example under NHIMS-11 where data dated 15 August is submitted on 16 August at 06:00 hours.

For companies, that puts IT architecture and master-data quality directly into the compliance discussion.

PNGRB Reporting Deadlines: One Calendar Will Not Fit Every Form

One of the easiest mistakes is to assume that all PNGRB filings follow the same date. They do not.

This is why any business looking for PNGRB compliance services should start with a format-wise compliance calendar, not a generic monthly reminder.

Who Is Responsible for PNGRB Reporting?

Different formats place responsibility on different people.

The Gazette therefore does not support a blanket statement that every return needs CA certification. Certification depends on the particular format. 

Can PNGRB Ask for Information Beyond Schedules A to H?

Yes. Regulation 5 allows the Board to ask for information that is not covered in the schedules if it is needed to meet the objectives of the Regulations.

The public notice may specify:

• the information required,
• the mode of submission,
• the manner in which it must be submitted, and
• the deadline for submission.

For this reason, businesses should continue to monitor PNGRB public notices even after completing their Schedule A to H reporting matrix.

What Happens Where the Same Data Is Required Under Another PNGRB Regulation?

There may be some scope to avoid duplicate reporting, but this should not be assumed automatically.

If information submitted under the Databank Regulations is also required under another applicable PNGRB regulation, the Board may consider the earlier submission for that requirement where the subject matter is the same.

The use of “may” is important here.

A company should not stop making a separate filing simply because similar information has already been submitted under the Databank Regulations. The position should be clear before relying on an earlier submission.

How Is Confidential Business Information Treated?

An entity can identify information as confidential when submitting it.

PNGRB is required to maintain the confidentiality of such information, subject to the PNGRB Act, applicable regulations and other laws. However, confidentiality is not absolute.

There may be situations where disclosure is considered necessary in the public interest. The Regulations also provide for anonymisation and, where applicable, an opportunity for the entity to be heard before the Board takes a decision on the confidentiality request.

Information marked as confidential may still be disclosed where:

• it is already available in the public domain,
• the entity has given prior written consent,
• disclosure is required by law, or
• a court, tribunal or other competent authority directs its disclosure.

In short, marking information as “confidential” does not by itself mean that it can never be disclosed.

PNGRB Can Verify Submitted Data

Regulation 7 gives PNGRB a clear verification power. If the Board wants to check the completeness, correctness or consistency of a filing, it can seek:

• additional information,
• records,
• explanations, and
• supporting documents.

The entity will have to provide the material within the period specified in the notice. PNGRB may also authorise an officer or technically competent person or agency for verification.

Such a person must:

• maintain confidentiality,
• disclose conflicts of interest, and use the information only for the authorised purpose.

What Happens If Data Is Late, Incomplete or False?

Regulation 8 makes one thing clear: filing something is not enough.

The information has to be complete, accurate and authentic, and entities are expected to exercise due diligence for timely compliance.

PNGRB can take action for:

• Late Submission: Where the entity fails to submit information or a return within the specified time.
• Incomplete Information: Where required information is missing.
• False, Fabricated or Tampered Information: This is treated more seriously under the enforcement provision.

Is There an Opportunity to Correct a Default?

For late filing and incomplete information, the Regulation provides a rectification route.

PNGRB can issue a notice and give the entity a period to correct the default. If the remedial action is taken to the Board's satisfaction within that period, the Regulation states that no punitive action will be taken for those specified defaults.

That protection should not be stretched to mean every violation automatically gets a cure period.

False, fabricated or tampered information is dealt with differently.

What Are the Penalties Under the PNGRB Databank Regulations?

A maximum penalty should not be confused with an automatic fine. Where the conditions for civil penalty proceedings are met, PNGRB must issue notice and give the entity an opportunity to be heard.

After examining the default and the response, the Board may:

• issue an advisory, or
• pass a civil penalty order.

The Regulation states that the penalty shall not exceed Rs 1 crore for each contravention.

For a continuing failure, an additional penalty may extend to Rs 10 lakh for every day.

So it would be inaccurate to say that every late PNGRB filing automatically attracts Rs 1 crore.

Public Display of Regulatory Information

Not every piece of information collected under this framework stays inside a PNGRB filing system.

The Board may require entities to display or publish specified data or extracts for consumer benefit and general awareness. The information may have to be made available:

• on the entity's official website,
• at its offices, and
• at business premises.

The Regulation also states that such information is to be provided in English, Hindi and the vernacular language, at the entity's cost.

How Will These Regulations Affect Different Teams?

The Regulations affect more than the team responsible for filing. The information required by PNGRB can come from different functions across the business, so each team may have a role in preparing, checking or approving the data before it is submitted.

This is one reason oil and gas compliance services increasingly need both regulatory and operational understanding. The filing itself may sit with compliance, but the underlying numbers often come from five or six separate systems.

Practical Internal Controls Businesses Should Put in Place

The following are good internal controls. They should not be confused with separate statutory obligations unless expressly required by a specific form.

Reporting Calendar: Maintain one master tracker containing:

• Schedule,
• format,
• reporting period,
• deadline,
• responsible team,
• certifying person, and
• submission status.

Data Owner Matrix: Every important field should have an identified internal owner. For example:

• consumer numbers- customer operations, 
• pipeline length- projects/engineering, 
• gas sales- commercial, 
• CAPEX/OPEX- finance, 
• incident information- HSE, 
• API data- IT/operations. 

Maker-Checker Review: Important returns should be checked by someone other than the person who prepared them.

Reconciliation: Financial and operational information appearing in several filings should be checked for consistency.

Submission Evidence: Retain:

• portal acknowledgements,
• signed copies,
• email records,
• certificates,
• working files, and
• supporting documents.

Incident Escalation: A four-hour reporting window leaves little room for internal confusion. Major incidents should have a pre-defined escalation chain.

PNGRB Compliance Checklist

A simple checklist can help businesses track the key requirements under the Regulations and identify gaps before submitting information to PNGRB.

What Could Make Compliance Difficult?

The Regulations do not create the same level of work for every entity. A smaller operation with one reporting stream may face a different burden from a large CGD or pipeline entity operating multiple assets.

The main practical challenges are likely to be:

• Multiple Filing Frequencies

Monthly, quarterly, annual, biannual, D+1 and event-based reporting can all sit in the same compliance environment.

• Cross-Department Data

The person filing the return may not own the underlying data.

• Financial Reconciliation

Quarterly figures, annual figures and audited accounts may need to agree.

• API and IT Readiness

Schedule H can require much tighter coordination between regulatory teams and IT systems.

• Certification

Some reports require senior-management or professional certification.

• Very Short Incident Timelines

A four-hour first-information requirement means the internal process must work before an incident happens, not after.

Is the New PNGRB Databank System Helpful or an Added Burden?

There are two sides to it.

For businesses with clean systems and clearly assigned data ownership, much of this may be manageable.

For businesses relying on manual spreadsheets, scattered departmental records and last-minute filing, the initial adjustment may be considerably harder.

Compliance Risks Businesses Should Avoid

Some risks are easy to prevent once they are identified.

• Do Not Assume One Deadline Applies Everywhere

A 20-day CGD timeline cannot be applied to a 60-day financial return or a four-hour incident intimation.

• Do Not Ignore the Instructions Below the Form

Important requirements such as signed-copy uploads often appear in the notes rather than the main table.

• Do Not Treat Certification as a Formality

Where the format requires CA, auditor, KMP or authorised-person certification, the supporting figures should be final before sign-off.

• Do Not Assume All Confidential Information Will Remain Private

Regulation 6 contains exceptions.

• Do Not Ignore Data Consistency

PNGRB has an express power to verify completeness, correctness and consistency.

• Do Not Treat NHIMS as Only an IT Project

The technical feed is ultimately regulatory data. Compliance, operations and IT need to agree on what is being transmitted.

What Should PNGRB-Regulated Entities Do Now?

A business does not need to redesign its entire compliance system overnight. It does need to know where the gaps are.

Start with these steps:

1. Identify your regulated activities. 
2. Map the applicable Schedule or Schedules. 
3. List every relevant form. 
4. Record the exact frequency and due date. 
5. Identify the internal data owner. 
6. Identify the nodal officer/signatory/certifier. 
7. Review portal, NHIMS and API requirements. 
8. Check whether existing data can be extracted in the required format. 
9. Build a maker-checker and reconciliation process. 
10. Retain evidence supporting every regulatory submission. 
11. Monitor PNGRB public notices. 
12. Keep a response process ready for correction or verification notices. 

A PNGRB compliance consultant can be particularly useful where an entity has several regulated activities and needs to translate multiple schedules into one workable internal calendar.

How Corpseed Can Help With PNGRB Compliance Services

The real difficulty with the 2026 Regulations is not understanding that “data must be filed.” The difficult part is identifying which data, under which format, by which team, on what date and with whose certification.

Corpseed's PNGRB compliance services can support businesses in organising this process around their actual activities.

1. PNGRB Applicability Assessment: Corpseed can help review the entity's business activity and determine which parts of the reporting framework are relevant.

This can include:

• CGD operations,
• natural gas pipelines,
• petroleum product pipelines,
• LNG terminals,
• POL infrastructure,
• safety reporting, and
• NHIMS-related data.

2. Schedule A-H Compliance Mapping: Instead of treating the 131-page Gazette as one reporting requirement, Corpseed can prepare an activity-wise mapping covering:

• Schedule,
• format number,
• data requirement,
• filing frequency,
• deadline,
• responsible team, and
• Signatory/certification requirement.

This makes the regulatory requirement much easier to operate internally.

3. Compliance Gap Assessment: Through a compliance gap assessment, the present reporting system can be checked against the applicable PNGRB formats.

The review can help identify questions such as:

• Is the required data already available?
• Is it held in the right format?
• Are different departments reporting conflicting numbers?
• Is certification planned in advance?
• Is NHIMS/API data correctly mapped?
• Are supporting records preserved?

4. PNGRB Reporting Calendar: Corpseed can support the preparation of a format-wise reporting calendar covering monthly, quarterly, annual, biannual and event-based obligations.

A proper calendar is particularly useful because the Gazette contains multiple deadlines rather than one universal filing date.

5. Compliance Documentation Services: Corpseed's compliance documentation services can assist businesses in organising the records that support regulatory submissions.

This may include:

• internal data checklists,
• supporting financial records,
• operational records,
• signed reports,
• certifications,
• submission acknowledgements, and
• regulatory correspondence.

6. Data and Reporting Readiness: Where reporting involves several internal departments, Corpseed can help businesses prepare a clear data-responsibility matrix.

This can reduce last-minute chasing between compliance, finance, operations, HSE and IT teams.

7. PNGRB Verification and Notice Support: Where PNGRB asks for clarification, correction or additional supporting documents, organised records become especially important.

Corpseed can assist with:

• identifying the information requested,
• arranging supporting records,
• reviewing the regulatory requirement, and
• preparing documentation for response.

8. Ongoing PNGRB Regulatory Compliance Support: Businesses with recurring reporting obligations may also require ongoing PNGRB compliance support rather than one-time assistance.

This can help with:

• reporting calendars, 
• regulatory updates, 
• new PNGRB public notices, 
• data-document readiness, and 
• periodic compliance reviews. 

Businesses looking for PNGRB regulatory compliance services can work with Corpseed to map the applicable reporting requirements, identify documentation gaps and build a clearer internal compliance process.

Key Takeaways

The PNGRB Databank and Information System Regulations 2026 create a much more organised reporting framework for petroleum and natural gas businesses.

The main points to remember are:

• The Regulations are effective from their publication in the Official Gazette. 
• Their scope covers a wide range of petroleum and natural gas activities. 
• Reporting is organised through Schedules A to H. 
• There is no single filing deadline for all entities. 
• CGD reporting covers far more than infrastructure, it also includes pricing, consumers, CAPEX/OPEX and financial information. 
• Natural gas and petroleum-product pipelines have separate physical, financial, throughput and capacity formats. 
• Safety reporting includes very short timelines for major incidents. 
• NHIMS introduces structured and API-linked transactional reporting. 
• PNGRB can request additional information beyond the schedules. 
• Data marked confidential remains subject to statutory exceptions. 
• PNGRB can verify submitted information against supporting records. 
• Late and incomplete filings may receive an opportunity for rectification in specified cases. 
• False, fabricated or tampered information can move directly into a more serious enforcement track.