Reset Search
 

 

Article

Open Integration, Limitations and Known Issues

« Go Back

Information

 
Article No:000012720
Question
CCH Open Integration,Limitations and Known Issues
Answer

Release Highlights  

Prerequisites  
1.              Limitations  
   1.1           General Limitations – Open Integration  
   1.2           General Limitations - Finsit 
   1.3           Xero  
   1.4           QuickBooks Online (QBO) 
   1.5           Sage Business Cloud (Sage One) 
   1.6           Twinfield  
   1.7           Exact 
   1.8           FreeAgent 

 
2.              Known Issues  
   2.1           Generic Issues applicable to all book-keeping systems  
   2.2           Xero  
   2.3           QuickBooks Online  
   2.4           Sage Business Cloud (Sage One) 
   2.5           FreeAgent: 

 

Release Highlights

These notes document the changes to Open Integration for the current release. They are intended for internal CCH use but are not confidential and can be sent to users.

Prerequisites

To be able to use the Open Integration within Accounts Production (AP) the user must enable the Task Permissions added to AP for the 2019.2 release (3.2).

1. Limitations

1.1 General Limitations - Open Integration

Open integration does not currently cater for 3rd party book-keeping systems using multi-currency. Currently the system is unable to warn users of multi-currency, so therefore please ensure all data integrated with OI does not have multi-currency.


Multicurrency not supported

1.2. General Limitations - Finsit

Transactions on first day of year may be missing - A single transaction may be missing in Finsit if dated on the first day of the year. Due to e resolved 12/08/2020.

Period report in Swedish - When a period report is sent to a user at an SME a paragraph can be added. The default paragraphs are in Swedish.

The only import method that OI users should use is Open Integration Import - This is important as it is hard to fix if a different option is chosen.

The client email links to the OneClick login page instead of the Finsit login page - We do not have date for this to be fixed.

You need to import all years to get the correct opening balances - Finsit will remove the choice, hopefully by 12/08/2020.

The button to launch the client email is in Swedish - This is expected by 12/08/2020.

The accounts receivable and payable report is not visible even though ticked for each bookkeeping system below. - Budgets are not yet available even though ticked for each bookkeeping system below.

The Finsit Balance Sheet may be out of balance - All mappings need to be corrected in Open integration. Otherwise the Finsit Balance Sheet may be out of balance.

Finsit does not support the Internet Explorer 11 Browser - After clicking on finsit launch, it doesn't redirect to the finsit URL.

1.3 Xero

Integration with finsit

The release of 4.2 introduced new integration with our new KPI and insights product finsit, not only is transactional data passed to finsit, but the following 4 specific end points were also implemented. Each booking system has its own limitations and these are documented below:
DivisionsScanned InvoicesAccounts Payable/ReceivableBudget Data
User-added imageUser-added imageUser-added imageUser-added image

Scanned Invoices

We are currently getting Scanned Invoices information for the following endpoints:
  • Invoice
  • Bank Transfers
  • Credit Notes
  • Bank Transactions
  • Receipts
  • Repeating Invoice
We are unable to retrieve scanned invoices for the following end points:
  • Contacts
  • Accounts (Not having functionality to upload attachment for Accounts endpoint)
  • Purchase Orders (which we are not implementing)
  • Manual Journals (We are calling journals endpoint for getting Manual journals data and it does not contain attachments related information).

Accounts Payable/Accounts Receivable (APAR)

Balance (outstanding) - the API does not take into account the date of partial payments or receipts, it just returns outstanding amount. If a partial payment is made on 1st June 2020 and you run a AP/AR report on 31 May 2020, you would expect the amount outstanding to ignore the 1st June 2020 part payment. Unfortunately, due to the APIs this is not possible.
Overpayments – The overpayments data is not flowing through the Xero API’s to OI. There is a different endpoint for overpayments in Xero that needs to be encorporated.

Budget Data

  1. Only the ‘Overall Budget’ can be synced from Xero to Open Integration, due to the Api response only providing the overall budget values.  You can only have one overall budget per organisation, but you can create additional budgets within Xero.
