Change History for 9.1

20 Sept 2022

additional fixes for 9.1r2 supplementary update at end

  • Date Picker
  • By popular request, date fields now feature a pop-up calendar date picker. This allows dates to be typed normally (and the calendar will reflect what you type), or you can click a date to enter it into the field. Note: You can enable or disable the date picker in the MoneyWorks Preferences → General tab.

             
    Mac
     
    Windows
  • On Windows, there is now an option in the Window menu to “Always open windows on main screen”, which is on by default. If you want modal and floating window positions on different monitors to be remembered, you will need to turn this option off
  • Tax numbers for different locales can now be specified in the setup part of the respective Guide form
  • VAT Guide UK: Fixed to correctly include EU/Northern Ireland Purchases
  • Tax by Currency report now checks for missing tax numbers
  • Build Product now supports BOMs that use serial- or batch-tracked parts and/or create serial- or batch-tracked built products. The BOM is expanded to allow all serial numbers to be specified prior to creating the build journal
  • Serial-tracked parts can’t be added to a BOM for an auto-built product. Turn off auto-build to add serial-tracked parts
  • Tax by Currency report now handles overpayment refunds
  • Customer payment method is now available for non-Debtors
  • MacOS Ventura compatibility for speech output
  • Account list was incorrectly showing the tax code column when initially displayed for documents where GST/VAT processing was turned off
  • Entering a date as only m/d when the system date format is middle-endian-with-alpha-month-names now works as (presumably) expected
  • Fixed a problem with drag & drop recognising .qbo files on Mac
  • Fixed a rounding issue with 50/50 split rules in bank statement import
  • Changing the Name code on a cash transaction imported from a bank statement will preserve the gross value of the transaction if the tax code changes as a result
  • Fixed multi-user concurrency issue with modifying the same filter rule simultaneously
  • Fixed high CPU usage in background when a coachtip or tooltip is scheduled to appear
  • Fixed memory leak when traversing APFS folders
  • Removed some spurious diagnostic log messages
  • Asset Report: Highlighted Only option now works correctly
  • Asset Register Report: Show correct bookvalue for asset purchased on last day of period
  • Asset Register Report: Fix acquisition quantity
  • Bank Balance report: Reinstated grand total
  • Added diagnostic mode to the SMTP preferences. Hold down the shift key when clicking Test to get a full log of the SMTP test session
  • Fixed address book import and email autocomplete on macOS versions later than High Sierra
  • Fixed SMTP emailing to multiple addresses for a role
  • Fixed incorrect cursor for certain drag operations
  • Fixed pinch zoom direction in Preview (Windows)
  • Enabled pinch zoom in Forms Designer
  • The Exclude Zero Qty Lines option in Product History no longer erroneously applies to Pending view
  • Fixed update issues in Analysis editor
  • Timesheet Location field is now reliably validated
  • Detailed Stock Report: Add Highlighted Only option
  • In future, Software Update on Mac will quit other instances of MoneyWorks for you. This is to prevent mysterious file system errors that can be experienced by a process whose executable has been replaced with a new version
  • Trial Balance Report: Option to show closing balances only
  • Stock History Report: Currency conversion issue with negative creditor invoices
  • Add Path button in the Scripting Preferences to select a folder to add
  • Fixed incorrect Accounts List toolbar when GST processing is turned off in document
  • Fix to Cash Projection report
  • Updated calendar holidays
  • Asset Register: Allow revaluation of Non Disposable Assets

🌻

Server

  • Addressed restart/recovery race condition on server
  • Ventura compatibility: Updating Datacentre on macOS Ventura and later launches the GUI installer app to complete the update install
  • Mac Datacentre Console no longer auto-installs/updates MoneyWorks Gold on the server. If Gold is installed on the server, just connect to the server to update it
  • Datacentre Console now gathers Mac crash logs when necessary
  • Fixed Datacentre installation failure on virgin Monterey OS (not upgraded from previous OS version)
  • Fixed potential server deadlock after certain SSL connection failures
  • Other stability fixes
  • Remove excessive logging for syntax errors in users’ custom column expressions
  • Updated paths for jpegoptim and ghostscript for serverside image recompression

🌻

