EDI 830 Planning Schedule: Turning Forecast Releases Into Shipments

The customer's plant calls on a Thursday afternoon: line 3 will stop on Monday unless 1,200 brackets arrive by Saturday. Your planner checks the last 830 and sees the quantity, but it sat in a forecast bucket, not a firm one, so nothing was built. Your shipping clerk swears 480 pieces left last week, while the customer's receiving count says they never arrived. By Friday you are paying for an expedited truck to cover a gap that existed only in two different cumulative totals.

The X12 830 Planning Schedule with Release Capability carries all the information needed to prevent that call: which quantities are firm, how far the buyer will pay for material and finished parts, and what the buyer believes it has already received. When each of those fields drives a specific action in production planning, the warehouse and the transport desk, schedule changes turn into routine shipments instead of premium freight.

• What this guide covers: the BFR header, FST forecast lines, ATH authorisations and SHP cumulative quantities, and how each one turns into a pick, a truck booking and an advance ship notice.
• What it adds: an annotated sample 830, a cumulative reconciliation formula, a worked US ($) and Indian (₹) release with GST invoice and e-way bill consequences, and an onboarding checklist for new trading partners.

What an 830 tells a supplier and what it deliberately leaves open

An 830 is a rolling statement of the buyer's expected requirements, split into near-term quantities the supplier may ship and longer-range quantities it should only plan for. It is not, by itself, a purchase order for every quantity listed. The firm portion, the authorisations and the trading partner agreement together decide what the buyer is committed to.

• Header area: the BFR segment with the schedule's dates and basis, plus parties in N1 loops and optional carrier details.
• Detail area: one LIN loop per part, listing its forecast buckets in FST segments, resource authorisations in ATH segments and the buyer's view of past shipments or receipts in SHP segments.
• Summary area: a CTT segment with transaction totals, then the SE trailer.

The companion transaction is the 862 Shipping Schedule. The 862 is meant to supplement the 830, not replace it, by sending more precise and frequent shipping requirements for just-in-time supply, and it can override certain shipping and delivery details from an earlier 830. Many buyers send an 830 weekly and an 862 daily; your translator has to know which one wins for a given date.

Reading the BFR header: schedule basis, horizon and release number

Read the BFR before any quantity, because it changes how every FST line must be interpreted. Two codes matter most: the schedule type in BFR04, which says whether dates are delivery or shipment dates, and the quantity qualifier in BFR05, which says whether quantities are discrete or cumulative.

• BFR01 purpose code: 00 for an original and 05 for a replacement are common. A replacement should supersede the whole previous schedule for the items it contains, not be added to it.
• BFR03 release number: the buyer's identifier for this version. Store it on every schedule line so a later shipment can be traced to the release that authorised it.
• BFR04 schedule type: DL means delivery based and SH means shipment based; planned variants such as PD and PS also exist. A delivery-based date must be moved back by the transit time before it becomes a ship date.
• BFR05 quantity qualifier: A for actual discrete quantities, C for cumulative quantities, D for net change and R for replacement quantities. Mixing these up is the fastest way to double a requirement.
• BFR06 to BFR08 dates: horizon start, horizon end and the date the forecast was generated. Reject a schedule whose generated date is older than the one already loaded.

Our article on warehouse wave release cutoffs deals with releasing work inside the warehouse against packing and carrier limits. The word "release" in an 830 is different: it is the buyer's permission to ship a quantity, which the warehouse later turns into its own picking release.

FST lines: firm, planning and immediate quantities by date

Each FST segment pairs a quantity with two qualifiers: what kind of commitment it is and what kind of time bucket it covers. Firm quantities are shipping instructions; planning quantities are inputs to capacity and material planning. Everything downstream depends on keeping the two apart.

FST02, the forecast qualifier, uses C for firm, D for planning and A for immediate, the last usually meaning past due or needed at once. Other values exist, such as Q for order release authorisation or W for cancellation, and a trading partner agreement should list which ones the buyer actually sends. FST03, the timing qualifier, uses D for a discrete date, W for a Monday-to-Sunday week, M for a calendar month and F for a flexible interval with start and end dates in FST04 and FST05.

ST*830*0457~
BFR*05**REL-26-0457*DL*A*20261109*20270430*20261108~
N1*ST*PLANT 3 RECEIVING*92*P3~
LIN**BP*84-2291-A*PO*4500127781~
UIT*EA~
ATH*FI*20261207*34560**20260101~       finished goods authorised to cum 34,560 through 7 Dec
ATH*MT*20270104*38400**20260101~       material authorised to cum 38,400 through 4 Jan
SHP*01*480*050*20261106~               last receipt: 480 pieces received 6 Nov
SHP*02*31680*051*20260101**20261106~   cum received 31,680 from 1 Jan to 6 Nov
FST*1200*A*D*20261111~                 immediate: behind schedule
FST*600*C*D*20261113~                  firm, delivery on 13 Nov
FST*1200*C*W*20261116~                 firm, week of 16 Nov
FST*2400*D*W*20261123~                 planning, week of 23 Nov
FST*9600*D*M*20270101~                 planning, January bucket
CTT*1~
SE*15*0457~

