Notas de la versión 26.0 de Scope

¿Busca notas detalladas de versión 26.0 de Scope?

Changelog

= New feature
= Enhancement
= Bug fix

**Scope general**
Type	Area	Description/Note
	Task management	Task management feature active per default after the completion of the piloting phase. See https://service.riege.com/en/knowledge/task-management for details.
	Upgrade Scope Runtime to 17.14.1 “Fall 2025”	Scope runtime for MS Windows Server does not update itself automatically. Updates must be performed manually by a system administrator.
	Order Tracking	Added “is/is-not Booking” applicability filter. It is recommended to use this new filter only on Milestones, not on Tracking Template applicability. This feature supports to create tasks automatically for the phase when a shipment is still a booking or for the phase after a booking became a shipment. See https://service.riege.com/en/knowledge/how-can-tasks-be-created-automatically for details.
	Interfaces	Sort options for EDI profile mapping tabs to allow easier identification of mapped entries.
	Scope home view	Tooltip on branch information in Status Line as well as on the branch switcher menu has been enhanced to show complete information (ORG, LE, BRA, Branch-Partner).

**Air**
Type	Area	Description
	Air Security	If a screening order has been issued for an air export shipment, then formerly the eAWB contained Field content of “Additional Security Information” from Security History and Screening instructions from the Screening order. This has been changed to include in the eAWB: Field content of “Additional Security Information” from Security History (unchanged) and Additional Security Information (formerly named Screening Remarks) from the Screening order result.
	Air Security	Added a new document type for EU air security risk analysis (“Risk analysis” / “Risikoanalyse”) This feature supports upload of documents related to new EU air security regulations on shipment level. Adding an explicit document type allows to complete milestones in Order Tracking depending upon upload of this specific type See https://service.riege.com/en/knowledge/how-to-automatically-complete-order-tracking-milestones-via-documents for details.
	Master data	Added a warning if partner codes contain characters that are not Riege Standard XML interface conform, because them containing special characters.
	Air Export	Removed superfluous AWB copies during AE finish.
	Tour	Fixed sequence in Tour where the start is not assigned to a business partner and when adding a transport order.
	Bug fixes	Air Security master: proceed without confirming security status not possible if master contains unconfirmed houses Fix duplicate preCarriage leg in CarbonFootprint calculation for special cases Fix duplicate onCarriage leg in CarbonFootprint calculation for special cases Tasks not moved from booking to shipment on conversion