User-added image 
  1. Tracking Category associated with Budget summary is not available, due to the Api not provide tracking category data associated with the budget.
  2. Accounting Periods, the Overall Budget summary can only be returned for the current accounting period.
  3. Deletion of Overall Budget, is not covered in the Apis and therefore to reflect these changes, a user will need to Disconnect and Reconnect within OI.

1.4 QuickBooks Online (BDO)

Integration with finsit

The release of 4.2 introduced new integration with our new KPI and insights product finsit, not only is transactional data passed to finsit, but the following 4 specific end points were also implemented. Each booking system has its own limitations, and these are documented below:
DivisionsScanned InvoicesAccounts Payable/ReceivableBudget Data
User-added imageUser-added imageUser-added imageUser-added image

Scanned Invoices

In QuickBooks, one attachment is linked with multiple transactions. If one of transaction link is removed, then QuickBooks does not update their audit trail to indicate that the link to the specific transaction has been removed.  We are not able to remove that reference from transaction in ingestion service.  To get this working as expected, the user will need to disconnect and reconnect to their data in Open Integration.

Accounts Payable/Receivable

Journal Entries to Accounts Payable/Receivable are not reflected within the APIs and therefore not returned to OI

Budget Data

  1. Accounting Periods, the Budget summary can only be returned for the current accounting period.
  2. Deletion of the Budget, is not covered in the Apis and therefore to reflect these changes, a user will need to Disconnect and Reconnect within OI.

Note on mappings with QBO if using code numbers

We have used nominal account names in our mappings with QBO.  If you have added nominal code numbers to your nominal accounts, you will be required to undertake the exercise of mapping to the appropriate financial category in Open Integration.
 

1.5 Sage Business Cloud (Sage One)

Integration with finsit

The release of 4.2 introduced new integration with our new KPI and insights product finsit, not only is transactional data passed to finsit, but the following 4 specific end points were also implemented. Each booking system has its own limitations and these are documented below:
DivisionsScanned InvoicesAccounts Payable/ReceivableBudget Data
User-added imageUser-added imageUser-added imageUser-added image

Divisions

