# Email Parser for Customer POs & Supplier Invoices | DigiParser Source: https://www.digiparser.com/solutions/email-parser [Solutions / Email parser](/solutions) DOCUMENT INTAKE, WITHOUT REPEATED UPLOADS # Your inbox. _Useful order and invoice data._ Put incoming customer POs and supplier invoices to work with DigiParser. Send the right content to a parser, capture fields and line items, and give your team reviewed output it can use. [Try DigiParser free](https://app.digiparser.com/auth/join) [Discuss your email workflow](/schedule-demo) Email body or attachments - Fields and tables - Review and handoff YOUR INCOMING EMAIL ## Customer PO - PO-4027 Please process the attached purchase order. PO-4027.pdfAttachment ![](/img/digiparser-vector-logo.svg)**DigiParser**Extract & review ILLUSTRATIVE ORDER OUTPUT Customer PO PO-4027 Requested date 2026-10-21 Item / quantity / unit BR-24 / 12 / EA Ready for your order-entry or tracking check. [Choose your workflow](#workflows)[Choose email content](#content)[Set up the stream](#setup)[Control the intake](#controls) TWO DOCUMENT STREAMS. TWO CLEAR JOBS. ## Same inbox habit. Different business data. Keep customer orders and supplier bills separate. Each stream needs its own field specification, review checks and destination. SELLER-SIDE / CUSTOMER ORDERS ### Customer PO intake Receive an order from your customer. Capture the details the order team needs without retyping the attached document. Capture Customer reference, delivery details, requested date and every item row. Review Product code, quantity and unit; check changed or repeated orders. Hand off Reviewed output for a tracker or configured order process. [Explore the customer PO parser](/solutions/purchase-order-parser) BUYER-SIDE / ACCOUNTS PAYABLE ### Supplier invoice intake Receive a supplier bill. Capture the fields and amounts your AP process needs, with a named owner for exceptions. Capture Supplier, invoice reference, dates, currency, line items, tax and total. Review Missing values, item amounts and totals against the source. Hand off Invoice-entry data; matching, coding and payment stay in the AP process. [Explore the supplier invoice parser](/solutions/invoice-parser) CHOOSE THE SOURCE BEFORE THE AUTOMATION ## Body, attachments or both? The attached PO and the message around it serve different jobs. Choose what becomes a document, then check the result. Use this preview to understand the options. Choose the content to processAttachments onlyAttachments, then body fallbackBody and attachmentsBody only Attachments in this exampleNo attachments1 attachment2 attachmentsProcess attachments together ILLUSTRATIVE PROCESSING RESULT**2documents** Read attached documents. Do not create a document from the body. * Attachment 1 document * Attachment 2 document Preview only. Save the matching setting in your parser. Document count is not order count, invoice count or billed page usage. Example assumes an allowed message and supported, unfiltered files. "No attachments" means none were attached. If filename rules reject every attachment, the message can be skipped rather than sent to body fallback. [Read the settings guide ->](/docs/guides/parsers/parser-settings/email-processing) A PRACTICAL INTAKE ROUTE ## Send documents. Keep the work organized. Use a parser inbox address to bring documents into DigiParser. Keep the selected content, extraction and review process aligned with the stream you are handling. [See the email settings guide](/docs/guides/parsers/parser-settings/email-processing) ![Public DigiParser email import overview showing a parser inbox address and organized document files](/_next/image?url=%2Fimages%2Fhow-it-works%2Femail-import.png&w=3840&q=75&dpl=dpl_2o9hiEDiLM4MvULB5VNbE8RVZa9R) Public product overview. Copy the actual inbox address from your own parser. START WITH ONE RECURRING STREAM ## From a sample email to a repeatable process. 1. 01 ### Define the useful data Choose a PO or invoice parser, then define the fields and repeating tables. Pick the tracker or configured system that will use the result. 2. 02 ### Select the content Open Settings -> Parser Settings -> Email. Choose body or attachment processing, check sender/file rules and save the parser. Connected mailboxes have their own content option. 3. 03 ### Send a permitted sample Copy the actual parser inbox address and send a representative message. Include the attachments or body you intend to process. Confirm the expected documents arrive. 4. 04 ### Verify and expand Review values and item rows, then check the export or configured destination. Add selective forwarding after provider setup, with an owner for exceptions. **Forward the relevant messages, not the entire inbox.** Gmail requires forwarding-address verification and supports filters for selected messages. Check your mailbox provider's setup and your organization's access rules before adding automatic forwarding. [Google's forwarding instructions ↗](https://support.google.com/mail/answer/10957?hl=en) A CLEANER DOCUMENT STREAM ## Be specific about what reaches the parser. Use the email controls that match your process. Test a message that should pass and one that should be excluded. ### Sender access Allow or skip selected senders. Check the actual forwarder or redirected sender, not only the vendor shown in quoted text. ### Attachment types and filenames Accept the formats you need. Use filename conditions to select relevant files when a message carries several attachments. ### Message conditions Apply subject or body text conditions before documents are created. Define whether all or any conditions must match. ### Saved email context Open the document's Email tab to inspect its saved message snapshot. This helps a reviewer check the instruction around an attachment. ### One email does not always mean one order. Repeated forwards and revised POs need a business check before records are created or changed. Keep that decision in the order workflow. [Read the worked email-intake guide](/blog/email-parser) A SMALL TEAM CAN START HERE ## A clear stream. A clear owner. In an 11-50 person office, one person may set up intake and review the results. In a 200-500 person team, those tasks may have different owners. Confirm who handles exceptions and who approves the pilot. DIGIPARSER STARTER**$69/month on monthly billing** * 500 page credits per month * 5 parsers - 3 members $588 annually - $49/month equivalent. Confirm processing options and destination costs. [Review all plans ->](/pricing) BEFORE YOU START ## Email parsing questions, answered. What does DigiParser's email parser do? DigiParser receives emailed content at a parser or folder inbox address and turns the selected body or attachments into document data. Define fields and repeating tables, review the result, then export or use a configured destination. Customer POs and supplier invoices use separate schemas and checks. Can it read both the message and its attachments? Yes. Choose body only, attachments only, body and attachments, or body fallback if attachments cannot be processed. Body-and-attachments creates a body document separately from attachment documents. The preview shows the grouping for a simple example. Can several attachments produce one result? The Process email attachments together setting groups matching attachments from one message into one document and combined extraction result. The email body remains separate when body-and-attachments is selected. Use grouping when the files belong together, and test separate orders or invoices before combining them. Can we control which messages and files are processed? Yes. Email settings include sender access, accepted attachment types and text rules for the subject, body or attachment filename. Check who appears as the sender after forwarding. A normal forward usually identifies the forwarder; a redirect can retain the original sender. Does email intake automatically create orders or approve invoices? Email intake creates documents for extraction. An export or configured integration handles the next step. Order IDs, revisions, duplicate checks, accounting decisions, payment and order release belong to the agreed downstream process. Test the actual destination result before expanding. How do we start with Gmail or Outlook? Start by sending a permitted sample to the parser address. You can then set up a selected forwarding route or a connected mailbox. Complete provider verification and access requirements. Connected Gmail and Outlook mailboxes use their own Email content option in connection settings. MAKE THE NEXT EMAIL USEFUL ## Start with the documents already arriving. Bring one customer PO or supplier invoice email. Turn it into reviewed data for your next step. [Try DigiParser free](https://app.digiparser.com/auth/join) [Discuss your email workflow](/schedule-demo)