October 2026 Updates

Ver 2.5.0#

Budgets#

• Budgets module: A Budgets module was added. Add it to a menu in the menu setup and give users access in User Access (Menu > Settings > Edit User Access).
  • The list shows each budget’s Status (Draft, Approved or Locked), Description, Start (the first month of the financial year), Version (Original, Revised or Forecast), Entity and Default. Filter by entity and status, then click View (button). Output > Export exports the list.
  • New adds a budget for the current financial year (from the Financial Year start month in General Settings). Double-click a budget, or right-click it and select Edit, to open it.
  • The edit view has the Status and Status Note at the top (the colour bar shows the status), the budget details below them, and the Statement of Profit or Loss accounts, with a column for each month and a Total. Enter the budget amount of each account for each month. Revenue and expense amounts are both entered as positive amounts. Use the arrows to go to the previous or next budget.
  • Sections, groups and the summary rows (for example, Net Profit) are added up when you click Save. Expand and Collapse (buttons) open or close all the account groups. Output > Export Budget exports the accounts.
  • Actions > Batch Update shows an update bar above the accounts. Select the accounts (Ctrl + left-click or Shift + left-click; a section or group updates all its accounts), select the update and the months From and To, and click Update (button). You need the Batch Updates user setting, and a locked budget cannot be updated. The updates are:
    • Amount per Month: The same amount every month.
    • Spread Total: The total split evenly over the months, with the rounding difference in the last month.
    • Adjust %: The existing amounts plus or minus a percentage.
    • Clear: Removes the amounts.
    • Prior Year Actual + %: The actual amounts of the same months in the previous year, plus or minus a percentage (blank leaves them as they are).
    • Copy from Budget + %: The amounts of another accounting budget (select it in From Budget), plus or minus a percentage.
    • Spread Total by Prior Year: The total split over the months in the same pattern as the previous year’s actual amounts (seasonal), or evenly if the previous year has no actual amounts.
  • Actions > Copy Budget, Copy as Revised and Create Forecast (also on the list’s right-click menu) add a draft budget with the same amounts. Copy as Revised sets the Version to Revised. Create Forecast (accounting budgets only) sets it to Forecast, with the actual amounts of the months before the current month and the budget amounts for the remaining months.
  • Only one budget of each type (accounting or sales) can be the default for the same start month and entity.
  • A Locked budget cannot be changed or deleted. To change it, set its status back to Draft (users with Edit access can still change the status). Deleting a budget deletes its amounts.
• Sales budgets: New > Sales adds a sales budget. The list’s Type column shows whether a budget is an accounting or a sales budget. A sales budget stands on its own and does not change any accounting budget.
  • Select up to two Tiers (Customer, Customer Category, Item, Item Category, Sales Rep and Branch). Each line is a combination of the tiers (for example, Customer Category + Item Category), with an amount for each month and, with Show Quantities, a quantity for each month.
  • A line can be limited to one Revenue Account (blank means all revenue accounts).
  • Delete Item (right-click the line, or click the line’s three dots (…), or press Ctrl + Delete) removes a line. The tiers cannot be changed once the budget has lines; they can be changed again once all the lines are deleted.
  • An incomplete line is not saved, and Save stays enabled until it is complete.
  • On a sales budget, Batch Update works on the selected lines: Amount per Month, Spread Total, Adjust % and Clear, for the Amounts or the Quantities.
• Budgets vs Actuals module: A Budgets vs Actuals report was added. Add it to a menu and give users View access in User Access. Select the Budget, the Month To (the period runs from the first month of the budget to this month, for example, year to date) and the Entity (the budget’s entity by default), then click View (button). The views are on the Menu button:
  • Profit/Loss: For each account, section and Net Profit: the Actual and Budget amounts for the period, the Variance and Variance % (green is favourable: revenue above budget or expenses below budget; red is unfavourable), the full Budget Year, the Forecast (the actual amounts for the period plus the budget for the remaining months) and the Remaining budget.
  • Monthly: The actual and budget amounts side by side for each month of the budget year, with the period totals. Actual amounts are shown up to the Month To only. The months after it are hidden; show them again from the band header customisation (grey, budget only).
  • Sales by Tier (sales budgets): The Actual, Budget, Variance, Budget Year, Forecast, Remaining amounts and quantities for each budget line. The actual amount is the posted revenue of all revenue accounts. Each sale counts once, against the first line (in the budget’s line order) it matches, and that line’s revenue account if it has one. A category includes its subcategories. Sales that match no line appear as Unbudgeted / Other. With Monthly, the sales grid shows the months.
  • Chart: The actual amount against the budget for each month, for the selected Statement of Profit or Loss row (or all the lines of a sales budget), with actual amounts up to the Month To.
  • Expand and Collapse (buttons, before View) open or close all the account groups. The choice is kept when you click View again or change the view.
  • The search box appears only when the view has data, and Reset Data Filter hides it. Output > Export exports the current view.
