WMC Manuals

Introduction

WM User Manual serves as a step-by-step guide for internal Walmart stakeholders interacting with the Imports platform. It focuses on reviewing, verifying, and managing shipment data (invoices, accessorial claims, detention charges, ebills) and documents shared by carriers. The goal is to ensure accuracy, compliance, and timely processing of import shipments.

This guide will help Walmart users:

• Access and monitor carrier submissions
• Review shipment and payload data
• Approve or escalate discrepancies
• Download relevant documents

Section 1. User Log In

1. WM user can access KNNX Asset Track platform via https://dlat.wal-mart.com/
2. Please add tenant name “Retail” (see image below)

1. Once tenant name is accepted, user will be redirected to Walmart Retail link log in page where carrier user must submit User ID & Password.

Log in details:

1. Password must contain minimum 6 characters including capital letter, digits, and special characters.
2. The password change will be requested every 180 days.
3. There is a maximum of 3 attempts before account is locked.
4. To update Password, click “Forgot your Password” button, add User ID and email notification to reset password will be sent.

IMPORTANT NOTE: We would like to insist that under no circumstances should you share your login credentials with anyone. These credentials are meant exclusively for your use and access KNNX platform. 

Section 2. Invoice review

1. Click on the Business Workflows page from the Navigation Panel on the left-hand side of the screen.
2. Select the required “Imports Shipments” (for OTR carriers only) and “Imports CNRU Shipments” (for CN Rail only) business workflows to review Imports invoices. 

1. Once user clicks on business workflow, the list of invoices is visible (1 row = 1 invoice/1 BOL ID).

Note: User can set up different columns by clicking “Filter” button (in the top of the table) and select required attributes (BOL ID, Carrier SCAC, etc.)

1. Click on the View Details button on the right side of the screen to view the invoice details.

In Invoice details, carrier user can see the details under the following sections:

• 
  
  • 
    
    1. Shipment Information
    2. Carrier Information
    3. Origin Location
    4. Destination Location
    5. Stop Details
    6. Invoice Details (billing info)
    7. Known Charges (Linehaul, fuel, etc.)
    8. Accessorial Claims & Variable Charges
    9. Invoice information (subtotal, total, tax, etc.)
    10. Payment information (updates from SAP)

5. All updates (value changes, user comments, etc.) made to an invoice can be traced via “Activities & Comments” section.

• WM user can download invoice (in pdf format) by clicking “Download” button.

Section 3. Accessorial Claim handling

Carrier can submit the following accessorial claim types in invoice available in “Imports Shipments” business workflow:

1. Heat
2. Hazmat
3. XORM (Extra Miles)
4. COD (Change of Delivery)
5. Miscellaneous (includes 4 types)
   1. Additional Stop
   2. Inbond
   3. Cleaning
   4. Other

Important note: In addition to accessorial claim submission, user can also submit “Spot Rate” (linehaul rate update) from the same “Update” window.

To submit accessorial claim, carrier user must click “Update” button (in the top right corner) and add required info.

Once claim is submitted, WM user can review accessorial claims (in review, approved, rejected) in “Import Accessorial Claims” business workflow.

1. Heat claim

A claim filed when temperature-sensitive cargo is used within shipments.

• Once carrier submits Heat claim in “Import Shipments”/” Imports CNRU Shipments” business workflows, claim will be created in “Import Accessorial Claims” business workflow.

• 
  
  1. If heat claim is created within tolerance rules (available in “Imports Tolerance” master table) provided by WM, then claim will be auto approved.

• 
  
  1. If heat claim is created out of the tolerance rules (available in “Imports Tolerance” master table) provided by WM, then claim will be manually reviewed by WM user.
     • Within manual review, WM user clicks “Update” button and provide approval status (Approved/Rejected) and WMC comments.
     • Once claim is approved/rejected, WM user must click “Send” button.

Note: 1 Heat Claim submission is allowed per 1 BOL ID.

• Once heat claim is confirmed by WM (auto/manually approved or rejected), carrier user can check claim details in “Import Shipments”/” Imports CNRU Shipments” business workflows via “Accessorial Claims” section in invoice details.

• If Heat claim is approved, heat claim charge is also visible in “Variable Charges” section in invoice details.

• If Heat claim is rejected, then heat claim status will be defined ‘’Rejected” and no charge is visible in “Variable Charges” section in invoice details.

1. Hazmat claim

A claim related to shipments containing hazardous materials within shipments.

• Once carrier submits Hazmat claim in “Import Shipments”/” Imports CNRU Shipments” business workflows, claim will be created in “Import Accessorial Claims” business workflow.

