Raw boundary: Raw mode preserves identified original segment rows, bypasses the 58-field Smart projection and 999 Smart Summary/validation, and is not de-identified. TA1, broader optional X231 structures, payer/partner companion rules, and lossless hierarchical export remain outside the current result schema.
Implementation acknowledgment editing guide
How to Edit an EDI 999 File
Edit the converted tabular representation without confusing an export change with a source-EDI repair.
To edit an EDI 999 file, convert a supported X231 or X231A1 acknowledgment with Smart Mapping, open the full Data Editor, locate the correct group, transaction, segment-error, or element-error occurrence, and change an unlocked converted field. Review the change, then export CSV, JSON, XLSX, or XML. The source acknowledgment remains unchanged.
Current converter contract
Smart routing requires ST01=999. A nonblank ST03 must be exactly 005010X231 or 005010X231A1; only blank ST03 may fall back to an exact supported GS08. Near matches and unsupported references are Raw-only.
Smart Mapping exposes one unified 58-field schema with no separate Key schema. It is a bounded, non-exhaustive X231/X231A1 projection with hybrid row grain: one row per IK4, an IK3-without-IK4 row, an AK2-without-IK3 row, or a group-summary row when no AK2 exists. Converter-generated ID is based on private physical occurrence identity and is not source-supplied.
IK401-3 is the repeating data-element position. CTX output preserves exact source text, case, physical order, and duplicates. Summary counts physical AK2, IK3, IK4, and every populated IK5/AK9 error-code position independently; AK9 counts are source-reported and are not reconciled to AK2 detail.
De-identification protects Smart rows, Summary, validation presentation, and CSV/JSON/XLSX/XML downloads. Raw mode preserves identified original segment rows and is not de-identified.
Select the correct acknowledgment occurrence
| Scope | Verify before editing | Why |
|---|---|---|
| Functional group | Original Functional Identifier, Original Group Control Number, AK9 result and counts | AK9 reports group scope, not a specific AK2 outcome. |
| Transaction set | Original Transaction Set ID, Original Transaction Control Number, IK5 result | Several error rows can belong to one physical AK2 transaction. |
| Segment error | IK3 segment ID, position, loop, error code, Segment Error Context | The same segment can recur. |
| Element error | IK401 element/component/repetition positions, IK402-IK404, Element Error Context | IK4 refines its owning IK3 occurrence. |
Preserve control numbers and other identifiers as text, including leading zeros. ID is converter-generated and stable for the physical row occurrence; it is not a source control number.
Synthetic mapped edit
IK3*NM1*18*2010BA*8~
CTX*CLM01:CLAIM001~
IK4*9:1:003*67*7*BADNPI~
IK5*R*5~In this fictional example, IK401 reports element 9, component 1, repetition 003; IK402 is 67; IK403 is error code 7; and IK404 is the bad value. An analyst may annotate an unlocked exported value, but that does not change the receiver’s reported IK5 result or repair the original transaction.
Edit in the application
- Open the EDI converter and Data Editor and add an authorized 999. Processing remains in the browser tab.
- Keep Smart Mapping selected and confirm exact X231/X231A1 routing.
- Convert and preview the original group, transaction, IK3, IK4, IK5, AK9, and CTX fields.
- Open the full editor and filter by group/transaction controls plus location fields.
- Edit an unlocked converted cell, then use Undo, Redo, Review changes, or Reset edits as needed.
- Download CSV, JSON, XLSX, or XML and compare the reviewed output with the source evidence.
Common editing mistakes
Editing a repeated detail row as if it were a separate transaction
Count AK2 transactions independently from IK3 and IK4 error occurrences and retain their owning controls.
Changing AK9-derived values without source provenance
Included, Received, and Accepted are source-reported AK9 values. Rejected is derived as Received minus Accepted, with impossible negative arithmetic preserved and flagged.
Dropping CTX or IK401-3
Exact CTX text and the repeating data-element position can distinguish repeated source locations.
Treating an export edit as source repair
Correct operational source data in the authoritative system and regenerate/transmit it through the applicable trading-partner workflow.
Frequently asked questions
Does editing rewrite the original 999?
No. It changes the converted representation used for review and download.
Which implementations route to Smart Mapping?
Exact 005010X231 and 005010X231A1 under the documented ST03/GS08 fallback rule.
Does an accepted 999 prove business acceptance?
No. It reports implementation acknowledgment status, not adjudication or payment.