• Statement of Financial Position budget: A General Setting Enable Financial Position Budget was added (default No). When it is set to Yes:
  • An accounting budget also shows the Statement of Financial Position accounts. Enter the budgeted closing balance of each account for each month (not the movement). The Total column shows the balance at the end of the year.
  • Retained Income is not entered. It is the actual balance on the day before the budget starts, plus the budgeted Net Profit up to the month. It is shown in grey, is read-only and is skipped by Batch Update.
  • Budgets vs Actuals > Menu > Financial Position shows, for each account, the actual balance at the end of the Month To against the budgeted balance, with the variance and the budgeted balance at the end of the year.
  • When it is set to No, budgets cover the Statement of Profit or Loss only, as before.

Multi-level BOM Estimates#

• Estimate Types > Model: Each Estimate Type has a Model, either Standard (as before) or Multi-level BOM. The model cannot be changed once the Estimate Type is used on estimates.
• BOM window: An item estimate of a Multi-level BOM Estimate Type opens in the new BOM window. It shows the estimate as a tree of assemblies with their materials, tasks and outwork, many levels deep.
  • Item adds an item from the item master, with its bill of materials (BOM) and routing. Custom adds a line that is not (yet) an item. Delete removes the selected lines.
  • An assembly can be expanded to its BOM or collapsed again. Lines can be moved by dragging and dropping them, or by right-clicking a line and selecting Move Up or Move Down. To replace an item, right-click the line and select Change to Similar Item. Each line also has an edit window, with arrows to move to the previous or next line.
  • Each line can override the quantity, the prices and the Supplier (materials and outwork) or the Cost Centre (tasks). The totals are recalculated through all the levels.
• Costs (tab): The materials and routing of the whole tree, added up by item and price. Production and purchasing use these lines. Only the Status can be edited here. Lines already linked to a purchase order or a goods issue are kept.
• Overrides (tab): The lines with values that differ from the item master (for example, the code, description, prices, quantity or supplier). A warning icon appears on the tab while there are any. Update sets the selected lines back to the item master values.
• Create Items: Turns custom lines into new items, from the lowest level up. Custom assemblies get their BOM and routing. For each linked assembly with changed lines, you select Create new Item, Update existing Item BOM or Skip.
• Copying a transaction item also copies its BOM tree, and deleting the item removes the tree.
• An item cannot be added to its own BOM, directly or through a sub-assembly.

Asset Enhancements#

• Transactions > Create an Asset: On Transaction Types with Enable Assets, right-click a line item and select Create an Asset to create an Equipment asset from it. The asset takes its description, code and note from the item, and its contact from the transaction. Only items from the item master can be used, not custom items.
  • The attribute sets of the item and of the transaction are copied with their values. A set that is set up for one module only (for example, Items) is changed to All modules so that it can be used on the asset. If the asset already has the set, only its blank values are filled in.
  • The new asset is linked to the transaction and to the item, and to the linked Service Manager job if that job has no asset yet. The notes and attachments of the transaction and of its linked Service Manager job are linked to the asset too, unless they are already linked to another asset.
  • If the item is already linked to an asset, no asset is created and you can open that asset.
