How These Docs Are Organized
The documentation is organized around what you’re trying to do, not around the product’s internal structure. Pick the track that matches your role — you don’t need to read the others.
Start with the Product Map (AP vs AR lifecycles) or the Glossary if terms are unfamiliar.
The three tracks
Section titled “The three tracks”🔧 Implementors
Section titled “🔧 Implementors”You’re standing up and configuring Tapr for an organization: legal entity, PEPPOL registration, AI extraction, intake channels, and approval rules. Most of this is one-time setup. Work top to bottom and finish at the Go-Live Checklist.
👤 Users
Section titled “👤 Users”You process invoices day to day in Invoice Manager — In Docs (AP) or Out Docs (AR). Guides are task-first.
→ Users · Creating sales invoices · Invoice Manager
🔌 Integrators
Section titled “🔌 Integrators”You connect Tapr to an ERP (ERPNext, D365, SAP) or to other systems via webhooks and the REST API. Each ERP connector follows the same shape: prerequisites → connection → testing.
→ Wire it up · REST API Reference
Shared sections
Section titled “Shared sections”- Troubleshooting — error reference and FAQs, including PEPPOL send/receive.
- PEPPOL — Overview, registration, API, MLR/BLR.
- Reference — REST API and e-invoice formats.
Not sure where to start?
Section titled “Not sure where to start?”Take Pick Your Path or open the Product Map.