Release Date: Rolling release beginning September 15, 2020

Versions Affected: QuickBooks Online Standard version

Improvements in v1.1

Improved data mappings for:

Invoices

Better handling of invoices without any lines. QuickBooks Online doesn't allow invoices with no lines, and they are always $0 invoices. Instead of presenting them as an error to the user (requiring the user to manually remove them in Manage if they don't want to see an error every run), we automatically mark them as batched and explain to the user in the task log "Invoice has no lines - not sent to QuickBooks".

better-handling

Use the Product ID in the GL Mapping for Deferred Revenue lines (IE: Down Payments). If no Product ID is specified then we'll default to "Down Payment".

product-id

Payments

Support for applying Credit Memos Credit memos must be created in Manage, and applied in QuickBooks Online. Payment records in QuickBooks Online that contain credit memos must only be applied to one invoice; a credit memo can be distributed across multiple invoices by separating it into multiple payments - this is required by how Manage handles credit memos differently from QuickBooks Online.

credit-memos

Better/more accurate payment sync. We have encountered some situations in the current version that could have caused a partial-paid invoice to have a larger payment applied to it in Manage than in QuickBooks Online. This is now resolved.

Expenses

Use the dateEnd from the expense report as the date of expense entries instead of the sync date.

date-end

Do not set the Payee to the employee for non-reimbursable expenses. This should make expense processing easier and less likely to accidentally pay an employee for a non-reimbursable expense.

payee

Inventory

Added unique identifier to the batch_id to ensure that they're unique. Now it won't fail to batch even if the same PO was received multiple times in the same day.

identifier

Supporting taxes on POs - added as a "Category" line applied to the tax account in Quickbooks Online for US, added as a Tax for other countries.

taxes

Added a warning when creating an item without a COGS account to preempt later problems receiving those items. Items without a COGS account can't be received, and it's no fun fixing lots of them later on when you could've fixed the GL mapping earlier.

warning

Improved error messages/error handling make troubleshooting easier

Quite a few improved/clarified error messages to make it easier to resolve issues with mismatched data.

improved-error

Fix bug where QuickBooks drops taxes from an invoice if the user hasn't completed their tax setup yet (US only). We now verify that the tax amount was saved as we sent it and when it isn't we remove the incorrect invoice and report an error to the user.

bug-fix

Add warning when creating an item without a COGS account to preempt later problems receiving those items. Items without a COGS account can't be received, and it's no fun fixing lots of them later on when you could've fixed the GL mapping earlier.

cogs-warning

Batch data view in the task log screen shows the data that we've received from Manage. This gives you a tool to determine when a data issue is because of bad data from Manage (usually a GL mapping issue), or if it's related to how we're interpreting the data.

batch-data

More complete invoice details

Sync CW invoice Reference field to QuickBooks invoice notes. This is especially useful for showing what period an agreement invoice is for. Better line description for discount invoice lines. Use the Product ID in the GL Mapping for Deferred Revenue lines (IE: Down Payments). If no Product ID is specified then we'll default to "Down Payment".

down-payment

Platform Improvements

Better Unicode support throughout the application (resolves some infrequently encountered bugs with special characters in some parts of the application). Container-based hosting for improved security, performance, and reliability. Usage of the ConnectWise REST API. The SOAP API that the current version was using is deprecated by ConnectWise and won't be supported in the future. Better backend logging - we get alerts on unexpected errors so, in many cases, we can resolve errors before they're even reported to us.

Read Next

Tags

Share

RSS Subscribe