History¶
Including all features, bugs and fixes released up until 3.2024.9.1
Features¶
This section contains a table that lists the features that were included in our releases. This article will be update with each release.
| Release Version | ID | Title |
|---|---|---|
| - | 848 | New Import for KBC CAMT053 |
| - | 858 | Parameters for invoice match on totals |
| - | 1365 | Add data entity on reconciliation rules |
| - | 2200 | Bankstatement number shown in F&SCM on journalline level |
| - | 2201 | Additional reconciliation rules for payment reference |
| Toolkit | 1371 | Toolkit - Added CustPackingSlip which can be used in the email templates body and description |
| 3.2024.8.3 | 2453 | Addition of CAMT053 ING bank Czech format |
| 3.2024.8.3 | 2595 | Report license variable and pipeline update |
| 3.2024.7.2 | 2539 | Activate 9A License report functionality - Extended Banking and Extended Banking Advanced |
| 3.2024.7.1 | 2353 | License report solution for Extended Banking and Extended Banking Advanced |
| 3.2024.7.1 | 2441 | Extended Banking menu improvements and additions |
| 3.2024.7.1 | 2183 | EB - Fill in LegalSequenceNumber in field ‘Document’ for KBC files |
| 3.2024.3.4 | 2171 | 3.2024.3.4 |
| 3.2024.3.4 | 2172 | 3.2024.3.4 |
| 1.0.1.61 | 2188 | Remove check if there is an external purchid but the record does not exist |
| 1.0.1.43 | 880 | Extension point in class PylWFVendInvoiceProposalPost method createJournalLine |
| 1.0.1.29 | 2186 | CAR report warning fix on class PylEBLedgerJournalCheckPost_Extension, method pylEBUpdateStornoSettlement |
| 1.0.1.29 | 1369 | Hash function fails if document is not available |
| 1.0.1.29 | 2191 | Add hash code value to vendor payment journal header |
| 1.0.1.29 | 2195 | Storno history not updated correctly on incassos with multiple invoices |
| 1.0.1.29 | 1364 | Number sequence issue when deleting bank statement to register resources |
| 1.0.1.24 | 856 | Reconciliation search history |
| 1.0.1.24 | 857 | Settled and Matched filters move to filter section on form |
| 1.0.1.21 | 878 | Extended banking - New Reconcile type ‘Open customer invoice - Foreign currency’ |
| 1.0.1.21 | 879 | Default currency code incorrect when selecting a customer (AV task 565) |
| 1.0.1.13 | 1354 | EB Advanced - make sure that any errors which are shown are more ‘user friendly’ |
| 0.2022.0.0 | 904 | New import method for Rabobank Belgium |
| 0.2022.0.0 | 906 | Extended Banking BP improvements |
| 0.2022.0.0 | 915 | CAMT053 - Support foreign currency bank account in multiple currencies |
| 0.2022.0.0 | 1093 | EB - RaboBank transactions in different currencies |
| 0.2022.0.0 | 1099 | EB - Vereffening allen functie houdt geen rekening van teken. Functie markeert een ontvangen klantbetaling met credit nota. |
| 0.2022.0.0 | 1103 | MT940 German - Sparkasse |
| 0.2022.0.0 | 861 | Add remittance information in settlement form |
| 0.2022.0.0 | 862 | Remittance info is gone when a line is deleted in the journal |
| 0.2022.0.0 | 883 | Labels renamed from Pylades to 9altitudes |
| 0.2022.0.0 | 884 | Extended Banking - Missing index on table PylEBLedgerJournalCustVendInv |
| 0.2022.0.0 | 885 | RegEx validator |
| 0.2022.0.0 | 961 | CAMT DK Extending changes required for customers |
| 0.2021.0.0 | 899 | Multi Company Bankstatements |
| 0.2021.0.0 | 948 | HASH totals banking (3185 - BR6!) |
| 0.2020.0.0 | 997 | Extended banking - Payment reversal |
| 0.2020.0.0 | 1000 | CAMT053 ABN AMRO support |
| 0.2020.0.0 | 1001 | Specify “Method of Import” for Importing bankstatement via IO |
| 0.2020.0.0 | 1019 | BNP CAMT053 |
| 0.2019.0.0 | 1026 | Localization CZE - extended banking ING-CZ |
| 0.2019.0.0 | 1029 | Bij bankontvangst staat nooit een factuurnummer (‘zie specificatie oid’) -> in dat geval alleen matchen op klant bankrekening |
| 0.2019.0.0 | 1032 | Swift\BIC koppelen aan bankrekening van klant |
| 0.2019.0.0 | 1126 | Inlezen bankafschrift bij verzamelbetalingen |
Bugs & Fixes¶
This section contains a table that lists the bugs and fixes that were included in our releases. This article will be updated with each release.
| Release Version | ID | Title |
|---|---|---|
| Removed | 2571 | Remove check if there is an external purchid but the record does not exist |
| 3.2024.8.3 | 1108 | KNOPPEN “Settle transactions” en “Reconciliate” inactief maken als Journaal status is Posted |
| 3.2024.7.1 | 2399 | EB - Search Term doesn’t look for Vendor account |
| 1.0.1.31 | 2187 | Fields Matched, Settled and icon NotSettled are not updated when changing the account type |
| 1.0.1.30 | 2190 | Import of Danish bank file fails with error “Instance of an object” |
| 1.0.1.29 | 1357 | Vendor bank account being linked to vendor erroneously |
| 1.0.1.28 | 826 | Storno not being processed correctly |
| 1.0.1.24 | 855 | Credit notes not taken into consideration in case of positive payment |
| 1.0.1.24 | 859 | Storno settles with credit note - error at posting |
| 1.0.1.24 | 860 | Reconciliation for credit notes not working |
| 0.2022.0.0 | 1121 | EB - Error icon “Niet vereffend” op journaalregel bij rekeningtype Grootboek is onjuist |
| 0.2022.0.0 | 1122 | Bankafschriftnummer vullen in veld Document |
| 0.2022.0.0 | 1123 | EB - Reconciliation sometimes takes too much time |
| 0.2022.0.0 | 1136 | Offset account changes when reconciliate general journal bankstatement. |
| 0.2022.0.0 | 1079 | Payment reversal not working |
| 0.2022.0.0 | 1083 | Function “Link bank account” in journal lines does not work in case of a vendor account |
| 0.2022.0.0 | 1085 | EB: Add check on Approved of vendor transaction for settlement |
| 0.2022.0.0 | 1090 | Hang up form Bank statement to register |
| 0.2022.0.0 | 1106 | Workspace Bank statements to register heeft zwarte letters terwijl andere blauw zijn. |
| 0.2022.0.0 | 1107 | Kan record niet verwijderen in form Bank statements to register na verwijderen journaal. |
| 0.2022.0.0 | 905 | CAMT053: DateTime format of elements - Error: String was not recognized as valid DateTime. (Simac 582) |
| 0.2022.0.0 | 907 | CAMT: import end balance (closing date) of bank statement incorrect in case of multiple bank statements, bank accounts, and cross company |
| 0.2022.0.0 | 922 | EB parameter Skip bank statement when bank account is not found does not support CAMT053 |
| 0.2022.0.0 | 947 | Vendor Invoice not reconciled |
| 0.2022.0.0 | 953 | Extended Banking Tag CreDtTm ABN AMRO |
| 0.2021.0.0 | 960 | Settle multiple invoices in one payment |
| 0.2021.0.0 | 979 | Invoice numbers of 20 characters can’t be posted |
| 0.2021.0.0 | 987 | Remove function “Reversal settlement” in bank journaal. (Cleanup retired functionality) |
| 0.2021.0.0 | 989 | CAMT053 Hungary error “Company bank account 109180010000000655720001 cannot be found” (AutoBinck) |
| 0.2021.0.0 | 991 | CAMT - Zoekt op oude nummer in plaats van op IBAN “BE59001784715326” |
| 0.2021.0.0 | 992 | Can’t process CAMT file from ABN AMRO |
| 0.2021.0.0 | 994 | CAMT053 - add account holder’s name to description field |
| 0.2021.0.0 | 995 | File extensie van download CAMT053 bestand |
| 0.2021.0.0 | 946 | Search on Customername in CAMT053 is not recognized |
| 0.2021.0.0 | 1042 | CAMT053 - Date of journal line should be based on ClosingBooked date of balance statement |
| 0.2020.0.0 | 1045 | Storno code not imported with import format MT940 ING NL bank |
| 0.2020.0.0 | 1074 | Method of payment should not set |
| 0.2020.0.0 | 996 | CAMT Hungary error “String was not recognized as a valid DateTime.” tijdens aanmaken journaal (AutoBinck Hungary) |
Detailed Notes¶
This section contains the workitems mentioned in the above sections, with additional details and applicable notes
2539¶
- Title: Activate 9A License report functionality - Extended Banking and Extended Banking Advanced|
- Release: 3.2024.7.2
- Type: User Story
- Notes 9altitudes is continually improving the way we bring
our ISV solutions to market, both directly and through partners. In line with
best practices in standard Microsoft solutions, we now collect telemetry data
on the actual usage of our solutions starting from this release. This usage
data is anonymized before leaving the customer’s environment and is sent to
9altitudes. The information is gathered once a week and shared with 9altitudes. Only this
anonymous data is leaving the customers environment and is used by 9altitudes
to validate alignment of the usage with the contractual agreement between the
customer and 9altitudes. If any excess usage is detected, the system will continue
to function properly, but 9altitudes may reach out to the customer to discuss
alignment with the contract.
1123¶
- Title: EB - Reconciliation sometimes takes too much time|
- Release: 0.2022.0.0
- Type: Bug
- Notes EB - Reconciliation sometimes takes too much time