You only receive this error when the Require suppliers to provide their tax ID on invoices transaction rule is enabled.

REF*BAA*[supplier ID]~

• Data Validation Error because the Sender ID [ID] is not yet setup on the network.
• Invalid Sender Qualifier/ID pair.

• The invoices reach your VAN, but do not reach the Ariba Network's VAN. A mismatch exists in the Industry Standard Architecture (ISA) identifier between your VAN and the your Ariba Network account.
• The ISA identifier in the GS02 segment includes "-T" at the end.
• The ISA identifier differs from the value configured in your account.

INV-15: This customer does not accept invoices for orders sent outside of Ariba Network.

When your customer sends a change PO, the original PO becomes obsolete. If you try to invoice the obsolete PO, the Ariba Network does not accept the invoice due to these errors.

If the TXI05 segment is not a Canadian location, PS, PG, or ST, the category is generated as:

• "sales": CS, CP, LT, ST
• "gst": CG, CV, GS
• "vat": VA
• "other": everything else

If the TXI05 segment is Canadian location, is either PS, PG or ST, the category is generated as:

• "qst": If TXI05 is '.qc.ca'
• "hst": If TXI05 is '.ns.ca', '.nf.ca' , '.nb.ca', or '.on.ca'
• "pst": for all other Canadian tax locations.

You must assign the jurisdiction code, which is captured by the <TaxLocation> element.

This means that there is no matching line item number on the purchase order.

• Change the IT108 segment from "VS" to "VP" if the value represents the vendor part number.
• Include the VP qualifier and its related part number in the IT1 segment if the value represents the vendor supplemental part number, which needs to be distinguished from the vendor part number.

automatic-action/MDN-sent-automatically; processed/Error: unexpected-processing-error

Your customer has disabled the Allow suppliers to send header credit memos and debit memos transaction rule.

For example, if the data in the field is 125, it is interpreted as 1.25.

The N3 segment maps to the <Street> attribute, while the N2 segment maps to the <DeliverTo> attribute of the <PostalAddress> element in the invoice cXML.

The REF02 segment designates the invoice line number (when REF01=FJ).

N404='US', mandating N402(State code), which is missing.

• The N404 segment referenced USA instead of US.
• The N402 segment was missing from the N4 segment.

Additionally, you must include a state code (N402 segment) when the N404 value equals US or CA.

See the ANSI X12 810 Implementation Guide for a list of state codes for US and CA.

x, y, and z represent cXML elements

When EDI service invoices are converted to cXML format, the line items are mapped to the InvoiceDetailServiceItem element.  In accordance with the cXML standard, there is no SerialNumber element within the InvoiceDetailServiceItemReference element (a sub-element of InvoiceDetailServiceItem).

For example, imagine an invoice has a total of $141.29. There are four line items with the following amounts:

• Line item 1: $303.70
• Line item 2: $52.43
• Line item 3: $58.90
• Line item 4: $29.96

The sum of the four items is $444.99, which does not match the total at the invoice header level of $141.29.

In this particular example, line item 1 needs to be removed. The sum of line items 2, 3, and 4 comes to $141.29, which would have matched the header-level total.

Keep in mind that this might not be the only reason for this invoice rejection message, but it is a common cause of the message.

No valid To credential was supplied.

• The Ariba Network ID (ANID) in the GS03 segment belongs to an expired customer account.
• The ANID you specified is missing a digit or has an extra number.

To verify your customer's ANID:

1. Click your company name in the upper right corner of the Home tab.
2. Select Customer Relationships under Account Settings.
3. Click your customer's name in the Current section.
4. Verify the ANID.

This ANID must match the value you provide in the GS03 segment of the EDI invoice. Make sure your customer's ANID has 13 or more characters. It begins with "AN" and is followed by 11 or more numbers.

x, y, and z represent cXML elements

N1*SO*Customer_Customer_Name~
N3*123 Any Avenue~
N4*Anytown*CA*12345*US~

Suppliers who send invoices using the EDI routing method receive an email notification containing the error message. The notification goes to the email address configured on the EDI Configuration page. Make sure to mark the check box next to the Send notification if outgoing documents are undeliverable or FAs are overdue setting.

1. Click your name in the upper right corner of the Home tab.
2. Select My Account.
3. Change the Default Currency value in the Preferences section.
4. Click Save.

Note that you can only use the REF*I5 segment with line-item credit memos. Each line-item credit memo must have an invoice reference, which forms the DocumentReference and InvoiceIDInfo elements in the InvoiceDetailRequestHeader of the invoice cXML.

When the BIG09 segment equals "NA," this corresponds to the isInformationOnly attribute of InvoiceDetailRequest.

Your EDI invoice has only one Terms of Sale/Deferred Terms of Sale (ITD) segment, but it is mapped to two identical InvoiceDetailPaymentTerms in the invoice cXML.

When the ITD01 segment equals "01," the ITD03 and ITD05 segments work together to indicate the discount terms and pay in days. ITD03 is the discount percentage, while ITD05 represents the number of days for payment.

If ITD03 equals "0" and ITD05 equals "30," this represents net 30 (no discount, payment in 30 days). ITD07 is for net payment days, so when ITD07 equals "30," this also represents net 30.

ITD*05*3*****30********0~

Setting ITD01 to "01" lets you send both a net payment term and a discount term at the same time. If you do not offer discount terms, using ITD01 equals "05" is recommended.  However, if you offer discount terms, you can use ITD01 equals "01" to provide the discount term as well as the net payment days.

1. Click your company name in the upper right corner of the Home tab.
2. Select Electronic Invoice Routing under Network Settings.
3. Choose the EDI routing method to accept either ANSI X12 810 or EDIFACT INVOIC documents from your invoicing system.
4. Click Save.

When you configure your invoice routing method as EDI, you can still create invoices manually and through cXML.

Note that this same error can occur for the ship-from address (N1*SF) as well.

There are two possible solutions:

• Remove the N1*ST segment from the line level (within the IT1 loop).
• Add segments N2 through N4 for the ship-to address provided at the line level.

When the EDI translator finds this character at the end of a segment or data element (before the segment separator or before the data element separator), it fails to process the document because the EDI translator uses this as a release character.

SAC*C*H850***0**********NO TAX~

Keep in mind that if either the PER03 or the PER04 segment is present, the other is required.

The PID segment generates the item description in the invoice cXML, and your customer requires item descriptions (the Require suppliers to provide line item descriptions transaction rule is enabled).

If no discount term exists, specify the 05 qualifier for the ITD01 segment.