Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Versions
  • VL.19.00
  • Workflows
  • WMS WorkFlows
  • Client Related

1. Client Related Names and Addresses

Written by sonia bahri

Updated at July 3rd, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Versions
    VL.19.010 VL.19.00 Legacy Ezlearn
  • What's New!
  • FAQ
  • Whitepaper & Case Studies
+ More

Table of Contents

1. Client Related Names And Addresses Workflow 1. Purpose 2. Step-by-Step Process 4. Outputs & Artifacts 5. Best Practices
Doc360_1.Client_Related_Names_and_addresses (800 x 655 px) by Sonia Bahri

1. Client Related Names And Addresses Workflow

1. Purpose

Define all master-data codes and records that support client billing, reporting, and identification—culminating in the creation and verification of the client’s Name & Address master record.


2. Step-by-Step Process

Start 🟢

  • MANDATORY SETUP CR.02: Payment Terms Codes 
    • Define standard payment-term entries (e.g., Net 30, COD, EOM) that will attach to client invoices.
  • MANDATORY SETUP CR.04: Client Service Representative & Account Manager Codes 
    • Create user-lookup codes mapping each CSR and Account Manager to their internal ID.
  • MANDATORY SETUP CR.05: Sales Group Codes 
    • Set up sales organization or territory codes used for client segmentation and reporting.
  • MANDATORY SETUP CR.12: Storage Period & Billing Date Codes
    • Configure allowable storage-period buckets and default billing-date triggers (e.g., monthly, upon receipt).
  • MANDATORY SETUP WP.11: Warehouse Codes 
    • Define each warehouse/location code where client stock may reside.
  • OPTIONAL SETUP AR.99: A/R Sub-Ledger Codes 
    • Establish sub-ledger segments for accounts receivable (e.g., domestic vs. export).
  • OPTIONAL SETUP CP.01: Currency Codes 
  • Enter valid ISO currency codes (e.g., CAD, USD) for multi-currency billing.
  • OPTIONAL SETUP CR.06: Client Names and Addresses
    • Paying Office Codes: Create codes for client payment centers or corporate headquarters.
  • OPTIONAL SETUP CR.26: Remittance Codes 
  • Define remittance-address identifiers if clients send payments to multiple locations.
  • OPTIONAL SETUP CR.06: Client Names and Addresses
    • Third-Party Bill-To Codes: Add codes for any third-party entities responsible for paying invoices on the client’s behalf.
    • Broker Codes: Configure codes for logistics brokers or agents who handle inbound/outbound shipments.
  • MANDATORY SETUP CR.06: Client Names & Addresses 
  • Finally, enter the client’s legal name, complete address(es), contact information, and assign the unique Client ID.
  • OPTIONAL SETUP OR.46: Query to View Client Information 
  • Run the “Name & Address” lookup to verify the entered data on-screen.
  • CR.42: Client Name & Address Report 
  • Generate and print the official Client Master-Data report for audit or distribution.

End 


4. Outputs & Artifacts

  • Payment Terms Table (CR.02)
  • CSR / Account Manager Directory (CR.04)
  • Sales Group List (CR.05)
  • Storage & Billing Calendars (CR.12)
  • Warehouse Master (WP.11)
  • A/R Sub-Ledger Config (AR.99)
  • Currency Table (CP.01)
  • Paying Office, Remittance, Third-Party, Broker Codes (CR.06 & CR.26)
  • Client Master Record (CR.06)
  • On-screen Name & Address Lookup (OR.46)
  • Client Master-Data Report (CR.42)

5. Best Practices

Sequence Enforcement: Complete code tables (steps 2–12) before entering the actual client record (step 13).

Cross-Validation: After entering CR.06, immediately run OR.46 to catch typos or missing fields.

Documentation: Archive the printed CR.42 report alongside the client’s signed service agreement.

Consistency: Use standardized naming conventions and code prefixes (e.g., PT_30 for Net 30) to simplify downstream integrations.

 

Next: 2. Client Related Rates

 

 

contact details customer info

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • CR.06: Client Names and Addresses
MAVES Logo

For more than fifty years, we have been exclusively focused on the development of multi-client third-party logistics software and supporting services.

Address

MAVES International Software Corp

140 Allstate Parkway

Suite #302

Markham, ON L3R 5Y8

905-882-8300

Email: info@maves.com

Links

  • Home
  • Contact Us
  • Careers
  • News and Events
  • Blog
  • Support Desk

Associations and Memberships

WERC CSCMP Global Cold Chain IARW IWLA

©Copyright 2025 MAVES International Software. Privacy Policy. Terms of Use. Site Map

Expand