JC Penney (CommerceHub)
/
Credit/Debit Adjustment
  • Specification
  • EDI Inspector
Import guide into your account
JC Penney (CommerceHub) logo

X12 812 Credit/Debit Adjustment

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Credit/Debit Adjustment Transaction Set (812) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to notify a trading partner of an adjustment or billback and may be used to request an adjustment or billback. It identifies and contains the details and amounts covering exceptions, adjustments, credits, or debits for goods or services. This transaction set is multi-directional between trading partners.

The JCPenney EDI 812 guide outlines the specific business rules and functional requirements that apply to JCPenney.
During the supplier on boarding process with CommerceHub you may contact the Partner Setup team by sending an email to partnersetup@commercehub.com. Please include the following information in your email:

  • Your company name
  • Your contact information
  • The fact that you are working with JCPenney - A detailed description of the issue
    Once your account is live and in the production environment you will need to work with the CommerceHub Customer Support team on all production related issues. You can contact Customer Support at: 518.810.0700 Option 2 or customersupport@commercehub.com.
    MESSAGE PURPOSE AND BUSINESS RULES:
    The Credit/Debit Adjustment message carries information regarding credits or debits associated with an Invoice. The Invoice Adjustment will be used to support adjustments for returned items, damaged items, and/or adjustments to product cost.
    DATA ELEMENT REQUIREMENTS AND USAGE:
    The following User Attributes are employed in this document:
    M - Mandatory by the X12 standard.
    M/U - Must be used to meet the SNBC requirements D - Dependent
    R - Recommended
    Any element not marked with one of the above indicators indicates that JCPenney has the ability to
Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/jc-penney-commerce-hub/creditdebit-adjustment/01GQQ88PN3EYF7NT0XYGPA1N29
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BCD
020
Beginning Credit/Debit Adjustment
Max use 1
Required
N9
040
Reference Identification
Max use 1
Optional
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required

Code identifying a group of application related transaction sets

CD
Credit/Debit Adjustment (812)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
812
Credit/Debit Adjustment
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BCD
020
Heading > BCD

Beginning Credit/Debit Adjustment

RequiredMax use 1

To transmit identifying dates and numbers for the transaction set and indicate the monetary value to the receiver of the transaction

  • BCD05 indicates whether the net of the detail is a credit or a debit.
Example
BCD-01
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCD01 is the credit/debit adjustment date.
Usage notes
  • Issue date for this adjustment
    This element contains the date of this transaction.
BCD-02
475
Credit/Debit Adjustment Number
Required
String (AN)
Min 1Max 22

Number assigned by issuer of a credit or debit memo

BCD-03
305
Transaction Handling Code
Required

Code designating the action to be taken by all parties

A
Off Invoice (Deduction from Original Invoice)
J
Payment Requested (Adjustment to Account)
L
Apply on Account
O
Deduct from Next Remittance
BCD-04
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • BCD04 is the net amount of this complete transaction.
Usage notes
  • Net amount of the adjustment
    This element contains the net amount of the adjustments being made.
BCD-05
478
Credit/Debit Flag Code
Required

Code indicating whether amount is a credit or debit

C
Credit
D
Debit
BCD-06
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCD06 is the invoice date.
Usage notes

Invoice date

BCD-07
76
Invoice Number
Optional
String (AN)
Min 1Max 22

Identifying number assigned by issuer

  • If using BCD07 or BCD10, do not use BCD14 to identify invoice number or purchase order number.
Usage notes
  • Invoice to which this adjustment pertains
BCD-09
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCD09 is the purchase order date.
Usage notes
  • Purchase Order date
BCD-10
324
Purchase Order Number
Optional
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

This element contains the JCPenney purchase order number.

BCD-13
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

1X
Credit or Debit Adjustment Number
RZ
Returned Goods Authorization Number
BCD-14
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9
040
Heading > N9

Reference Identification

OptionalMax use >1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

DP
Department Number
IA
Internal Vendor Number
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N1 Loop
RequiredMax >1
N1
100
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

PO
Party to Receive Invoice for Goods or Services
N1-03
66
Identification Code Qualifier
Optional

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N1 Loop end
Heading end

Detail

CDD Loop
RequiredMax >1
CDD
160
Detail > CDD Loop > CDD

Credit/Debit Adjustment Detail

RequiredMax use 1

To provide information relative to a line item adjustment

Example
At least one of Amount (CDD-04) or Credit/Debit Quantity (CDD-07) is required
If either Credit/Debit Quantity (CDD-07) or Unit or Basis for Measurement Code (CDD-08) is present, then the other is required
If Credit/Debit Quantity (CDD-07) is present, then Unit Price (CDD-11) is required
If either Price Identifier Code (CDD-10) or Unit Price (CDD-11) is present, then the other is required
If either Price Identifier Code (CDD-12) or Unit Price (CDD-13) is present, then the other is required
CDD-01
426
Adjustment Reason Code
Required

Code indicating reason for debit or credit memo or adjustment to invoice, debit or credit memo, or payment

01
Pricing Error
02
Allowance/Charge Error
04
Item Not Accepted - Damaged
06
Quantity Contested
07
Incorrect Product
10
Pallet/Container Charge Error
12
Returns - Quality
15
Returns - Recall
16
Non-Invoice Related Allowance/Charge
19
Duplicate Billing
24
Incorrect Discount
26
Invoice Cancelled
49
Processing Charge
52
Credit for Previous Overpayment
54
Freight Deducted
55
Tax Deducted
59
Item not received
70
Advanced Ship Notice Not Received
72
Authorized Return
93
Field Destroy
97
Handling Charge
L2
Discount
SF
Shipping and Freight Charge
CDD-02
478
Credit/Debit Flag Code
Required
Identifier (ID)
Min 1Max 1

Code indicating whether amount is a credit or debit

CDD-04
610
Amount
Optional
Numeric (N2)
Min 1Max 15

Monetary amount

Usage notes
  • Extended adjustment amount
    This element contains the net amount of the adjustments being made for a particular line.
CDD-07
477
Credit/Debit Quantity
Optional
Decimal number (R)
Min 1Max 10

Number of supplier units credited or debited

Usage notes

This element contains the number of supplier units debited or credited.

CDD-08
355
Unit or Basis for Measurement Code
Optional

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
CDD-09
427
Unit Price Difference
Optional
Decimal number (R)
Min 1Max 15

Per unit (case) price or allowance/charge difference between original billing and corrected amount (may be unit full list price or allowance/charge where item was not on original billing or where full credit/debit amount is being transacted, i.e., returns or contested quantities)

CDD-10
236
Price Identifier Code
Optional

Code identifying pricing specification

UCP
Unit cost price
CDD-11
212
Unit Price
Optional
Decimal number (R)
Min 1Max 17

Price per unit of product, service, commodity, etc.

CDD-12
236
Price Identifier Code
Optional

Code identifying pricing specification

  • If comparison pricing is used, then CDD12 and CDD13 are required.
OPP
Original Purchase Order Price
CDD-13
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

This element contains the unit cost of the item on the purchase order.

LIN
170
Detail > CDD Loop > LIN

Item Identification

OptionalMax use 1

To specify basic item identification data

Example
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

This element contains the line number from the JCPenney purchase order.

LIN-02
235
Product/Service ID Qualifier
Required

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
SK
Stock Keeping Unit (SKU)
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

This element contains the JCPenney SKU for the product.

CDD Loop end
SE
270
Detail > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Detail end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.