Read-only to the source by default
InvoicePortalX receives and presents configured information without changing the ERP or back-office system. Write-back is scoped separately.
Security & deployment
Security controls and operating responsibilities are documented for each deployment.
Architecture & access controls
InvoicePortalX receives and presents configured information without changing the ERP or back-office system. Write-back is scoped separately.
Supported deployments isolate each customer organisation and its data rather than combining organisations in a shared data store.
Authorised users are mapped to the customer accounts and information they are permitted to access.
Supported web deployments use TLS in transit, and administrative activity is logged for operational review.
Data connection
Available patterns include manual upload, scheduled file delivery or SFTP, API integration and another scoped connection where the environment requires it.
Hosted deployment
GX Code manages the hosted InvoicePortalX deployment within the boundaries set by the proposal or statement of work. Hosting location, backup arrangements, maintenance, monitoring, support and any availability commitments are confirmed there.
Self-hosted deployment
A container-based deployment can be scoped where required. The agreement assigns responsibility for infrastructure, networking, certificates, backups, operating or container platform, monitoring, deployment, upgrades and support.
Source of truth
Imported information is presented for customer access. Corrections should be made in the source system and supplied through the next configured data exchange.
Data lifecycle
Import, storage, retention, export and termination deletion arrangements are documented in the applicable project agreement, including any contractual or legal recordkeeping exceptions.
First rollout
Tell us what customers ask for and where the information lives. GX Code will recommend a practical first scope and connection approach.