Skip to main content

xPOS

Release history

What each xPOS version brings: new capabilities, improvements and fixes by country.

Which version do you have?

Type your installed version, for example 2.7.0 — we will tell you what is new and until when it is supported.

v2.7.0

Release

Multi-company support —a single xPOS installation can operate with more than one issuing company, each with its own tax identity, certificate, environment and folios— and Peru joins the xPOS family, with integration with SUNAT and with OSE. The release is completed by a renewed dashboard with Excel export, one-click maintenance tools, a built-in watchdog that keeps the service always available on native installations, and country-specific improvements.

Highlights

  • Multi-company: a single installation serves several issuing companies, each with its own certificate, environment and folios.
  • Peru joins xPOS, with integration with SUNAT and with OSE.
  • Renewed dashboard, with Excel export that respects your filters.
  • The service recovers on its own if it stops or stops responding (native installations).
  • Contingency in Colombia resolved on the device itself, without depending on external services.

This version also includes all the new features for installations that update directly from 2.4.x.

· 44 changes in 15 areas

Multi-company9
  • Until now, each issuing company required its own xPOS installation. Now a single installation serves several, and each document is issued, queried and stored under the identity of the company that made the sale.
  • One device, several companies: chains and groups that operate more than one tax ID in the same store no longer need separate devices.
  • Independent environments: one company can be in production while another is still in certification, without interference.
  • Certificates per company: each issuer uses its own digital certificate, validated against the document being issued.
  • Isolated contingency: if the tax authority has an outage affecting one company, the operation of the others continues normally.
  • Folios and numbering per company: each company keeps its own sequence, with no crossovers.
  • Traceability per company: dashboard, reports, duplicate control, kiosk and history operate under the identity of the right company.
  • Configurable numbering: the connection to the folio manager is set up from the portal, per company, without updating the installation.
  • All of it built on the principle that defines xPOS: the sale never stops. None of this adds connection dependencies at the moment of issuing.
🇵🇪 Peru1
  • Peru joins the xPOS family, with integration with SUNAT and with OSE.
🇨🇱 Chile5
  • The Carátula is completed from the portal: if the point of sale does not send the SII resolution data, xPOS takes it from the company configuration. Fewer rejections for missing data.
  • SII queries with the right identity: each DTE is tracked with the tax ID of the company that issued it, and each response is tied to its real issuer.
  • Digital certificate validity check: xPOS validates validity when issuing and immediately recognizes a certificate just renewed in the portal.
  • The final result of each contingency before the SII is always reported, including its detail, and the cancelled status is reflected as a final status.
  • Better connectivity on networks with advanced configurations.
🇨🇴 Colombia5
  • Contingency is resolved on the device: when the DIAN is unavailable, xPOS converts and issues the document in its contingency mode (type 03) locally, without depending on external services, and regularizes it afterwards. To use this feature the Folio Manager must be enabled, and its activation must be requested from the consulting team.
  • Contingency independent per company: it is activated only for the affected company; the others keep issuing online.
  • More precise rule 90: the message retrieves the previously accepted document by querying the correct environment of each company.
  • DIAN response readable on screen with the «View ET response» option of the dashboard.
  • Fix of the date format in the self-reference that the DIAN flagged in certain contingency documents, and a configuration download that leaves the installation exactly as the portal defines it.
🇨🇷 Costa Rica2
  • More robust credential renewal with Hacienda: a single renewal at a time —even if several submissions need it at once— and validity read from the credential itself. Fewer rejections for expired credentials during peak activity.
  • More resilient contingency: a connection outage with Hacienda no longer affects the document; it waits and is resent automatically when the service recovers. The final status is reflected when the authority responds.
🇬🇹 Guatemala2
  • Prior validation of the signed document against the official SAT schemas, online and in contingency: format problems are detected before sending.
  • More stable issuing in multi-company installations: each submission to Megaprint travels with the identity of the right issuer.
🇩🇴 Dominican Republic3
  • Improved handling of the dual summary/invoice receipt (RFCE): each status is precisely tied to the right document.
  • Summary tracking automatically uses the right provider according to the document type.
  • Documents can now be issued for recipients with a foreign identifier.
🇵🇾 Paraguay1
  • The detail of SIFEN rejections is recorded and synchronized, including the authority's acknowledgement.
🌎 All countries2
  • Better behavior on corporate networks: typical interruptions of managed networks are recognized as temporary and resolved with automatic retry.
  • Early validation of the signing certificate as a step before processing.
🖥️ Renewed dashboard and Excel export3
  • Excel export in Processed Documents, Contingency and Errors, respecting the applied filters (dates, document type, status, folio).
  • Search, sorting and filters over all the information, not only the visible page.
  • Tax authority status unified across the whole interface, and date filters in the device's local time.
🧰 One-click maintenance2
  • On-demand database compaction from Settings: it recovers disk space when it suits the operation and reports how much was freed. It can also be run remotely and centrally.
  • Log of the automatic nightly cleanup, with a searchable history, and disk space monitoring.
🔄 Service continuity: built-in watchdog5
  • Native installations (Windows and Linux) include permanent supervision that lives inside the service itself, with no additional components to install or maintain.
  • Recovery from unexpected stops: if the xPOS service stops, it restarts on its own.
  • Health watchdog: it continuously checks that the service is not only running but responding; if it detects that it stopped responding, it recovers it automatically. The store does not need to notice or intervene.
  • It coexists with operations: it tells a real crash from a planned stop, so it does not interfere with updates or scheduled maintenance.
  • Important: the Watchdog service is not installed automatically if version 2.7.0 comes from an update of earlier versions.
🎨 Custom outputs and documentation2
  • Custom output templates declare their own response format (XML, JSON or text): each integration receives exactly what its system expects.
  • API documentation reviewed end to end, including the issuing company identification in multi-company installations.
🔒 Security and platform1
  • Security components updated in xPOS, in the dashboard and in the updater.
System Integrator publishing channel1
  • This version includes the foundation of a new document publishing channel with real-time status confirmation. It will be enabled gradually and per organization, coordinated by the Gosocket team; while an organization does not have it active, xPOS publishes through the current channel with no change.

Dates correspond to the release package of each version. For questions about a specific installation, contact Gosocket support.