haqlLabs

haql-closeout · public guide

Does the month actually tie together?

A per-row QC pass can clear every record and still leave a month that cannot be closed. haql-closeout checks whether the period reconciles — well tests, downtime, field balances, cumulatives and duplicate well-days — before you commit the number.

month-end reconciliationoffline and deterministicclean or blocked

Product: haql-closeout · Public guide · Updated 8 November 2026

What haql-closeout does

haql-closeout is the period-level check that follows row-level QC. It asks whether the month ties together, then names the wells and days that stand in the way of a clean close.

In one sentence: It turns “everything looked fine” into a clean-or-blocked decision with evidence.

Production and operations

Protect the close

Find the contradictory well or field balance before the number is committed.

Partners and JV teams

Answer queries

Show that the period was reconciled, not merely summed.

Reporting teams

Carry a trail

Give every blocker a rule ID, a well, a day and a source row.

Why it matters

A period close is a commitment to partners, royalty owners or a filing. When a well test disagrees with the daily average or a field sells more than it produced, the contradiction usually surfaces on the last working day — after the number has already been sent.

  • A row-level pass can clear every record while the period still contradicts itself.
  • A well can be marked shut-in in one column and produce normally in another.
  • A field can deliver more than it produced; the summary may not expose it.
  • The person who locks the close is often not the person who has to defend it later.
Without haql-closeoutThe hidden problem

The period is locked because the summary looks plausible. A well test that disagrees with the daily average ships in the reporting package anyway.

With haql-closeoutThe visible answer

The blockers are named before the lock: the well, the day, the rule and the source row. The close becomes a decision backed by a report.

What goes in

Closeout uses the records you already keep. Missing optional inputs are treated as gaps, not guessed.

What goes inWhat it means
Production CSVDaily or monthly volumes for the period being closed.
Well test ratesTest results that should reconcile with reported daily volumes.
Downtime reason codesThe operational record that should agree with shut-in and producing days.
Field sales or disposition volumesWhere available, used to test whether the field sold more than it made.

What comes out

The report is built to support a close decision, not just to list exceptions.

What comes outHow to use it
Closeout reportBlockers by well, day, rule ID and source row.
Clean or blocked signalA clear period-level verdict for the person locking the month.
Signed evidenceOptional digital signature (Ed25519) attestation and a deterministic inspection bundle.
Reconciliation trailA record that the period was checked, not assumed.

What it checks

The checks are period-level questions that a single-row review cannot answer.

Check areaWhat it flags
Well test vs daily averageA test rate that does not reconcile with reported daily volumes.
Downtime vs productionA well recorded shut-in while volumes say it was running.
Date continuityA reporting gap measured against that well's own cadence.
Field balanceVolumes sold or delivered exceeding what the field produced.
Cumulative continuityTotals that go backwards inside the period.
Duplicate well-daysThe same well reported twice for one date.
Signed closeoutAn optional attestation over the report and findings root.

Closeout is best run after haql-qc: QC clears the records, then closeout confirms that the period ties together.

What it does not do

A useful tool should be clear about its boundaries. These are the current limits, not hidden caveats.

  • It is a reconciliation check, not a full accounting close or an ERP posting.
  • It depends on the well-test, downtime and sales data you provide.
  • It does not generate regulator forms or make filing decisions.
  • It reports blockers; it does not decide whether a commercial disagreement is material.

Findings are advisory. The tool names a contradiction or a risk with the evidence behind it. The engineering, legal or commercial judgement remains with you.

How to try it

Send one month of data for a free check, or run the standalone binary on your own machine.

  1. Send a month of production data and, where available, well tests and downtime records.
  2. Receive a closeout report naming the blockers, with source rows.
  3. Decide whether to fix the records, investigate the operation or accept the finding.

Access

AccessWhat you get
Sample checkFree. One month of data, no key and no card.
Team$349/month. Annual commitment, up to 10 users and unlimited fields.
On-premise$1,750/month. Annual, per site, unlimited users on that site.

Nothing leaves your machine. The paid tools run offline. The free libraries have no account, cloud call or telemetry.

Common questions

Is this the same as haql-qc?

No. QC asks whether a row is defensible; closeout asks whether the month ties together. They are designed to be used together.

Does it need an accounting system connection?

No. It works from exports and files, not a database or ERP integration.

What does “blocked” mean?

A blocker is a contradiction that needs a decision before the period can be signed off. It is not automatically an error; it is something a person must resolve.

What is a well test?

A measured flow rate taken while a well is tested. It should agree with the daily average reported for the same period.