This functionality is currently unavailable, although a user can enter divisional information within the UI (Analysis Types), this information is not currently exposed to the API.  (https://developer.sage.com/api/accounting/guides/line_items/)

Accounts Payable/Receivable

Sales/Receipt or Purchase/Payment transactions which allows to do payment on account are not covered in Sage Business Cloud APAR functionality.

Budget Data

This functionality is currently not unavailable within Sage Business Cloud.
 

1.6 Twinfield

Integration with finsit

The release of 4.2 introduced new integration with our new KPI and insights product finsit, not only is transactional data passed to finsit, but the following 4 specific end points were also implemented. Each booking system has its own limitations and these are documented below:
DivisionsScanned InvoicesAccounts Payable/ReceivableBudget Data
User-added imageUser-added imageUser-added imageUser-added image

Scanned Invoices

We only support storing and retrieving the document link for Sales and Purchase ledgers entered via Basecone for this release. We also have only looked at PDF filetype as a source of the scanned invoices.

Accounts Payable/Receivable

Using newer Blue “neo” tiles for data entry
Twinfield does not have APi support yet for the newer “Neo” Blue Tiles.  One issue we have found is that Sales invoices entered via the Sales Invoice Blue tile can be marked as “paid”. The marking of “paid” does not update any existing Twinfield API, so we are unable to retrieve this information. We recommend the user pays via “Bank Data Entry” until Twinfield provide support for this.
Currently we do not support Journal entries made to Customer or Supplier accounts. We will look to support this in a future release.

Budget Data

Accounting Periods, the Budget summary can only be returned for the current accounting period.
Dimensions - associated with Budget summary is not available, due to the Api not providing the dimension data associated with the budget.

Other connections

Whilst you can use OI to connect with Twinfield and use finsit, you cannot currently connect Twinfield to CCH Accounts Production via OI.
We are considering this for a future release, as we have some work to do to support the synchronisation of Dimension data from CCH AP to OI.
 

1.7 Exact

Integration with finsit

The release of 4.2 introduced new integration with our new KPI and insights product finsit, not only is transactional data passed to finsit, but the following 4 specific end points were also implemented. Each booking system has its own limitations and these are documented below:

Divisions

Scanned Invoices

Accounts Payable/Receivable

Budget Data

User-added image

User-added image

User-added image

User-added image

Divisions

If a user recodes/edits a cost centre within the UI of Exact, the amendments do not get reflected as a change to the Transactions, and therefore because we are unaware that a transaction  has changed the changes made to the divisions do not flow through to OI. The only way to see these changes being reflected in OI, would be to Disconnect and Reconnect the business.

Scanned Invoices

    1. Deletion Issue – If User deletes attachments against given transaction, deleted attachments are not are not provided by Exact in API response.To resolve this, a user will need to disconnect and reconnect the business in OI.

    2. If we create Sales Invoice using "Send Based on Account", Exact creates different "FinancialTransactionEntryID" in Document API response. We still have handled it in Fresh sync (You have to disconnect a client then reconnect). It will not work in subsequent sync If you have added attachment without altering the transaction.

Accounts Payable/Receivable

In Exact, when we create General Journal for G/L account type “Acccount Payable” and “Account Receivable”  then the value of total comes as “0” and balance comes as expected in APAR details API Note – General Journal for G/L account Creditor and debitors in exact is working fine.

Budget Data

In Exact,  Past, Current and future financial year Budget data are displayed  in get api call but in all other Bookkeeping systems budget data are displayed for only current accounting period via get api call. There is a inconsistency the way bookkeeping solutions get API call represent budget data.

1.8 FreeAgent

We are unable to get transactional information from FreeAgents APIs, so currently we only support Trial Balance import.

Integration with finsit

The release of 4.2 introduced new integration with our new KPI and insights product finsit, not only is transactional data passed to finsit, but the following 4 specific end points were also implemented. Each booking system has its own limitations and these are documented below:

Divisions

Scanned Invoices

Accounts Payable/Receivable

Budget Data

User-added image

User-added image

User-added image

User-added image

Integration with Accounts Production (AP)

Accounting Periods

Due to the fact that we only integrate with FreeAgent at Trial Balance level, a pre-requisite to link to Accounts Production is that the accounting periods within AP must match those in FreeAgent.

 

2. Known Issues

2.1 Generic issues applicable to all bookkeeeping systems

VSTS 142520 – Data tab in OI is showing cached information from Azure Search Engine even after you disconnect and delete blob storage - When the user disconnects the business from OI this deletes the data in the storage. When they re-connect this loads fresh data in OI and addresses some issues with edited/modified transactions when doing synchronisations. However, we have found a bug in the Data “view” as it is behaving inconsistently and is incorrectly caching and showing data that has been deleted from storage.

VSTS 120047 – The ability to delete the data stored in Open Integration “blob” storage and re-create it to overcome data issues where data edited in 3rd party book-keeping systems - We have some scenarios in the various 3rd party book-keeping systems, especially QuickBooks Online and Sage One, where the data in OI does not get updated.

Typically, this occurs when the user has already synchronised the data and then has gone back into the book-keeping system and performed a certain task e.g. deletion of an invoice, edited transactions and moved them from one code to another.

For example, QuickBooks Online (QBO) has a feature called Products and Services which QBO users can use to move transactions from one nominal code to another. This issue we have is that a change using this method is not picked as a modification when we query the General Ledger API.

A work-around in this scenario, is to go to the SETUP tab, click on the Disconnect button, which will delete the data we store in the OI blob storage.


User-added image 

The data will be re-created when you do a new connection i.e. Go through SETUP tab configuring you source of data and pressing Connect. There is a pop-up message as a warning to prevent accidental disconnections.
User-added image 

VSTS XXXX – Accounting Period end date is 29th February - If the account end date is set to 29th February, it results in incorrect calculation of Financial periods in OI for Finsit.

VSTS 63817 - Creating new account in Exact/Xero, Sync. with OI from AP, there is an issue with the Deleting Account as using the Sync 2 Way: Account is still displayed - The user has created a new nominal account in book-keeping system, the Sync. with OI has been run the new account will be added as a client mapping. If you subsequently delete the mapped code in the book-keeping system this causes an issue when you run the Sync again the new account is still being displayed in the External Code.

VSTS 58439 - The organisation from 'Data Source' card, does not refresh automatically when you change the company - If the user changes the organisation in the Setup tab and selects Save there is a refresh issue on the Data Source card as it will not reflect the new organisation. The user will need to manually refresh the screen.

VSTS 156456 –

1.  If User has already synced with QuickBooks/Xero in Open Integration. Further He/she inactivates/deletes all the dimensions at QuickBooks/Xero and performs sync again. Bookkeeping Dimension Api does not reflect this change .

If at least one dimension is active,  Bookkeeping Dimension API will reflect results correctly.
2.  If user has already synced with Bookkeeping system in Open Integration and He deletes/inactivates one or more dimensions and performs subsequent sync. Transaction’s dimension information will not be updated. It is because dimension’s status change does not bring any change in transaction, hence it is not reflected at public Bookkeeping transaction API. User will have to disconnect and connect again to reflect correct dimensions information.

 

Xero
VSTS 146159 – Issue with period ends that do not match calendar month e.g. Sole traders with 5 April - Issue reported on a sole trader client having year end date 05 April 2020 where the sync adds both 2019 and 2020 figures when it brings the TB in. The TB figures when compared with ZERO we can see it is adding 2019 and 2020.

Issue is caused by Xero Trial Balance API which uses Xero’s old Trial Balance Report. Xero do not expose their Trail Balance (new) via API yet. No timescale given by Xero.
A work-around in this scenario, is to use the TB option only or disconnect and import TB into AP.
 

QuickBooks Online

VSTS 634599 – Editing, deleting or void a transaction - When using CCH OneClick 2.7 online release i.e. with full synchronisation between Accounts Production(AP) and Open Integration(OI) using QuickBooks(QB), there is an issue if you edit, delete or void a transaction in QB.

Any edit done in QB will be shown in OI but it will not flow through to AP. This is because QB does not keep a full audit trail.

VSTS 64552 - QuickBooks – transaction not balanced - At every synchronization the system, it sometimes fails when we see in AppInsights a transaction that do not balance e.g. like payments with one line.
We need access to the advisor’s client’s QuickBooks data to resolve this issue, but we are having some confidentiality issues with our users at present.

VSTS 141363 – Moving transaction from one nominal account code to another using QB Products and Services feature (via Sales>Products and Services) - Issue editing and moving transaction from one nominal account code to another using QB Products and Services feature (via Sales>Products and Services).
We use the QB General Ledger API to pick the transactions. The issue is the QB API does not appear to mark or update the Last Modified date and we do not therefore recognise a change in the OI data.
Work-around currently is to disconnect the data in OI and re-connect to flush and load new QBO data into OI blob storage.
 

Sage Business Cloud (Sage One)

VSTS 120347 – Issue in SageOne when transaction is edited - We have addressed the issue where a reversed transaction and the initial transaction come across as single transaction (basically grouping together as one doing an update i.e. not triggering a new transaction). The reversal did not appear in CCH Accounts Production after the synchronisation. This has now been addressed.

 

FreeAgent

Transactions are not downloaded individually, only as a Trial Balance - In the Data tab of OI the transaction stored from the trial balance has a date set to the last day of the financial period. For example if the accounting period is 1st Jan 2020 to 31st Jan 2020 then all the transactions in OI would be dated as 31st Jan 2020. So if we enter 1st Jan 2020 to 30th Dec 2020 in the date range filter of OI nothing would be shown.

Incorrect balances are shown for 29th February year end - If the account end date is set to 29th Feb, it results in incorrect calculation of Financial periods.

File Attachment 1 
File Attachment 2 
File Attachment 3 
File Attachment 4 
File Attachment 5 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255