Posting to Xero and MYOB from Continuum (Update 243)

One of the key areas of testing in Continuum has been the integration between Ostendo and external Accounting Software.

Future Direction

Historically, posting from Ostendo to Accounting Software has been controlled via our scripting engine. In Continuum, we will be transitioning away from this model.

The new approach will see Ostendo invoking Stored Procedures directly from the database using a dedicated service on the database Server similar to the current API service and Remote Database Service, rather than calling Accounting Scripts via the scripting engine. This change will:

• Improve performance of the posting process

• Simplify ongoing maintenance

• Allow enhancements and fixes to be deployed more quickly

At this stage, our focus remains on Xero and MYOB, as these represent the majority of accounting integrations across Ostendo sites. These will be modified over the next month.

Our original intention was to replace the existing Xero and MYOB posting scripts prior to the public release of Continuum. However, development of these Stored Procedures will take additional time and therefore in the interests of not delaying testing or deployment of 243, for the initial release of Continuum (Update 243), posting to Xero and MYOB will continue to use the existing scripting method. (MoneyWorks and QBO will be available over the coming days.)

Temporary Posting Method in Continuum (Xero & MYOB)

In prior versions of Ostendo, posting could be triggered as long as any user was logged into Ostendo.

Due to architectural changes in Continuum, it is no longer practical to execute posting from the same executable instance that users are actively working in.

New Temporary Approach (Continuum Only)

Posting will now be triggered by running a separate instance of ostendo.exe with specific start up parameters.

• This instance is dedicated to GL posting

• It runs independently of normal user sessions

• It must remain running for posting to occur

• It only needs to be launched once per day

Once this parameter-driven executable is closed, posting will cease.

User Flag Change

Previously, a flag on the User record controlled which users could initiate posting.

This flag is now redundant and has been removed from the User Security & Options screen.

Posting control is now managed by launching Ostendo with specific parameters — not by user-level permissions.

How It Works Operationally

• A dedicated “posting” desktop icon must be created

• This launches Ostendo with defined parameters (Launching will automatically check for any Accounting script updates)

• The program is typically launched once per day and then can be minimised by the user/

• Users continue using their normal Ostendo icon as usual

• Posting frequency continues to follow the settings in System Master
  
   

Existing GL Setting Record for sites upgrading to Continuum

Licensing

Because this dedicated posting instance consumes a local license:

Development-X will automatically deploy one additional licence to each organisation running Continuum.

Important

These changes apply to Continuum (Update 243) and do not affect sites running Update 242 or earlier.

Deployment of the Posting Executable

1. Confirm Version

Ensure you are running at least:

Ostendo.exe Build 2026.1.1.214

2. Create Dedicated Posting User

Create a new Ostendo User, for example:

GLPOSTING

• Do not assign any Security access

• This prevents users logging in interactively

• Log in as this user and change the default password

3. Create Desktop Icon

Create a new Desktop Shortcut with the following syntax in the Target field (adjust the path and values as required):

"C:\Ostendo Continuum\ostendo.exe" STARTUPID="243_Xero_Demo" USERNAME="GLPOSTING" PASSWORD="F44D" /glpost

Where:

• "243_Xero_Demo" = Company Name defined in the Ostendo Configuration Utility

• "GLPOSTING" = Dedicated posting user

• "F44D" = Password defined for that user

• /glpost = Required parameter

4. Daily Operation

• Launch the dedicated Posting icon once per day

• Minimise the window

• Leave it running during the day

• Exit it at the end of the day

As long as this instance remains running, postings will occur according to the frequency defined in System Master.