Federal orders arrive as PDFs, and the line-item grid on a DD Form 1155 or an SF 1449 is not a flat table. Upload the award and get the CLINs and SLINs, unit prices, quantities, delivery dates, DPAS rating, and ship-to codes back as Excel, CSV, JSON, or an API response in about ten seconds, with the line structure intact.
Submit your purchase orders
Drop documents here, or click to file
Up to 50 files per batch
Uploading...
A commercial purchase order has a simple item table: part, quantity, unit price, total. A federal order does not. The line-item numbering on a DoD award carries meaning, the pricing does not sit where a naive extractor expects it, and an accept-or-reject clock may already be running when the PDF lands in your inbox.
Under DFARS 204.71, a contract line item number is four digits, 0001 through 9999. Below it sit subline items, and there are two different kinds. Informational SLINs are numeric, such as 000101, and DFARS states they shall not be scheduled separately for delivery or priced separately. Separately identified SLINs are alpha, such as 0001AA and 0001AB, never using the letters I or O, and each can carry its own price, delivery date, destination, and accounting citation. Flatten all of that into one table and you produce totals that double-count, delivery schedules that are wrong, and fund citations attached to the wrong line.
On the SF 1449 the item grid is blocks 19 through 24: item number, schedule of supplies or services, quantity, unit, unit price, and amount. The form itself says to use the reverse and attach additional sheets as necessary, so on any order of real size the items continue on pages the first-page parser never reads.
If block 13a of the SF 1449 or block 5 of the DD 1155 carries a DPAS priority rating, 15 CFR 700.13 requires you to accept or reject that order in writing or electronically within 15 working days for a DO rating and within 10 working days for a DX rating. A PDF sitting unread in a shared mailbox is a compliance problem, not just a backlog.
This is not a legacy edge case. DLA policy at DLAD 4.502, procurement note L01, gives a contractor the choice of receiving award notices as an email containing a link to an electronic copy of the DD Form 1155 on DIBBS, or as an EDI 850 through an approved network. EDI is opt-in. The PDF route is official, current, and extremely common.
Upload the DD 1155, SF 1449, OF 347, or a prime contractor's subcontract PO. The AI reads the document rather than matching a template, so it handles the block layout of a federal form, the continuation sheets, and the sublines beneath each CLIN, and returns it as data you can load into your accounting system or your contract file.
The item number comes back as it is printed, so 0001, 0001AA, and 000101 stay distinguishable and you can see which sublines carry a price and which are informational. You review the output on screen before you export it.
Continuation sheets are read along with the face of the form, which matters on any award where the schedule of supplies runs past block 24.
The priority rating, the required delivery date, the ship-to code, and the contract and order numbers are captured as their own fields, so you can sort a stack of awards by what is closest to its acceptance deadline.
The same structure every time, whichever contracting office sent it, so the export drops into the spreadsheet or system you already use without reshaping.
The SF 1449, Solicitation, Contract, or Order for Commercial Products and Commercial Services, is the combined form used for commercial items and under simplified acquisition procedures, which means the same document you quoted against comes back to you as the award. The blocks worth knowing are 2 and 4, the contract and order numbers; 13a and 13b, the DPAS rated-order box and the rating itself; 15, deliver to; 19 through 24, the item grid; and 25, the accounting and appropriation data.
The DD Form 1155, Order for Supplies or Services, is what DoD issues in place of the OF 347, and its completion instructions live at DFARS PGI 253.213-70. Block 1 carries the procurement instrument identification number, block 2 the delivery order or call number, block 5 the priority, blocks 6 and 7 the issuing and administering offices with their DoDAAD codes, block 9 the contractor with its CAGE code, block 14 the ship-to with a DoDAAD or MAPAD code, block 17 the accounting classification and the ACRNs, and blocks 18 through 23 the item, supplies or services, quantity, unit, unit price, and amount. The same instructions cover purchase orders, delivery orders, and calls.
The OF 347 covers simplified acquisitions, purchases under blanket purchase agreements, and orders under basic ordering agreements, per FAR 53.213, and GSA Schedule orders ride on these same forms rather than on a Schedule-specific one. An SF 30 modifies what any of them said, which is its own capture problem, because the modification carries only the lines that changed.
DFARS 204.7101 defines an ACRN as a two-position code that relates an accounting classification citation to the detailed line item information in the schedule. In plain terms, it is how a single order can be funded from several appropriations, with different lines drawing on different money. If your extraction flattens the sublines, the ACRN mapping is the first thing that breaks, and the invoice you build from that data will be charged against the wrong funds. That is a problem you find out about slowly and expensively.
If you are a sub rather than a prime, the DPAS rules follow the order down to you. 15 CFR 700.15 requires a person to use rated orders with their own suppliers to obtain items needed to fill a rated order, using the rating from the customer's order, and states that the rating continues from contractor to subcontractor to supplier throughout the entire supply chain. So a rated purchase order arriving from a prime carries the same required elements listed in 15 CFR 700.12: the priority rating and program identification symbol such as DO-A1 or DX-A4, a required delivery date (the regulation is explicit that the words immediately or as soon as possible do not constitute a delivery date), an authorized signature, and the certification statement declaring it a rated order for national defense use. And you are on the same 15 or 10 working day clock to accept or reject it in writing.
Two separate rules apply and they are easy to state wrong. Under FAR 4.703(a) a contractor keeps records for three years after final payment, or for the specific periods set out in FAR 4.705, whichever expires first, and FAR 4.704 counts those periods from the end of the fiscal year in which the cost was charged. Purchase order files for supplies and equipment, and purchase orders for material and services, each carry a four-year specific period under FAR 4.705. Separately, 15 CFR 700.91 requires records of rated-order transactions to be preserved for at least three years. So the honest one-liner is that PO files carry a four-year period, capped by the three-years-after-final-payment rule, whichever expires first. Structured data in a spreadsheet is a far easier thing to retain and produce on request than a folder of PDFs nobody indexed.
This tool captures data from the awards you receive. It does not submit an acceptance, file an invoice in WAWF, generate a receiving report, or post anything to your accounting system. Worth being precise on that, because the systems get conflated: under DFARS 232.7002 the only acceptable electronic form for payment requests and receiving reports is WAWF, while contract documents themselves are distributed through EDA. Neither of those reads a PDF award into your own spreadsheet. That is the gap this fills. Related routes: purchase order line item extraction covers how the item table is captured, bulk purchase order upload clears a backlog of awards in one batch, the PO PDF to Excel converter is the quickest route if all you need is the spreadsheet, and the purchase order API is there if you want the fields pulled programmatically into a contract management system.
The differences that decide whether your extraction produces usable data or quietly wrong data.
| Commercial purchase order | Federal order (DD 1155 / SF 1449) | |
|---|---|---|
| Line numbering | A simple sequence, 1, 2, 3 | CLIN 0001, priced SLIN 0001AA, informational SLIN 000101 |
| Are all lines priced? | Yes, generally | No. Informational SLINs carry no separate price |
| Delivery schedule | One date for the order | Can differ per separately identified SLIN |
| Funding | One account | Multiple appropriations, mapped by ACRN |
| Ship-to | An address | A DoDAAD or MAPAD code, plus an address |
| Priority rating | None | DPAS DO or DX rating, block 13a or block 5 |
| Response obligation | Commercial acknowledgment, by agreement | Accept or reject in writing: 15 working days (DO), 10 (DX) |
| Item detail per line | Whatever the supplier printed | One NSN, description, or part number per CLIN |
| Where the items live | A table on page one | Blocks 19 to 24, continued on attached sheets |
PurchaseOrders.io extracts data from these documents. It does not accept or reject a rated order on your behalf, submit anything to WAWF or PIEE, generate a receiving report, determine your DPAS obligations, or post to your accounting system. Rating and acceptance obligations are yours and are set out in 15 CFR part 700. Always work from the award document itself.
The same four steps whether the award came from DIBBS, a contracting officer's email, or a prime.
Drop in the DD 1155, SF 1449, OF 347, or the subcontract PO, as a PDF or a scan. Several at once if a batch came in.
It captures the contract and order numbers, the issuing office, the CAGE and DoDAAD codes, the priority rating, the required delivery dates, and the full item schedule including the sublines and any continuation sheets.
Review the item numbers, quantities, and unit prices on screen against the award, paying attention to which sublines are priced and which are informational. This is the step that catches the fund-citation errors before they reach your books.
Send it to Excel, CSV, JSON, or your API. With the rating and the delivery date as fields, a stack of awards can be sorted by which acceptance deadline lands first.
DD Form 1155, Order for Supplies or Services, is the form the Department of Defense uses to issue purchase orders, delivery orders, and calls, in place of the civilian OF 347. Its completion instructions are set out in DFARS PGI 253.213-70. The item schedule sits in blocks 18 through 23, covering item number, supplies or services, quantity, unit, unit price, and amount, and block 5 carries the priority rating.
A contract line item number is a four-digit number from 0001 to 9999 identifying a deliverable, and under DFARS 204.7103-1 it must have a single unit or total price, be separately identifiable to one item or scope, have its own delivery schedule, and carry a single accounting classification. A subline item sits beneath it. Numeric sublines like 000101 are informational and are not separately priced or scheduled. Alpha sublines like 0001AA are separately identified and can each carry their own price, delivery date, and funding.
Under 15 CFR 700.13 you must accept or reject a rated order in writing or electronically within 15 working days of receiving a DO rated order, and within 10 working days for a DX rated order. Rejection has to state the reasons. The regulation also requires acceptance of every rated order you are able to fill, and forbids rejecting one simply because you prefer an unrated order.
Both are DPAS priority ratings under 15 CFR part 700. All DO rated orders rank equally with each other and take preference over unrated orders. All DX rated orders rank equally with each other and take preference over both DO rated orders and unrated orders. The DX rating is reserved for the highest national defense priority, and it carries the shorter 10 working day acceptance deadline.
Yes. DLA policy at DLAD 4.502, note L01, expressly offers contractors award notices either as an email containing a link to an electronic copy of the DD Form 1155 on DIBBS, or as an EDI 850 through an approved value added network. EDI is a choice the contractor makes, not a universal channel, so PDF awards remain a normal, current way federal orders are delivered.
Yes. 15 CFR 700.15 requires a person to use rated orders with their own suppliers to obtain items needed to fill a rated order, carrying the same rating from the customer order, and states that the rating continues from contractor to subcontractor to supplier throughout the supply chain. A rated PO from a prime carries the rating, a required delivery date, an authorized signature, and the mandatory certification statement, and the sub is on the same acceptance clock.
Two rules interact. FAR 4.703(a) requires records to be kept for three years after final payment, or for the specific periods in FAR 4.705, whichever expires first, with periods counted from the end of the fiscal year in which the cost was charged. Purchase order files carry a four-year specific period under FAR 4.705. Separately, 15 CFR 700.91 requires rated-order records to be preserved for at least three years.
No, and the two are often confused. Under DFARS 232.7002 WAWF is the required electronic form for submitting payment requests and receiving reports, and contract documents themselves are distributed through EDA. Both sit inside PIEE. Neither of them takes a PDF award and gives you the line items in a spreadsheet, which is what this tool does. We capture the data; you still file in WAWF.
How the CLIN table is captured.
Clear a backlog of awards in one batch.
Compare with outsourcing the keying.
Pull award data programmatically.
Any PO PDF to a spreadsheet.
Z tej samej rodziny narzędzi