• Transactions > Open Linked Asset: Right-click a line item that is linked to an asset and select Open Linked Asset to open the asset. The option appears only for items linked to an asset.
• Assets > Open in Assets Module: An asset opened from another module (for example, with Open Linked Asset) has Menu > Open in Assets Module, as items do. It closes the popup and opens the asset in the Assets module.
• Transactions > Asset filter: On Transaction Types with Enable Assets, the transactions list has an Asset filter (next to Company and Entity). It shows the transactions linked to the selected asset.
• Assets > tabs:
  • A Notes & Attachments tab was added, laid out like the Service Manager’s: the notes at the top (with Expand) and the attachments below. Note and Attachment add one. Double-click a note, or right-click it, to edit or delete it. The attachments can be filtered by Description (the attachment description list, as in the Attachments module).
  • A new Transactions tab lists all the transactions linked to the asset, grouped by Transaction Type, newest first. Double-click one to open it.
  • A Services tab lists all the Service Manager jobs linked to the asset, newest first. Double-click one to open it. Its column is called Ticket No.
  • The previous Transactions tab (depreciation postings, shown only for assets with depreciation) was renamed Depreciation.
  • The Meter tab (previously Odometer, for vehicles only) also appears on Equipment assets.
• Notes and Attachments linked to the asset: A note or attachment added to a transaction or a Service Manager job that is linked to an asset is linked to that asset too, so it also appears on the asset’s Notes & Attachments tab.
• Links (button): In transactions and the Service Manager, the Links button also lists the linked asset (at the bottom), which opens the asset.

Enhancements#

• Output Templates > Output Name: An Output Name was added: the file name of the PDF attached when the template is emailed. In the output setup, right-click a template and select Edit Output Name. It can include the same [params] as the email subject, for example, Invoice [trans_no] - [company].
  • When the email is created, the [params] are filled in, the characters that file names cannot contain (/ ? < > \ : * | and &) are removed, and .pdf is added.
  • The Output Name column in the templates list shows which templates have one. Templates without an output name still use the template’s Description as the file name, as before.
• Transactions > Unit (Select): A Unit (Select) column was added to the line items. On an item from the item master, select another unit of the item from the list. The list shows the item’s prices with the same price type and currency as the transaction (Supplier, Cost, Sell or Price List, from the Transaction Type settings), with the unit price and the Qty the line has in each unit.
  • Changing the unit converts the Qty to the new unit (for example, 30 ea = 3 box when a box is 10 ea). If the unit has no convert quantity, the Qty is kept. The prices and cost are set from the selected price in the same way as when the item is added (VAT Inc/Exc, Price List, converted to the transaction’s currency, and the cost from the cost price). Stock is updated when the transaction is saved.
  • Only users with Edit Prices can change the unit, and not on read-only transactions. Custom items keep the free-text Unit column.
• User Access > Hide Costs and Edit Prices: Two columns were added to the user access of a Transaction Type:
  • Hide Costs (unchecked by default): Hides the cost, markup and profit columns in the transaction lists and items. Applies only to Transaction Types with the Pricing setting Sell Price or Sell Price (Any Currency).
  • Edit Prices (checked by default): When unchecked, the Fixed Price, Unit Price, Adj%, MU%, VAT Type, Inc and the Unit (item price) cannot be changed on the items, and their column headers are no longer blue. Adj%, MU% and VAT are also removed from Batch Update.
  • Both can be set with Batch Update, and are copied with Copy Access and Copy Users and when a Transaction Type is copied.
  • They replace the user setting Hide Cost/Profit, which the upgrade removes.
    • Note: The upgrade does not set Hide Costs for the users who had Hide Cost/Profit. Check Hide Costs on each Transaction Type for those users after the upgrade.
• Notes and Attachments > Search: The search box always appears above the notes and attachments lists.
• Customer Age Analysis and Supplier Age Analysis > Email: Select several rows in the list (Ctrl + left-click or Shift + left-click), select Email and a template: one email is created for each selected customer or supplier, with its PDF attached, and saved in the Outbox without the email edit window opening.
  • The Emails module then opens on the Outbox, where the emails can be checked, edited and sent. A message shows how many emails were created and how many have no email address (fill these in before sending).
  • With one row selected, Email works as before (the email opens for editing).
