AccountsIQ SOAP API Update Bulletin (17 06 2022) - accountsIQ/API-Wiki GitHub Wiki
Welcome to the API update bulletin!
You are receiving this as a registered user on our API who has opted in during your initial setup. This bulletin will notify you of any changes, additions and bug fixes made to the API in general.
These changes should not affect existing integrations. An update will only be required if you wish to take advantage of the new methods or fields added, unless otherwise stated.
Please refer to the API wiki for more details on the API, and contact us if you require a Postman Collection to be sent to you.
This method works exactly like CreateGeneralJournal however, it will return the created transaction IDs when needed for further processing. CreateGeneralJournalGetBackTransactionID.
Examples: Use this new method when creating a General Journal and the transaction ID is required for further processing, similarly to PostSalesCreditJournalGetBackTransactionID
A New field, AccountCode added to Invoice object
Status: Released Type: Enhancement
We have added the AccountCode in the Invoice object returned along the AccountID which was already present.
Examples: Now, after calling GetInvoice, you could directly call GetCustomer or GetSupplier providing this new value returned, saving one API call to find it by using its AccountID, as you would have done before.
Departments/BI Codes created with leading and trailing tabs or white spaces
Status: Released Type: Bugfix
Before this fix, leading and trailing tabs and spaces were included on the ID when creating a Department/BI Code (CreateDepartment). Now they'll be removed and not stored in the Database.
Examples: This caused issues for some integrations when copying and pasting IDs from an Excel spreadsheet or other source, where tabs or white spaces would be unknowingly added and would cause issues later when they tried to search or use these IDs.
Issue when Saving an Invoice, Order or Quote with a long Payment Method ID
Status: Released Type: Enhancement
Normalised the Payment Method ID data type across the system.
Examples: When sending a long 'PaymentMethodID' in the Invoice object, the value is truncated and an exception thrown. The field will now be saved as expected without issue.
Missing journal validations implemented
Status: Released Type: Bugfix
Ensure that an Account code exists before allowing it to be saved on any of the posting web methods. Ensure that a GL Account on journal lines are not of type control when using posting web methods.
Examples: These methods were allowing non-existent accounts and Control GL accounts to be processed and causing more issues later on and threw exceptions. These issues should not cause these more problems down the line in the process.