**Ocean**
Type	Area	Description
	Sea Import Master, Houses and Transport Orders	Sea Import Master now includes container movement type: Delivery to door. By adding these Dates on either master or house, when creating a new delivery order, the planned container delivery time will be defaulted from there. Otherwise the time will be defaulted from houses requested date of delivery.
	Softcoded B/L Layouts	The B/L layout editor now shows the size of the preview image in pixels (width/height) for .img, .jpg, .gif, .bmp and displays a warning in case the values are too big. Information is shown to support the maintenance of layouts.
	Sea Import	Arrival agent partner must have a liner agent role to be available for selection. This is an alignment with the behavior in sea export.
	Simple Shipment	Users can be restricted for creating a shipment copy as we have introduced a permission.
	Dakosy	Dakosy connection supports shipments number length greater 16 by using a compressed USI as forwarder reference.
	Sea Export	BL Layouts support country sensitive formatting of numbers, decimals, dates, monetary amounts with currency.
	Sea Export & Import	We made the temperature obligatory for relevant container types (reefer, insulated, tank) if the box for temperature controlled is checked.
	Sea Export & Import	Ocean carrier name for sailings of the DBH (Germany only) schedule gets displayed properly and is taken over into shipment when selected.
	Sea Export & Import	To be able to exclude/hide shipments from the overview we have added a new filter criteria “is not” in addition to existing “is not part of the group”.
	Sea Export	Added a new field for loading reference in bookings for carrier haulage.
	Sea Export	Scope to submit the carrier bookings for FCL also in Version 3 of INTTRA’s IFTMBF which was already in place for LCL carrier bookings
	Sea Export	Changed order of the pages on House Bill of Lading / House SeaWayBill: terms and conditions now always last page of the PDF version
	Prealert	It is now possible to receive a sea import master prealert with consolidated house FCL prealert(s) by EDI (from the CC) and convert the master prealert into a sea import master shipment with consolidated house FCL shipment(s).
	DBH	DBH Communication changes to a single FTP for all customers which will improve the setup for new customers and the issue tracing for existing customers.
	Tracking	Fixed an error in ocean tracking where an empty return event came as a full gate in event.
	Ocean Carrier EDI	Fixed a bug where a `forwarding:GenericFCLEventSpecialHandling` job failed due to some non-reproducible database issue.
	Portbase	Fixed a bug, where an exception during an API call of Portbase (for subscriptions) resulted in being unable to store sea import shipments.
	Transport Order Overview	Fixed a Bug where the totals, pieces, weights and number of containers where not pulled/updated correctly from the parent shipment.
	Transport Order	Fixed a bug where the transport order XML message was missing the shipment data for a simple shipment of type road.
	Sea Export	Fixed a bug where the booking confirmation editor did not display the charge lines to select or de-select.
	Sea Import	When consolidating import house shipments from a different branch onto an import consol master, the handling units got lost on the house shipment. This bug has been fixed now.
	Portbase Webhook Events	When receiving Portbase Webhook Events in Scope and trying to store the converted message, an exception occurred in case the goods descriptions of the event were longer than 512 characters. This issue has been fixed by truncating the goods information before storing the data.
	Sea Carrier EDI Clearing Center	When subscribing a shipment with a SCAC and booking/BL number at Gatehouse a later change of the shipment, where the booking/BL number is changed by prepending the SCAC code or by removing the originally prepended SCAC code no new subscription is sent to Gatehouse anymore.
	Vessel Schedule	We have fixed broken sailings which don’t contain date-time for departure or arrival. They can be adjusted manually after selecting them.
	Settings	We have fixed an upload button for the HBL Layout which was missing for users on Windows operating system.
	Transport Order	Customs orders data have been made visible on the container transport order editor’s general tab. Users are able to dismiss the data too.