• Emails > Send: Several emails can be selected in the list (Ctrl + left-click or Shift + left-click). Send then sends only the selected emails. With one row selected, Send sends all the listed emails, as before.
• Financial Reporting > Expand and Collapse: The Statement of Profit or Loss and the Statement of Financial Position keep the last Expand or Collapse choice when you click View (button) again. Previously, they always opened expanded.
• Transactions > Language: A transaction’s Language cannot be changed once the transaction has items, because the item descriptions are in that language. Changing the customer or supplier still sets the language from the contact, but only while the transaction has no items.
• Transaction Types > Item location by branch: On Transaction Types with Enable Entities = Branch, an item’s Location can only be one of the locations linked to the transaction’s branch. The restriction applies to the Location dropdown list, Batch Update and the default location set when an item is added.
  • The Default Location setting is ignored for these Transaction Types. If the branch has only one location the item can use, it is filled in automatically.
  • Transaction Types shows a warning when Enable Entities is not Registered and a Default Location is set.
• User Access > Entity: The Entity list of a Transaction Type or Service Type follows its Enable Entities setting (Registered, Branch or Till), and so does the column caption: Entity, Branch or Till (PoS).
  • A new transaction always gets an entity of the kind set in Enable Entities. If the user access or Transaction Type entity is a registered entity on a branch type, the first branch under it is used (a till gives its branch, a branch on a registered type gives its registered entity, and so on). Cancelled entities, and branches or tills that are not linked to a registered entity, are no longer selected by default.
  • With Trans No. by Entity, a transaction with an entity that has no registered entity now shows a clear error instead of failing.
  • When Enable Entities of a Transaction Type or Service Type is changed, the user access Entity of that type is reset to All for every user, because the previous entity is no longer the right kind.
• User Access > Filter Caption and Filter SQL: The Filter Caption and Filter SQL columns, the View/Edit Filter SQL menu option and its action column were removed. Transactions and Projects no longer apply a filter for each user. The upgrade removes the two columns, so any filter SQL that was set is removed.
• Transaction Types > Select Attributes to show in List View and Edit View: The two settings list the items of every attribute set for Transactions or All modules, sorted by set code. Previously, only the sets selected in Default – Attribute Sets were listed. When a value is entered in the edit view for a set the transaction does not have yet, the set is added to the transaction, as before.

Fixes#

• Fixed: Items > Reserved and On Order: Reserved and On Order were only reduced by the transaction copied directly from the reserving or ordering transaction. They are now reduced by the issues and receipts anywhere in the same transaction flow. For example, Sales Order (reserve) → Delivery Note → Invoice (issue) now clears the reservation, and a receipt on a Purchase Order copied in steps clears the On Order quantity. Production material reservations work as before.
  • An item issued in a larger quantity than was reserved no longer lowers the Reserved quantity of the other transactions.
  • Note: Run Rebuild Inventory Report (Items module) once after the upgrade, so that the Reserved and On Order quantities of existing transactions follow the flow too.
• Fixed: Statement of Financial Position > Retained Income: With Fin Year (Months), the Retained Income of each month added the expenses instead of subtracting them, so the month columns (and the totals and balance check under them) were too high. It now shows revenue less expenses up to the end of each month, the same as the single-date Statement of Financial Position.
• Fixed: Contacts > Duplicate name warning: The duplicate Name / Known as warning compared persons with entities. It now compares only contacts of the same type, so a person and an entity with the same name no longer show the warning.
• Fixed: Service Manager > Transactions: The Transactions tab of a Service Manager job (and the asset’s new Transactions tab) did not list older transactions that never had the deleted flag set. They are now listed.
• Fixed: Replenishment > Last Order: The Last Order and Last Order Date columns could show a cancelled purchase order. They now show the latest purchase order that is not cancelled, also when its status does not update stock.
• Fixed: Transactions > Allocation amount: Allocate on the Allocation screen allocated the full amount of the transaction. It now allocates the smaller outstanding amount of the two transactions: allocating a receipt of 500 to an invoice of 1 000 allocates 500 (previously 1 000).
  • When several transactions are selected, each one gets what is left of the outstanding amount. Once the transaction is fully allocated, nothing more is allocated and a message appears.
  • A receipt or payment with no amount still takes the full outstanding amount, so Update Transaction to the Allocated Amount works as before.
  • Foreign currency (both transactions in the same currency): the smaller currency amount is allocated, with the smaller of the two local amounts. The exchange rate difference stays outstanding in local currency only (currency amount 0), so it can be allocated by a Forex Gain or Loss transaction in local currency. For example (local currency ZAR): an invoice of 1 150 USD at RoE 0.05 = 23,000, and a receipt of 1 150 USD at RoE 0.06 = 19 166.67. The allocation is 19 166.67 / 1 150 USD, and the invoice keeps 3 833.33 outstanding for the Forex Loss. Previously, the allocation was 23,000, the receipt showed −3 833.33 outstanding and the Forex Loss could not be allocated. Existing allocations are unchanged: remove them and allocate again.
  • A Forex Gain or Loss transaction (local currency) no longer stays in the outstanding list after it is fully allocated.
  • Editing the allocated amount in currency now converts the local amount at the allocation’s exchange rate (and the other way round). Previously, the same number was copied to both.
  • In currency view, the Allocation screen now lists only outstanding transactions in the same currency that still have an outstanding currency amount.