Cumulative check (all quantities in pieces):
  gap = CumShipped_supplier - CumReceived_buyer - InTransit
      = 32,160 - 31,680 - 0 = 480   -> must be explained before the next ship date
  InTransit counts only shipments dated after the last SHP receipt date (050)
Ship date for a delivery-based (DL) line:
  ShipDate = DeliveryDate - TransitDays - DockBufferDays

The annotations after each segment are ours, not part of the X12 syntax; a translator would reject them. They show how a planner should read the sample: one immediate bucket says the buyer thinks it is already short, two firm buckets are ship instructions, and the planning buckets are only for capacity. The cumulative check at the bottom already shows a 480-piece gap that has to be explained.

ATH authorisations: how much material and labour the buyer will pay for

ATH segments tell the supplier how far it may commit resources at the buyer's financial risk. They are the field that decides who pays when a planning quantity is cut. The X12 note for ATH01 says the negotiations defining that commitment must already have happened, so the segment reports an agreed liability rather than creating one.

• ATH01 resource code: FI covers finished goods, meaning labour, material and overhead; MT covers material only; LB is labour and LM is labour and material. PQ reports the cumulative quantity required before the first schedule period, and PR covers previously released requirements.
• ATH02 through date: the date up to which the buyer authorises the supplier to commit that resource.
• ATH03 cumulative quantity: the quantity authorised from the cumulative start date in ATH05 through the ATH02 date.
• ATH04 high-water mark: the maximum cumulative requirement; if the forecast falls, ATH03 can fall with it, but ATH04 does not decrease.

In the sample, the buyer authorises finished parts to a cumulative 34,560 through 7 December and material to 38,400 through 4 January. If the supplier has shipped 32,160 pieces since 1 January, it may build 2,400 more finished parts and buy material for 6,240 more at the buyer's risk, subject to the contract. Anything beyond those numbers is the supplier's own bet.

X12 830 planning schedule liability is read from the ATH segment: ATH03 gives the authorised cumulative quantity from the ATH05 start date through ATH02, and ATH04 records a high-water mark that never decreases, so a supplier holding 2,400 finished parts above cumulative shipments can claim them only within those authorised limits.

Store every ATH value by release number in a liability ledger. When a buyer cuts volume or ends a programme, that ledger, not the latest 830, is the evidence of what was authorised and when. Many disputes over obsolete stock come down to whether the supplier kept the old authorisations or only the newest schedule.

Cumulative quantities and the SHP segment: closing the gap with the buyer

A cumulative schedule only works when both sides agree on the cumulative start date and on what has been shipped and received since then. The SHP segments state the buyer's view; the supplier's ERP holds its own. Reconcile the two on every 830, before planning any new shipment.

SHP01 uses 01 for a discrete quantity and 02 for a cumulative quantity; codes 07 to 10 cover cumulative quantities of rejected material by disposition. SHP03 qualifies the date: 011 for shipped, 050 for received, 051 for the cumulative quantity start and 052 for its end. A cumulative SHP must carry both the start date in SHP04 and the end date in SHP06.

• In-transit adjustment: subtract shipments that left after the buyer's last receipt date; they are real but not yet counted by the buyer.
• Rejected material: if the buyer returned or scrapped parts, compare its rejected cumulative quantities with your return authorisations and credit notes.
• Cumulative reset: agree in writing when cumulatives restart, such as the start of a calendar year or model year, and check that SHP04 matches your start date.
• Unexplained remainder: anything left after these adjustments is an exception with a named owner and a deadline, not a number to carry forward silently.

Cumulative reconciliation for an X12 830 compares supplier shipments with the buyer's SHP02 quantity between the SHP03 code 051 start date and the SHP06 end date, after removing in-transit shipments; any remainder above a tolerance such as 0.5% of the weekly firm quantity should block automatic shipment planning.

Turning a firm bucket into a pick, a truck booking and an 856

A firm FST line becomes a shipment only after three conversions: from delivery date to ship date, from quantity to packs and pallets, and from pallets to a booked truck. Each conversion has its own lead time, and the shortest firm horizon a buyer offers must exceed their total.

