Recent reports in Yuki

Modified on Tue, 18 Aug at 10:05 AM

On our radar

On this page we keep you informed about recent reports or technical outages we are currently working on. We aim for maximum transparency, so that you always know the status of a specific report in our software. Please note that only reports with a major impact on you as a customer are shown here.

What does this mean for you?Do you see a report that matches what you are experiencing? Then we are already aware of it. There is no need to create a support ticket for this.

Always up to dateAs soon as new information is available or a report has been fully resolved, we update the status on this page immediately. So keep an eye on this page for the latest updates.

VAT centralisation sends you back to the home screen

Published on: 18/08/2026

After clicking "VAT centralisation" you are sent back to the home screen, the pop-up closes immediately, or you see a blank white screen.

Temporary workaround:

So that you can continue in the meantime:

Click "VAT centralisation" and then use your browser's back button. You will end up on the screen from which you can run the centralisation.
Or open VAT centralisation in a new browser tab. That also lets you run the centralisation normally.

Status: In progress

Error message "User blocked" when logging in

Published on: 18/08/2026

We have received reports from users who get an error message when logging in saying that their user is blocked. This is caused by the system automatically redirecting you to the wrong domain name after logging in (yukiworks.nl instead of yukiworks.be).

Temporary workaround:

Check your browser's address bar immediately after logging in. If the URL ends in .nl, change it manually to yukiworks.be. You will then be able to log in normally and everything will be visible again.
If needed, clear your browser's cache and cookies so that your browser stops sending you to the .nl version automatically.
Have you saved the Yuki website as a bookmark? Make sure to update it to the correct address (yukiworks.be).

Status: In progress

Problems logging in via the portal (yukiworks.be)

Published on: 17/08/2026

We have received reports from users who have trouble logging in to their portal because they are automatically redirected to the wrong domain name (.nl instead of .be).

Temporary workaround:

Check in your address bar that the URL ends in yukiworks.be and not yukiworks.nl.
Are you still redirected to .nl after logging in? This is most likely caused by stored cache and cookies. Clear your browsing history and cookies, and change the URL manually to yukiworks.be after logging in.
Have you saved the page as a bookmark? Update it to the correct address.

Status: In progress

Scheduled maintenance: Yuki unavailable during the weekend of 15 and 16 August

Published on: 14/08/2026

During the weekend of Saturday 15 and Sunday 16 August we are carrying out scheduled maintenance on our infrastructure. This makes Yuki even more stable and future-proof.

What does this mean for you?

Yuki is unavailable for the whole weekend (15 and 16 August). This applies to both the web version and the Yuki Assistant app.
Our login page remains available and shows the current status of the maintenance. If the maintenance finishes earlier, you will be able to log in again earlier too.
Please note: do you normally log in via www.yukiworks.nl? After the maintenance this will only be possible via www.yukiworks.be.
Are your customers sending documents to their Yuki email address that weekend, or receiving them via Peppol? No problem: these are automatically queued and forwarded to the correct domain on Monday, and processed in Yuki straight away where possible.
We are also informing your entrepreneurs, via a banner in the software and by email.

Our team is doing everything possible to make the maintenance run as quickly and smoothly as possible. Thank you in advance for your understanding.

Status: Scheduled maintenance – weekend of 15 and 16 August - resolved

API endpoint changes: is your integration no longer working?

Published on: 14/08/2026

From 15 August, Yuki is separating the API environments for the Netherlands and Belgium. If your integration no longer works, we advise you to contact your software partner and share the information below.

In concrete terms this means:

api.yukiworks.nl will only work for Dutch domains from 15 August.
api.yukiworks.be will only work for Belgian domains from 15 August.
api.yukiworks.com (the old, shared endpoint) is being phased out entirely.

What does this mean for your integration? If your system still calls api.yukiworks.nl (or the old api.yukiworks.com), it needs to be changed to api.yukiworks.be.

For the party that built the integration:If you work with both Dutch and Belgian customers, it is important that your system uses the correct endpoint per customer based on the country of the Yuki domain, rather than one fixed endpoint for all customers. From Monday 17 August, an integration still pointing at the wrong endpoint may return an "invalid access" error. Nothing else changes for authentication, endpoints or the request/response format; it is purely about the correct base URL per country.

Could you check whether the integration(s) with Belgian domains already point to api.yukiworks.be? If this is not yet correct, please adjust it as soon as possible so that the data exchange is not interrupted.

Status: Action required from your software partner

Message "No access" when logging in

Published on: 11/08/2026

Some users report that after logging in they end up on a page showing the message 'No access'.

What causes this?
This problem is usually related to the cache (the storage) of your internet browser. It can occur when you have access to several Yuki files with one email address and open them in the same browser. Because of leftover cookies and cache data, the browser sometimes gets confused about the active permissions, which causes Yuki to deny access.

Still experiencing problems after following these steps? Please contact our support team so that we can look into it with you.

Temporary workaround:

You can easily solve this yourself via your browser settings:

Clear your cache and cookies: Delete the browsing data of your internet browser (such as Google Chrome, Safari or Microsoft Edge) and try logging in again.
Use an incognito window: Open a private or incognito window in your browser and log in there. Because an incognito window does not use old cookies, logging in should work straight away.

Status: Resolved