Buc EDI 812 Credit/Debit Adjustment

Schema Reference

12 segments · X12 812 Credit/Debit Adjustment

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Interchange Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

ST03 Implementation Convention Reference

O AN 1-35

BCD01 Date

M DT 8-8

BCD02 Credit/Debit Adjustment Number

M AN 1-22

BCD03 Transaction Handling Code

M ID 1-2

BCD04 Amount

M N2 1-15

BCD05 Credit/Debit Flag Code

M ID 1-1

BCD06 Date

O DT 8-8

BCD07 Invoice Number

C AN 1-22

BCD09 Date

O DT 8-8

BCD10 Purchase Order Number

C AN 1-22

BCD13 Reference Identification Qualifier

C ID 2-3

BCD14 Reference Identification

C AN 1-50

SAC01 Allowance or Charge Indicator

M ID 1-1

SAC02 Service, Promotion, Allowance, or Charge Code

C ID 4-4

SAC05 Amount

O N2 1-15

N1 Loop Repeat: 200

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

C ID 2-2

N403 Postal Code

O ID 3-15

CDD Loop Repeat: 25

CDD01 Adjustment Reason Code

M ID 2-2

CDD02 Credit/Debit Flag Code

M ID 1-1

CDD04 Amount

C N2 1-15

CDD07 Credit/Debit Quantity

C R 1-10

CDD08 Unit or Basis for Measurement Code

C ID 2-2

CDD09 Unit Price Difference

O R 1-15

CDD10 Price Identifier Code

C ID 3-3

CDD11 Unit Price

C R 1-17

LIN01 Assigned Identification

O AN 1-20

LIN02 Product/Service ID Qualifier

M ID 2-2

LIN03 Product/Service ID

M AN 1-48

LIN04 Product/Service ID Qualifier

C ID 2-2

LIN05 Product/Service ID

C AN 1-48

LIN06 Product/Service ID Qualifier

C ID 2-2

LIN07 Product/Service ID

C AN 1-48

SAC Loop Repeat: 25

SAC01 Allowance or Charge Indicator

M ID 1-1

SAC02 Service, Promotion, Allowance, or Charge Code

C ID 4-4

SAC05 Amount

O N2 1-15

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Buc EDI 812

Stacksync validates, transforms, and delivers your 812 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync processes Buc EDI 812 (Credit/Debit Adjustment) documents automatically — syncing data to your system in real time with no manual intervention required.

Buc EDI 812 FAQ

Common questions about 812 Credit/Debit Adjustment transactions with Buc.

How long does it take to set up Buc EDI with Stacksync?

Most suppliers are fully connected and processing live Buc EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Buc?

No. Stacksync handles the entire EDI transport layer. We connect directly to Buc's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Buc compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Buc?

Stacksync supports all EDI document types required by Buc — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Buc EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Buc's EDI network and your system in real time.

What happens when Buc updates their EDI specifications?

Stacksync monitors Buc's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.

Buc X12 812 Credit/Debit Adjustment

Schema Reference

Automating Buc EDI 812

Buc EDI 812 FAQ

Alex Marinov

Schema Reference

Automating Buc EDI 812

Other Buc EDI transactions

Buc EDI 812 FAQ

Alex Marinov