Scripting and Automation

  • Adopt WKWebView for embedded web views on Mac; this provides script-based webviews with access to latest WebKit and Nitro Javascript. See New web views in MoneyWorks 9.1 and later for more information
  • Adopt WebView2 for embedded web views on Windows (where installed); this provides script-based webviews with access to the Chromium/Edge browser engine instead of the IE11 browser offered by IWebBrowser2. See New web views in MoneyWorks 9.1 and later
  • Using the new web views, you can now call out to MWScript from Javascript in a web view’s content. You can also inject javascript into a Web view’s content from MWScript. See Communicating with Javascript in a Web View
  • Fixed assignment to window bounds properties
  • Fixed crash with extremely long array keys
  • Fixed potential crash when SetFieldValue is used in bulk and results in a progress dialog
  • Improved REST error reporting
  • Added Regex_SearchStr returns the first matched substring or empty string if no match
  • Added Regex_GetMatches returns an array of tokens matched by parenthesised subexpressions in the regular expression
  • Improved regex error reporting
  • Reduced threshold of regex_complexity error on Windows
  • HexDecode no longer enforces output being valid utf-8. This is to facilitate re-encoding binary data such as the output of HMAC as Base64
  • GetWindowProperty now returns NULL if the property is not found, rather than throwing a runtime error
  • LoadPicture now displays “PDF” on Window when a PDF was loaded from the server (Windows cannot display PDFs)
  • Timestamp() added TSF_Unix, TSF_Unix_ms, and TSF_Unix_us formats for Unix epoch decimal timestamps
  • Timestamp() format parameter may now be a strftime format string
  • DateToText() format parameter may now be a strftime format string
  • Added ModalTransactionWindow function to invoke a standard transaction entry window modally
  • Added CreateFolder to create a folder
  • Added AddSafePath function to invoke the preferences for user to add a safe path
  • Implementing the same handler name twice (where the first implementation has a non-empty handler body) is now flagged as an error when you do an explicit compile in the Script Editor. In order to not break existing scripts that might have this issue, this error does not prevent existing scripts from compiling at load time. The script will need to be fixed (by removing the earlier extraneous handler definition) when it is modified in the Script Editor
  • Fixed potential crash when SetFieldValue is used in bulk and results in a progress dialog
  • Built_In:__SendSMTPMail now has the option to add multiple attachments by passing an array of paths instead of a single path string

9.1r2 — 4 Oct 2022

General

  • Fixed randomly auto-cancelled Print command on Windows
  • Increased network timeout for Open New Period to better accommodate very very very very large charts of accounts

Scripting

  • Fixed and intermittent crash when closing custom script windows

9.1r1 — 30 Sept 2022

General

  • Fixed a Daylight Saving glitch in the Mac date picker affecting timezones more than 12 hours ahead of UTC
  • Fixed crash when attempting to output a report or form on Windows when there are no printer devices available
  • Navigator panel will now reload if you drill down to overdue debtor or creditor invoices
  • Fixed a resource leak in the Edit Filters command

Scripting

  • Fixed crash when putting up a print spool dialog from a PostedTransactions handler on Windows (although doing this kind of thing from a PostedTransactions handler is absolutely not recommended)
  • Fixed the “open links in external browser” option for WebViews on Windows
  • DoForm() function with non-existent form no longer produces an empty PDF file. The output path will now begin with “[ERROR]”. You should test for this rather than assuming that the path identifies a valid PDF output file
  • The Mail() function will fail with an alert if the attachment path begins with the text “[ERROR]”
Posted in Change History | Comments Off on Change History for 9.1

Fixing window and column sizing problems — window doesn’t fit on screen

If you find that a window in MoneyWorks is opening with too large a size and does not fit within the MDI frame window (on Windows), or is extending off the screen, this may be due to customised column widths in a list in the window being too wide (perhaps they were set when the document was used on a computer with a larger monitor).

How to fix:

  • On Mac, hold down the option key when opening the window
  • on Windows, hold down Control and Shift when opening the window

This will open the window with a default size and position, and will reset customised column widths.

If you are using an older version of MoneyWorks, you might want to consider upgrading to the latest version. MoneyWorks 9 has much better support for multiple monitors and screen resolutions, especially on Windows.

Posted in Uncategorized | Comments Off on Fixing window and column sizing problems — window doesn’t fit on screen

Change History for 9.0.9

27 June 2022

9.0.9r2

  • Fixed failure to import small XML files on high-latency network connection
  • F5 Report: Was incorrectly calculating Box 3 (Singapore)
  • Detailed Stock Listing Report
  • Fixed crash with open(1) with a moneyworks:// scheme url identifying a server folder (Mac)
  • Bank Balance Report: Resolved rounding issue with large Forex balances
  • Fixed initial Account list column format when GST/VAT processing is disabled for the document
  • Print setup dialogs are scriptable

9.0.9r1

  • Fixed a problem in the search optimiser in 9.0.9 that broke some date searches in reports
  • Fixed a 9.0.9 crash in the MWScript Ask() function