• 
  
  • 
    
    1. If hazmat claim is created within tolerance rules (available in “Imports Tolerance” master table) provided by WM, then claim will be auto approved.

• 
  
  • 
    
    1. If heat claim is created out of the tolerance rules (available in “Imports Tolerance” master table) provided by WM, then claim will be manually reviewed by WM user.
    2. Within manual review, WM user clicks “Update” button and provide approval status (Approved/Rejected) and WMC comments.
    3. Once claim is approved/rejected, WM user must click “Send” button.

Note: 1 Hazmat Claim submission is allowed per 1 BOL ID.

• Once Hazmat claim is confirmed by WM (auto/manually approved or rejected), carrier user can check claim details in “Import Shipments”/” Imports CNRU Shipments” business workflows via “Accessorial Claims” section in invoice details.

• After claim submission, it will be checked by WM team and claim status will be updated as “Approved” or “Rejected” and Hazmat claim status and details will be visible accordingly.

• If Hazmat claim is approved, Hazmat claim charge is also visible in “Variable Charges” section in invoice details.

• If Hazmat claim is rejected, then hazmat claim status will be defined “Rejected” and no charge is visible in “Variable Charges” section in invoice details.

1. XORM claim (Extra Miles)

A claim raised when a carrier travels additional, non-agreed miles due to rerouting, incorrect address, or delivery inefficiencies, leading to added costs.

• To submit XORM claim, carrier user opens “XORM Claim” section and provides the following details:

1. Extra Miles (mandatory)
2. XORM Reason (mandatory)
3. XORM Additional file_1 (mandatory)
4. XORM Additional file_1_Description (mandatory)
5. XORM Additional file_2 (optional)
6. XORM Additional file_2_Description (optional)

• Once carrier submits XORM claim in “Import Shipments”/” Imports CNRU Shipments” business workflows, claim will be created in “Import Accessorial Claims” business workflow.

Note: 1 XORM Claim submission is allowed per 1 BOL ID.

Important Note: If “Extra Miles” value is less than 10 miles, XORM claim will be automatically rejected.

• Within the manual review, WM user clicks “Update” button and provide approval status (Approved/Rejected) and WMC comments. Additionally, WM user can update Extra miles value if required.
• Once claim is approved/rejected, WM user must click “Send” button.

Note: 1 XORM Claim submission is allowed per 1 BOL ID.

• Once XORM claim is confirmed by WM (auto/manually approved or rejected), carrier user can check claim details in “Import Shipments”/” Imports CNRU Shipments” business workflows via “Accessorial Claims” section in invoice details.

• After claim submission, it will be checked by WM team and claim status will be updated as “Approved” or “Rejected” and XORM claim status and details will be visible accordingly.

• If XORM claim is approved, XORM claim charge is also visible in “Variable Charges” section in invoice details.

• If XORM claim is rejected, then XORM claim status will be defined “Rejected” (including comments from WM team) and no charge is visible in “Variable Charges” section in invoice details.

IMPORTANT NOTE: XORM Claim is not available for CN Rail

1. COD claim (Change of Delivery)

A claim for reimbursement due to changes in the original delivery location or delivery instructions after the shipment was en route or dispatched.

• To submit COD claim, carrier user opens “COD Claim” section in “Import Shipments”/” Imports CNRU Shipments” business workflows and provide the following details:

1. Destination ID (mandatory) – Dropdown to select new destination (from DCs’ list)
2. COD Charge (mandatory) – reimbursement carrier can request for destination change (in addition to Linehaul rate update)
3. COD Additional file_1 (mandatory)
4. COD Additional file_1_Description (mandatory)
5. COD Additional file_2 (optional)
6. COD Additional file_2_Description (optional)

• Once carrier submits COD claim in “Import Shipments”/” Imports CNRU Shipments” business workflows, claim will be created in “Import Accessorial Claims” business workflow.

Note: 1 COD Claim submission is allowed per 1 BOL ID.

• Within the manual review, WM user clicks “Update” button and provide approval status (Approved/Rejected) and WMC comments. Additionally, WM user can update COD charge value if required.
• Once claim is approved/rejected, WM user must click “Send” button.

Note: 1 COD Claim submission is allowed per 1 BOL ID.

• Once COD claim is confirmed by WM (auto/manually approved or rejected), carrier user can check claim details in “Import Shipments”/” Imports CNRU Shipments” business workflows via “Accessorial Claims” section in invoice details.

• After claim submission, it will be checked by WM team and claim status will be updated as “Approved” or “Rejected”, and COD claim status and details will be visible accordingly.

• If COD claim is approved, COD claim charge is also visible in “Variable Charges” section in invoice details. Additionally, as destination ID is changed, linehaul charge will be also updated.

