What are chargebacks and how can I avoid them?

A chargeback is a fee that a customer (usually a retailer) places on a supplier for errors in not following the retailer’s business requirements. The chargeback was introduced to offset the extra cost the retailer incurs as a result of the supplier’s non-compliance.

 
Chargeback schemes began in the 1980’s as a way for retailers to recoup costs incurred due to supply chain errors. At the time, many suppliers objected to them as unfair profit centers for large, powerful retailers. Although purely punitive fines are not legal, cost recovery is—so chargebacks quickly became adopted by most retailers. It’s easy to understand how mislabeled, mis-packed, late, and wrong-quantity shipments add up to real labor costs and out of stock difficulties for retailers. Distasteful as they may be for suppliers, chargebacks make business sense for retailers in trying to recover costs and are here to stay for the foreseeable future.
 
What can lead to a chargeback being applied to my organization?

·         Early, late, or non-authorized partial delivery of goods or services.

·         Missing, incorrect, non-readable or wrongly placed shipping labels.

·         Substituting products without prior agreement.

·         Ship to incorrect location.

·         Product packaged wrongly according to retailers agreement.

·         Damages that did not occur during transit.

·         EDI 810 invoice not matching original purchase order and/or with wrong terms and details

·         EDI 856 ASN (Advance Ship Notice) does not arrive on time or does not match items in carton.

 
How can my organization eliminate chargebacks or at least reduce greatly the potential of receiving them from my customers?

·         Comply fully with customers EDI requirements.

·         Make sure labels are correct and can be read or scanned easily.

·         Do not substitute products without prior approval.

·         Ship to the correct location.

·         Pack items correctly according to retailer’s requirements.

·         Try to make sure goods arrive in perfect order.

·         Deliver the correct products, quantities and cartons

·         Send accurate and complete EDI 810 invoices.

·         Make sure EDI 856 ASN (Advance Ship Notice) arrives on time and details are correct.

 
To comply fully with your customers EDI requirements and business rules, I would recommend that you enlist the help of a good 3^rd party EDI provider. 3^RD Party EDI providers immediately know retailers requirements, what is expected and how they must be delivered. If you would like to know more about outsourcing your EDI needs to B2BGateway and how we can help you eliminate or greatly reduce potential chargebacks please call +1 (401) 491 9595 or email Sales@B2BGateway.Net

The differences between EDI X12 and EDIFACT

 

Question: Hi Roger, we recently got a contract to supply an organization in Germany which will require EDI. This would normally be no problem to us as we have been doing EDI with our North American trading partners for over four years; however, our new German contract requires us to use EDIFACT rather than X12 as their preferred EDI standard. Could you highlight the main differences between X12 and EDIFACT and suggest what I should do?

 

Answer:  In 1979 the American National Standards Institute (ANSI) chartered the Accredited Standards Committee (ASC) X12 to develop uniform standards for inter-industry electronic exchange of business transactions – now known commonly as Electronic Data Interchange (EDI). These transaction sets, abbreviated to X12, are the predominant EDI standards used by organizations in North America today.

In 1986, the United Nations Economic Commission for Europe (UN/ECE) approved the acronym "UN/EDIFACT," which translates to United Nations Electronic Data Interchange for Administration, Commerce and Transport. UN/EDIFACT is an international EDI standard designed to meet the needs of both government and private industry. EDIFACT is the most popular worldwide EDI data standard outside of North America.

Here is a brief list of some of the different names given to documents in the X12 and EDIFACT transactions sets. You will notice that X12 assigns numeric values to documents whereas EDIFACT lists names or abbreviations.

TRANSACTION SET/DOCUMENT	X12 SET	EDIFACT
PRODUCT/PRICING TRANSACTIONS
Price Sales Catalog	832	PRICAT
Price Authorization Acknowledgement/Status	845	ATHSTS
Specification/Technical Information	841	PRDSPE
Request For Quotation	840	REQOTE
ORDERING TRANSACTIONS
Purchase Order	850	ORDERS
Purchase Order Acknowledgement	855	ORDRSP
Purchase Order Change	860	ORDCHG
Purchase Order Change Acknowledgement	865	ORDRSP
MATERIALS MANAGEMENT TRANSACTIONS
Planning Schedule/Material Release	830	DELFOR
Shipping Schedule	862	DELJIT
Production Sequence	866	--
Ship Notice/manifest (ASN)	856	DESADV
SHIPPING/RECEIVING TRANSACTIONS
Shipment Information (Bill of Lading)	858	IFTMCS
Receiving Advice	861	RECADV
Non-conformance Information-Disposition Transaction, Cause/Correction	842	NONCON
INVENTORY MANAGEMENT TRANSACTIONS
Inventory Inquiry/Advice	846	INVRPT
Product Transfer and Resale Report	867	SLSRPT
FINANCIAL TRANSACTIONS
Invoice	810	INVOIC
Freight Invoice	859	IFTMCS
Payment order/Remittance Advice (EFT)	820	REMADV