**Customs DE**
Type	Area	Description
	IntraStat	Es wurden einige Verbesserungen an unserem IntraStat Modul sowohl für die Erzeugung der Bestandspositionen als auch für die Bearbeitung der Meldedateien implementiert: Nun kann die IntraStat Meldedatei auch ohne die Rolle IntrastatPartner im eigenen Geschäftspartner erstellt werden. Es wird automatisch ein IntraStat-Bestand angelegt, wenn in der Zollanmeldung das Verfahren 42 oder 63 angemeldet wurde und Steuerlicher Verweis FR1 (Einführer) existiert mit Rolle IntrastatPartner, oder Steuerlicher Verweis FR3 (Fiskalvertreter) existiert mit Rolle IntrastatPartner. Ein weiterer Punkt, der verbessert wurde ist die EU-Erwerber-Logik. Es wird nun in jeder Bestandsposition die EU-Erwerber Adresse mit der Adresse aus dem steuerlichen Verweis FR2 gefüllt. Es ist jetzt auch möglich, Positionen unabhängig vom Sendestatus zu löschen. Wenn der Sendestatus gesetzt ist, gibt es vorher eine Warnung: “Es wurde bereits eine Meldedatei erzeugt und möglicherweise übermittelt.“ Außerdem gibt es eine neue Aktion im HomeView, mit der auch erzeugte Meldedateien direkt gelöscht werden können. Beim Löschen wird der Transferstatus aller zugehörigen Positionen zurückgesetzt.
	ATLAS - NCTS	Users can send the presentation of AES-MRN, which are destined to be taken over into transit from out of the NCTS declaration Inside the NCTS declaration users can take over all goods item data into the single house shipments from the Exit Allowance received in AES
	Scope SCI	Direkte Lieferung von “weiteren Lieferketten-Beteiligten“ über die Schnittstelle Es gibt in der Scope SCI Struktur jetzt ein eigenes Element für die Angabe weiterer Lieferketten-Beteiligter. Die Struktur ist im `countryDEImportType` angesiedelt und heißt `additionalDutyReference`. Sie enthält den FR-Code plus die EORI-Nummer. Damit entfällt der Umweg über die Umsatzsteuer-ID.
	ATLAS AES	In ATLAS AES kann nun IHB-konform eine Beipack-Position erfasst werden.
	ATLAS Einfuhr	Der Actionlink zur Aufteilung der Frachtkosten wurde in allen Verfahren zur endgültigen oder vorübergehenden Einfuhr vom rechten Bildschirmrand an den linken Bildschirmrand verschoben.
	ATLAS Einfuhr	Wegfall der Vorbelegung der Unterlage D008 Bei Warentarifnummern, für die Antidumpingzölle anfallen könnten, hat Scope die Unterlage D008 vorbelegt. Da dieser Unterlagencode mittlerweile in mehrere unterschiedliche anzuwendende Dokumente aufgeteilt wurde, entfällt in Scope künftig sowohl die Vorbelegung als auch die Warnung, wenn ein User die Unterlage D008 entfernt hatte.
	ATLAS AES	Scope hatte die maximal zulässige Anzahl von Zeichen in der Warenbeschreibung einer Ausgangs-SumA fälschlicherweise mit 280 validiert, obwohl 512 Zeichen erlaubt sind. Dieser Fehler wurde korrigiert.
	ATLAS Einfuhr	Validierung der EU-Codes ‘E01', 'E02' und '8E2’ Scope prüfte die o. a. EU-Codes gegen die “Art des Geschäfts” = ‘32' statt '12’. Der Fehler wurde korrigiert.
	ATLAS SumA	Im ATLAS SumA Homeview wurde der Status des Vorgangs nicht richtig angezeigt, wenn eine Position zollseitig storniert wurde. Dieser Fehler wurde behoben.
	ATLAS Einfuhr	Wenn in ATLAS Einfuhr die Positionsdaten per CSV Import erzeugt wurden und der Nettopreis der einzelnen Positionen in einer anderen Währung als EUR mitgegeben wurde, hat Scope dem User erstmal eine rote Validierung angezeigt, die ausgesagt hat, dass die Währung des Kurses nicht mit der Währung des Betrags übereinstimmt. Dieser Fehler wurde behoben. Es wird keine Validierung mehr angezeigt und der Umrechnungskurs ist direkt nach dem Positionsimport vorhanden.
	ATLAS NCTS	Beim Erstellen einer Versandanmeldung aus einer Luftfracht-Importsendung heraus werden House- und Master-AWB korrekt in die Vorpapiere und nicht mehr in die Unterlagen übernommen.

