Reference Data: Whistl Client (Billing) Account Fields [Guide]

Modified on Tue, 16 Jun at 11:00 AM

Article 1: Whistl Onboarding Requirements and Configuration Guides [Information]Article 2: Reference Data: Whistl Baseline Account Fields [Guide]Article 3: Reference Data: Whistl Client (Billing) Account Fields [Guide]Article 4: Reference Data: Order-Level Whistl Fields [Guide]
Onboarding and ConfigurationBaseline Account(Billing) AccountOrder-Level Fields
      You are hereYou are here   

  

This reference lists the carrier-specific Whistl Client (Billing) Account fields used in techSHIP.


Use it together with the linked Client (Billing) Account setup steps: the setup guide covers the shared configuration flow, while this article defines the confirmed field values, field behavior, and client-specific carrier configuration details.

  

   
Note   

  

For a complete overview of supported carriers and related setup guides, refer to techSHIP supported Carriers - Master List [Guides List].

   

   

   


Warning

Review and complete Reference Data: Whistl Baseline Account Fields [Guide] before configuring the Client (Billing) Account so the carrier connection is available.

 
   


TABLE OF CONTENTS


Adding a Client (Billing) Account


Follow the UI Navigation steps in How to Add a Carrier Billing Account [Step-by-Step guide], using the carrier-specific values provided in this guide.

   

Go to Go to    
Article: Essential ConfigurationArticle: Carrier-Specific
Essential ConfigurationCarrier-Specific

   

Carrier-Specific Instructions

   Return to Go to 
Article: Essential ConfigurationArticle: Carrier-Specific
Essential ConfigurationCarrier-Specific

     

The Carrier tab contains the Client (Billing) Account fields used to define confirmed carrier-specific behavior for this client. Highlighted fields indicate mandatory and optional configuration groups.


[Insert screenshot here]


A

Service code: Defines the Whistl service used by the Client (Billing) Account. Select [Use Order] to use the service selected on the order.

     

B

Override WMS Service Code: Controls whether the configured Service code is used instead of the service code received from the integrated system.

     

C

Currency: Defines the currency used by the Client (Billing) Account for configured shipment values.

     

D

Terms of sale: Defines the terms of sale value used by the Client (Billing) Account when required for the shipment.

     

E

Category Of Item: Defines the item category value used by the Client (Billing) Account when item category information is required.

     

F

Default contents description: Defines the default contents description used when shipment contents information is not otherwise provided.

     

G

Importer VAT number: Defines the importer VAT number used for shipments where importer VAT information applies.

     

H

Sender name: Defines the sender contact name used for this Client (Billing) Account.

     

I

Sender company: Defines the sender company name used for this Client (Billing) Account.

     

J

Override sender address: Controls whether the sender address configured for this Client (Billing) Account is used instead of the sender address inherited from the carrier connection.

     


Warning

Select Save before continuing so the configured settings are applied.

 
   

    

Next Steps (Optional)


Optionally, after the Client (Billing) Account is configured and saved, continue with Reference Data: Order-Level Whistl Fields [Guide].

   

         Go to Go to 
Article 1: Whistl Onboarding Requirements and Configuration Guides [Information]Article 2: Reference Data: Whistl Baseline Account Fields [Guide]Article 3: Reference Data: Whistl Client (Billing) Account Fields [Guide]Article 4: Reference Data: Order-Level Whistl Fields [Guide]
Onboarding and ConfigurationBaseline Account(Billing) AccountOrder-Level Fields

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article