North Dakota NDIC Reporting
Bakken filings. Methane overlap. One source of truth.
North Dakota Industrial Commission monthly production filings sit at the intersection of frac-stage tracking, GOR reporting, condensate allocation, and methane regulatory (NDIC venting/flaring rules + EPA OOOOb/c + North Dakota gas-capture targets). WorkSync assembles all four from one DataHub source and reconciles against your accounting system before submission.
Four Bakken pain points
What makes NDIC harder than the rest.
Pain 01
Frac-stage tracking
The pain
NDIC requires well-test cadence tied to frac stages for the first 90 days of production. Tracking stages by hand from completion reports through to monthly filings is fragile.
WorkSync fix
Completion data pulled from FracFocus and operator stage logs, mapped to NDIC well-test schedule automatically. Missing stages flagged before they become a filing exception.
Pain 02
GOR granularity
The pain
Gas-oil ratio reporting in the Bakken is tighter than other basins because the oil-cut window is narrow. GORs that look like they should flag a gas breakthrough often pass NDIC review only if the underlying data is clean.
WorkSync fix
GOR calculated per well per day from SCADA, reconciled against well tests, and submitted with the audit trail intact. Outliers flagged before filing.
Pain 03
Condensate allocation
The pain
Multi-well pads with shared sales meters mean condensate volumes must be allocated back. The allocation factor drives the severance tax math, royalty calc, and NDIC volume reporting all at once.
WorkSync fix
Allocation engine produces a single factor used consistently across NDIC, severance tax, and revenue distribution. No three-way reconciliation cycle.
Pain 04
Methane regulatory overlap
The pain
NDIC venting/flaring rules + EPA OOOOb/c methane requirements + ND gas-capture targets means one missed survey can trigger multiple filings and one missed well can fail multiple compliance thresholds.
WorkSync fix
LDAR survey schedule, fugitive emission events, capture percentages, and venting volumes all assembled from one data layer. NDIC, OOOOb/c, and gas-capture filings generate from the same source.
Continue the cluster
NDIC filings touch every part of the upstream stack.
Other state filings
Multi-state operators
Bakken specific
Bakken playbook
How the loop closes
Capability deep-dives
Frequently asked
What ND production accountants ask about NDIC automation.
What does NDIC require?
The North Dakota Industrial Commission requires monthly production filings (Form 5/5B) per well, with oil, gas, water, condensate volumes, GOR, well-test data, and run-ticket totals. Filings are due by the 5th business day of the second month after production. Methane reporting overlaps with EPA OOOOb/c on quad-O wells.
What makes Bakken NDIC reporting harder than other states?
Four things. Frac-stage tracking through the first 90 days of production drives the well-test cadence required by the commission. GOR reporting is more granular than other basins because the Bakken oil-cut window is tight. Condensate allocation across pads with shared sales meters requires SCADA-anchored allocation factors. And the methane regulatory overlap (NDIC plus EPA OOOOb/c plus North Dakota gas-capture rules) means one missed leak survey can trigger multiple filings.
How does WorkSync automate NDIC?
DataHub pulls volumes and well-test data from Enertia, Quorum, W Energy, PakEnergy, Oildex, plus SCADA from Ignition, AVEVA PI System, or Cygnet. The allocation engine handles commingled condensate across multi-well pads. Methane regulatory reports (OOOOb/c, gas-capture plans) generate from the same source of truth as the NDIC filing. Reconciliation against your accounting system runs before submission.
Does it cover gas-capture compliance?
Yes. The North Dakota gas-capture rule (75 percent minimum, target 90 percent) requires monthly per-well capture-versus-flare/vent tracking. WorkSync pulls flare and venting volumes from your facility SCADA and meter data, calculates the per-well capture percentage, and flags wells trending toward non-compliance before the filing deadline.
Does it replace our existing accounting / regulatory system?
Your system of record stays where it is. WorkSync reads your production accounting and SCADA read-only and adds the regulatory assembly and reconciliation layer on top.
How fast can NDIC automation deploy?
Two weeks to integrate accounting + SCADA + methane LDAR records. Four weeks to a live production filing under the Impact Guarantee. We anchor on analyst hours per filing cycle and on the number of NDIC versus accounting variance flags caught before submission, with license fees only when that metric moves.
Automate NDIC in 4 weeks.
One field. One filing cycle. Day 7 we show variances against your current filing. Day 28 you decide.