Reviewing & Validating

After files are uploaded, review the import session before approving. Approval promotes staging data to live transactions and pipeline readings used in the ledger, reports, and reconciliation.

Open an import session

1. Go to Imports.
2. Click a row in the Import Sessions table.
3. For multi-day uploads, use the day navigation bar to switch between linked sessions.

The session page shows:

• Production day, facility, and overall status
• Import intelligence summary (loads, volumes, issues)
• Batches — one per uploaded file
• Pipeline readings tab (if pipeline files were included)
• Approve and Reject actions (requires approve permission)

Session scorecard

The session page highlights items that need attention:

Item	What it means
Unmapped codes	Shipper or carrier codes in the file do not match a Partner in Coyote
Duplicate tickets	Same ticket number appears more than once in a batch
Cross-bay tickets	Same ticket appears on multiple bays in this session
Sequence gaps	Missing ticket numbers on a bay (possible missing loads)
Data changes	Rows edited since last validation
LACT flags	Producer LACT rows need allocation or matching

Click each banner or scorecard item to open the focused review modal.

Review a batch (bay / carrier file)

1. From the session page, scroll to Import Batches on the session page (or click a batch file name for row-level detail).
2. Review each batch in the table:
   • Ticket number, volumes (GV, GSV), temperature, API
   • Shipper and carrier codes (and resolved partner names)
   • Errors (must fix) and warnings (review before approve)
3. Use filters and sorting to find problem rows quickly.

Click a batch file name to open row-level detail for that bay file.

Fix row-level issues

Action	When to use
Edit row	Correct volume, ticket number, or codes
Delete row	Remove a bad line from the batch
Acknowledge alarm	Accept a BS&W or measurement alarm with a reason
Add manual transaction	Add a load missing from the file

After edits, run Revalidate on the session so Coyote re-runs validation rules.

Resolve unmapped codes

If shipper or carrier codes from the file are not mapped to Coyote partners:

1. Open Unmapped codes from the session scorecard.
2. Map each code to an existing Partner or create the partner in Admin → Partners first.
3. Revalidate the session.

Unmapped codes block a clean approve if they leave transactions without a resolved partner.

Duplicate tickets

1. Open Duplicate tickets review.
2. For each duplicate group, choose which row to keep and which to remove or mark.
3. Revalidate after resolving.

Cross-bay review

When the same ticket number appears on more than one bay in the same session:

1. Open Cross-bay review from the banner.
2. For each ticket, confirm which bay is correct.
3. Complete cross-bay review before approving the session.

Cross-bay tickets are flagged during upload so you can reconcile split or mis-assigned loads before they go live.

Sequence gaps

Coyote checks ticket number sequences per bay. A sequence gap means ticket numbers are missing — possibly a missing file or a gap in the terminal export.

• Review the gap list on the session page.
• Import the missing day or file if the gap is real.
• Document and proceed only if you have confirmed the gap is acceptable.

Producer LACT batches

LACT imports follow a different review path:

1. Open the LACT batch from the session.
2. Review meter allocations and flagged rows.
3. Assign producer and link pipeline readings where required.
4. Use bulk assign producer or bulk link reading when many rows share the same values.
5. Resolve auto-match suggestions when Coyote finds candidate readings or tickets.

LACT batches may stay in Needs Review until all external tickets are matched or staged appropriately.

Pipeline readings

If you uploaded pipeline files:

1. Open the Pipeline readings tab on the session page.
2. Confirm reading date, daily GSV/volume, and pipeline assignment.
3. Readings are approved together with bay batches when you approve the session.

Revalidate

Click Revalidate on the session after:

• Editing or deleting rows
• Resolving unmapped codes, duplicates, or cross-bay tickets
• Adding manual transactions

Revalidation refreshes discrepancies, mapping results, and session status.

Approve the session

When all blocking issues are resolved:

1. Click Approve session.
2. Optionally add approval notes.
3. Confirm.

Approval:

• Promotes staging transactions to approved loads
• Approves pipeline readings linked to the session
• Updates session and batch status to Approved
• Makes data available in Loads, Report Ledger, and Reconciliation

You need the import approve permission (facility:imports:approve).

Note

If Approve is disabled, check for remaining errors on batch rows or incomplete cross-bay / LACT review steps.

Reject the session

If the import cannot be corrected:

1. Click Reject session.
2. Enter a reason (required).
3. Confirm.

Rejected sessions do not create live data. Export corrected files from source and start a New Import.

What happens after approval

Area	Result
Loads / Transactions	Approved truck loads appear with report day set
Report Ledger	Rows available for daily and monthly reports
Reconciliation	Loads ready to match against producer statements
Pipeline readings	Daily meter totals available for settlement and analytics

Next: Troubleshooting Imports if something fails during upload or review.