InvoicePortalX

Security & deployment

A controlled customer-facing layer beside your existing system

Security controls and operating responsibilities are documented for each deployment.

See how it works

Architecture & access controls

Controls matched to each deployment

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.

Tenant and data isolation

Supported deployments isolate each customer organisation and its data rather than combining organisations in a shared data store.

Authentication and access

Authorised users are mapped to the customer accounts and information they are permitted to access.

Transmission and administration

Supported web deployments use TLS in transit, and administrative activity is logged for operational review.

Data connection

Choose how information reaches the portal

Available patterns include manual upload, scheduled file delivery or SFTP, API integration and another scoped connection where the environment requires it.

Hosted deployment

Managed as part of the defined service

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

Deployed in customer-controlled infrastructure

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

Your ERP or back-office system remains authoritative

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

Defined for each deployment

Import, storage, retention, export and termination deletion arrangements are documented in the applicable project agreement, including any contractual or legal recordkeeping exceptions.

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.

Launch plan

Tell us about the current setup

Share the system you use and the requests creating repeat work. GX Code will recommend a practical first rollout.

  • Recommended first scope
  • Connection and hosting approach
  • Indicative project pricing

Your current setup

Required fields are marked

Optional preferencesConnection, hosting and other requirements

Leave these blank and GX Code will recommend an approach.

Do not include passwords, financial records or other sensitive information.