• Fixed: Transactions > Exchange rate (RoE): Changing the RoE on a foreign currency transaction often left the other rate at its previous value, so the local totals were wrong (for example, the RoE was changed from 1.12 to 1.40, but the local total of 1 000 USD stayed 889.80 instead of 714.29). It now always updates the other rate (Local > Cur and Cur > Local) and recalculates the local totals of the items, also for Transaction Types without a customer or supplier.
  • On foreign currency items, MU% (a fixed sell price) and the price calculated from the cost and MU% (a fixed cost, for example, on estimates) now convert between the local currency and the transaction’s currency in the right direction. Previously, the rate was applied the wrong way round (for example, MU% 25.5% on an item sold below cost).
  • Existing transactions are unchanged by the upgrade. They are recalculated when the RoE or an item is changed.
  • The General Setting Accounting > Decimals in Currency (3 decimals) is now used for the totals of transaction items. Previously, item totals were always rounded to two decimals.
• Fixed: Price Lists > Delete: A Price List could be deleted while it was used in item prices or set as a customer’s Price List, which left those prices and customers pointing to a missing Price List. It can no longer be deleted while it is in use, and a message says where it is used.
• Fixed: Transactions > Default attribute sets when copying: When a transaction was copied in the same flow, the default Attribute Sets of the new Transaction Type were saved to the copy only and never shown (for example, a Sales Order copied to an Invoice did not show the Invoice’s default sets). They are now added to the flow; sets the flow already has are skipped, so a set is never added twice. Copies that start a new flow are unchanged: the new transaction gets its own default sets, as before.
  • The upgrade fixes transactions copied before: their hidden sets are added to the flow. If the flow already has the set, its blank values are filled in from the hidden set and the hidden set is removed, so each set appears once.
• Fixed: Form Designer and Preview > Connection lost: The Form Designer lost its data (or closed BOS with “We cannot connect to the database right now”) while its Preview tab was open, and leaving a preview or the Form Designer open for a few minutes dropped the database connection. Both now keep the connection.

Ver 2.4.1#

Enhancements#

• Transaction Types > Code: A warning is displayed when the Code of a Transaction Type is also used by other Transaction Types, and it lists those Transaction Types. Codes are compared without regard to upper and lower case or leading and trailing spaces. Transaction Types without a code are not checked. The warning is refreshed when you save the Transaction Type.
• Output Templates: Transaction output templates can show the Location Code of each line item (the location_code field in the transaction items data, next to location).
• Edit Reports > Copy Report: A Copy Report action was added to the right-click menu of the report list and to the Actions button.
• Proposals: The Caption and Item columns in the proposal items list were combined into one Description column. On a group row, enter the group’s name. On an item row, select the item from the dropdown list.
• Help > About: The About window shows a health check list, grouped by Computer, Application, Database and Internet, with the Check, Result, Status and Advice for each item. Use it when you contact support.
  • When the window opens, it shows the computer details (the Windows version, processor, memory, free disk space, screen, time zone, and number and date format) and the application details (the BOS version, the version, date and location of the .exe file, and the memory BOS uses). Items that need attention are marked with a warning and advice on what to do.
  • The Run button also tests the database connection (the connection, latency, PostgreSQL version, and the computer’s clock compared with the server’s) and the internet connection (latency, download speed and upload speed). The internet tests run in the background. A database latency of up to 100 ms is OK, up to 250 ms is a warning, and above 250 ms is a problem. For the internet connection, the limits are 150 ms and 500 ms.
  • The Copy and Save to File (a text file) buttons let you share the results with support.