• If COD claim is rejected, then COD claim status will be defined “Rejected” (including comments from WM team) and no charge is visible in “Variable Charges” section in invoice details.

1. Miscellaneous Claims

A catch-all category for claims that don’t fall under standard types, covering the following claim types:

1. Additional Stop
2. Inbond
3. Cleaning
4. Other

To submit Miscellaneous Claim, carrier user opens “Miscellaneous Claim” section and provides the following details for any of the claim types listed below:

1. Additional Stop 
   1. Number of additional stops (mandatory) 
   2. Miscellaneous Claim file (mandatory) 
   3. Miscellaneous Claim file Description (mandatory) 
2. Inbond 
   1. Miscellaneous Claim amount (mandatory) 
   2. Miscellaneous Claim file (mandatory) 
   3. Miscellaneous Claim file Description (mandatory) 
3. Cleaning 
   1. Miscellaneous Claim amount (mandatory) 
   2. Miscellaneous Claim file (mandatory) 
   3. Miscellaneous Claim file Description (mandatory)  
4. Other 
   1. Miscellaneous Claim amount (mandatory) 
   2. Miscellaneous Claim file (mandatory) 
   3. Miscellaneous Claim file Description (mandatory) 

• Once carrier submits MISC claim in “Import Shipments”/” Imports CNRU Shipments” business workflows, claim will be created in “Import Accessorial Claims” business workflow.

Note: Each MISC Claim type submission is allowed only once per 1 BOL ID.

