Ich nutze den Hibiscus Payment Server und bekomme beim Kontoauszugs-Abruf seit kurzem den Fehler "Auftragsart nicht unterstützt".
Es liegt vmtl. an der Einstellung "Umsätze im neuen SEPA CAMT-Format abrufen"
Wie können wir diese Einstellung im Hibiscus Payment Server vornehmen???
Schonmal Danke, Thomas.
Thu Nov 27 10:45:53 UTC 2025 Name: INFO, Level: 100: Führe Geschäftsvorfall aus: "Kontokorrent, IBAN..: abrufen"
Thu Nov 27 10:45:53 UTC 2025 Name: INFO, Level: 100: Führe Aufträge aus...
Thu Nov 27 10:45:53 UTC 2025 Name: INFO, Level: 100: adding job SaldoReq to queue
Thu Nov 27 10:45:54 UTC 2025 Name: INFO, Level: 100: adding job KUmsAll to queue
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: executing check for job SaldoReq
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: execution state: tan needed: false, tan-cancel: false, executed: false, success status: false, error status: false
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: global status:
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: job status:
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: mark job failed
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: Error while fetching balance of account: Unknown Error
Thu Nov 27 10:45:55 UTC 2025 Name: WARN, Level: 300: Error while fetching balance of account: Unknown Error
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: executing check for job KUmsAll
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: mark job unsupported/failed
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: Auftragsart nicht unterstützt
Thu Nov 27 10:45:55 UTC 2025 Name: WARN, Level: 300: Auftragsart nicht unterstützt
Thu Nov 27 10:45:55 UTC 2025 Name: WARN, Level: 300: found errors or synchronization cancelled, mark PIN cache dirty [have error: true, interrupted: false]
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: closing resources
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: closing pin/tan passport
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: pin/tan passport closed
Thu Nov 27 10:45:55 UTC 2025 Name: ERROR, Level: 500: error while synchronizing
org.kapott.hbci.exceptions.HBCI_Exception: error while creating new job KUmsAll
at org.kapott.hbci.manager.HBCIHandler.newJob(HBCIHandler.java:417)
at de.willuhn.jameica.hbci.synchronize.hbci.HBCISynchronizeBackend$HBCIJobGroup.executeJobs(HBCISynchronizeBackend.java:338)
at de.willuhn.jameica.hbci.synchronize.hbci.HBCISynchronizeBackend$HBCIJobGroup.sync(HBCISynchronizeBackend.java:273)
at de.willuhn.jameica.hbci.synchronize.AbstractSynchronizeBackend$Worker.run(AbstractSynchronizeBackend.java:401)
at de.willuhn.jameica.system.Server.startnow(Server.java:149)
at de.willuhn.jameica.hbci.synchronize.AbstractSynchronizeBackend.execute(AbstractSynchronizeBackend.java:289)
at de.willuhn.jameica.hbci.synchronize.hbci.HBCISynchronizeBackend.execute(HBCISynchronizeBackend.java:146)
at de.willuhn.jameica.hbci.payment.server.ExecuteServiceImpl.syncumsaetze(ExecuteServiceImpl.java:636)
at jdk.internal.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
Es liegt vmtl. an der Einstellung "Umsätze im neuen SEPA CAMT-Format abrufen"
Wie können wir diese Einstellung im Hibiscus Payment Server vornehmen???
Schonmal Danke, Thomas.
Thu Nov 27 10:45:53 UTC 2025 Name: INFO, Level: 100: Führe Geschäftsvorfall aus: "Kontokorrent, IBAN..: abrufen"
Thu Nov 27 10:45:53 UTC 2025 Name: INFO, Level: 100: Führe Aufträge aus...
Thu Nov 27 10:45:53 UTC 2025 Name: INFO, Level: 100: adding job SaldoReq to queue
Thu Nov 27 10:45:54 UTC 2025 Name: INFO, Level: 100: adding job KUmsAll to queue
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: executing check for job SaldoReq
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: execution state: tan needed: false, tan-cancel: false, executed: false, success status: false, error status: false
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: global status:
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: job status:
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: mark job failed
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: Error while fetching balance of account: Unknown Error
Thu Nov 27 10:45:55 UTC 2025 Name: WARN, Level: 300: Error while fetching balance of account: Unknown Error
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: executing check for job KUmsAll
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: mark job unsupported/failed
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: Auftragsart nicht unterstützt
Thu Nov 27 10:45:55 UTC 2025 Name: WARN, Level: 300: Auftragsart nicht unterstützt
Thu Nov 27 10:45:55 UTC 2025 Name: WARN, Level: 300: found errors or synchronization cancelled, mark PIN cache dirty [have error: true, interrupted: false]
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: closing resources
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: closing pin/tan passport
Thu Nov 27 10:45:55 UTC 2025 Name: INFO, Level: 100: pin/tan passport closed
Thu Nov 27 10:45:55 UTC 2025 Name: ERROR, Level: 500: error while synchronizing
org.kapott.hbci.exceptions.HBCI_Exception: error while creating new job KUmsAll
at org.kapott.hbci.manager.HBCIHandler.newJob(HBCIHandler.java:417)
at de.willuhn.jameica.hbci.synchronize.hbci.HBCISynchronizeBackend$HBCIJobGroup.executeJobs(HBCISynchronizeBackend.java:338)
at de.willuhn.jameica.hbci.synchronize.hbci.HBCISynchronizeBackend$HBCIJobGroup.sync(HBCISynchronizeBackend.java:273)
at de.willuhn.jameica.hbci.synchronize.AbstractSynchronizeBackend$Worker.run(AbstractSynchronizeBackend.java:401)
at de.willuhn.jameica.system.Server.startnow(Server.java:149)
at de.willuhn.jameica.hbci.synchronize.AbstractSynchronizeBackend.execute(AbstractSynchronizeBackend.java:289)
at de.willuhn.jameica.hbci.synchronize.hbci.HBCISynchronizeBackend.execute(HBCISynchronizeBackend.java:146)
at de.willuhn.jameica.hbci.payment.server.ExecuteServiceImpl.syncumsaetze(ExecuteServiceImpl.java:636)
at jdk.internal.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