Fixes#

• Fixed: Transaction Types: The error “Proposals can only be enabled if Pricing = Sell Price” was displayed when Pricing was set to Sell Price (Any Currency).
• Fixed: Ledger: An “Access violation” (or “Cannot assign a nil to a TFont”) error occurred when you opened or created a transaction from the Ledger and clicked Back to return to the Ledger list.
• Fixed: Entities: In the Entities list, Monthly Cost, production weeks per year and hours per week are shown as whole numbers, and Rate always shows two decimals.
• Fixed: Customer Age Analysis and Supplier Age Analysis: An “out of shared memory” error occurred when you opened Customer or Supplier Age Analysis, or printed or emailed a statement from it, in a company with many customers or suppliers. In these companies, the report was also slow to open.
• Fixed: Assets > Supplier: The error “invalid input syntax for type integer” was displayed when you saved an asset. The Supplier attribute on the asset edit view is now selected from the dropdown list of suppliers instead of being entered as text.
  • Note: The upgrade converts the supplier names already entered on assets to the matching supplier. If a name matches no supplier, or more than one, the asset’s Supplier is blank: open the asset and select the supplier again.

Ver 2.4.0#

Item Tracking (Batches and Serial Numbers)#

Tracking is turned on for each Transaction Type with the Inventory > Enable Tracking transaction setting (Batches or Serial Numbers). Below, “receive” and “issue” refer to transactions that receive stock in or issue stock out.

• Transactions > Expiry Date: An Expiry Date item column was added to transactions that receive stock.
• Transactions > Batch No.: A Batch No. item column was added.
  • When you receive stock, enter the batch number.
  • When you issue stock, select the batch from a list of the item’s batches that still have stock at the line’s location. The list shows the Batch No., Expiry Date and Qty Balance, with the soonest expiry date first. Each issue line takes one batch.
  • After you change a line’s location, save the line so that the list shows the batches at the new location.
• Transactions > Serial Numbers: Right-click the line item and select View/Edit Tracking.
  • When you issue stock, the window shows the Available serial numbers in stock at the line’s location (with their expiry dates, soonest first) and the Selected ones. Move them with the arrow buttons (Add Selected, Add All, Remove Selected and Remove All), or by double-clicking. You can still scan or enter a serial number. A message appears if the number is unavailable or is already selected.
  • An issue line needs a location before you can open View/Edit Tracking.
  • When you receive stock, enter or scan the serial numbers as before.
• Moving stock: Moving stock between locations (issuing it at one location and receiving it at another) works without any extra step.
• Warnings: Warnings are shown for each location. They do not stop you from saving, but you cannot click Done while they are shown:
  • Batches: “Batch received more than once”, “Batch issued Qty more than received Qty” and “Batch not received at the location”.
  • Serial numbers: “Serial Number received more than once”, “Serial Number issued more than once” and “Serial Number not in stock at the location”.
  • A serial number moved between locations is no longer reported as received twice.
• Copy: Copying a transaction or a line also copies its batch or serial numbers and expiry date.
• Items > Serial Numbers and Batches views:
  • The Serial Numbers view lists every item with its serial numbers, and shows the last received and issued transaction (coloured by transaction status) and the location. Filter by date (Received or Issued), category and status (In Stock or Complete), or search by serial number. A search looks across all statuses.
  • The Batches view shows the same information for batches, plus the Base Unit, Qty Received, Qty Issued, Balance and First Received date. The status is based on the remaining balance in the base unit.
  • In either view, use the Actions column or right-click a row to open the Item Summary, edit the item, or open the received or issued transaction. Double-click a row or press Enter to edit the item.
  • The Serial Numbers view appears only when at least one Transaction Type has Enable Tracking set to Serial Numbers, and the Batches view only when one has it set to Batches.
• Item Summary > View: The Movement, Reserved, On Order and Price History buttons were replaced by a single View dropdown button next to the Location caption. The button shows the current view, and the menu marks the selected one with a tick. New Serial Numbers and Batches views list the item’s serial numbers or batches at the location selected in the Location grid, filtered by In Stock or Complete. Double-click a row to open the received transaction, or use Actions to open the received or issued transaction.

