OneStop Reporting Cloud Agent

OneStop Reporting (OSR) is a service providing reporting, budgeting and analysis for businesses and accountants in the cloud. In addition to cloud-based ERP services, it also supports a hybrid setup by enabling the cloud to use an ERP system in an on-premise location for reporting data and showing vouchers from a local file storage. The cloud agent is what enables this connection by acting as a bridge, performing queries and retrieving data on behalf of OSR cloud. It is an application that is installed on a server in the local domain.


Minimum requirements:

  • 64-bit version of Windows Server 2012 R2 (or later)


  • 4 core CPU
  • 4 GB memory
  • SSD storage
  • 64-bit version of Windows Server 2012 R2 (or later)

How the agent works


  1. The cloud agent connects to OSR’s data gateway and starts listening for requests. It is ensured that it is OSR’s server by verification of the certificate for the domain.
  2. A user runs a report, triggering a request from OSR’s reporting server to the data gateway.
  3. The data gateway finds the established connection with the customer’s agent and passes on the request. The actual process of finding the corresponding agent is done using a Pairing Key that is a manually transferred secret that is entered into the OSR Portal by the customer administrator.
  4. The agent looks up the credentials and settings for the requested data source and executes the request; be it a query against an SQL server or reading a file.
  5. The agent reads the result data from the data source.
  6. The agent starts streaming back the result data to the data gateway.
  7. The data gateway passes on the stream to the reporting service.

Note that all report queries are run directly on the ERP system; thus, always providing up-to-date information. The data generated by queries and retrieved files are not stored by OSR in the cloud in any other form than rendered reports.

Supported types of data sources

The agent supports the following types of data sources.

  • SQL Server – This is usually the ERP system’s database.
  • Files – This is usually one or more file shares where voucher data is stored.

Storing SQL Server credentials

When you add a SQL Server data source to the agent, you need to provide credentials (pairing key) for that database. All queries to the database will run using these credentials. The credentials are encrypted securely, using asymmetric encryption so that they cannot be decrypted by a third party.

All credentials are only stored locally on the agent machine and are never communicated outside of the agent.

Controlling file access

If a data source is to be used to fetch files, such as vouchers, you need to explicitly add one or more paths that the agent is allowed to read from.


The agent creates an outbound connection to OSR’s servers. It communicates on outbound port TCP 443. The agent does not require any inbound ports.

If you are experiencing connectivity issues due to firewall constraints it is recommended that you whitelist the IP addresses for the Azure north Europe region in your firewall. You can download the Microsoft Azure Datacenter IP list, which is updated weekly. The agent communicates with the servers via HTTPS using the fully qualified domain name (FQDN). The current domain names are and


NOTE: Traffic going to or are for app telemetry and insights and are not required for the agent to function.