🌻

  • Import with update product/name control accounts was broken in 9.0.8
  • Stocktake list report
  • Bill of Materials Costing Report: Sometimes used buy price instead of average unit value
  • Asset Register: Fixed depreciation of assets in period of purchase if purchased on last day of period
  • Asset Register: Fixed issue with departmentalised asset disposal account
  • Parsing of Yodlee data is much faster
  • Fixed opening PDF files (manual/tutorial) on Monterey 12.3
  • Importing transactions: Transaction.promptPaymentDisc % field is now set as a side effect of setting promptPaymentAmt via work-it-out
  • Option to autobuild out-of-stock BOM products when requisitioning for a job (see the Job Costing Preferences panel to turn on this option)
  • Fixed Windows save file dialog sometimes not showing the locations sidebar
  • Simultaneous Process+Print of SO by two different users could result in both invoices being printed by one of the users
  • MoneyWorks for Windows is now built against the Windows SDK v143 from Microsoft. This SDK does not support Windows 8.0 (it does support Windows 7). If for some reason you are still running Windows 8.0, please update to the Microsoft-supported “Windows 8.1 Update”, or, preferably, Windows 10
  • Fixed Stock Enquiry Sum Selection for Pending Purchase Orders incorrect results
  • Fixed crash with Aged Debtors invoked from 64-bit Gold client on Windows when connected to a server
  • Addressed modal and floating window positioning issues on Windows with multiple monitors
  • Detail.Account work-it-out when importing a purchase of a stock item for a job, will now insert the expense account instead of the stock account for the item (the same as you get when manually entering such a purchase)
  • Plugin zipping will no longer add ._ files from Mac file shares on Windows
  • Fixed a potential crash in the Lookup() function
  • Added sign setting for CSV statement importing
  • Improve traversal of “notwork security” packet inspection proxies for software updates and web services on Windows

🌻

Server

  • REST read-only polling when file is not otherwise in use could result in the latest backup being removed
  • Fixed potential deadlock during dropped-connection recovery
  • Windows Console software update browser now supports modern CSS
  • IP blocklist facility to drop unwanted connections by IP range
  • Default blocking of egregious portscanners
  • Fixed incorrectly formed Recent Items link after logging into a non-ASP Datacentre with an email address as a username
  • Small data imports (<2K) will no longer run on the server (prevent extreme server load from iBodyShop)
  • Searching for timestamps now works reliably when the server’s service locale does not use d/m/y date format

🌻

Scripting

  • New JSON parser (500x faster)
  • JSON_Parse correctly interprets \uXXXX where XXXX is non-ASCII UTF16 (9.0.8 only fixed this on Mac; Now works on Windows)
  • Fixed formatting of very large integers (such as JSON numeric IDs)
  • Leaked object handles are now logged when a script is unloaded
  • UpdateOrderLines allows linking to unposted invoice
  • UpdateOrderLines now clears the order’s ShipQty in invSeq linking mode
  • SetProgressMessage is now per-script
  • foreach loop bounds range may now be larger (64 bit long long int instead of 32 bit)
  • foreach loop bounds generates an error when out of long long range
  • spurious “overriding intrinsic” warning is no longer given for ‘uses’ statements
  • Runtime errors no longer auto-unload the offending script (9.0.8 change). As well as a potential circumvention of business rules, this was causing additional instability even after recompiling the script—in particular window handles would not be passed as parameters
  • CURLOPT_CERTINFO/CURLINFO_CERTINFO to capture and retrieve full certificate dump from a TLS connection
  • Loading external script packages with LoadScriptFile is now logged
  • ItemHit handlers for editable list cells may now have more detailed specific naming (down to the column name of the active cell) and will receive additional parameters (namely the list handle, the current row number, and the current column number). e.g. on ItemHit:F_TRANS:L_LIST:DI:Location(winRef, listId, listHdl, rownum, colnum) for an ItemHit handler that responds only to kepresses in the location column of Debtor Invoices. Note that for the transaction entry form, you must supply the type specifier. Note also that due to backwards compatibility, the list is identified by its underlying identifier L_LIST rather than a tab name like By_Item. This does have the benefit that you can respond to, eg, the job column in either the By_Item or By_Account tabs using the same specific handler
  • Fixed display of popup idents in the UI editor
  • Fixed the ModalListWindow() function on Windows which incorrectly instantiated an MDI window instead of a top level window, resulting in UI lockup
  • The Alert function now recognises an empty string button name as “no button” on Windows for the second and third buttons. You can also use NULL if you need to pass all button parameters to specify the timeout parameter
  • Curl_Exec on Windows will add CURLSSLOPT_REVOKE_BEST_EFFORT | CURLSSLOPT_AUTO_CLIENT_CERT options to curl requests by default. Without these, packet inspection proxies will typically not be traversed. If you do not want this security downgrade on your client, you can set the strictRevocationCheckinginCURL registry key in the MoneyWorks Preferences to 1
