Choose Main document only, Each document separately, or Everything together when sending packet parents and multipage files from Parsedit. Choose Main document only, Each document separately, or Everything together when sending packet parents and multipage files from Parsedit.
Create your first parser in minutes. No code, no setup calls.
Authorize Parsedit from Zapier, map Upload Document or New Parsed Document to a parser, and manage connections from the Integrations page.
When a file has more than one logical document, or a long multipage extract, Save & send asks how to deliver. Pick wrong and your sheet gets one mashed row, or your API gets three posts you did not expect.
Parsedit exposes three modes. Learn them once; reuse them on every packet-heavy parser.
Per-document send versus envelope payload.
| Mode | UI label | Behavior |
|---|---|---|
| Primary | Main document only | Sends the main / parent extract |
| Per document | Each document separately | Sends each logical document (each child) as its own delivery |
| Envelope | Everything together | Sends the full file extract as one payload |
Docs: Document packets. Narrative: How document splitting works.
Google Sheets AP tracker
Usually Each document separately so each invoice child becomes its own row.
QuickBooks / Xero bills
Per invoice child, separately. Do not envelope an invoice+PO packet into one bill.
Webhook to custom API
Depends on the consumer. Envelope if your API expects one job per upload; per document if it expects invoice objects.
Zapier
Per document when each child should trigger downstream tasks independently.
Review children individually before trusting auto-send. Auto-send vs manual.
Packet parent with child documents.
Child review limited to its page range.
Send modes sit in the same review → deliver loop as single invoices. Soft CTA: upload one mixed AP PDF and try each mode into a staging sheet. Related: Invoice AP extraction.
Write the choice into an internal runbook so every reviewer does not reinvent it.
For one mixed PDF, send to a staging sheet three times (or three copies of the file with tiny differences if dedupe blocks retries), once per mode, and screenshot the outcomes. Keep those screenshots in your ops wiki.
History parent/child links plus the mode you chose should make those answers boring. If they are not, retrain and keep auto-send off.
History: Packet · 3 documents. Children: invoice p1–2, PO p3, remittance p4.
Do not assume one mode fits every destination on the same click without checking.
“For mixed AP packets, send invoice children separately to Sheets/QBO; never envelope into the ledger.”
People search after a wrong Sheets row. A clear table for Main / Each / Everything prevents repeat mistakes and earns links from internal wikis.
Can modes differ per destination on one click? Choose the mode for that send; configure destinations you include. Test combinations in staging.
Does mode change page credits? Credits follow processing pages, not how many times you send.
What if children should use different parsers long term? Create separate parsers for clean intake; children can still appear under the upload parser.
Test all three modes on one packet before production auto-send. Sign up.
