These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- EV Fleet Management
- Features
- Activity and Financial Evidence
Activity and Financial Evidence
Inspect actual operation results and load-linked financial records without confusing execution, verification and payment.
OverviewReceipt Exceptions×
EV Fleet Management · Activity and Financial Evidence
New
Receipt Exceptions
Operation receipts
| Receipt number | Parent | Action | Expected revision | Operation key | Status | |
|---|---|---|---|---|---|---|
| OR-94536 | AL-49064 | ACT-467 | 160 | OK-851 | Recorded | |
| OR-68238 | AL-49099 | ACT-686 | 640 | OK-437 | Verified | |
| OR-60036 | AL-18480 | ACT-652 | 160 | OK-406 | Failed | |
| OR-98728 | AL-10784 | ACT-330 | 820 | OK-708 | Corrected | |
| OR-33919 | AL-66579 | ACT-853 | 80 | OK-360 | Recorded |
6 of 6 records
ACT-467Operation receipts · OR-94536
RecordedParentAL-49064
Expected revision160
Operation keyOK-851
Result statePending
Occurred at04 Oct
What you can do
Explain the load outcome from its evidence
The Operations Overview presents a ranked exception queue across dispatch, fleet upkeep and evidence, with linked-record detail. The Operations Reviewer can use it to find a case needing attention, then inspect the receipt, decision or source record behind the exception. The team can see what was requested and what result was actually retained.
Operation receipts carry an action identity, expected revision and result state, along with external and effect references when those exist. Their verification status is separate from the result state. A Completed result describes the recorded action outcome; the receipt can still need verification. Financial records have another lifecycle and should be read on their own terms.
How the work is organized
- Inspect the operation. Read Pending, Failed or Needs review results with the recorded failure reason and source context. Compare the claimed outcome with the actual load, charging or delivery evidence before deciding what to do next.
- Retain the decision. Review records keep the source revision, reviewer and reason. Attachments retain their title, evidence type and visibility so a colleague can locate the supporting material later.
- Follow financial state. The Finance Officer maintains freight charges by load, charge type, amount and currency. Draft, Approved, Invoiced, Paid and Void are financial outcomes that remain distinct from the transport’s execution status.
What to agree during setup
Agree which source record and effect reference are needed to verify each operation. An external reference should identify a real outcome in the connected source. Decide who investigates missing or contradictory evidence before any retry or correction is authorized. Keep the original case available when later evidence changes the result.
For finance, agree the accounting handoff and how invoice or payment evidence reaches the freight charge record. The load’s freight amount is expressed in USD, while individual charges have their own currency. Keep those meanings clear and avoid adding unlike currencies into an unexplained total. Set Internal or Shared attachment visibility according to the intended audience.
Check the handoff on an actual case
Use a delivery operation whose result is marked Completed while the delivery proof remains Disputed. The Operations Reviewer inspects the receipt and compares it with the actual source case. The discrepancy needs a recorded reason and investigation before the receipt is treated as Verified.
Next, take a freight charge still in Draft and inspect the associated delivery evidence. Have the Finance Officer follow the agreed review and accounting process without treating receipt verification as a payment event. Rehearse a correction to an executed load and retain the earlier receipt and decision. A colleague should be able to explain the original outcome and its correction without reconstructing the story from private messages.
What your team sees
- Receipt Exceptions — Operations with unresolved result states and the failure reason needed for investigation.
- Freight Charge Review — Draft freight charges with their load, charge type and currency.
- Shared Load Evidence — Supporting load material marked for the shared audience.
Follow the work through
Read correction and reconciliation and dispatch and delivery proof for the verification and recovery paths.
What it keeps track of
Data model- Operation receipts
- Recorded operational outcomes awaiting verification
- Review decisions
- Approval, rejection and escalation decisions on records
- Record attachments
- Documents, photos and signature evidence attached to records
- Freight charges
- Freight, accessorial and service charges billed against a load
- All loads
- Planned and executed transport loads
- Proof of delivery
- Delivery confirmation captured at the stop
- Charging sessions
- EV charging sessions supporting close a verified charging session; an actual charger receipt is required and range remains an estimate.
- Fuel transactions
- Fuel and energy purchases recorded per asset
Who uses it
Permissions- Operations Reviewer
- , Finance Officer, Charging Coordinator.
- The reviewer investigates outcomes, finance follows charge evidence and the coordinator supplies charging and energy context.
Set up EV Fleet Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.