Enhancements#

• Transactions > Link to From Transaction: A Link to From Transaction action was added to the transaction’s Actions menu, in the Update Transaction group under Link to Service. It links the open transaction to an earlier transaction in the workflow, for example, a Sales Order that was created on its own but belongs to a Quotation.
  • Select the From Transaction Type and number, then match each line to a line on the From transaction. Lines are suggested by item, and the Link to From Item list shows the description and quantity of each From line.
  • When you confirm, the transaction and every transaction created from it (e.g. a Delivery Note or an Invoice) join the workflow of the From transaction, together with their notes, attachments, attributes and project.
  • Matched lines reduce the outstanding quantity of the From lines.
  • Unlink From Transaction makes the transaction, and the transactions created from it, a separate workflow again. Before you confirm, BOS lists the transactions created from it that are unlinked too.
  • Note: Linking is only allowed when a Copy Rule exists from the From Transaction Type, and the From transaction is not cancelled or deleted.
• Transaction Types > Attributes in the list and edit views: Two transaction settings were added to choose which transaction attributes are displayed. Select from the attribute sets selected in Default – Attribute Sets. The attributes are shown in the order you select them, and each Transaction Type has its own selection.
  • Select Attributes to show in List View: Each attribute becomes a read-only column in the transaction list. Columns can be hidden or moved, and your saved layout keeps them. Numbers, dates and checkboxes sort correctly.
  • Select Attributes to show in Edit View: Each attribute gets an editor in the transaction header (in the fourth column, after Entity, Category and Terms). Changes are saved when you save the transaction. If the attribute’s set is not on the transaction yet, entering a value adds the set with its defaults.
  • Transaction attributes are shared across the workflow, so the Quotation, Sales Order, Invoice and the other transactions in it all show and edit the same values.
• Transactions > Prices in other currencies: When the price option is Sell Price (Any Currency), the sell prices in every currency are listed, not only those in the transaction’s currency. A price in another currency is converted to the transaction’s currency at the transaction’s exchange rate. Previously, the amount was copied unchanged (e.g. a THB price on a USD transaction).
• Attributes > Read Only: A Read Only checkbox was added to the attribute items grid of the Attributes setup. Copying an attribute set copies it. A read-only attribute cannot be edited in the Attributes window (Transactions, Projects, Items, Contacts and Assets), the item and asset edit views, the contact details, the estimate attributes or the transaction header. Default values are still filled in when a set is added.
• Estimates > Substrate (Square Metres):
  • The quantity in square metres uses the part area when the part has no printing imposition. Previously, it was 0.
  • Setup units are calculated from the setup worksheets multiplied by the worksheet area, plus the run waste %.
  • Quantities in square metres are no longer rounded up.
  • Substrate (Square Metres) items are included in the job weight.
  • Substrate SQM items can be selected in the bill of materials (BOM) of Costing and Assembly items.
  • On a Substrate SQM item, Add Attributes in the item edit view shows the item’s own attribute sets.
• Transactions: The Transactions module opens faster, especially in databases with many contacts. The Outstanding and Outstanding (cur) columns are available only when allocation is enabled for the Transaction Type.
• Statement of Profit or Loss and Statement of Financial Position: When you open them from Financial Reporting, the Set filter defaults to Fin Year (Months).

Fixes#

• Fixed: Output preview, print and email: Several causes of the “Access violation” error that some users still saw after Ver 2.3.0, when previewing, printing or emailing output, were fixed:
  • Loading a template that refers to a module that is not open yet (e.g. Projects).
  • Uploading files and email attachments.
  • Emailing a PDF when the template could not be loaded.
  • Sending emails from Emails > Send while previewing or printing at the same time. You can now close the Emails window during a send, and one failed email no longer stops the rest.
  • Losing the connection while a report prints or previews. The report now shows “Printing error” and closes, and BOS reconnects at your next action.
• Fixed: Emails > Send: Sending from the Emails window now records the Date Sent. Previously, it kept the date the email was created.

Ver 2.3.0#

Enhancements#

