Phase 1
Review
- Review the current systemConfirm where account information and documents live.
- Choose the first customer scopeSelect the requests that create the most repeat admin.
How it works
Keep the ERP. Add the customer-facing layer.
InvoicePortalX gives authorised customers access to selected account information while your existing system remains authoritative.
The operating model
Your existing system remains authoritative
InvoicePortalX imports or receives the required account information and presents it to authorised customers. No ERP write-back occurs by default; any write-back integration would be scoped separately.
Source of truthERP, accounting or back-office system
Customer-facing layerInvoicePortalX
Secure accessAuthorised customer
From review to launch
Four practical phases from review to rollout
Phase 2
Connect
- Select the connectionChoose upload, file/SFTP, API or another practical method.
- Map customer accessDefine accounts, contacts, branches and sites.
- Configure documentsSelect the records, fields and files customers may see.
Phase 3
Launch
- Apply the brandConfigure the customer-facing identity.
- Pilot a groupValidate source data and access with initial accounts.
- Go liveOpen the initial scope and support the rollout.
Phase 4
Expand
- Expand when justifiedAdd scope only when there is a demonstrated reason.
Connection options
Use the lightest connection that is reliable
Start with the interface your system can support reliably. The connection can deepen later when there is a business reason.
What we need to assess a rollout
- The system holding account information
- A sample document
- An explanation of account structure
- An example export or available interface
- The customer requests creating the most admin
First rollout
Start with the requests creating the most admin
Tell us what customers ask for and where the information lives. GX Code will recommend a practical first scope and connection approach.