Everything between your ERP and Cobra

Every feature here answers a real month-end problem, and new checks are added as they're finished.

From your ERP export to the files Cobra imports

Load the export you already run from SAP, Oracle or Costpoint. Get back actuals in the layout Cobra documents, tied to the ERP to the cent.

Load the export you already run from SAP, Oracle or Costpoint. Get back actuals in the layout Cobra's Integration Wizard documents, tied to the ERP to the cent. Your Cobra administrator confirms it on a test copy first.

Stratholt™ won't mark the Cobra files ready while a row Cobra would reject is still open. The files are plain CSV, by work package, cost element and month.

Find problems before Cobra sees them

Solves: hand-checking

More than 100 automatic checks

Totals, duplicates, missing hours, closed periods and more.

Every run checks totals, duplicates, missing hours, closed periods and more. Each check names the EIA-748 guideline it relates to.

Solves: chasing the same error

One list, grouped by cause

One bad charge number is one problem, not 300 lines.

One bad charge number is one problem, not 300 lines. Your team decides once, and Stratholt™ remembers.

Solves: cost on dead charges

Closed and idle charge numbers

Cost on closed charges and closed work packages.

Flags cost on closed charges and on work packages closed in Cobra, and lists charges that should be closed.

Solves: bad schedule status

Schedule health

Data date and dates checked before status goes out.

Before the schedule statuses Cobra: a wrong data date, dates on the wrong side of it, and percent complete that doesn't match the actual dates. Also work the schedule shows in progress with no cost for months. Reads P6 and Microsoft Project files.

Fig. 1 · Schedule healthFrom the real software · made-up demo data
Schedule status updatePercent complete Stratholt™ measures from material, for the schedule activities that carry it, as of FY2026-P09.
Schedule health

Data date (the date the schedule was statused to): 2026-09-30 · expected 2026-09-30 Matches

2 activities with dates on the wrong side of the data date · 1 whose percent complete does not match its dates · 1 work package in progress with no cost

CheckActivityWhat to fixForecast finish% complete
DatesDated on the wrong side of the data dateA-ORPHAN-01'Management review milestone': not started but forecast to start 2026-05-01, before the data date 2026-09-30. Fix it in the schedule before it statuses Cobra.2026-09-300.0
DatesDated on the wrong side of the data dateA-WP-P2-0106Not started but forecast to finish 2026-06-27, before the data date. The activity was not statused, or the schedule was not rescheduled.2026-06-270.0
ProgressPercent complete and dates disagreeA-WP-P2-0203Actually started 2026-05-03 and finished 2026-09-27, but shows 95% complete. Percent complete and actual dates must agree: This status drives earned value in Cobra.2026-09-2795.0

Get material right

Solves: cost on the wrong work package

Your parts list, checked

Parts the ERP booked elsewhere, with a drafted request.

When the ERP charges a part to a different work package than your master parts list, Stratholt™ lists the part, the amount and both work packages, and drafts the request for accounting.

Solves: guessing material progress

Material progress and estimates

What's issued and still needed, priced from POs.

See what's issued and what's still needed, priced from open POs and actual cost.

Solves: hidden scrap and leftover stock

Scrap and excess

Scrap over allowance and leftover stock, flagged.

Tracks scrap on each work package. Flags scrap over the planned allowance, and leftover stock worth a decision that has none.

Solves: material priced the wrong way

Costs material the way your ERP does

Set per ERP: timing, valuation, price variance.

Set per ERP: when cost reaches the job, how the ERP values material, and where price variance lands.

Fig. 2 · Master parts listFrom the real software · made-up demo data
Master parts listWhich work package a part's cost belongs to, even when the ERP charges it somewhere else.
ERP disagrees with the master33 parts

$64,724 charged by the ERP to a different work package

In the ERP, not in the master6 parts

$6,893 that cannot be placed until assigned

No work package0

parts in the master

Master parts list5,020

5,020 from file

Part on a different work package than the master listlargest first
PartERP chargedMaster list saysAmountRequest
HS-14379WP-P1-0505WP-P1-0503$15,595.38JEV request, not yet posted
HS-12084WP-P1-0303WP-P1-0301$7,085.44JEV request, not yet posted
HS-14354WP-P1-0501WP-P1-0503$4,891.76JEV request, not yet posted
HS-13150WP-P1-0401WP-P1-0402$3,690.10JEV request, not yet posted
HS-14136WP-P1-0503WP-P1-0502$3,457.79JEV request, not yet posted
HS-11526WP-P1-0202WP-P1-0203$2,930.80Override this month

