# Can an Invoice Carry FSMA 204 Traceability Data? > Why the EDI 810 invoice cannot carry lot-level traceability the way an 856 can, what a PDF invoice is genuinely useful for under FSMA 204, and where the reference document KDE fits. An invoice can carry a reference document number and, in simple cases, a lot code. It cannot express mixed-lot lines, because invoice lines are flat and have no pack hierarchy. Under FSMA 204 the EDI 856 ASN is the traceability vehicle. Invoices matter most when they are the only document a supplier sends. A question that comes up constantly once distributors start FSMA 204 scoping: we already receive invoices from everybody, so can we just pull traceability data off the invoice? The answer is a qualified no, and the qualification is where the useful part lives. ## What FSMA 204 asks an invoice to do Among the Key Data Elements at the Receiving CTE is a reference document type and number. An invoice satisfies that cleanly. So does a PO or a bill of lading. That part is genuinely easy. The problem is everything else. The rule wants the Traceability Lot Code tied to a specific quantity of a specific product received on a specific date. An invoice is a financial document that happens to describe goods. The mismatch shows up fast. ## The structural problem: invoice lines are flat An [EDI 810 invoice](/guides/edi/810-invoice) line looks roughly like this: ``` IT1*1*40*CA*18.50**UP*012345678905*VN*ROM-24CT ``` One line: 40 cases of romaine at $18.50. There is nowhere in that structure to say that 24 of those cases were lot `ROM20280714-B2` and 16 were lot `ROM20280715-A1`. You can attach a single lot reference to the line with an `REF*LO` and many suppliers do. That is fine when the line is single-lot. It is actively misleading when it is not, because it asserts something false in a record you will rely on during a recall. Compare the [856 ASN](/guides/edi/856-ship-notice), which nests `HL` loops from shipment down to order down to pack down to item. That hierarchy is exactly what expresses which cartons held which lot. We walk the full mapping in [the Shipping CTE on an 856](/blog/fsma-204-edi-856-shipping-cte). This is not an EDI quirk. A paper invoice has the same limitation for the same reason. A line item is one row. ## Where the mismatch bites **Mixed-lot lines are normal in produce.** A pallet of romaine assembled from two harvest days is routine. Any traceability approach that assumes one lot per invoice line will be wrong on a meaningful fraction of receipts, and wrong in the direction of under-reporting during a recall. **Invoices arrive after the goods.** Often days after. Your Receiving CTE record is due based on when you received the food, not when accounting got the paperwork. Building receiving records off invoices puts a lag into a record that is supposed to be contemporaneous. **Invoice quantities are billed, not received.** Short shipments, damages, and substitutions mean the invoice and the receipt disagree. Financial reconciliation handles that discrepancy. A traceability record that inherits the billed quantity records food you never took in. **Catch weight makes it worse.** For variable-weight items the invoice carries weight for pricing while the receiving record needs the lot and the count. These do not reconcile without the pack detail. ## So when do invoices matter for traceability? When they are the only document you get. This is not an edge case. For a large share of small growers, co-packers, and specialty producers, the invoice or a packing list attached to it is the entire electronic record of the shipment. There is no ASN because there is no EDI. In that situation the invoice is not the ideal traceability vehicle, it is the only one, and the practical question becomes how to get its contents into a structured, sortable form without hand-keying. Two things help: 1. **Ask for the packing list, not just the invoice.** A packing list is a shipping document and is far more likely to carry lot detail per line, because it was generated by the warehouse rather than by accounting. Suppliers often already produce one and simply do not send it. 2. **Automate the conversion.** Whatever document you settle on, it needs to stop being a PDF the moment it arrives. ## Where OrderSync fits We handle the second point. OrderSync reads inbound invoices, packing lists, and order documents, whether they arrive as [PDF](/pdf-order-processing), [email](/email-order-processing), fax, CSV, or EDI, into structured line-level records with a full audit trail. Which fields get captured is configurable per trading partner, so if a given supplier prints a lot code in a corner of their packing list, it can be mapped like any other field. What we do not do is hold the traceability ledger or model Critical Tracking Events. That belongs in your food safety platform or ERP. We are the intake layer that stops your traceability data from arriving as a scan. More on that boundary in [capturing KDEs from non-EDI suppliers](/blog/fsma-204-kde-capture-non-edi-suppliers). ## Practical guidance - **Use the invoice for the reference document KDE.** It is good at that. - **Do not build your Receiving CTE record off the invoice.** Use the receipt. - **Ask for a packing list from non-EDI suppliers.** Better lot fidelity, closer to the actual shipment. - **Push EDI suppliers toward lot detail in the 856**, at the item level under the pack loop, not a single lot code stapled to the shipment. - **Treat single-lot assumptions as a known risk**, and know which of your categories routinely ship mixed. For the corrected compliance timeline, which is July 20, 2028 rather than the January 2026 date still circulating, see our [FSMA 204 compliance guide](/fsma-204). To see what lot references a supplier's actual EDI file contains, paste it into our [free EDI Inspector](/edi-inspector). ## Sources - [FDA: FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods](https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods) - [GS1 US: standards and guidance for food traceability](https://www.gs1us.org/industries-and-insights/standards) ## FAQ ### Does the EDI 810 have a lot number segment? You can carry a lot reference at the line level with `REF*LO`, and some trading partner specs define it. It works for single-lot lines. It cannot express multiple lots within one invoice line, which is the case that matters most for FTL produce. ### Is an invoice acceptable as the FSMA 204 reference document? Yes. The reference document type and number KDE is satisfied by an invoice, a purchase order, or a bill of lading. That is separate from whether the invoice can carry the lot and quantity KDEs, which is where it falls down. ### Our supplier only sends invoices. What should we ask for? Ask for a packing list per shipment with lot codes at the line level, sent at ship time rather than with the billing. Most warehouse systems already produce this document. Getting it emailed to a monitored address is usually a smaller ask than getting a supplier onto EDI.