**Customs CH**
Type	Area	Description
	Passar Durchfuhr	Der AccessCode einer Sicherheit wird nun verschlüsselt in Scope angezeigt. Diese Verschlüsselung kann mittels Passworteingabe aufgehoben werden.
	Passar Ausfuhr	Wenn Fahrzeuge verzollt werden, müssen unter Zusatzinfo bestimmte Felder ausgefüllt werden. Es wird nun eine Codeliste gezogen für die Fahrzeuge.
	Transport-anmeldung	Die AEO Nummer wird nun aus den Stammdaten des Geschäftspartners (Rolle zugelassener Wirtschaftsbeteiligter) vorbelegt, falls vorhanden.
	Passar	Unter “Dokumente anzeigen” sind nun alle Dokumente sowie die E-Mail-Registerkarte sichtbar. Zudem ist es möglich, Dokumente erneut ans Archivsystem zu senden.
	Aktivierung NC123	Wenn ein Vorgang aus einer Luftfrachtsendung gestartet wurde, wird nun bei der Aktivierung NC123 der Luftfrachtbrief vorbelegt.
	Passar Ausfuhr	Um die Vorlagen besser nutzen zu können, ist das Textfeld unter Zusatzinformationen kein Pflichtfeld mehr.
	e-dec Export	zur Vorbereitung der Abschaltung des Moduls e-dec Export per 31.12.2025 haben wir eine neue Berechtigung gebaut, die es zur Zeit erlaubt, einen neuen e-dec Export Vorgang anzulegen. Nach dem 1.1.26 werden wir diese Berechtigung auf allen Scope Systemen entziehen. So stellen wir sicher, dass ab Neujahr keine neuen e-dec Export Vorgänge angelegt werden können.
	Passar Ausfuhr	Falls die TN ein Nettogewicht verlangt, gibt es nun eine gelbe Validierung im entsprechenden Feld
	Passar Durchfuhr	Die Sicherheit wird aus den Stammdaten des Verfahrensinhabers gezogen.
	Ankunfts-anmeldung	Es gibt neu die Möglichkeit, eine Spalte mit der Referenz ZE anzeigen zu lassen sowie nach dieser Referenz suchen zu können.
	Passar WA-A	Die Packstückinformationen Master/Bypack werden validiert, ob die Angaben plausibel sind und die Korelations ID wird automatisch übernommen.
	Passar SCI	In einem Scope Customs Event wird nun das Element ItemCount mitgeschickt.
	e-dec Import	Wenn in den Stammdaten ein Zollansatz hinterlegt ist, wird dieser automatisch gezogen. Ein Richtigcode muss gesetzt werden.
	Passar	Schreibweise der Status angepasst auf Gross-/Kleinschreibung
	EDEC Import	Status für terminiertes Senden auf “Geplant” geändert, sodass dies besser erkennbar ist.
	Passar Ausfuhr	Das Gewicht wird aus der Sendung in die erste Position übernommen. Korrigiert der User das Gewicht, wird die Differenz in die nächste neue Position übernommen.
	Passar Allgemein	Die Dokumente in Passar werden nun über eine neue Methode abgeholt und sollten damit nun korrekt in Scope dargestellt werden. Teilweise waren Dokumente doppelt eingelaufen.
	Passar Ausfuhr	Nach einer freigegebenen WA-A ist nun kein Rückzug mehr möglich.
	Passar Ausfuhr	Die Regel NS30108 wurde in Scope implementiert. Bei bestimmten Ländern und Konstellationen wird die Zahlungsmethode zum Pflichtfeld.
	Passar Durchfuhr	Nach einer abgelehnten WA-nD wird nun unter Neue Nachricht die NT513 Korrektur einer WA-nD angezeigt.
	Passar Ausfuhr	Wenn aus einer Sendung eine WA-A erstellt wird, werden die Daten nun korrekt aus der Vorlage übernommen.
	Passar Ausfuhr	Die Korrektur einer Transportanmeldung funktioniert nun korrekt, ohne Validierungsfehler der Sendungsnummer.

