Notas de la versión 26.8 de Scope
Con tu ayuda, estamos mejorando Scope cada día. Estas son las últimas mejoras y funciones añadidas.
Changelog
= New feature
= Enhancement
= Bug fix
|
Type |
Area |
Description |
|
Upgrade Scope Runtime to 17.18.0 |
Scope runtime for MS Windows Server does not update itself automatically. Updates must be performed manually by a system administrator. |
|
Type |
Area |
Description |
| |
Air Export |
Storing House/IATA draft AWB(s) as documents linked to the airfreight file. Scope continues to open draft AWBs in PDF viewer but now additionally add the generated PDF to the shipment documents silently. Draft AWBs PDFs have new corresponding document types. |
| |
Air Security |
Approved Haulier EU database A new role ‘approved haulier’ got added in the partner profile to maintain approved haulier IDs. The previous transporteur ID field in the RegB partner profile got moved here. Users should manually validate vs. the EU database to ensure the correctness of existing data, or perform manual checks and manually add the expiration date. This can not be done by Scope. More information: New role approved haulier in Scope Approved hauliers' IDs are validated manually as well as via batch against the EU database in the same way as KC and RA, new credentials are not required. Approved hauliers' validation impacts the security chain calculation for EU shipments. |
| |
Shipment Monitor |
Shipment Monitor got a new option (via Extras > Cleanup) to cleanup exceptions. The action performs similar to the cleanup for milestones but instead of closing milestones it would close all exceptions which match the selected tracks and the given date range. |
| |
Scope API
Access |
We provide Scope API access for shipment data and documents. The API is primarily intended for Scope users operating their own customer portal. |
| |
Air Export |
FSR (Freight Status Request) message functionality removed The seldom used FSR feature in Airlines Messaging got removed - It’s successor feature, Airline Messaging Premium provides a much more easy , more reliable and automated fully integrated event data feed into Scope, with much higher carrier and event coverage, no requirement for a IATA/CASS registration and applicability for air import and simple shipments. |
| |
Air Export |
Changed trigger for Airline Messaging Premium subscription: Subscription to event updates is now triggered in the moment the IATA AWB is finished or printed, no longer in the moment the IATA AWB is entered. |
| |
Air Import |
Improved handling of deviating flights in air import: |
| |
Simple Shipment |
Added Airline Messaging Premium support for simple shipments air which are back-to-backs or houses shipments. Enhanced the existing logic which already worked for simple shipments air being master or directs. |
| |
Master Data + Air Export |
For agent role in partner maintenance, it is now possible to select a warehouse address for airfreight, if multiple warehouse addresses are maintained. The selected warehouse is used as default address in shipments. |
| |
Air Export | Show info when selected export warehouse differs from default partner warehouse. |
| |
Temperature control |
Support for the IFS Logistics Standard (https://www.ifs-certification.com/de/ifs-portfolio/standards/logistics-standard) which is another relevant certification for cool (and non-cool) freight, additionally to the already existing GDP Standard:
|
| |
Air Export / AOG |
Enhanced “Print freight as agreed” to carrier shipment templates Already existing for House shipment templates, the “Print freight As Agreed” setting got improved to apply from carrier shipment templates with higher priority as in “AWB Print Configuration” when calculating the “Print freight As Agreed” flag on the AWB. The feature now behaves consistent for houses and back-to-back/master/direct shipments, e.g. to ease handling of AOG shipments. |
| |
Air Export |
Added upcoming new IATA other charge codes ZM for Mandatory SAF Contribution / CO₂ compensation. The IATA Cargo Operations and Technology Board has proposed a new charge code which is expected to become valid. Note the usage of SAF other charge codes (ZD, ZE, ZM) does not have any impact on the CO₂ calculation. Assignable via Master Data > Finance > Charge Types for a charge type in Profiles > AWB Other Charges > IATA-Other Charge Code. |
| |
Air Export / Tracking |
Added event types CIMP_FOW and CIMP_FIW Although only available from some airlines via Airline Messaging Premium (see https://service.riege.com/en/knowledge/reliable-automatic-tracking-for-air-freight-main-carriage), Scope supports events FOW and FIW, e.g. in tracking templates. FOW = Freight out of (export airport = GHA) Warehouse (to tarmac) |
| |
Green Pixels |
Additional download option for CO₂ PDF report. In the CO₂ dialog, a convenience option got added to download and open the CO₂ report in a PDF viewer. |
| |
Air Export | Improved date suggestions for flights, derived from scheduled flight day and current month, especially for shipments from previous month. |
| |
Shipping Order Interface | We added more data fields to Scope Shipping Order XML interface, available with schema version 4.0. |
| |
Air Export |
Improved default date for flight month during flight entry, especially for 2nd, 3rd etc․ flight where the month should never default prior previous flight. |
| |
Air Export |
Improved default date for flight schedule lookup. |
| |
Air Export | Fixed export terminal partner not adopting automatically in an Air Export shipment when the departure airport changes and the airline is known. |
| |
Tracking Templates |
For automatic milestone completion, two criteria of same type but with different values should behave as logical OR - like with filters in homeviews. This did not work the expected way. |
| |
Green Pixels |
Misc minor improvement on ocean shipment CO₂ calculation and error handling. |
| |
Green Pixels |
CarbonCare: Fix calculation for pre- or on-carriage leg if the place of receipt matches the origin of the first main leg or the place of delivery matches the destination of the last main leg |
| |
Order Tracking |
Fixed flight fields having wrong language in order tracking emails. |
| |
Air Export |
Fixed some air freight tariff issues for gross weight and DGR tariffs. |
| |
Event Interface |
Fixed event code CCD not processed for inbound event interface. |
| |
Air Export |
Error sending eAWB when dimensions missing or invalid in AWB tariff lines. |
|
Type |
Area |
Description |
| |
Sea Import FCL Oncarriage and Freetime Handling on General Tab |
We have completely redesigned the oncarriage tab within the goods tab now showing the three main stages terminal - delivery to door – empty return to depot with more details, automatic updates from inbound events as well as freetime calculation on container level pre-defined by user on the general tab. |
| |
Ocean Carrier EDI |
We have teamed up with the EDI portal “Coneksion” to offer a broader coverage to connect Scope with ocean carriers and NVOCC’s, which comprises booking requests and responses, shipping instructions and seawaybill draft responses, VGM and responses, ocean events; |
| |
Portsystems Dakosy EMP |
Scope supports Dakosy EMP by the PortOrderXML interface. Scope customers using the integration with Dakosy have to sign a new contract with Dakosy for switching to new interface while the old interface will by shut down by Dakosy by end of the year 2026. |
| |
DUX order (Dakosy) |
We have enhanced the “Dux without MRN” order type to allow more than one position. |
| |
Portbase MID |
Portbase MID Procedure has been enhanced, so that the terminal id, the customs reference and the container number of the relating outgoing MID message is stored with the procedure, allowing to search for specific procedures. By doing that, the NL customs procedures can prevent automatically creating duplicate MID registrations, preventing errors at Portbase. |
| |
IMP Status (Dakosy) |
Received IMP Status messages, for which Scope Events are created, are now linked to the relating container for which the original IMP order had been issued. By that change, the Scope Events might now trigger an update of import container movement data (for that container). |
| |
IMP Status Codes |
The IMP Status code list has been updated, now holding more (maybe still not all) of the codes provided by Dakosy. |
| |
VGM Weight Validation |
Additional weight validation has been implemented for the VGM: In case the entered weight is “0” or less than the tare weight of the container, an error is shown and a related Vermas message may not be sent. |
| |
Portbase Cargo Controller |
Following two changes have been implemented for the portbase cargo controller messages: A subscription can not be created / transmitted for consolidatable shipments anymore (i.e. for house / house fcl) and when changing the shipment type of a shipment which has been registered at portbase for cargo controller messages, the registration will be voided in case the selected new type is “master with house / house fcl”. The new master then can be registered again for the same bl number. |
| |
Generic FCL Events |
When receiving Portbase Cargo Controller Webhook events, events for “DISCHARGE” and “GATE_OUT” now also trigger Generic FCL Handling. By that change, these events might set/update import container movements. |
| |
Pre-Alert |
The prealert dialog, which can be opened from the shipment editor (air/sea import) to show the relating prealert now also displays the edi reference of the prealert. |
| |
Ocean Carrier EDI |
Messages from INTTRA (e.g. booking confirmation) do allow for a wider characterset (e.g. German Umlauts). |
| |
Sea Export / Import via Hamburg |
We have improved the appearance of dangerous goods on Dakosy order documents. |
| |
Sea Import |
We have enabled the revenue print selector on arrival notices globally. |
| |
Sea Export and Sea Import |
We have implemented a stronger validation of OBL numbers to comply with the standard. |
| |
FCL Transport Order Sea Import |
We have further improved the defaulting of references captured in shipment, also pulling from new oncarriage container level data. |
| |
Sea Import Pre-alert |
We have improved the data integration for UN/Location codes, in particular for unofficial codes of seaports in pre-alerts. |
| |
Portbase | No bug within Scope, but fixing problems at Portbase, when registering MID procedures twice on different shipments. Background is some automated registration triggered in Scope (from NL customs methods). Additionally when reindexing MID Procedures, some properties (terminal ID and customs reference) were not initialized properly and were not visible in the Portbase appliance. That is fixed too now. |
| |
Freight Term switch-back | The problem of “switching back” freight terms (prepaid/collect) to the old (previous) value, when storing a shipment in air / sea has been fixed. |
| |
Ocean Tracking |
Fixed a bug when processing Gatehouse Events without container number |
| |
Container Movements |
Fixed a bug that resulted into Container Movements not being updated from master when consolidating a House FCL onto a Master shipment. |
| |
Ocean Tracking |
Fixed a bug that resulted into existing shipments not getting events after activation of ocean tracking. |
| |
Ocean Carrier EDI |
Fixed a bug that resulted into real shipper and consignee being transmitted to INTTRA in case of self-filing AMS. |
| |
TransportOrder XML |
Partners in Scope with a code containing a space were not valid in TransportOrder XML. This has been fixed in the schema to allow spaces for addressIds. |
| |
(Export) Ocean Consolidated Superhouse |
A bug was fixed that allowed on consolidated superhouse in the sea export module to add containers after the superhouse has been consolidated on a master. |
| |
Booking from Quotation |
A bug was fixed in booking created from a quotation where a non-standard pickup address was used but not taken over. |
| |
Sea Import Superhouse FCL |
We have fixed a bug which caused duplicated goods lines in house shipments when created within the superhouse quick-create workflow. |
| |
Dakosy |
Fixed a crash in the Dakosy dimension entry, if all dimensions have been left empty. |
| |
Dakosy |
Fixed a crash when trying to open a Dakosy message after Dakosy has been disabled for the branch. |
| |
Ocean BL |
Fixed a crash when emptying Shipper in the Ocean BL dialog. |
| |
Sea Carrier EDI |
When receiving responses on a sea carrier booking (e.g. from Inttra) and parameter ‘seaCarrierEdi.SEA_CARRIER_EDI_NOTIFICATION_EMAIL’ is set, Scope filed an exception in case this parameter contains an invalid email address. This has been fixed now. |
|
Type |
Area |
Description |
| |
ATLAS SumA |
In der Positions-Ansicht des ATLAS SumA Homeviews kann nun mittels Rechts-Klick auf die jeweilige Position eine neue CUSPRL (SumA) Vorgang aus den vorliegenden SumA Daten angelegt werden. |
| |
ATLAS SumA |
Im ATLAS SumA Homeview wurde in der Positions-Ansicht die Mehrfachselektion für die über einen Rechtsklick verfügbaren Programmaktionen hinzugefügt. |
| |
ATLAS WKS |
In der Positions-Ansicht des ATLAS SumA Homeviews kann nun mittels Rechtklick auf die jeweilige Position eine E_EXS_DAT (ASumA) aus den vorliegenden SumA Daten angelegt werden. |
| |
ATLAS WKS |
Ausgehende ATLAS WKS Nachrichten können nun zusätzlich an ein externes System über die Scope Dokumentenarchiv Schnittstelle übermittelt werden. Dies kann im Geschäftspartner der jeweiligen Niederlassung in der Rolle ATLAS Deklarant konfiguriert werden |
| |
ATLAS WKS |
Im ATLAS WKS Homeview wurde in der Detail-Ansicht jeweils eine Spalte für die angemeldeten, die überlassenen und die offenen Packstücke hinzugefügt. |
| |
ATLAS WKS | Im ATLAS WKS Homeview wurde die Programmaktion “Manuell erledigen“ hinzugefügt. Diese kann über einen Rechtsklick auf den jeweiligen Vorgang aufgerufen werden. |
| |
ATLAS AES |
Scope kann nun aus den verschiedenen Sendungstypen sowohl anhand einer MRN einen konkreten Ausfuhrvorgang finden als auch über die Bezugsnummer. Dies ist insbesondere dann hilfreich, wenn eine Ausfuhranmeldung noch nicht an den Zoll übermittelt wurde. |
| |
SCI |
Bei der Übermittlung einer SCI XML-Nachricht für das Verfahren ATLAS AV ist die Angabe des Elements removalAmount nun optional. |
| |
SCI |
Für die Angabe des Container-Indikators in einer SCI XML-Nachricht wurde das optionale Element transportInContainer für die E_EXP_DAT und E_DEP_DAT hinzugefügt. |
| |
Dokumenten-schnittstelle / ATLAS WKS |
Es ist nun möglich, ausgehende ATLAS XML Nachrichten für den Verfahrensbereich WKS über unsere Standard Dokumentenschnittstelle zu empfangen. Die technische Dokumentation ist unter dem nachfolgenden Link zu finden: https://riege.github.io/scope-document/atlas-xml.html Diese Funktion steht aktuell so nur für den Verfahrensbereich ATLAS WKS zur Verfügung. |
| |
ATLAS Statistik Zolllager |
In der Zolllager-Bestands- und Bewegungsliste gibt es nun einen neuen Filter „Abweichung-Bestandsinformation“. |
| |
SCI | Es wurde ein Fehler im Mapping korrigiert, bei dem der Warenort der E_EXS_DAT (ASumA) nicht richtig übernommen wurde. |
| |
ATLAS WKS | Es wurde eine fehlende Validierung für das Packstück Zeichen ergänzt. |
| |
ATLAS EAS | Die Warenbeschreibung unterstützt nun sowohl bei der manuellen Erfassung als auch beim CSV-Import die mit ATLAS AES 3.0 eingeführte maximale Feldlänge von 512 Zeichen. |
| |
ATLAS Artikelverwaltung | Die Warenbeschreibung unterstützt nun auch in der Artikelverwaltung die mit ATLAS AES 3.0 eingeführte maximale Feldlänge von 512 Zeichen. |
| |
ATLAS AES | In der Nachricht “Nachtrag zur Anmeldung zur Ausfuhr“ (E_EXP_AMD) wurde eine fehlende Validierung auf dem Netto- bzw. Bruttogewicht ergänzt, da man in dieser Nachricht entweder beide Gewichte oder gar keins angeben muss. |
| |
ATLAS AES | Verbesserung der Verarbeitung bei Dienststellenwechseln im Exit-Prozess: Nach Schließung einer Ausgangszollstelle kann nun der neue Dienststellenschlüssel ohne Fehlermeldung verwendet werden. Scope zeigt hier nur noch einen gelben Warnhinweis anstatt einer roten Fehlervalidierung. |
| |
ATLAS NCTS | Der Zollstellenfilter lässt sich nun wieder problemlos bedienen. Ein Hängenbleiben beim Öffnen der Dropdown-Liste wurde behoben. |
|
Type |
Area |
Description |
| |
Passar Ausfuhr | Durch eine Checkbox in der Rolle BAZG Deklarant: Abruf der EVV Belege kann verzögert werden auf den Folgetag um 4:00 Uhr morgens. |
| |
Passar | Es ist nun möglich Zusatzabgeben zu berechnen, wenn Daten importiert werden per SCI oder CSV. |
| |
Passar Ausfuhr | Positionen - Bewilligungen - Zusatzinformationen; es wurden weitere Codelisten hinterlegt. |
| |
Passar Einfuhr | Die neue Nachricht NI062 Vorselektion zur Kontrolle WA-E wurde implementiert. |
| |
Passar Einfuhr |
Es gibt die Option, dass man Dokumente via Chartera Input an den Zoll übertragen kann. Dafür Rechtsklick auf den Status - Dokumente anzeigen öffnen und den Tab Chartera anklicken |
| |
Passar Einfuhr |
Es wurde für Passar Einfuhr ein neues Feature zur Berechnung der Zusatzabgaben gebaut. |
| |
ISF Filing | Die Validierung für das Feld Warenbezeichnung wurde auf max 1000 Zeichen verlängert. |
| |
Passar Einfuhr |
Mit Rechtsklick auf den Status - Dokumente anzeigen - Chartera - gibt es einen Reiter Dokumente, welche auch die Sendungsbezogenen Dokumente anzeigt. |
| |
Passar Ausfuhr | Das Dokument 9541 - digitales EUR 1 ist nun als Begleitpapierzulässig und wird nicht rot validiert. |
| |
Passar | In der Artikelverwaltung wurden neue Felder für Zollbegünstigung und den Zollansatz ergänzt. |
| |
Passar Ankunftsanmeldung | Verbesserung im UI: Wenn der Haken bei Abladebemerkung konform gesetzt ist, verhindert eine rote Validierung, dass im Feld Abladebemerkung etwas eingetragen werden kann. |
| |
Passar Einfuhr | In der Übersicht der Verpackungen sieht man nun auch die Versandzeichen als Spalte. |
| |
Passar Einfuhr |
Neue Nachricht NC075 - Bedingungen Akzeptanz Warenanmeldung wurde implementiert. |
| |
Passar Einfuhr |
Neue Nachricht NC076 -Bestätigung der Richtigkeit wurde implementiert. |
| |
Passar Einfuhr |
Neue Nachricht NC077 - Antwort Bestätigung der Richtigkeit wurde implementiert. |
| |
Passar Ankunfts-anmeldung |
Verbesserung im UI: Wenn der Haken bei Abladebemerkung konform gesetzt ist, verhindert eine rote Validierung, dass im Feld Abladebemerkung etwas eingetragen werden kann. |
| |
Passar Druchfuhr |
Wenn eine technische Ablehnung einläuft, wird bei der neuen NT015 die Dossiernummer mitkopiert. |
| |
Passar Ausfuhr | Wenn auf eine WA-A mit Verfahrensbeteiligter eine Korrektur angelegt wird, wird diese nun korrekt kopiert. |
| |
EDEC Import | EVV Belege werden ca. 4:00 Uhr des Folgetags abgeholt. Durch eine Checkbox in der Rolle BAZG Deklarant kann die EVV von e-dec Import noch später abgeholt werden. Somit ist die Bordereau Nummer in der XML wieder vorhanden. |
| |
EDEC Import | Spalten in der Dokumentenansicht können vergrößert/verkleinert werde. |
| |
EDEC Import | Schnellere Kommunikation mit dem BAZG über Webservice. |
|
Type |
Area |
Description |
| |
Customs NL | When registering MRN documents using the options will result in a corresponding event available to Order tracking. Register Export MRN → scp.customs.EXPORT_MRN_REGISTRATION Register Import MRN → scp.customs.IMPORT_MRN_REGISTRATION Register NCTS MRN → scp.customs.NCTS_MRN_REGISTRATION |
| |
Customs NL | When a DMS reminder message (Documents. Supplemental declaration) is received a Pending Customs event will now be registered on the corresponding shipments, for usage in Order tracking - Exceptions, with the event scp.customs.PENDING.CUSTOMS |
| |
Customs NL | With the SCIN it is now possible to process an SCIN message for an NCTS departure, including auto-calculation and auto-send. |
| |
Customs NL | In the NL Customs Profile of an article it is now possible to indicate that for NCTS /DVA only 6 digits of the entered HS code are to be used. |
| |
Customs NL | Create DMS from XLS has been changed, it now also supports write-off information for supporting documents (CERTEX) “0005:NR1:2026-08-01:LIFE:1:100:KGM:1000.00:EUR,N853:NR2:2026-08-01:LIFE:1:100:KGM:1000.00;EUR” |
| |
Customs NL |
NL Customs Reporting has been extended with reporting on VWA declarations. |
| |
Customs NL | In creation DMS declarations from XLS/CSV the mapping of Customs Value did not work. This is now solved. |
| |
Customs NL | Defaulting of the Country of Origin in DMS declarations is improved. In case of preference 2xx or 3xx it will now be defaulted as preferential Country of Origin. In other cases it will be defaulted as non-preferential Country of Origin. |
| |
Customs NL | The sending of Documents for DMS declarations with representation status 3 failed. NL Customs did handle this in the past differently so an adjust was made. Now NL Customs handles this according their specifications so the adjustment is now removed. |
| |
Customs NL | Added logic to not update the customs order reference when CHED number ends on “XXXXX” |
|
Type |
Area |
Description |
|
|
Web services |
A new Quotation API is now available, enabling external systems to create and manage quotations in Scope. In this initial release, external applications can create and view quotations. Quotation creation is currently limited to general quotation data without income and costs information. Future releases will extend the API with additional functionalities, including:
For detailed documentation, see: https://riege.github.io/scope-rest-webservices/quotation-api.html |
|
|
Web services |
To support the new Quotation API, additional master data APIs have been introduced:
These APIs provide access to the master data required when creating quotations through external parties. For more information and API documentation, see: |
|
|
e-Invoice France |
A new interface has been implemented to receive e-invoices from an accredited platform for Scope branches in France, ensuring compliance with French e-invoicing regulations. E-invoices received through the Accredited Platform are automatically imported into the Accounts Payable Import Appliance in Scope. Scope does not yet support the issuance of electronic invoices or the submission of e-reporting data required under the French e-invoicing regulations. Support for these features is planned and will be available in Scope well ahead of the compliance deadline of September 1, 2027. For more information, see the knowledge base article: https://service.riege.com/en/knowledge/scope-e-invoicing-support-in-france |
|
|
Accounts Payable Import |
The Accounts Payable Import Appliance now supports prepaid invoices, including prepaid e-invoices from countries such as Poland and France. The Accounts Payable Import Editor now indicates whether an invoice has been partially or fully paid. Once the invoice is posted in Scope, the prepaid amount is automatically transferred to the Scope Payment module, provided that the module is enabled and payments are entered manually in Scope. |
|
|
Accounts Receivable | The Invoice Information dialog in the Accounts Receivable editor, which displays invoice metadata, now also shows correction invoices that were created for the current invoice. This provides greater transparency into the relationships between invoices. |
|
|
Invoice Overview |
An optional Cost Center column has been added to the read-only Invoice dialog in the Invoice Overview appliance, allowing users to view the cost center assigned to each invoice line together with other accounting-related data. |
|
|
Activity Types | Activity types associated with a cost center must now be assigned to the cost center's branch. This makes it explicit that activity types linked to a cost center are valid only within that branch. |
|
|
Document Types | A new document type, “Party Credit Information” has been added to Scope for uploaded documents. Documents classified with this type are included in exports via the document archive interface. |
|
|
Quotations | Fixed an issue where the secure shipper check for the automatic activation of the Security Measure order type on air export quotations incorrectly used the prospect partner instead of the consignee partner. |
|
|
Accounts Payable |
Resolved an issue that prevented Accounts Payable entries in Poland from being finished when the KSeF e-invoice integration was enabled. This fix has been backported to Scope Release 26.6. |
|
|
Accounts Payable Import | Resolved an issue in the Accounts Payable Import appliance where ZUGFeRD e-invoices with minor PDF document issues were not recognized correctly. |
|
|
Payments (Invoices) | Fixed an issue that occurred when opening an invoice to be canceled via the link in the title of the Payments (Invoices) editor. This issue could result in an incorrect open balance being displayed in the Payments (Invoices) overview. |
|
|
Estimates | Fixed an issue where cost centers on estimates were not updated when a customs declaration, originally created without a shipment reference, was assigned to a shipment after the customs assessment had been imported into Scope. |
|
|
Consol Profit Analysis |
Fixed an issue that prevented the consol profit analysis from being performed. The fix has been backported to Scope release 26.6. |
|
|
Partner Editor | Fixed an issue in the partner editor where partner groups assigned to the current partner were not displayed. Additionally, the error icon has been removed for groups to which the current partner is not assigned. |
|
|
XRechnung | It is now possible to create a German XRechnung even when the invoice issuer has only a German Tax ID and does not have an EU VAT ID. |
|
|
KSeF Interface |
Fixed an issue in the KSeF interface where outgoing invoices were incorrectly rejected if the invoice recipient's tax ID contained a whitespace character, for example in Swiss CH UID VAT numbers. The fix has been backported to Scope release 26.6. |
|
|
QR Bill |
Fixed an issue that caused UBL e-invoice generation to fail in certain cases when QR bill generation was enabled. The fix has been backported to Scope release 26.6. |
|
|
Document Archive Interface |
Resolved an issue in the document archive interface where invoices imported through the Accounts Payable Import appliance were not exported. The fix has been backported to Scope release 26.6. |
|
|
Partner API | Fixed an issue in the Partner API that caused child debtor profiles to return incorrect account numbers under certain conditions. |
|
|
Order API | Resolved an issue in the Partner API that prevented the “Status to Billed Date” from being returned in API responses. |
|
|
Partner Editor | Fixed an issue that allowed the partner editor to be closed despite validation errors related to partner group assignments. |
|
|
Quotations | To prevent incorrect totals in very rare cases, all amounts are now recalculated before a quotation is saved. |