Posted in Change History | Comments Off on Change History for 9.0.9

Change History for 9.0.8

22 Mar 2022

  • Fixed issues with 9.0.7 BAS Guide (spurious zeroes on box G11, box G1 not including GST Free Sales)
  • Support for mapping tax codes to foreign tax guide codes. See Paying GST/VAT in Multiple Countries
  • Available Shopify support
  • Available BigCommerce support
  • Available WooCommerce support
  • Product Sales Enquiry: Fixed various cosmetic issues
  • Product Sales Enquiry: Fixed various cosmetic issues
  • Product History: option to exclude zero qty lines
  • Customer Sales Enquiry: unposted setting is respected in movements list
  • Product Sales Enquiry: support include unposted on network
  • Email subject lines can now be pinned and stored for re-use
  • Save a Copy as Clone: Now includes asset categories
  • Pre-installed holidays now work on APFS and Windows
  • Stock transfer journals now auto-split lines to streamline entering serial numbers for created stock
  • Credit notes now respect quantity price breaks
  • Age by Due Date Report now omits cancellations
  • Autocomplete email addresses is now less aggressive
  • Prepayment deposit lines no longer omit tax codes when the deposit control account includes a department
  • Importing Job Sheet items – the type (IN/EX) may now be explicitly specified instead of relying solely on the sign
  • A negative stock purchase (return) with a discount no longer generates a spurious stock/cogs adjustment
  • When updating MoneyWorks, the std scripts are now replaced rather than merged. Don’t keep your own scripts in the std scripts folder
  • Fixed potential double & in Asset Category code popup on Windows
  • MoneyWorks will now post warning messages when document size approaches the maximum size (4GB)
  • Fixed a random crash on startup related to progress dialogs and software update check
  • Period numbers can be shown in the Period Maintenance dialog (hold down the Shift key)
  • Name.WebURL was allowing too many characters to be entered (field size is 63 chars)
  • Fixed some pixel alignment issues in budget spreadsheet window
  • Unposted cash transaction stock movements now show in Stock Enquiry with Include Unposted
  • Product importing no longer spuriously sets multiple price flag when updating existing products
  • More informative progress messages on clients when retrieving data from the server
  • Bank feeds: Yodlee Fastlink 4 — Localised default banks for New Zealand
  • Fixed software update download progress display when downloading manual
  • Fixed software update temp files being left behind
  • Statement importing: Coding a transaction to the same bank the statement is for is now flagged as an error

🌻

