The RFF segment carries a reference number. The qualifier identifies what the reference is. Common qualifiers: ON=order number, DQ=delivery note, BM=bill of lading, AAK=despatch advice, IV=invoice number, VA=VAT/ABN registration number, CT=contract number, VN=vendor's order number. RFF is used at header level (order references) and line level (line-specific references).
RFFHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
RFF+ON:PO-2026-12345'Buyer's order number: PO-2026-12345.
| 1.1 | Reference: Qualifier | ONBuyer's order number |
| 1.2 | Reference: Number | PO-2026-12345 |
{
"references": {
"buyersOrderNumber": "PO-2026-12345"
}
}Example shape. In production the field names and structure follow your own API contract.
Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.
| Position | Element | Parts |
|---|---|---|
| 1 | Reference | 1.1 Qualifier, 1.2 Number, 1.3 Line number |
| Code | Meaning |
|---|---|
ON | Buyer's order number |
VN | Supplier's order number |
DQ | Delivery note number |
AAK | Despatch advice number |
AAU | Despatch note number |
IV | Invoice number |
CT | Contract number |
PL | Price list number |
LI | Line item number |
VA | VAT / ABN registration |
ALO | Receiving advice number |
CR | Customer reference |
BM | Bill of lading number |
API | Additional party ID |
Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.
Have a real message with RFF in it? The explainer breaks down every segment and runs in your browser.
Explain my message