Skip to content
Front End Engineering Consultancy

FEEC software

Production allocation,
with a trace behind every barrel.

ReservoirLedger is FEEC's production allocation software: one traceable system for operators who still allocate in Excel, with measured production allocated back to wells and partners by a written accounting method and every barrel traced to its meter reading. It is not a reservoir simulation or reserves tool.

Where ReservoirLedger stands. It is being built with design partners, starting with an offshore test-based profile. This page describes what the pilot and the product are built to do; nothing here claims a live deployment or a named customer.

Built by FEEC

Built by process engineers, not a generic software shop

Excel allocation works until a partner, an auditor or the person who owns the workbook asks how a barrel was allocated, and by whom. The people designing the method are the people you talk to.

Process engineers, not a generic software shop

Flow networks, well tests, fuel, flare and vent, and stock are the working vocabulary here, not features added afterwards.

A method you can read and sign

The accounting method is written down first: the algorithm per phase and node, the conservation rules, the exception policies and the tolerances. Your side signs it before any allocation is run.

Records that stand up to a partner

Each run stores its inputs, source files, well tests, factors, profile and engine versions, and the override and approval records behind it. A re-run supersedes a run; it never overwrites one.

Founder-led, with design partners

You deal directly with the engineers building it. One or two design partners shape the first release.

What it does

Allocation you can explain to a partner

The same disciplines a production accountant applies by hand, made repeatable: a method written down, inputs checked, runs that cannot be overwritten and approvals that leave a trail. The screens are on reservoirledger.com as mockups drawn on fictional data.

See the mockups
Accounting method

A written accounting method.

Before any engine code runs, the method is specified per allocation profile: the algorithm per phase and node, conservation rules, exception policies, tolerances, rounding and manual overrides. You sign it, and the engine implements only what it says.

More on reservoirledger.com
Excel-first import

Keep Excel as the way your team enters data.

Templates that look like your daily production report, row-level validation before anything is saved, an error report you can fix in Excel, and a mapping wizard for your own workbook layout.

More on reservoirledger.com
Daily and monthly

Daily provisional allocation, monthly close.

Daily facts are allocated provisionally each production day. The monthly close checks that every day is allocated, every well test approved and every override approved before the period locks.

More on reservoirledger.com
Flow network

A flow network that is yours.

Fields, wells, completions, fiscal, allocation and check meters, tanks and the nodes and edges that join them define the allocation topology, with working-interest owners versioned over time.

More on reservoirledger.com
Audit trail

A trace for every barrel.

Every allocated barrel traces to its meter reading, well test, hours on, factor and any approved override. Runs are immutable and versioned: a re-run supersedes a run and never overwrites it.

More on reservoirledger.com
Governance

Overrides need a reason and a second person.

Approved months lock, and a later change is a restatement with its own reason and approval.

More on reservoirledger.com

Outputs are report profiles: customer-prepared internal outputs. ReservoirLedger is not approved, certified or endorsed by any regulator. The client remains responsible for official volumes, royalty and regulatory submissions. The first release leaves out revenue, royalty and joint-interest billing accounting, PSC entitlement accounting, reservoir simulation and reserves estimation, and mobile data entry.

Time and units

Production days and units, handled the way operators do

Native units throughout, in the demo data too: oil in barrels, gas in thousand standard cubic feet and water in barrels.

Time and units

Production day

Each facility has its own cut-off time (06:00 by default) and time zone. Every daily value belongs to the facility’s production day, not to UTC midnight.

Clock changes

A day on which the clocks change has 23 or 25 hours. Each production day stores its length, and hours on are checked against that length, never against 24.

Native units

Oil, condensate, gas and water are shown in their own units. Barrels of oil equivalent appear only after you set your own conversion factor; there is no default value.

Gas conditions

Reference conditions are explicit for each meter and never assumed.

Parallel-run guarantee

We reproduce your closed month, or the pilot fee is refunded

The paid pilot sets our allocation beside your own spreadsheet, well by well. A data processing agreement is signed before any data is shared.

Paid pilot

One facility, up to 25 producing wells and one allocation profile, for 3 months from kick-off. We reproduce your closed month or months within the tolerance in the signed method, or the pilot fee is refunded in full after one remediation cycle.

Standard onboarding

For up to two facilities: templates, 12 months of history and the parallel run against your own spreadsheet.

Complex onboarding

For many networks or legacy data. Quoted after we have seen the workbooks.

Start with your current workbook

Join the design-partner programme or book a demo. Tell us how many facilities you allocate, what you keep in Excel today and how long your month-end close takes.