Requirement: 

To enable this functionality, the connector program must be installed on the same physical or virtual machine as the Sage software.


Features:

1.Customers:


  • Export Customers from ServiceBox to Sage50.
  • Import Customers from Sage50 to ServiceBox. 


Limitation:

  • Currently, ServiceBox lacks the capability to set payment terms on a customer level and synchronize this data with Sage50; however, this enhancement is planned for implementation in our backlog.


2.Jobsites: 


  • Jobsites in ServiceBox will be displayed under Shipping Address field on the invoice in Sage 50


Limitation: 

  • Due to the absence of the 'sub-customer' concept in Sage 50, ServiceBox lacks the capability to synchronize Jobsite information with Sage 50. Sage 50 typically revolves around a customer-centered approach. Nevertheless, ServiceBox employs the Sage 50 SDK, enabling the display of Jobsite addresses in the 'Shipping Address' field on invoices when the synchronization with Sage 50 occurs.



3.Invoices :

  • Export Invoices from ServiceBox to Sage50. 
  • Invoices are marked as paid in ServiceBox once the payments have been received in Sage50 (or downloaded from ServiceBox) to the full amount of the invoice.
  • Sales taxes are linked between ServiceBox Tax Levels and Sage50 sales taxes.
  • Enables customers to opt for either their ServiceBox invoice number or their existing Sage50 invoice series. This choice affects the displayed invoice number after synchronization. If Sage50 invoice numbers are selected, ServiceBox invoice numbers can be included in the memo field for streamlined cross-software reference.
  • Customer's can choose that the invoice notes initially displayed on the ServiceBox invoice remain visible on the synced invoice in Sage50. 
  • Customer can also choose to import work notes into a Sage Invoice. 


Limitation:


  • Just setting an invoice to 'Paid' in ServiceBox will not mark the invoice as paid in Sage50 because Sage50 requires payments in the full amount of the invoice to consider it paid. 
  • ServiceBox will not create items in Sage's Inventory and Services list, however if an item in that list is an exact match to an item used on an invoice, the item will be used..
  • Due to the large number of business rules in any accounting system related to changing already posted transactions, ServiceBox cannot update Sage50 invoices post-sync.  If absolutely required, re-syncing an invoice by deleting the invoice in Sage is a possible work around.


4. Payments: 


  • ServiceBox does have the ability to import payments as receipts into Sage 50, however due to limitations in the Sage 50 development kit, the approach we had to take is not supported by Sage 50 and is used at the customer's risk.
  • ServiceBox also offers a 'manual' import, displaying a list of payments from ServiceBox that have not been entered into Sage and allowing the user to mark those payments as imported.


Limitation:

  • Payment on an invoice should be either created in ServiceBox or Sage50. Create the payment in both will result in a duplicate payment record in Sage.
  • If payment received on invoice in Sage50 payment records are not uploaded back into ServiceBox, just the invoice status is marked as Paid.
  • In order to prevent potential data integrity problems during the synchronization of data from SB to Sage 50, ServiceBox has provided various payment choices and limited the automatic payment synchronization option when Sage is operating in multi-user mode. For additional information, please access these articles by clicking on the provided links.:
    1.Sage 50- Payment Options
    2.     Sage: Introducing Automatic Payment Sync Control in Multi-User Mode


5.Timesheets:

  • Due to limitations in the Sage 50 development kit, there is no facility to automatically download timesheet data into Sage 50. Nevertheless, our technical team is actively exploring alternative solutions, such as importing data through spreadsheets, and we have plans in our pipeline to develop a workaround specifically aimed at addressing the needs of Sage 50 customers in the near future.

6.Inventory :

  • Inventory items used on invoices downloaded from ServiceBox should have the quantity removed from the total quantity on hand.
  • When inventory line items are utilized in invoices and subsequently synced to Sage50, they are cross-referenced with existing inventory line items using an exact name match, provided they are present at the invoice level.


Limitation: 

  • While we presently do not facilitate a direct synchronization of the inventory list between ServiceBox and Sage50, it's worth noting that this feature is on our agenda for future development.


7.Vendor/vendor order:


Limitation:

  • Once a Vendor Order is transmitted to Sage50 with a status denoting item receipt, ServiceBox lacks the capability to subsequently modify the receipt (Bill) in Sage50; however, we do offer alternative solutions to address this situation.

8.Product/Services List: 


  • Export Inventory/Services from Sage50 to Non-Inventory items in ServiceBox.
  • Items used on Invoices are matched with existing Inventory/Services items via exact name match.
  • As new items are created in ServiceBox and used in invoices, they will be added to your Inventory/Services list in Sage50.


Limitation: 

  • Revenue accounts for new items are created based on item category not individual items. Expense accounts are not set with new items created by the sync.
  • The fact that Sage 50's SDK does not grant us the capability to update pricing from Sage 50 to ServiceBox. This limitation restricts the seamless transfer of pricing information between the two platforms, leading to the current inability to synchronize pricing data effectively.





FINAL NOTE: ServiceBox, by design, is not meant to replace your accounting system. Rather the sync to Sage50 is meant to prevent or at least decrease the amount of double entry required to update your books.

Charges applied: 

ServiceBox will be implementing a nominal charge for the unlinking of data when users switch from one company file to another within the same accounting software. 

 

Here's why this charge is necessary:

 When users switch company files within the same accounting software, such as QuickBooks Online (QBO) or QuickBooks Desktop (QBD), it can lead to unintended consequences. One significant concern is the risk of linking invoices or other data to incorrect customers due to the way ServiceBox manages data linkage based on unique IDs. For instance, if Customer A has the ID 2344 and you move from Company File A to Company File B within QBO, there's a possibility that Customer B in File B could inadvertently share the same ID as Customer A, leading to data misalignment.

It's important to note that this policy applies specifically to transitions between company files within the same accounting software. If you decide to switch from one accounting software to another (e.g., from Sage to QBO), you can do so without incurring any charges or encountering the same issues.