Scripting fixes and additions

  • Allow scripts to use intrinsic function/global names as handler/local var names. In this case the local identifier will hide the global one. The declaration will be coloured purple by the syntax colouriser
  • RemoveLeading and RemoveTrailing functions to truncate the beginning or end of a string
  • GetFieldValue on a period popup: pass true as third parameter to decode to period number
  • UI editor: popup control idents and z-order now redraw properly
  • UI editor: fix crash on Monterey when showing idents
  • Script editor: autocomplete window was not wide enough on Monterey
  • UI editor: prevent resizing objects to a negative dimension
  • UI editor: tab control selection frame+resize handle now show on Windows
  • UI editor: popup control selection frame+resize handle now shows properly on Mac
  • Installing scripts from .mwxml: better progress logging
  • Navigator() function may now be used from PostedTransactions handler (it executes asynchronously)
  • Fixed double & in popup menu controls on Windows
  • Removed unintended 32K length limit on concat and syslog functions
  • AppendPopupItems now interprets ( item prefix as disable this item (per documentation)
  • Fixed Mac script editor not deactivating when in background
  • Fixed potential crash if a script is called from a custom list column
  • JSON_Parse now correctly interprets \uXXXX where XXXX is non-ASCII UTF16 (update: this only got fixed on Mac; Windows fix coming in 9.0.9)

🌻

Server

  • In ASP mode, the server now logs any folder login attempt
  • enableReconnections was not being maintained properly in the conf file
  • HTTP GET on the DC port now gives a 418 error
  • Console now flushes folder settings on exit field (in addition to changing list selection)
  • Correct reporting of certain REST request errors as 4xx or 5xx as appropriate
  • Changed the config variable name for verbose logging so that it gets turned off when updating. Do not turn it on verbose logging unless Cognito support asks you to
Posted in Change History | Comments Off on Change History for 9.0.8

MoneyWorks and WooCommerce

A module to download new sales from a WooCommerce ecommerce store is available as a service for MoneyWorks Gold/Datacentre. Once setup, this allows you to download new WooCommerce sales into MoneyWorks at the click of a button.

The service is enabled in File>Manage Services (you will need to restart your MoneyWorks after enabling the service). You will also need to configure your WooCommerce store.

Configuring WooCommerce

In the administration area of WooCommerce, you will need to get REST API read access so that MoneyWorks can read your orders. For information on how to do this see WooCommerce REST API. Copy and paste the Consumer Key and Consumer Secret from here into the MoneyWorks WooCommerce Settings window as described below.

Configuring MoneyWorks

Having installed the WooCommerce service (and restarted MoneyWorks), choose Command>WooCommerce Settings (only users with Account Enquiry privileges can access this). The WooCommerce settings will open:

MoneyWorks WooCommerce Settings

You first need to enter your Store URL, Consumer key and Consumer Secret into the corresponding fields in the Settings window. Click the Test button to check your settings. If they are correct, the ID of the most recent order in WooCommerce will be displayed.

The MoneyWorks Settings determine how you want MoneyWorks to handle your WooCommerce transactions.

Transaction Type: The type of transaction to create (Receipt, Invoice, Sales Order).

Bank Account: If you are creating receipts, the bank account for the transaction.

Taxable Tax Code: For sales which have tax/GST/VAT applied to them, the MoneyWorks tax code to use.

Exempt Tax Code: For sales which are tax exempt, the MoneyWorks tax code to use.

Default Customer Code: The default customer code to use on transactions. For example you might set up a customer “WEBSALE” and use this. The customer must be a debtor.

Create New Customer Records: Turn this on if you want to create new customer records in MoneyWorks for each sale. If the customer already exists in MoneyWorks, that customer’s code will be used, otherwise a new one will be created. The match is based on the email address.

Default Item Code: The item code to be used if the SKU on the WooCommerce store is not found in MoneyWorks. This must be an item in MoneyWorks that is sold.

Discount Item Code: An item for any WooCommerce discounts. This must be an item that you sell (and is required even if you don’t intend to have WooCommerce discounts).

Freight Item Code: The item code for any freight (this must be an item in MoneyWorks of type Freight).

Gift Card Item Code: The item code for Gift Cards. This should be an item that you buy and sell. As the sale of a gift card imposes a liability until the card is redeemed, both the sales and expense account should be of type Current Liability.

Transaction Fee Code: The item code for any transaction fees that might be incurred. The fee is deducted from the sale total. At present this is used only if the Payment Method in WooCommerce is “stripe”.

MoneyWorks Customisation Code: Although the WooCommerce service should “just work”, there are many permutations of settings and different ways that a store can be set up, and it may be that the script has to be “tweaked” to work with your store. If this is required you will be issued with a Customisation Code which needs to be entered here (otherwise leave this field blank). Note that such customisations will be charged for.

Once your settings are correct, click the OK button to save them.

Downloading WooCommerce Transactions

To download new sales from WooCommerce:

  1. Click the green Woo Orders button on the Transaction list toolbar. You will be asked for confirmation.
  2. Click OK to download new orders. Any new orders created since the last one listed will be downloaded. This may take a few seconds. Upon completion an alert will display the number of transactions downloaded and the transactions will be shown in the transaction list.
  3. Click Specific Order to download a nominated order. You will be prompted for the ID of the order (this is the Receipt/Order No in MoneyWorks). If you want to reset the order id (so subsequent downloads will be orders made after this id), set the Reset Importing check box.

Notes:

  1. The first time you download sales you need to “seed” it with the ID of the first transaction that you want to download (otherwise you risk importing lots of old orders). Use the Specific Order and Reset Importing to do this.
  2. The ID to use is the WooCommerce ID. You get this from the administration area of your store, or by clicking the Test button in the WooCommerce Settings. This ID is also stored in the transaction.ourref field of any transactions imported from WooCommerce.
  3. A maximum of 25 orders will be downloaded at one time (so if it says there were 25 orders, click the Woo Orders button again in case there are more).
Posted in FAQ, Resources | Tagged | Comments Off on MoneyWorks and WooCommerce

MoneyWorks and BigCommerce

A module to download new sales from a BigCommerce ecommerce store is available as a service for MoneyWorks Gold/Datacentre. Once setup, this allows you to download new BigCommerce sales into MoneyWorks at the click of a button, and optionally order the product from your supplier.

The service is enabled in File>Manage Services (you will need to restart your MoneyWorks after enabling the service). You will also need to configure your BigCommerce store.

Configuring BigCommerce

In the administration area of BigCommerce, you will need to create a new API Account that allows MoneyWorks to have read-only access to Orders. To do this log into your store and choose Advanced Settings>API Accounts and click the Create API Account button. This will give you an Access Token and a Store Hash (the store hash is the last chunk of the API path, excluding the slashes). These need to be entered into the BigCommerce Settings in MoneyWorks (see below). Your store designer should be able to do this for you if you can’t figure it out,

Configuring MoneyWorks

Having installed the BigCommerce service (and restarted MoneyWorks), choose Command>BigCommerce Settings (only users with Account Enquiry privileges can access this). The BigCommerce settings will open:

MoneyWorks BigCommerce Settings

You first need to enter your Access Token and Store Hash into the corresponding fields in the Settings window.

The MoneyWorks Settings determine how you want MoneyWorks to handle your BigCommerce transactions.

Transaction Type: The type of transaction to create (Receipt, Invoice, Sales Order).

Bank Account: If you are creating receipts, the bank account for the transaction.

Taxable Tax Code: For sales which have tax/GST/VAT applied to them, the MoneyWorks tax code to use.

Exempt Tax Code: For sales which are tax exempt, the MoneyWorks tax code to use.

Default Item Code: The item code to be used if the SKU on the BigCommerce store is not found in MoneyWorks. This must be an item in MoneyWorks that is both sold and purchased.

Coupon Discount Code: An item for any BigCommerce discounts. This must be an item that you sell (and is required even if you don’t intend to have BigCommerce discounts).

Freight Item Code: The item code for any freight (this must be an item in MoneyWorks of type Freight).

Transaction Fee Code: The item code for any transaction fees that might be incurred. These are based on the Payment Fees table. If the transaction fee is exempt of GST/VAT, make sure the sales account associated with the item is exempt of GST/VAT.

Default Customer Code: The default customer code to use on transactions. For example you might set up a customer “WEBSALE” and use this. The customer must be a debtor.

Create Purchase Invoices: Turn this on if you want to create a purchase invoice for every item sold (effectively you are not holding stock, but are sourcing the product only on demand).

Default Supplier Code: The code of the default supplier to use for purchase invoices if the supplier cannot be determined from the value in the item’s Usual Supplier field in MoneyWorks.

Payment Fees: Use this table if you want to automatically deduct fees from the imported transaction based on the BigCommerce payment, or if you want different payment methods to be targeted to different bank accounts (if you are bringing in the transactions as receipts). Use the Add and Delete row icons on the right of the list to add lines. The columns are:

  • Payment: The payment method, exactly as given in BigCommerce.
  • Bank: The MoneyWorks bank account for the transactions to be coded against if you are bringing them in as receipts.
  • Fee: The per transaction fee for the payment type. Leave zero if none.
  • Pct: The percentage fee per transaction for the payment type.

In the screenshot above, two payment types have been added. Paypal in this example has a per transaction fee of 45 cents, plus 3.4% of the transaction gross.

MoneyWorks Customisation Code: Although the BigCommerce service should “just work”, there are many permutations of settings and different ways that a BigCommerce store can be set up, and it may be that the script has to be “tweaked” to work with your store. If this is required you will be issued with a Customisation Code which needs to be entered here (otherwise leave this field blank). Note that such customisations will be charged for.

Once your settings are correct, click the OK button to save them.

Downloading BigCommerce Transactions

To download new sales from BigCommerce:

  1. Click the green BC Orders button on the Transaction list toolbar. You will be asked for confirmation.
  2. Click OK to download new orders. Any new orders created since the last one listed will be downloaded. This may take a few seconds. Upon completion an alert will display the number of transactions downloaded.
  3. Click Specific Order to download a nominated order. You will be prompted for the ID of the order (this is the Receipt/Order No in MoneyWorks). If you want to reset the order id (so subsequent downloads will be orders made after this one), set the Reset Importing check box.

Notes:

  1. The first time you download sales you need to “seed” it with the ID of the first transaction that you want to download (otherwise you risk importing lots of old orders). Use the Specific Order and Reset Importing to do this.
  2. The ID to use is the BigCommerce ID. You get this from the administration area of your store. This ID is also stored in the transaction.ourref field of any transactions imported from BigCommerce.
  3. If the sale already exists in MoneyWorks it will be skipped (this avoids duplicating entries).
  4. Only completed orders are downloaded. This does mean that if a customer starts an order and completes it some days later, the order will need retrieved specially.
Posted in FAQ, Resources | Comments Off on MoneyWorks and BigCommerce

MoneyWorks and Shopify

A module to download new sales from a Shopify ecommerce store is available as a service for MoneyWorks Gold/Datacentre. Once setup, this allows you to download new Shopify sales into MoneyWorks at the click of a button.

The service is enabled in File>Manage Services (you will need to restart your MoneyWorks after enabling the service). You will also need to configure your Shopify store.

Configuring Shopify

In the administration area of Shopify, you will need to create a new “app” that allows MoneyWorks to have read-only access to Orders using the Admin APIs (your store designer should be able to do this for you if you can’t figure it out — the Shopify documentation is a bit daunting). Creating the app will give you an Access Token which starts with “shpat_”. You need to enter this into the Shopify Settings in MoneyWorks (see below).

Prior to 2022, Shopify apps used an API Key and an API Password. If you already have an older app with access to Shopify orders, you can use these.

Configuring MoneyWorks

Having installed the Shopify service (and restarted MoneyWorks), choose Command>Shopify Settings (only users with Account Enquiry privileges can access this). The Shopify settings will open:

MoneyWorks Shopify Settings

You first need to enter and check your store details.

  1. Enter your store URL. This will be something like mystore.myshopify.com.
  2. Enter the Access Token, or (if you are using a pre 2022 app) turn on the Use OLD APIs checkbox and enter your API Key and API Password.
  3. Click the Test button to check that MoneyWorks can access the store.

The MoneyWorks Settings determine how you want MoneyWorks to handle your Shopify transactions.

Transaction Type: The type of transaction to create (Receipt, Invoice, Sales Order).

Bank Account: If you are creating receipts, the bank account for the transaction.

Taxable Tax Code: For sales which have tax/GST/VAT applied to them, the MoneyWorks tax code to use.

Exempt Tax Code: For sales which are tax exempt, the MoneyWorks tax code to use.

Default Customer Code: The default customer code to use on transactions. For example you might set up a customer “WEBSALE” and use this. The customer must be a debtor.

Create New Customer Records: Turn this on if you want to match the sale to an existing customer, or, if a match cannot be found, to create a new customer record. The matching is done on the email address in Contact 1 of the customer record. New customer codes are generated based on the settings in Edit>Document Preferences>Terms.

Default Item Code: The item code to be used if the SKU on the Shopify store is not found in MoneyWorks.

Discount Item Code: An item for any Shopify discounts. This must an item that you sell (and is required even if you don’t intend to have Shopify discounts).

Freight Item Code: The item code for any freight (this must be an item in MoneyWorks of type Freight).

Gift Card Item Code: The item code for Gift Cards. This should be an item that you buy and sell. As the sale of a gift card imposes a liability until the card is redeemed, both the sales and expense account should be of type Current Liability.

When no delivery address, do not substitute billing address: When there is no delivery (shipping) address specified in Shopify, the Billing address will be inserted as the delivery address. Turn this option on if you want the delivery address to be left empty.

MoneyWorks Customisation Code: Although the Shopify service should “just work”, there are many permutations of settings and different ways that a Shopify store can be set up, and it may be that the script has to be “tweaked” to work with your store. If this is required you will be issued with a Customisation Code which needs to be entered here (otherwise leave this field blank). Note that such customisations will be charged for.

Once your settings are correct, click the OK button to save them.

Downloading Shopify Transactions

To download new sales from Shopify:

  1. Click the green Shopify Orders button on Transaction list toolbar. You will be asked for confirmation.
  2. Click OK to download new orders. Any new orders created since the last one listed will be downloaded. This may take a few seconds. Upon completion an alert will display the number of transactions downloaded.
  3. Click Specific Order to download a nominated order. You will be prompted for the ID of the order. If you want to reset the order id (so subsequent downloads will be orders made after this id), set the Reset Importing check box.

Notes:

  1. The first time you download orders you need to “seed” it with the ID of the first transaction that you want to download (otherwise you risk importing lots of old orders). Use the Specific Order and Reset Importing to do this.
  2. If you are using the OLD APIs, the ID to use is the Shopify “name”, which corresponds to the ourref field in MoneyWorks. For the new APIs you need to use the Shopify ID, which is a 13 digit number. You get this from the administration area of your store, and it will stored in the transaction user5 field of any transactions imported from Shopify.
  3. Imports are limited to 25 transactions per batch. If you have more than 25 transactions you will need to repeat the Shopify Orders process.
Posted in FAQ, Resources | Comments Off on MoneyWorks and Shopify

Moving MoneyWorks Datacentre to a new computer

To move MoneyWorks Datacentre to a new computer:

Important: If you are using a Mac server, do NOT use Apple Migration Assistant to migrate to a new Mac. (It will offer to migrate MoneyWorks Server but it will make a complete mess of it. Don’t do it).

  1. Request the MoneyWorks Datacentre installer. Please contact us to request the Datacentre installer. Include your Datacentre serial number and the platform of the new machine (Windows or Mac). Note that we may not have installers for older versions of Datacentre that are out of maintenance.
  2. When you are ready to install, turn off the old Datacentre. Make sure that no-one is connected, and wait for a few minutes until all the files are closed and any backups made.
  3. Run the Installer on the new machine. Follow the MoneyWorks Datacentre setup instructions.
    • Re-enter the configuration information (serial number and other settings, including SSL certificates if you are using TLS, and webkey if you have one) in the Console.
  4. Make sure the new server computer is set to not go to sleep. Note that Mac servers will go to sleep by default. Change the sleep setting on macOS Ventura
  5. Copy the existing Datacentre file to the new machine. The Datacentre Documents directory can be located by clicking the Show button next to the Documents Folder entry on the Configuration panel of the Datacentre Console. Use this to find the location on the old machine and the target location on the new machine.
  6. Copy over the Archives and Backups if necessary and desired. These may be in the same directory as the Documents (so already copied over), or in a different directory. If they are located on a different server there is no need to copy them, just point the Archives and Backups directory on the new machine to the same location.
  7. Check the Documents and Permissions. Click on the Documents tab of the new Datacentre Console to see that the files are there. You may be prompted to update the Document permissions at this point. Note that if the Datacentre is installed on macOS Catalina or later you must give Datacentre full disk access (In System Preferences → Security & Privacy → Privacy).
  8. Check that you can log in. On a client machine, start MoneyWorks Gold and click the Connect button. You should see the new Datacentre listed when you Connect Using Local Browser. Choose that and check that you can then successfully log in to your file.
  9. Uninstall the old Datacentre. You definitely don’t want to leave this running in case people inadvertently log in and start working on old files (and also your Datacentre licence only covers one machine). See Uninstalling MoneyWorks Datacentre.
  10. Check users’ Recent Documents. If users are connecting to Datacentre using the Recent Document link, it is likely that these will no longer work (this is because, unless you have specifically set it. the IP address of the new computer is likely to be different from that of the old). Clients should choose File → Open Recent → Clear Menu to clear the old Recent Documents (it will clear on next restart), and connect using the Connect button (this will make a new entry in the Recent list, which should work from then on).

If you have configured your router for remote access and the internal IP address of the new machine differs from that the original, you will need to reconfigure your router to point to the new machine (see Using MoneyWorks over the Internet). Also ensure that you set the machine to a fixed IP so it doesn’t change in the event of a reboot. It is easier to change the IP of the old machine and fix the IP of the new one to that of the original (this also means the Open Recent should continue to work).

Posted in FAQ, Resources | Comments Off on Moving MoneyWorks Datacentre to a new computer

Change History for 9.0.7

Performance enhancements and bug fixes

16 Dec

  • Fix SMTP on Windows (the built-in SMTP MWScript was not being loaded due to being installed with an incorrect file extension)
  • Importing payments on invoices: performance improvement
  • Importing payments on invoices: fixed potential crash with unbalanced payments
  • Export XML performance improvement
  • Import progress window was not displaying progress on Mac
  • Canada GST report no longer showing for all locales
  • Datacentre/Console now times out if a database server becomes unresponsive
  • Budget importing now tolerates blank lines in the input
  • Fixed manpage installation on Mac
Posted in Change History | Comments Off on Change History for 9.0.7

Change History for 9.0.6

Mostly bug fixes

7 Dec

  • Print from Preview (Mac) was being vertically offset on the page. This has been fixed, but if you normally Print from Preview, you may have adjusted your forms to account for this vertical offset. If so, you may need to adjust them back.
  • Fixed a number of issues introduced by the switch to the new Scintilla text editing framework on Mac…
    • Script Editor (Mac) performance issue syntax colouring XML fixed
    • Script Editor (Mac) high CPU usage fixed
    • Script Editor (Mac) fixed MWScript syntax colouring missing the final token after using html/xml/json syntax colouring lexer
    • Script Editor (Mac) for Report custom control was not active
  • Fixed Report-to-Excel only working half the time (Mac)
  • Bank Reconciliation Status Report: performance optimisation
  • Datacentre: Stale-disconnect time may no longer be less than 5 minutes
  • Datacentre: Rate-limit for reconnect attempts to give more time for the network to come back up if it has gone down
  • Fixed Yodlee account linking error when there are not yet any linked accounts
  • Fixed a stack overflow crash in the in-field expression evaluation when the expression is very long
  • Stock History report: corrected handling of revaluations and negative stock
  • Copy Records as XML command is now in the contextual menu (Gold)
  • Correct handling of UK VAT Flat Rate scheme submissions using MTD

Previously included in 9.0.5r1 DC

  • Fixed Tax rates dialog being read-only on a server in 9.0.5
  • Fixed high CPU usage in the import dialog (Mac)
  • Cosmetic fix to edit list column resize on Mac
  • Scripted clipboard access (GetClipboardText and PutClipboardText)
  • Fixed potential crash on server shutdown (mainly on Windows)
Posted in Change History | Comments Off on Change History for 9.0.6