# PDF Parser: Extract Fields & Tables from PDFs | DigiParser Source: https://www.digiparser.com/solutions/pdf-parser [Solutions / PDF Parser](/solutions) PDF PARSER - FIELDS + TABLES # Turn PDFs into _usable data._ Extract the fields and item rows you need from digital or scanned PDFs. Give customer orders and supplier invoices a consistent structure your team can review, export and use. [Try your PDFs](https://app.digiparser.com/auth/join) [See the output](#example) No code needed to start. API available for developers. CUSTOMER PO.pdf PO-1048 Maple Works Mounting bracket **24 EA** End cap **10 EA** TOTAL **$380.00** YOUR FIELDS STRUCTURED OUTPUT po\_number PO-1048 customer\_name Maple Works line\_items 2 rows Ready for review and export Illustrative example - fictional data Digital + scanned PDFs Named fields + repeating rows CSV - XLSX - JSON - XML EXPLORE[Output example](#example)[Field setup](#setup)[How it works](#workflow)[PDF checks](#formats)[Start a pilot](#start) THE DIFFERENCE ## A page of text is not an order record. Copying text out of a PDF still leaves your team finding the right reference, fixing columns and separating item rows. DigiParser gives that information names and types, so the same fields can be used across the documents you process. **Define the output first.** If your order sheet needs a customer reference, item code, quantity and unit, those are the fields and columns to extract. Keep descriptions as text and quantities as numbers. FROM DOCUMENT TO DATA ## See what useful output looks like. Two different workflows. One clear principle: keep document fields and every item row together. Customer POSupplier invoice Illustrative data - not a live extraction 01 / SOURCE PDF Maple Works ### Purchase order PO-1048 Your customer sends this order to your team. Requested delivery 2026-10-16 Currency USD **Mounting bracket**BR-12 - 24 EA x $12.50**$300.00** **End cap**CP-08 - 10 EA x $8.00**$80.00** Total**$380.00** Fictional document shown as a simplified illustration. 02 / STRUCTURED DATA ### Names and rows your team can use. Spreadsheet rowsJSON customer\_name Maple Works po\_number PO-1048 requested\_delivery 2026-10-16 currency USD On small screens, scroll the table to see all columns. line\_items - 2 rows Item code Quantity Unit Unit price Line total BR-12 24 EA 12.50 300.00 CP-08 10 EA 8.00 80.00 The CSV sample repeats document fields on each item row. Document totals are omitted so they cannot be double-counted when summing rows. [Download sample CSV](/examples/pdf-parser/po.csv)Example structure, not an API response envelope. **What happens next?** Use the rows for order entry or tracking. Map customer and item IDs before creating a sales order in a connected system. YOUR STRUCTURE, YOUR TERMS ## Choose what matters. Leave the rest. Start with suggested fields for a purchase order or invoice, then edit the names, types and descriptions to match your task. * TEXT Keep references and item codes as text, including leading zeros. * NUMBER Use numeric fields for quantities, prices and amounts. * DATE Distinguish invoice dates, due dates and requested delivery dates. * TABLE Define a repeating row with its own named columns. [Read the field setup guide](https://www.digiparser.com/docs/guides/working-with-parsers) [![DigiParser Fields and Tables settings showing named invoice fields, field types, a line items table and Save Fields.](/_next/image?url=%2Fimages%2Fsolutions%2Fpdf-parser%2Ffields-and-tables.png&w=3840&q=75&dpl=dpl_CPQnEhggmYn43eUERpeVtf8KHiV2)](/images/solutions/pdf-parser/fields-and-tables.png) Real product screen from the public documentation. Open the image to inspect the fields at full size. A REPEATABLE ROUTE ## Set up once. Use it for the next PDF. Keep one parser per document type. The same field definitions give the next file a consistent output structure. 1. 01 ### Tell it what to extract Choose a document type. Name your fields and define the columns for repeating rows. Customer POs and supplier invoices use separate parsers. 2. 02 ### Add your PDFs Upload files, send attachments by email or use a configured source. Test different layouts and scans. Start with documents your team actually receives. 3. 03 ### Review the complete result Compare values and item rows with the source. Configure assigned approval stages when exports must wait. Check references, dates, units and page breaks. 4. 04 ### Put the data to work Download a file or map data to a configured destination. Check the actual sheet or system record. A useful result reaches the place your team works. [Configure review stages](https://www.digiparser.com/docs/guides/reviews-approvals/overview) [Choose an export format](https://www.digiparser.com/docs/guides/managing-data/exporting-data) MAKE THE TEST COUNT ## Bring your difficult PDFs, too. A clean first page is a weak test. Include the files that create work for your team. CHECK 1 ### Digital PDFs Check references and codes, not just totals. A readable PDF still needs the right field definitions. CHECK 2 ### Scanned PDFs Use readable, complete scans. Check faint values, cropped edges and similar-looking characters. CHECK 3 ### Multi-page tables Count every item row. Check repeated headers, page breaks, long descriptions and units. CHECK 4 ### Protected PDFs Configure the password rule before processing. Test one permitted file before sending a batch. **Upload limits** Up to **500 files per batch** and **100 MB per file** in the Document Inbox. Follow queued and processing status for large batches. [File and processing guide](https://www.digiparser.com/docs/guides/document-processing/supported-files-and-limits) CHOOSE THE NEXT STEP ## For your spreadsheet. Or your software. Use the app to get a useful output first. Add a connected workflow when you know where the data belongs. FOR OPERATIONS & FINANCE ### Start with a usable file. Download CSV or XLSX for order tracking or AP entry. Flatten fields and tables into rows, or export tables as separate XLSX sheets. Check the file your colleague will actually use. [Explore PDF to Excel](/solutions/pdf-to-excel) FOR DEVELOPERS ### Connect a verified API route. The REST API supports parsers, fields, documents, exports and webhooks. Use the base URL for your team's region, an API key and the documented `/api/v1/` endpoints. Follow processing status before retrieving results. [Open the API reference](https://www.digiparser.com/docs/api) A BETTER FIRST TEST ## Test the record. Not just the PDF. For a small office, involve the person who enters the orders or bills. For a larger team, also include the person who owns review and the destination setup. [See the manufacturing workflows](/solutions/for-manufacturing) 1. 1 ### Select real variation Choose permitted files with different layouts, scans and page counts. 2. 2 ### Compare every field and row Record missing values, incorrect units and the time needed to correct them. 3. 3 ### Open the destination result Check the actual sheet or record. Decide who handles revisions and failed handoffs. PDF PARSING QUESTIONS ## Before you start. Fields, files and the next step. What is a PDF parser? A PDF parser turns information in a PDF into data that another program can use. DigiParser lets you define named fields and repeating table rows, process PDFs, review extracted values and export structured data. Can DigiParser parse scanned PDFs? Yes. DigiParser accepts PDFs, including scans. Test clear digital PDFs and your typical scanned files against the same field and table setup. Blurry, cropped or low-resolution documents can need correction or a better source file. Can I extract tables from multi-page PDFs? Define a Table field and its columns for repeating item rows. Test rows across page breaks, repeated headers and long descriptions. Check every item and unit against the original document before relying on the output. Can DigiParser open password-protected PDFs? Configure a password rule in the parser settings before processing password-protected PDFs. Make sure your team is permitted to process the file and use the correct password. Does PDF parsing require code? No. You can create a parser, define fields and tables, upload documents and download results in the app. Developers can use the REST API for document processing and other parser resources. Use the API reference for regional URLs, authentication and request details. Which export formats are available? Download CSV, XLSX, JSON or XML. Choose flattened fields and tables for spreadsheet rows, or separate table sheets in XLSX. Automatic delivery to a connected destination needs integration configuration and field mapping. Can I process several PDFs together? The Document Inbox accepts up to 500 files per upload batch and up to 100 MB per file. Large batches can be queued. These are intake limits, not a guarantee of processing speed. Does extracting a customer PO create a sales order? Extracted customer PO data can support order entry or tracking. Creating a sales order in another system requires destination field mapping, customer and item ID resolution, and a tested record write. Supplier invoice processing is a separate buyer-side workflow. LESS COPYING. MORE USABLE DATA. ## Make your next PDF useful to your team. Bring a customer PO or supplier invoice. Define the output, review it and use it. [Try DigiParser free](https://app.digiparser.com/auth/join) [Discuss your workflow](/schedule-demo) [Customer PO parser](/solutions/purchase-order-parser)[Supplier invoice parser](/solutions/invoice-parser)[PDF to CSV](/solutions/pdf-to-csv)[Pricing](/pricing)