• Within the manual review, WM user clicks “Update” button and provide approval status (Approved/Rejected) and WMC comments. Additionally, WM user can update MISC charge (or # of additional stops) value if required.
• Once claim is approved/rejected, WM user must click “Send” button.

• Once MISC claim is confirmed by WM (auto/manually approved or rejected), carrier user can check claim details in “Import Shipments”/” Imports CNRU Shipments” business workflows via “Accessorial Claims” section in invoice details.

• After claim submission, it will be checked by WM team and claim status will be updated as “Approved” or “Rejected”, and Miscellaneous claim status and details will be visible accordingly.

• If Miscellaneous claim is approved, Miscellaneous claim charge is also visible in “Variable Charges” section in invoice details.

• If Miscellaneous claim is rejected, then Miscellaneous claim type status will be defined “Rejected” (including comments from WM team) and no charge is visible in “Variable Charges” section in invoice details.

1. Spot Rate claim

A claim related to shipments moved under a spot rate (one-time quoted rate) rather than contract rate.

• To submit Spot Rate claim, carrier user opens “Spot Rate Claim” section and provide the following details:

1. Spot Rate – one-time linehaul rate (mandatory)
2. Spot Rate Reason (mandatory)
3. SR Additional file_1 (mandatory)
4. SR Additional file_1_Description (mandatory)
5. SR Additional file_2 (optional)
6. SR Additional file_2_Description (optional)

• Once carrier submits Spot rate in “Import Shipments”/ ”Imports CNRU Shipments” business workflows, claim will be created in “Import Accessorial Claims” business workflow.

Note: Spot rate submission is allowed only once per 1 BOL ID.

• Within the manual review, WM user clicks “Update” button and provide approval status (Approved/Rejected) and WMC comments. Additionally, WM user can update Spot rate charge value if required.
• Once claim is approved/rejected, WM user must click “Send” button.

• Once Spot claim is confirmed by WM (auto/manually approved or rejected), carrier user can check claim details in “Import Shipments”/” Imports CNRU Shipments” business workflows via “Accessorial Claims” section in invoice details.

• After claim submission, it will be checked by WM team and claim status will be updated as “Approved” or “Rejected”, and Spot Rate claim status and details will be visible accordingly.

• If Spot Rate claim is approved, “Linehaul charges” in Known Charges will be updated in invoice details.

• If Spot Rate claim is rejected, then Spot Rate claim status will be defined “Rejected” (including comments from WM team) and no change is applied to Linehaul charge in invoice details.

1. Additional (Optional) actions in “Update” Window

• User can submit additional files if required.
• Carrier user can submit Invoice ID (optional)

Section 4. Invoice dispute handling by WM user (Auditor)

WM Account as Auditor must be onboarded separately. 

• Carrier user can raise a dispute for invoice in KNNX platform if:

1. Carrier user observes discrepancy/error in Invoice/ebill details (linehaul charge, fuel charge, invoice/ebill amount, etc.) in “Import Shipments”, “Imports CNRU Shipments” & “Imports WMC to Carrier” business workflows.
2. Carrier user does not agree with “Rejected” accessorial claim status.
3. Invoice will be auto disputed when it is sent for payment and total invoice amount is over $15,000.

• To raise a dispute, carrier user must click “Dispute” button

• Once “Dispute” button is clicked, carrier user must provide Dispute details and click “Raise” button.

• Once Dispute is raised, WM user with Auditor access will receive email notification and can see # of disputed invoices in business workflows as the following:

Use case #1: Carrier raised a dispute due to discrepancy/error in Invoice/ebill details (linehaul charge, fuel charge, invoice/ebill amount, etc.)

• WM Auditor can check dispute details in “Activities & Comments” section.

• If any rate must be updated, WM user can update Master table, so invoice will re-calculated with correct values.
• WM Auditor can also update invoice values by clicking “Update” button.

• Once value is updated, WM user clicks “Update” button to save changes.

• Once all changes are made, WM auditor clicks “Resolve Dispute” button and provide comments (if required), so invoice will be sent back to carrier for further review and submission for payment.

• Once Dispute is reviewed and resolved by WM, carrier user can check WM comments via “Activities & Comments” section.

Use case #2: Carrier user does not agree with “Rejected” accessorial claim status.

• WM Auditor can check dispute details in “Activities & Comments” section.

• WM Auditor can check claim and update claim status to “Approved” by clicking “Update” button.

• Once value is updated, WM user clicks “Update” button to save changes.
• Once all changes are made, WM auditor clicks “Resolve Dispute” button and provide comments (if required), so invoice will be sent back to carrier for further review and submission for payment.

• Once Dispute is reviewed and resolved by WM, carrier user can check WM comments via “Activities & Comments” section.

Use case #3: Invoice will be auto disputed when it is sent for payment and total invoice amount is over $15,000.

• WM Auditor can check dispute details in “Activities & Comments” section.

• WM Auditor can check total invoice amount and click “Update” button

• If amount over $15,000 is ok for WM Auditor, WM user selects YES in “Invoice Approve via Dispute” dropdown under “Invoice Information” section.

Note: If invoice amount is not ok due to incorrect rates, WM Auditor can update Master table for correct rates.

• Once value is updated, WM user clicks “Update” button to save changes.
• Once all changes are made, WM auditor clicks “Resolve Dispute” button and provide comments (if required), so invoice will be sent back to carrier for further review and submission for payment.

• Once Dispute is reviewed and resolved by WM, carrier user can check WM comments via “Activities & Comments” section.

Section 5. Invoice submission for payment

• WM user can follow status on invoice via “Invoice Status” attribute under “Invoice Information” tag. 

Invoice status = Not Ready for Payment à Invoice is not sent for payment (on carrier review)

Invoice status = Initiated à Invoice is sent for payment (not accepted by SAP).

Invoice status = Processed à Invoice is accepted by SAP but not paid.

Invoice status = Settled à Invoice is paid by WM.

Section 6. Detention Claim handling

A claim filed when a carrier is delayed beyond the agreed free time during pickup or delivery at distribution centre resulting in extra charges for the waiting time. This compensates the carrier for idle time due to factors like slow loading/unloading or paperwork delays.

• Carrier user can submit Detention claim via “Imports Detention Claim” business workflow. 

Important note: Detention claim workflow is not used by CN Rail.

• After entering “Imports Detention Claim” business workflow, click “Create” button (in top right corner)

• To create detention claim, the following attributes must be added: 
  1. Detention_BOL_ID (mandatory) – to create detention charge for existing BOL ID.
  2. Appointment_nbr (mandatory)
  3. Detention_Origin_ID (mandatory) – Origin name available in invoice
  4. Detention_Destination_ID (mandatory) - Destination ID available in invoice
  5. IN_Date (mandatory) - Date the carrier arrived at DC gate. This marks the start of the detention clock.
  6. OUT_Date (mandatory) - The date the carrier departed from DC after loading or unloading was completed. This marks the end of the detention period.
  7. POD_file (optional) – Proof of delivery file upload
  8. BOL_file (optional) – BOL file upload
  9. Upload_Email (optional) – Any email upload
  10. Detention_Comments (optional)

Important Note: 1 Detention claim submission is allowed per 1 BOL ID.

• Carrier user can send detention claim for WM review (approval/rejection).
• Detention claim can be auto approved or send to WMC user for manual review (approval/rejection). 
• Auto-approval scenario: If number of chargeable days is less than day value in “Imports Tolerance” master table for each carrier for pre-defined period. 

• Detention claim will be sent for WMC Manual review if: 
  1. Detention DC is location in Region 1. 
  2. # of chargeable days is over the allowance value in “Imports Tolerance” master table. 
  3. If Detention charge is over $10,000.
• Once Detention claim is on WMC review, WM user can review all claims are on review by using filter on Delivery Status and select “Sent to WMC Imports”.

• If Detention charges or other inputs are incorrect, WMC user can reject claim, provide comments and click “Confirm” button, so carrier will be able to update required inputs.

• If detention claim is correct and align with WM internal data, then WM user can confirm by clicking “Accept”.

Note: After accepting a claim, WM user still has option to update detention details as “IN Date”, “OUT Date” and “Detention comments” via “Update” window.

• If no updates are required, then WM user can click “Send” button to submit detention invoice for payment.

Section 7. Ebill (Credit) submission by WM user for carrier 

This concept is used in KNNX platform to submit credits to the carrier’s account in SAP.

• WM user can submit credit ebill via “Imports Ebill WMC to Carrier” business workflow. 

• After entering “Imports Ebill WMC to Carrier” business workflow, click “Create” button (in top right corner)

• To create Ebill, the following attributes must be added: 
  1. Load_carrier_scac (mandatory) – to define the owner of credit ebill
  2. Ebill_BOL_ID (mandatory) – to create ebill for existing BOL ID.
  3. Ebill_reason (mandatory)
  4. Ebill_business_reason (mandatory)
  5. Ebill_GST_rate(%) (optional)
  6. Ebill_PST_rate(%) (optional)
  7. Ebill_QST_rate(%) (optional)
  8. Ebill_HST_rate(%) (optional)
  9. Additional_file (optional)
  10. Additional_file_Description (optional)
• Open “Ebill charges” section and click on “Add more” to submit the following attributes
  • 
    
    • Charge_name (mandatory)
    • Charge_amount (mandatory)
    • Charge_description (mandatory)

Note: If user needs to add more charges, he/she must click “add more” and update the same 3 mandatory attributes.

• Once the details are added, click on the Create button to generate detention claim.

• Once ebill is created, it can be viewed in business workflow. User must click on “View details” button for ebill details. Based on inputs, KNNX platform will calculate subtotal and total accordingly.

Note: If provided Ebill BOL ID does not exist, user will not be able to send ebill from KNNX platform.

• To review ebill charge details, please click “Ebill charges/View table

• If ebill details are calculated correctly, WM user can send it for Carrier review (approval/rejection).

1. If ebill is approved, it will be sent as credit ebill by carrier and “Invoice status” attribute (under Invoice Information will be updated as “Invoice Initiated”.
2. If carrier does not agree with ebill credit details, then carrier can raise a dispute. In this case, WM auditor can resolve a dispute as it is shown in Section 4 (Dispute resolving),

Note: Further updates on payments are similar to the scenario described in “Invoice submission for payment” section. 

• WM user can review the invoice flow by clicking the “Show Timeline” button.

Section 8. Ebill (Credit/Debit) submission by carrier 

This concept is used in KNNX platform for carriers to submit charges (adjustments/deductions) missed from the primary invoice.

• Carrier user can submit credit/debit ebills via “Imports Ebill Carrier to WMC” business workflow.
• After submission of credit/debit ebill, WM user will be able to review approve/reject ebill. (use filter “Sent to WMC Payables” in “Delivery status” column.

• If ebill details are incorrect, WMC user can reject claim, provide comments and click “Confirm” button, so carrier will be able to update required inputs.

• If Ebill is correct and align with WM internal data, then WM user can confirm by clicking “Accept”.

Note: After accepting credit/debit ebill, it will be automatically submitted for payment.

• If no updates are required, then WM user can click “Send” button to submit detention invoice for payment.

Section 9. KNNX Support - Troubleshooting

In case of issues with system functionality, data accuracy, or workflow processing, users can follow the steps below before escalating to KNNX Support:

Common Troubleshooting Steps:

• Refresh & Re-login: Log out and log back into the platform to reset session-based issues.
• Check Data Entry: Ensure all required fields are completed accurately, especially container numbers, invoice references, and date formats.
• Review Error Messages: Read any on-screen error messages carefully—they often indicate missing or invalid inputs.
• Confirm Workflow Stage: Ensure the action aligns with the current status of the shipment or claim (e.g., invoice approved before submitting a debit).
• Browser Compatibility: Use a supported browser (Chrome/Edge) and clear cache if needed.

When to Contact KNNX Support:

• System errors preventing task completion
• Data discrepancies not resolved through resubmission
• Access issues (e.g., locked accounts, missing permissions)
• Workflow failures or missing automation triggers

How to contact KNNX Support and raise a ticket

• User must click on Support link in the bottom left corner (see image below) and raise a ticket under one of the provided categories.