Bindinglaw

US · guidance

BOP Program Statement 8241.03 § 7

DEFINING ACCURACY OF ORDER ENTRY DATA. All data entered into

activein force · 2003-08-01 – presentact-effective-date

SAP must match that shown on the customer’s order before it will

be considered accurate. The CSC and the field locations will

review these items as part of order data accuracy sampling.

˜ Purchase order number

˜ Payment Method

˜ Partners: “sold to”, “ship to”, “bill to”, and “payee”

˜ Line item part numbers and descriptions

˜ Line item pricing

˜ Line item quantity

˜ Due date/Delivery date

˜ Customer point of contact (POC)

˜ Special shipping instructions

˜ Configuration line item

˜ Customer address

History

PS 8241.03 dated 2003-08-01

Provenance

Source
bop.gov
Retrieved
2026-09-20
Edition
bop-ps-2026-09-20
Content hash
b61e9a386f7be0d5b04d551acca58fec1a7746532c92fdcff7a77a69c2eb26e2
View the official source →

The link goes to the issuing authority’s own document — the one we read to produce this record. Where a source publishes whole titles rather than sections, your browser may need a moment to jump to the provision.

Unofficial copy of government-published law, reproduced from official sources with full provenance. Not an official publication; verify against official sources before relying on it in a filing. Records in the 'guidance' corpus, and only that corpus, are sub-regulatory (interpretive guidelines, survey procedures) and are not binding law. Validity bounds follow each jurisdiction's declared temporalBasis.

Coverage · API docs

Bindinglaw

Point-in-time US law with the receipt attached. Source URL, retrieval time, content hash, and validity dates on every answer.

curl api.binding.law/v1/law/coverage

© 2026 binding.law · a Jubal, Inc. productAttorneys and firms never pay. Ever.