• Assets > Transactions (tab): A Transactions tab was added to the asset edit view. It lists the depreciation postings linked to the asset (the line items added by Add Depreciable Assets), with their transaction numbers, dates, references, descriptions and totals. Right-click a posting and select Open Transaction to open it.
• Entities > Staff View:
  • The view lists only the contacts that have the Staff attribute set.
  • The Status, ID No, Website, Position, Sales Rep, Project Resource, Timekeeping Resource and Hourly Cost columns were added, and the Entity ID, Entity, Note and Monthly Cost columns were removed.
  • An Actions > Batch Update option was added (see How to Batch Update Staff). It updates the Status, Sales Rep, Project Resource, Timekeeping Resource, Position or Hourly Cost of the selected staff members. Yes/No fields are updated with a checkbox.
• Staff Attributes: A Status field was added to the Staff attribute set, with the options Pending (the default), Active and Cancelled.
• Contacts > Addresses > Batch Update: Billing can now be selected for the Default field.
• Proposals: When a transaction that uses Sell prices is updated from its proposal, the customer’s Price List price is used. If the customer has no Price List price for the item, the Sell price is used.
• PoS > Open PoS Session: The list of active PoS sessions shows the entity, the date the session was opened and the till of each session.
• Output Templates: Transaction templates print the Category, Status and Credit Term in the transaction’s language, using the translations in the Language Editor. Text that has no translation is printed as it was entered. Existing templates do not need to be changed.
• Help > Knowledge Base: Opens this documentation site, bosdocs.vibecraftedsoftware.com.
• Performance: The main menu loads faster, the startup session check uses one query instead of three, and the periodic session check runs in the background, so the app no longer freezes while it runs. If the check cannot connect, no message is displayed and it checks again at the next interval.

Fixes#

• Fixed: Dates and time zones: Dates were calculated in the server’s time zone (UTC) instead of yours. For example, a PoS session opened at 01:30 in Thailand was filtered under the previous day, transactions copied between 00:00 and 07:00 were given the previous day’s date, and the Updated date and time were shifted by the time difference. Time zones with half-hour and quarter-hour offsets (e.g. +5:30) are now also supported.
  • Note: Records updated before this fix keep their shifted Updated date and time. They cannot be told apart from correct records, so they are not corrected.
• Fixed: PoS: The time zone was applied twice to the end time in the users’ session and timekeeping notes.
• Fixed: Print and Preview: An access violation could occur when you previewed or printed an output template on computers with German regional settings, or when the connection dropped. A report could also show the columns of the previous transaction. If a template cannot be loaded, an error is now displayed instead of a partly loaded report being printed.
• Fixed: Trial Balance: The current year’s profit was counted twice in Retained Earnings (Retained Income). The account now shows the opening balance only, so the Trial Balance balances for the financial year.
• Fixed: Transactions > Batch Update: A new Category was not saved.
• Fixed: Transactions > Copy Transaction: When a transaction was opened from another view (e.g. All Items), the copied items could come from a different transaction. If a copy fails, “Copy Failed.” is displayed and no items are copied.
• Fixed: Transactions > New (by entity): Creating a transaction for an entity did not run the same checks as New (e.g. the PoS till setting) and opened the selected transaction instead of the new one.
• Fixed: Transaction Types > Copy Categories From: Copying categories left the transactions that used the replaced categories with a blank Category. Categories can no longer be copied if any category of the Transaction Type is used by a transaction, and a message displays how many are in use.
• Fixed: Assets > Copy: The copy had an empty description, and each of its attribute sets was given all the attributes of the original asset. The copy now has the description (followed by “(Copy)”), code, status, type, entity, contact, status note, note and groups of the original, and each attribute set has only its own attributes.
  • Note: Assets copied before this fix keep their duplicated attributes.
• Fixed: Contacts > Addresses > Batch Update: Updating the Default field saved the wrong value.
• Fixed: Items / Assets: Menu options that did nothing were removed: the Actions button (Update Attributes in Items) in the item setup, and Menu > Edit Lookups in the asset setup.
• Fixed: Move Up / Move Down: Records and statuses with a missing or duplicate order number did not move correctly.

Ver 2.2.1#

Fixes#

• Fixed: Regional settings: An error occurred when the decimal symbol in the computer’s regional settings was set to a comma (,), as in German regional settings. Lookups could fail to load: the languages were missing, so the Language field on transactions was hidden, the main menu could be empty, and dates could be shifted.