There are many differences between an X12 and an EDIFACT document and I would recommend that if you do not have the capabilities to do EDIFACT in house that you outsource to a strong global EDI solution provider who can handle both data formats. At B2BGateway, we have offices located in North America, Europe and Pacific/Asia regions and can handle all internationally recognized EDI data formats including not only X12 and EDIFACT but many, many more (Tradacoms in the UK for example).

For further information on B2Bgateway’s international data standards capabilities please visit www.B2BGateway.Net or call (401) 491 9595. 

Roger Leyden is Director of Global Business Development at B2BGateway.

 

Most common EDI transaction sets used by Third Party Logistics providers (3PL’s).

 

Most common EDI transaction sets used by Third Party Logistics providers (3PL’s).
ANSI X12 Transaction	Transaction Name	Transaction Description
940	Warehouse Shipping Order	Data contents of the Warehouse Shipping Order Transaction Set (940) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable the depositor to advise a warehouse to make a shipment, confirm a shipment, or modify or cancel a previously transmitted shipping order.
943	Warehouse Stock Transfer Shipment Advice	Data contents of the Warehouse Stock Transfer Shipment Advice Transaction Set (943) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a depositor or an agent of the depositor to advise the recipient that a transfer shipment has been made. This transaction set provides a receiving location with detail information concerning product being shipped to that location.
944	Warehouse Stock Transfer Receipt Advice	Data contents of the Warehouse Stock Transfer Receipt Advice Transaction Set (944) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a receiving location to advise a depositor or an agent of the depositor that a transfer shipment has been received. This transaction set provides the depositor or the depositor's agent with detail information concerning product that has been received
945	Warehouse Shipping Advice	Data contents of the Warehouse Shipping Advice Transaction Set (945) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by the warehouse to advise the depositor that shipment was made. It is used to reconcile order quantities with shipment quantities.
946	Delivery Information Message	The transaction set can be used by a receiving location to advise a depositor or an agent of the depositor that a transfer shipment has been received. This transaction set provides the depositor or the depositor's agent with detail information concerning product that has been received. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you
947	Warehouse Inventory Adjustment Advice	Data contents of the Warehouse Inventory Adjustment Advice Transaction Set (947) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to inform a warehouse/depositor of a quantity or status change to inventory records. This transaction set provides detail information concerning the internal adjustments which occur between a warehouse and a depositor.
997	Functional Acknowledgement	Data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.
856	Advance Ship Notice/Manifest	Data contents of the Advance Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

 For a full list of all EDI X12 documents supported bt B2BGateway.Net please visit http://www.b2bgateway.net/edidocs.asp

Why outsourcing EDI may make sense for your organization.

Although EDI (Electronic Data Interchange) has been around since the late 1970’s, it started gaining increased traction in the early to mid 1990’s. The increased popularity in the 1990’s was mainly due to a heavy push from large organizations with large transactional volumes to reduce costs and increase efficiencies through automation.

Unfortunately, the very thought of EDI, can be daunting for an organization that has not used EDI before or has limited IT resources. The initial reaction is that EDI has been ‘forced’ on their organization by a large retailer or trading partner. Terms such as ANSI X12, UN/EDIFACT, Tradacoms, VAN, AS2, seem like Double Dutch and better still, the traditional English language has been replaced by numeric values, e.g. a Purchase Order is now called an 850, an Invoice becomes an 810, a Ship Notice becomes an 856, and so on. After a short period in production, the new EDI user will suddenly understand the benefits of EDI for their organization – reduced errors, shorter order to payment cash cycles, and reduced costs.

As mentioned above, there are many standards and communication protocols associated with EDI – in North America ANSI X12 is the predominant EDI standard, whereas in Europe and the Far East a far more popular standard is UN/EDIFACT. Some trading partners prefer to communicate through a VAN (Value Added Network), whereas others will prefer AS2 or FTP. Add to this mix a myriad of 318+ recognized EDI documents, customized mapping and reporting functions and it is clear to see why EDI becomes a daunting task for any organization.

It is at this stage that outsourcing your EDI requirements should make sense to your organization. Outsourced EDI solution providers come in various shapes and sizes. Some providers will require you to invest in your own mapping solution and they then develop the maps. Then there are others, like B2BGateway.Net, that provide the entire service and are also the first point of contact between your organization and your trading partners to resolve any EDI issues that may arise.

For further information on B2BGateway.Net’s fully outsourced EDI solutions please visit www.B2BGateway.Net or email Sales@B2BGateway.Net