**Finance**
Type	Area	Description
	E-Invoicing	A new interface has been implemented to enable sending and receiving e‑invoices via the Peppol network for Scope branches in Belgium, ensuring compliance with national e‑invoicing regulations. To send e‑invoices Peppol participant IDs must be maintained in the field buyer electronic address (BT‑49) on the debtor role of the partner. When an outgoing invoice is issued, its status will temporarily appear as “finish pending” until confirmation is received from the Peppol service provider. Incoming e‑invoices from the Peppol network are automatically imported into the Accounts Payable Import appliance in Scope. Additionally, users can configure an email notification to be informed whenever new Peppol e‑invoices are received. To configure an email notification, please contact the Riege Service Team. The new Peppol interface has also been backported to Scope release 25.10 to ensure general availability on Jan. 1st.
	Accounts Payable Imports	When Scope is connected to an e‑invoicing network such as Peppol, all incoming invoices are automatically retrieved and imported into the Accounts Payable Import appliance. However, some invoices - typically administrative cost invoices - should not be booked in Scope and instead belong in an external system, such as an accounting system. In addition, these external invoices often should not be visible to all Scope clerks. To support these evolving requirements, the Accounts Payable Import appliance has been enhanced. At the customer’s request, an invoice classification function can be activated. Scope distinguishes between invoices that must be booked in Scope and those that should not. When classification is enabled, Scope attempts to automatically identify invoices that must be booked in Scope. This is done when a vendor partner with a creditor role has been matched and/or when the invoice could be matched to an order in Scope. Such invoices are assigned the familiar status Open. Invoices that are intended for an external system must be marked as Not for Scope. Once marked, these invoices cannot be booked in Scope. They can still be downloaded from the document tab of the Accounts Payable Import editor or forwarded via email using the email tab, in the respective local e‑invoice format (e.g. Peppol BIS Billing). The email address autocompletion offers all contacts maintained on the current branch partner, making it easy to forward such invoices to the correct external team or system. Optionally, access to invoices that have not yet been classified or that are intended for external systems can be restricted to selected users via a new permission. This ensures that not every clerk has access to non‑operational invoices. To activate invoice classification, please contact the Riege Service Team.
	Aggregated Invoices	Scope now supports the creation of aggregated outgoing self‑billing credit notes within the Aggregated Invoice appliance. The appliance introduces a new workflow that allows users to generate outgoing self‑billing credit notes based on cost estimates from multiple orders. Depending on master data configurations, Scope automatically aggregates cost estimates per partner into new entries of the type “Self‑Billing Credit Note” shown in the upper table of the appliance. These can be converted into new outgoing self‑billing credit notes using the lower table. To activate the feature and ensure that only applicable entries are available for the creation of self‑billing credit notes, the following configurations must be changed: Charge type activation: A new option is available in the Charge Type editor to mark a charge type as eligible for aggregated outgoing self‑billing credit notes. This setting is stored on legal‑entity level. Creditor activation: The creditor profile has a new configuration option that designates the creditor as eligible for aggregated outgoing self‑billing credit notes. Both settings need to be active for a given charge type to be self-billed to a given creditor.
	Accounts Payable Imports	Entries in the accounts payable import appliance can no longer be deleted when the invoices were received via the Peppol network. Invoices received through this channel that should not be booked in Scope must now be moved to one of the following statuses to indicate that they should not be further processed: Rejected: The invoice was rejected due to its content. Not for Scope: The invoice is addressed to an external system (for example, an accounting system) and should not be booked in Scope.
	Shipment overview	The detailed and grouped reports on shipment overview now display the user name instead of the user ID.
	Partners	The partner spreadsheet export on partner overview now includes the seller’s electronic address from the debtor partner role.
	UBL E-Invoice Export	The UBL namespace prefixes used for UBL e-invoice generation have been changed. Scope now adopts the standard prefixes commonly used in UBL, including cac, cbc, ext, n0, qdt, sac, sbc, and udt.
	Accounts Receivable	An issue has been resolved where new cost estimates were incorrectly added as taxable to an existing invoice issued to a tax‑free recipient on an export shipment in the EU. The system now correctly adds these estimates without taxes, as expected for tax‑exempt exports.
	Accounts Payable	An issue has been resolved where the cancellation and re‑submit workflow for imported accounts payable was losing information: The accounts payable file was missing on the cancelled invoice The re‑submitted invoice did not retain the marker indicating that it originated from an imported invoice Both issues have now been corrected, and all relevant information is preserved throughout the workflow.
	Contracts	The sanction list check is now triggered automatically for customers when opening the Contract editor.
	Shipment Editor	An issue has been resolved where an unpaid invoice was incorrectly shown as “Partially paid” on the invoices tab in the Shipment editor. This occurred for invoices that had previously been marked as paid.
	Accounts Receivable	Several issues affecting the bank account selection during the creation of QR Bills in Switzerland have been resolved. These fixes ensure correct and consistent bank account handling when generating QR Bills and have also been backported to Scope release 25.10.
	CFDI	The validation rules for CFDI correction credit notes have been updated. If the original invoice does not include withholding taxes, charge types with SAT code 84111506 can now be added to the correction credit note in addition to the charge types already present on the original invoice.
	Enhanced Credit Limit Check	Previously, clerks were required to manually estimate duties and tax amounts for ATLAS Einfuhr customs procedures as a part of the enhanced credit limit check when Scope calculated a zero amount. This has been corrected and clerks no longer need to enter an estimated amount in such cases.
	Order API	An issue has been resolved where carrier partner details were missing for transport orders returned by the Order API. The API now provides the carrier information correctly.
	E-Invoicing	Automatic sending of invoice emails based on the debtor‑role setting failed when the invoice was transferred via Peppol. This has now been fixed, and it is possible to send an invoice email in addition to an e‑invoice.

Notas de la versión 26.0 de Scope

Con tu ayuda, estamos mejorando Scope cada día. Estas son las últimas mejoras y funciones añadidas.

Changelog