Know who changed what, and why

Solves: changes with no trail

A log that can't be quietly edited

Who, when and why, for every decision.

Every decision is saved with who, when and why. The ERP numbers themselves are never changed.

Solves: one person fixing their own numbers

Second-person review

Flagged until a second person reviews it.

A correction request is ready for finance at once. Until someone other than its preparer reviews it, it's marked as not yet reviewed.

Solves: hiding an overrun

Overrun warning

Flags cost moved out of an overrunning control account.

Flags a correction request that would move cost out of an overrunning control account into a work package with budget left. A notice, not a hold.

Solves: "what moved since last week?"

Preliminary and final runs

Early for the CAMs, then final, with what moved.

Run early for the CAMs, then final. See exactly what moved between the two, and why.

The details a practitioner would ask about

Compare with Cobra

Every difference, with its likely cause.

Upload Cobra's Assignment Export and see every difference by work package, resource and month, rolled up to control account, with its likely cause.

Cobra's ETC workbook, filled in

This month's estimates, before and after.

Export the forecast from Cobra, get it back filled with this month's estimates. Before and after for every row.

Set up from Cobra

Structure and baseline from a Cobra export.

Control accounts, work packages and the baseline load straight from a Cobra export.

Late postings held

Last month's numbers don't quietly change.

Cost posted into a closed month waits for a decision. Last month's numbers don't quietly change.

JEVs tracked to posting

Matched when posted, so the same cost isn't counted twice.

Tracked from drafted to posted. When the ERP shows the transfer, Stratholt™ matches it, so the same cost isn't counted twice.

Accruals that reverse themselves

Reversed when the invoice posts.

Enter work done but not yet billed. It reverses on its own when the matching invoice posts, or next period.

"What changed" for every CAM

Down to the ERP line, before the CAM signs.

What moved since last month, down to the ERP line, before the CAM signs.

Re-run any past month

Rebuilt from its exact files and decisions.

Rebuilt from its exact files and decisions, and compared with the original.

Set up by answering questions

A short set of plain questions, no custom code.

A short set of plain questions on how your company runs EVM. Differences become settings, not custom code.

Stops a bad file

An export that drops past months is stopped.

An export that drops or shrinks past months is stopped before it wipes out history, with the missing months listed.

Your calendar, your periods

4-4-5 or your own; 5x8, 4x10 or 9/80 weeks.

4-4-5 or your own period dates, your holidays and shutdowns, 5x8, 4x10 or 9/80 weeks.

Several programs, one server

Each program kept separate.

Each program keeps its own files, settings, decisions and backups. People see only the programs they're given.

The typical spreadsheet process

Most teams still move ERP cost into Cobra by hand.

Capability
Spreadsheets
Stratholt™Built for this step
Flags problems before Cobra sees the file
By hand
Yes, before Cobra
Ties every dollar to the ERP
If someone checks
Every run, to the cent
Shows where the parts list says material belongs
By hand
Yes, and drafts the request
Prepares status and ETC
By hand
Status file and ETC files
Records every change
No
Who, when and why
Rebuilds a past month
No
Exactly, from kept files
  • Flags problems before Cobra sees the fileSpreadsheets: by handYes, before Cobra
  • Ties every dollar to the ERPSpreadsheets: if someone checksEvery run, to the cent
  • Shows where the parts list says material belongsSpreadsheets: by handYes, and drafts the request
  • Prepares status and ETCSpreadsheets: by handStatus file and ETC files
  • Records every changeSpreadsheets: noWho, when and why
  • Rebuilds a past monthSpreadsheets: noExactly, from kept files

See it in a demo

Typical of a spreadsheet process, not a review of any one team or product.

See what the checks catch

A short exercise on the data that ships with Stratholt™. Nothing you do here leaves your browser.

Fifteen rows from a made-up SAP export. Five of them would put bad numbers in Cobra. Click the rows you'd question, then see what Stratholt™ flagged.

This needs JavaScript. Ask for a demo to see it live.

The challenge rows are exactly as the made-up export has them, and the five flags are the ones Stratholt™ raised on that file.

Easy for the whole team

Solves: copying screens into Excel

Download to Excel

Every table, one click.

Every table, one click, ready to filter and pivot. For CAMs and analysts alike.

Solves: sharing sensitive files

Extract scrubber

A safe sample with made-up values.

Makes a safe sample of a report on your own machine: same layout, made-up values.

Solves: data leaving your network

Runs on your servers

Your program data never comes to us.

Installed inside your network. Your program data never comes to us.