1. Date conversion: for a delivery-based schedule, subtract the lane's transit days and the buyer's dock buffer from each firm date. For a shipment-based schedule, the FST date is already the ship date.
2. Pack rounding: round quantities to the standard pack, and decide in advance whether rounding goes up and is netted against the next bucket or is held back.
3. Warehouse release: create the delivery or outbound order in the WMS on the ship date minus picking lead time, carrying the 830 release number as a reference.
4. Carrier booking: book the truck with enough notice for the carrier's cut-off, using TD5 routing from the 830 where the buyer controls freight.
5. Ship notice: send the 856 with the quantities actually loaded, so the buyer's receiving and cumulative totals start from the same numbers as yours.

Our guide to EDI 856, 940, 945 and 214 integration covers the ship notice and warehouse messages in detail, and the article on dock appointment scheduling covers the receiving side where the buyer books slots for inbound trucks.

A cumulative mismatch traced from release to premium freight

Cumulative disputes rarely start with a wrong number. They start with a correct shipment recorded on one side only, which then quietly turns a firm quantity into a shortage. The trace below is an illustrative composite of how a 480-piece gap became an expedited truck.

1. Thu 6 Nov, 16:40, shipment: the supplier ships 480 pieces of 84-2291-A on bill of lading BL-226118 and sends 856 number 90331. The buyer's translator rejects the 856 because the packing slip number is longer than the agreed 22 characters.
2. Sat 8 Nov, 05:10, new 830: release REL-26-0457 arrives. SHP shows cumulative received of 31,680, including the 6 Nov load. The supplier's ERP still lists that load as in transit because its 856 was rejected, so cumulative shipped of 32,160 less 480 in transit appears to match exactly.
3. Mon 10 Nov, 09:00, planning: the planner sees no cumulative gap and plans only the firm 600 for 13 Nov. The immediate bucket of 1,200 is treated as noise.
4. Thu 13 Nov, 14:20, line-stop warning: the buyer's material controller calls. A 480-piece receipt from 31 Oct had been posted against a different purchase order, so the buyer's cumulative is genuinely short and the immediate bucket was real.
5. Fri 14 Nov, 07:30, recovery: an expedited truck leaves with 1,200 pieces. Both sides agree a weekly cumulative call, and the supplier changes its rule so a load counts as in transit only if dated after the buyer's last receipt in SHP.

The fix in the trace is procedural as much as technical. A rejected 856 should raise an alert to the supplier's EDI analyst within the hour, and an immediate FST bucket should always trigger a check of the cumulative before a planner dismisses it.

GST invoices and e-way bills for releases under an Indian scheduling agreement

In India, many component buyers issue long-running scheduling agreements and send delivery schedules against them, through EDI or other channels. Whatever the channel, each physical dispatch against a release is a separate supply for GST, so it needs its own tax invoice and, above the threshold, its own e-way bill.

• Tax invoice timing: section 31(1) of the CGST Act requires a registered supplier of taxable goods to issue a tax invoice before or at the time of removal of goods where the supply involves movement.
• E-way bill threshold: Rule 138(1) of the CGST Rules requires an e-way bill before movement where the consignment value exceeds ₹50,000.
• E-invoice reporting: suppliers above the ₹5 crore aggregate turnover threshold set by Notification 10/2023-Central Tax must report the invoice and obtain an IRN.

US practice has no equivalent federal document per shipment. A US supplier's per-release documents are commercial: the bill of lading, the 856 and the invoice or 810 as the trading partner requires. The worked example uses illustrative prices and an assumed 18% GST rate to show the cost of each field going wrong in both markets.

Scheduled releases from Indian auto suppliers each need a tax invoice before removal under section 31(1) of the CGST Act, and an e-way bill under Rule 138(1) once consignment value exceeds ₹50,000; one 1,200-piece weekly firm bucket at ₹420 per piece reaches ₹5,94,720 with assumed 18% GST.

The rupee column also shows a practical rule: never raise the tax invoice from the 830 quantity. Raise it from the quantity actually loaded and confirmed in the WMS, because a pack-rounding or short-pick difference between the release and the truck would otherwise put a wrong quantity on a government-reported document.

Translator validations versus planner judgement on each new schedule

The EDI translator and ERP should reject malformed or out-of-sequence schedules automatically, and flag cumulative gaps and authorisation changes for a person. Deciding whether to build ahead, expedite or challenge a buyer's cumulative stays with the planner and the commercial team.

Onboarding a new 830 trading partner without a cumulative dispute

Most 830 problems are settled, or created, during onboarding. Agree the codes, the cumulative rules and the liability terms in writing before the first production schedule arrives, then test them with real part numbers in a parallel run.

For related supplier delivery topics, see our guide to milk-run supplier time windows and the wider logistics and supply chain hub. If you are mapping a new OEM's schedules into your ERP and WMS, or need a cumulative reconciliation built, you can send us the scope and we will reply with a plan.