Retail and multi-location businesses often operate many branches or POS locations under one TRN. This raises real design questions: how should the Peppol Participant ID be scoped, how should sequencing work per branch, and should reporting be consolidated or branch-level?
One Participant ID is maintained at the legal-entity level, while each branch is tagged with its own branch code in the invoice data model. Sequencing and numbering are managed per branch/till, and reporting can be produced consolidated, branch-level, or both.
Multi-branch retail operations report cleanly under a single TRN without losing branch-level traceability - a pattern directly reusable for any client operating more than one location.
Tell us about your ERP and the mandate you fall under — we’ll show you how we’d handle it.