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.
- Consumer Electronics OMS
- Features
- Payment and reconciliation
Payment and reconciliation
Compare captured payment evidence, line progress and fulfillment events with the order's operation receipts.
OverviewCaptured Payment Evidence×
Consumer Electronics OMS · Payment and reconciliation
New
Captured Payment Evidence
Payment evidence
| Evidence number | Order | Method | Amount | Captured at | Verified | |
|---|---|---|---|---|---|---|
| PE-35573 | CO-15750 | Card | 680 | 25 Oct | ||
| PE-34394 | CO-22019 | ACH | 910 | 08 Oct | ||
| PE-93445 | CO-63907 | Wire | 580 | 05 Oct | ||
| PE-23667 | CO-75725 | Store Credit | 640 | 06 Oct | ||
| PE-13439 | CO-24654 | Check | 240 | 27 Oct |
6 of 6 records
CO-15750Payment evidence · PE-35573
CardAmount680
Captured at25 Oct
Verified✓
StatusCaptured
What you can do
Review the order's evidence together
Operations Manager needs more than a shipped status to close an order confidently. Payment evidence has a method, amount, reference, captured date, verification flag and state. The customer order has its net amount. Order lines and fulfillment events show what the team allocated and shipped. Operation receipts describe what each execution run recorded. Reconciliation reads these linked records for a selected order and writes a receipt showing whether the evidence matches.
A matching run produces a Verified operation receipt. A discrepancy produces a Failed receipt and raises a warranty check for investigation. The reconciliation workflow may advance an Allocated order only when everything matches. This makes a failed result visible rather than quietly treating an attempted close as completion.
How the work is organized
- Payment record. Each payment evidence record stays linked to its order with method, amount, reference, state and verification marker.
- Operational trail. Fulfillment events show quantities and types; receipts keep the source order, owner and result of each run.
- Exception path. A mismatch produces a failed receipt and a warranty check for a named coordinator to assess.
What to agree during setup
Decide who enters payment evidence, who sets the verification flag and where the payment processor’s authoritative confirmation originates. Card, ACH, wire, store credit and check may need different references; agree a consistent reference format so an Operations Manager can compare them with an external statement. A captured state and verification flag have distinct meanings and should not be used interchangeably.
Define what the team expects to match for an order with multiple lines, partial shipment or a refund. Reconciliation should use the actual order, payment and fulfillment records, with an exception routed for review when they differ. The team should keep each failed receipt attached to its source order so later correction can be traced. Payment settlement and refunds remain with the connected payment system.
Check the handoff on an actual case
Select a shipped device order with its lines, shipping events, captured payment evidence and earlier operation receipts. Check the payment reference and amount against the order. Run reconciliation and inspect the resulting receipt. When all evidence agrees, the result should be Verified. Change the case to a discrepancy, such as a payment amount that does not agree, and inspect the Failed receipt and linked warranty check.
Ask Operations Manager to explain the discrepancy from the order record and its attachments. A later correction should leave the earlier failed receipt visible. A team member examining the same order should be able to see the confirmed payment, the actual shipping events and the final reconciliation result without searching across disconnected lists.
What your team sees
- Captured Payment Evidence — Captured payments with method, amount, reference and verification state.
- Failed or Corrected Operations — Receipts requiring follow-up after failed or corrected runs.
- Shipped Customer Orders — Shipped orders whose payment and fulfillment evidence can be reconciled.
Follow the work through
What it keeps track of
Data model- Payment evidence
- Captured payment evidence for an order with method, amount and reference.
- Customer orders
- Customer orders moving through draft, review, approval, execution and cancellation.
- Order lines
- Product lines belonging to a customer order with quantity, price and line total.
- Fulfillment events
- Allocation, pick, ship, delivery and return events recorded against an order.
- Operation receipts
- Durable receipts for each executed operation with status and source record.
- Warranty checks
- Warranty registration and coverage checks raised against a customer order: serial match, activation, warranty window and damage assessment.
Who uses it
Permissions- Operations Manager
- Enters or reviews payment evidence and runs reconciliation.
- Fulfillment Operator
- Explains shipping events.
- Service Coordinator
- Investigates warranty checks raised by mismatches.
- Order Reviewer
- Sees the linked decision history.
Set up Consumer Electronics OMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.