---
title: "Handling eAttest error messages"
description: "This article explains the possible error messages or difficulties you may encounter when submitting an eAttest, and how to resolve them."
url: https://helpcentrum.crossuite.app/en/articles/213-handling-eattest-error-messages
collection: "eAttest"
updated: 2026-11-21
language: en
alternates: [nl, fr]
---

# Handling eAttest error messages

This article explains the possible error messages or difficulties you may encounter when submitting an eAttest, and how to resolve them.

**Where can I find the error message for my eAttest?** Click the arrow at the bottom right and then the “View eAttest history” button.

## Error messages without a code

### **I cannot send an eAttest**

You can only send an eAttest if the treatment date is the current date.

The **only** exception is that all treatments performed between requesting the approval and receiving the approval can still be submitted together via eAttest at the next treatment.

### **I just requested an eAgreement for my patient but I cannot send an eAttest. Has the request already been approved?**

Refresh the page and see whether the button is now available.

If it still doesn't work, you have to wait until the pathology is approved. Don't worry: once it is approved, you can send all treatments you performed between the request date and the approval date in one go with the next eAttest.

### **Internal server error or “Cannot read properties of null (reading '0')” when sending an eAttest**

Check the RIZIV number of the prescribing physician. If this is an old contact, the RIZIV number may no longer be up to date. To be sure, look up the physician via CoBRHa so you always have the correct details.

If sending keeps loading for several minutes and then shows “Cannot read properties of null (reading '0')”, the prescription is usually linked to an old version of the physician. Select the physician again via CoBRHa (the version with the current RIZIV number) and send again.

### **Sending keeps loading and ends with an error or time-out**

When the mutuality responds slowly, sending can take several minutes and still fail. Often the mutuality did receive your eAttest. Send the same eAttest again; do not delete it to create a new one. If you then get \[190\] or \[270\], see those codes below: the first attempt has arrived.

### **“Payment failed” when submitting an eAttest**

First send the eAttest without a payment. Then add the payment via “Add payment” in the financial panel.

### **Invoice already exists for this treatment**

Refresh your page.

### **I get several error messages after creating an eAttest, but my eAttest is approved**

This is probably related to sending the proof to the patient via eBox. You can try to send the proof manually via the “Proof” button.

A common error message is “Error while executing web service call: Received Code **\[101\]** Reason: The destination entity has no active eBox. The publication was sent to a recipient who never consulted his e-Box.”  
This means that the patient has never logged in to their eBox, so it has not been activated yet. By law, you must print the proof for these patients.

### **“Proof could not be sent via eBox message” for all patients**

This happens when the name of your practice (or of the patient) contains a special character, such as ē, ł or ş. Your eAttest itself is fine. For now, send the proof by email or print it; we are working on a fix.

### **Unable to send messages to contacts without a specialisation code**

This error occurs when an eBox message is sent automatically and means that the patient does not have an active eBox.

## Error messages with a code

### **\[111\] The format of the KBO number of the collecting entity is missing or incorrect / “Enterprise number of the practice is missing”**

You can enter your practice's enterprise number via your profile picture at the bottom left > “Practice details” > “Business info”, in the Enterprise number field. Make sure it is a 10-digit number without “BE” in front and without spaces or special characters such as dots. Only the owner of the practice can change this field.

### **\[140\] When cancelling an eAttest: the author is not authorised for this type of request**

Solidaris currently refuses cancellations of eAttests by physiotherapists. Ask Solidaris to cancel the eAttest. In the meantime, do not send a new eAttest or paper certificate for that session, because the first eAttest is still valid.

### **\[140\] Prescriber not authorised**

Look up the prescribing physician again via CoBRHa and choose the version with the current RIZIV number. If it still doesn't work, contact support.

### **\[171\] (Pseudo-)nomenclature code not allowed for this type of provider**

Check via your profile picture at the bottom left > Edit profile > Profession whether you still have a provisional RIZIV number entered in the system. If your RIZIV number ends in “17”, change it to “27”. Also check the RIZIV number in your eHealth integration via your profile picture > Integrations > eHealth. In both places it must end in “27”.

### **\[190\] Maximum number of services already reached in the permitted period**

If you get this after an earlier attempt that kept loading or failed, the mutuality registered that first attempt and your patient will be reimbursed. Do not send anything else for that session: no new eAttest and no paper certificate. Do not move the treatment to another date either, or the same session will be reimbursed twice.

If there was no earlier attempt, ask your patient whether another physiotherapist already attested a service that day.

### **\[191\] Code not allowed for a service in the past**

Some codes, such as the intake (file fee), cannot be attested afterwards via eAttest. Cancel the eAttest of the first session and give a paper certificate with all codes, or invoice via eFact if you apply the third-party payer scheme.

### **\[267\] The medical decision reference does not exist at the insurance institution**

The medical reference refers to your eAgreement. Check whether an approval is linked to the period.

If you get the error right after receiving a new approval (especially with CM), the mutuality does not yet know that approval on the eAttest side. Do **not** request the approval again, or the process starts over. Try again later in the day. If it doesn't work that day, give a paper certificate for that session; the following sessions normally work.

If your patient has changed mutuality, you need a new approval from the new mutuality.

### **\[269\] The referenced medical decision is not an open agreement**

You may have linked the wrong open approval to your period. Check the start and end date of the approval to see whether it concerns the correct pathology. If you linked the wrong period, you can select “External period” again under “Period” in the list of existing approvals to unlink the approval and the period.

Often it is last year's approval: an approval for a common pathology runs per calendar year. Unlink it and link this year's approval. If there is none yet, request a new approval.

### **\[270\] Maximum number of reimbursable services reached for the referenced medical decision**

If you get this after an earlier attempt that kept loading or failed, the same applies as for \[190\]: the first attempt has been registered, so do not send anything else for that session.

Otherwise, it means that the code you are trying to attest may already have been attested the maximum number of times for this pathology. Ask your patient whether they have already been to another physiotherapist. If your patient has definitely not been to another physiotherapist, you can contact their mutuality to find out why the eAttest is being refused.

### **\[280\] Prescription not known at the insurance institution for this prescriber and this prescription date**

If the prescription is not yet linked to the running approval, you can still add it via the period > click the arrow next to “Approval details” > Complete approval request. Select only the prescription you want to add to the approval and send it.
