Intake Channels Overview
Overview
Section titled “Overview”TaprNext accepts documents through multiple channels. AP channels create Purchase Invoices in In Docs. AR channels create Sales Invoices in Out Docs.
AP channels (In Docs)
Section titled “AP channels (In Docs)”| Channel | Automation | Ideal use | Format |
|---|---|---|---|
| PEPPOL | Highest | Structured B2B e-invoices | XML / SBDH |
| SharePoint | High | Microsoft document libraries | Multi-format |
| Azure Blob | Highest | Continuous cloud drop folders | Multi-format |
| Manual Upload | Lowest | Exceptions and pilots | PDF / image / XML |
Approved Purchase Invoices can also be pushed out to an SFTP server for a downstream system — see SFTP Exchange.
AR channels (Out Docs)
Section titled “AR channels (Out Docs)”| Channel | Automation | Ideal use | AI BYOK? |
|---|---|---|---|
| New Invoice | Manual | Under ~5 / month | No |
| Upload Invoice | Medium | 5–20 PDFs / month | Yes (plain PDF) |
| AR Email | Medium | Email-driven sales PDFs | Yes (plain PDF) |
| ERP fetch | Highest | Bulk, ERP is source of truth | No |
| API | Highest | Custom systems / XML | No |
| SFTP | High | Systems that drop files on an SFTP server | Plain PDF only (XML / JSON need none) |
Details: Creating & Sending Sales Invoices.
AR Email is configured under Tapr Settings → AR Settings — see AR Email Configuration. It is not the same as a general AP email intake channel.
Processing notes
Section titled “Processing notes”- XML-first: embedded e-invoice XML is preferred over AI.
- AI: plain PDFs need a configured provider key.
- Quotas: plan message limits can block intake when exceeded. Inbound PEPPOL is never blocked by the quota.
Recommended setup
Section titled “Recommended setup”- PEPPOL for e-invoice capable partners (AP and AR).
- SharePoint or Azure for bulk AP PDF drops when needed.
- AR ERP fetch or API for high outbound volume; Upload / AR Email for mid volume.
- Manual upload for exceptions and first-time testing.