# EDI 997 Functional Acknowledgment Reject Log Worksheet

> Source: https://netray.co/tools/edi-997-functional-acknowledgment-reject-log-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Log every rejected or partially accepted 997 with the AK3/AK4 error, root cause, owner and resend status, and export it to Excel.

## Category

supply-chain

## Audience

- EDI coordinator
- B2B integration analyst
- EDI support

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Date received

**Key:** date

**Type:** date

#### Trading partner

**Key:** partner

**Type:** text

#### Transaction set

**Key:** txn

**Type:** select

**Options:**

- 850
- 855
- 856
- 810
- 940
- 945
- 860
- 846
- Other

#### Group control no.

**Key:** ctrl

**Type:** text

#### AK5 status

**Key:** ak5

**Type:** select

**Options:**

- A - Accepted
- E - Accepted with errors
- R - Rejected

#### AK3 segment / AK4 element

**Key:** seg

**Type:** text

#### Error code

**Key:** errcode

**Type:** select

**Options:**

- 1 Mandatory element missing
- 2 Conditional element missing
- 3 Too many elements
- 4 Element too short
- 5 Element too long
- 6 Invalid character
- 7 Invalid code value
- 8 Invalid date
- 9 Invalid time

#### Root cause

**Key:** cause

**Type:** select

**Options:**

- Map defect
- Master data gap
- Partner spec change
- ERP data issue
- Envelope / control number
- Unknown

#### Owner

**Key:** owner

**Type:** text

#### Docs affected

**Key:** docs

**Type:** number

#### Minutes to resolve

**Key:** mins

**Type:** number

#### Resent

**Key:** resent

**Type:** select

**Options:**

- Yes
- No
- Pending

**Rows:**

#### Map defect

**Date:** 2026-10-12

**Partner:** Northwind Retail

**Txn:** 856

**Ctrl:** 000004417

**Ak5:** R - Rejected

**Seg:** HL / HL03

**Errcode:** 7 Invalid code value

**Owner:** R. Mehta

**Docs:** 14

**Mins:** 95

**Resent:** Yes

#### ERP data issue

**Date:** 2026-10-13

**Partner:** Contoso Aerospace

**Txn:** 810

**Ctrl:** 000002281

**Ak5:** E - Accepted with errors

**Seg:** IT1 / IT107

**Errcode:** 6 Invalid character

**Owner:** S. Ortiz

**Docs:** 3

**Mins:** 40

**Resent:** No

#### Envelope / control number

**Date:** 2026-10-14

**Partner:** Fabrikam Auto

**Txn:** 855

**Ctrl:** 000009036

**Ak5:** R - Rejected

**Seg:** ISA / ISA06

**Errcode:** 1 Mandatory element missing

**Owner:** R. Mehta

**Docs:** 1

**Mins:** 25

**Resent:** Yes

#### Master data gap

**Date:** 2026-10-15

**Partner:** Northwind Retail

**Txn:** 810

**Ctrl:** 000004452

**Ak5:** R - Rejected

**Seg:** DTM / DTM02

**Errcode:** 8 Invalid date

**Owner:** A. Khan

**Docs:** 22

**Mins:** 120

**Resent:** Pending

**Totals:**

#### Total documents affected

**Key:** docs

**Agg:** sum

**Format:** integer

#### Total minutes spent

**Key:** mins

**Agg:** sum

**Format:** integer

#### Reject entries

**Key:** partner

**Agg:** count

**Format:** integer

**Summary:**

#### Average minutes per entry

**Key:** avg_mins

**Expr:** sum_mins / count

**Format:** decimal

#### Minutes per affected document

**Key:** mins_per_doc

**Expr:** sum_mins / sum_docs

**Format:** decimal

**Notes:** A 997 only confirms syntax and envelope acceptance, not business acceptance. Keep a separate record of application-level rejections (for example an 855 that declines a line).

## Content

**Intro:** A 997 Functional Acknowledgment tells you whether a trading partner could parse what you sent. When it comes back rejected, someone has to read the AK3 and AK4 segments, find the cause and resend. This worksheet gives the EDI desk one place to log each reject so patterns become visible.

**Sections:**

#### How to use the log

**Body:** Add one row per rejected or partially accepted acknowledgment. Pick the AK5 status, then record the AK3 segment position and the AK4 element position the partner cited, along with the element error code. Choose the root cause category honestly, because that column is what you will filter on at the monthly review. Record the number of documents in the rejected group and the minutes spent. Mark the resend status so open items are easy to find. Export to Excel to share with the partner or your integration vendor.

**Bullets:**

- AK5 A means accepted, E accepted with errors, R rejected
- AK3 names the segment in error, AK4 names the element
- Always note the group control number so you can trace it in your VAN or AS2 log

#### Reading the AK4 error codes

**Body:** The AK4 element syntax error codes in the X12 standard are short numeric values. A code 1 means a mandatory element is missing, 2 a conditional element is missing, 3 too many elements, 4 and 5 too short or too long, 6 an invalid character, 7 an invalid code value, 8 an invalid date and 9 an invalid time. Code 7 is the most common in practice, usually a qualifier or unit of measure the partner does not accept. Code 1 often points to an ERP field that is empty for one customer or part.

#### Finding patterns

**Body:** After a month, sort by root cause and by partner. Many map defects against one partner usually mean a spec change you were not told about. Many master data gaps point at the item or ship-to setup in your ERP, for example a missing GTIN or an unpopulated buyer part number on SAP customer-material info records or Infor customer item records. Envelope and control number issues usually trace to the translator or VAN configuration, not the map.

#### Common mistakes

**Body:** Do not treat an accepted 997 as proof the partner processed the order. Do not resend before the root cause is fixed, since repeated rejects can trigger partner penalties or disable your connection. Do not overwrite the original control numbers when resending unless the partner guide requires a new interchange. Keep the evidence of the original transmission for disputes.

**Cta:** If rejects keep coming from the same master data gaps, Netray can help build a read-only check that flags missing partner fields in your ERP before a document is sent.

**Faq:**

#### What does a rejected 997 mean?

**Answer:** An AK5 status of R means the receiver could not accept the functional group because of syntax or envelope errors. The business content was not processed. You need to correct the data or map and resend, following the partner's guide on whether to use new control numbers.

#### Is an accepted 997 the same as the order being accepted?

**Answer:** No. A 997 with AK5 A only says the file was readable and correctly structured. Business acceptance of an order comes through an 855 purchase order acknowledgment or the partner's own order status messages.

#### How long should I keep 997 records?

**Answer:** Keep them at least as long as your contract and audit requirements demand, often several years for trade documents. Many companies match their retention to financial records. Check your customer agreements and local tax rules.

#### Do I need a 999 instead of a 997?

**Answer:** The 999 Implementation Acknowledgment is the newer acknowledgment used with later X12 versions and is required by some partners and healthcare rules. Many supply chain partners still use the 997. Follow each partner's specification.

## Search terms

edi 997 reject log, 997 acknowledgment error tracking, edi rejected 997 spreadsheet, x12 ak3 ak4 error codes, edi error log template excel, edi 997 rejected what to do, edi exception tracking worksheet

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json