Help
This page lists the messages Electronic Documents shows, grouped by where you meet them, with an explanation and what to do. Where a message contains a variable value, such as a customer number, it is shown as "…". Errors found when received documents are checked are shown in the document's error list in the eDoc Worksheet. Problems that come up without a message are at the bottom of the page.
Some messages are not translated and also appear in English in the Icelandic interface. They are marked.
Sending documents
| Message | Explanation | What to do |
|---|---|---|
| eDoc … no longer exists. It may have been deleted or recreated by another process. Refresh the list and open the document again. | Sending can no longer find the eDoc; another process may have deleted or recreated it. | Refresh the eDoc Worksheet, open the document again and retry sending it. |
| Failed to create electronic document, you do not have access to Rue de Net Electronic Documents. Please contact your system administrator. | You posted an invoice without the EDOCS permission set. The invoice is posted but no electronic document was created. | Ask your administrator for the EDOCS permission set, then create the document afterwards. See Create an electronic document from an invoice. |
| Customer … does not have a delivery site setup for electronic documents. Do you want to open the customer Card? | The invoice's bill-to customer has no Delivery Site, so no electronic document can be created. | Choose Yes, fill in Delivery Site on the card and try again. See Verify recipients. |
| Please setup customer delivery site to continue | Shown if you don't open the customer card from the question above. | Fill in Delivery Site on the customer and create the document again. |
| This Invoice already exists as an electronic document. Do you want to open it? / This Credit Memo already exists as an electronic document. Do you want to open it? | An electronic document already exists for this posted document. No second one is created. | Open the existing document. To create it again, use Recreate. See Open an electronic document. |
| Process done! Created: … Already exist: … With customers missing delivery site: … | Summary after documents were created for several posted documents. Documents for customers without a delivery site were not created. | If the last number is above 0, set a delivery site on those customers and run it again. See Create an electronic document from an invoice. |
| No eDoc for … … | No electronic document was found for the posted document you selected. | Create the document. See Create an electronic document from an invoice. |
| No document was found to show in browser (not translated) | No document was found to show in the browser. | Check that the electronic document has been sent and exists at the message broker. See Open an electronic document. |
| The document is not ready to be sent. | The document isn't in a status that allows sending, for example because of an error when it was created. | Look at the errors on the document, fix them and choose Recreate. See Resolve errors. |
| eDoc … is not ready to be sent. Its status is …. | Sending only works for documents with the status To be sent. The message shows the document's current status. | If the document has errors, fix them and choose Recreate. See Resolve errors. |
| eDoc … cannot be sent because no Delivery Site is specified. Specify a Delivery Site on the eDoc, and then try again. To use a Delivery Site for future eDocs, set it on the customer. | The document has no Delivery Site. | Fill in Delivery Site on the document and send again. Also set it on the customer so later documents get it. See Delivery sites. |
| eDoc … cannot be sent because Delivery Site … does not exist. Specify an existing Delivery Site on the eDoc, and then try again. To use a Delivery Site for future eDocs, set it on the customer. | The Delivery Site on the document has been deleted or renamed. | Choose an existing delivery site on the document and send again. Fix the delivery site on the customer too. See Delivery sites. |
| The maximum number of send attempts (…) has been reached. The document will not be retried automatically. Correct the issue and recreate or send the document manually. | Sending failed as many times as Max. Send Attempts in eDoc Setup allows. The document gets Automatic Send Blocked and the job queue stops retrying it. The message is added to the document's errors. | Read the other errors on the document and fix the cause. Then choose Recreate, or send the document manually. See Resolve errors. |
| The electronic document no longer exists. Refresh the list and try again. | The document was deleted while sending was being stopped for it. | Refresh the eDoc Worksheet and try again. |
| You can only send outgoing Documents. | You tried to send a received document. | Nothing. Only outgoing documents are sent. |
| The operation was not completed | The sending didn't succeed. | Look at the errors on the document and the status of the delivery site. See Delivery sites and connections. |
| Pre-validation failed. Check the Errors factbox for details. | The document failed a check before it was sent. | Read the errors in the factbox on the document, fix the cause and send again. |
| Receiver party (…) is missing identifier (GLN or Legal Entity Company ID). | The customer has neither a GLN nor a registration number. | Fill in the registration number or GLN on the customer and choose Recreate. See Master data. |
| Receiver party (…) is missing Fallback E-Mail (required as fallback delivery address by Unimaze in the case of JSON metadata invoices). | Unimaze requires a fallback email when invoices are sent as JSON metadata. | Fill in Fallback E-Mail on the customer. See Unimaze JSON metadata. |
| Customer … (…) cannot receive electronic documents. Please remove the delivery site. | Unimaze reports that the customer can't receive electronic documents. | Remove Delivery Site from the customer and send the invoice another way. See Verify recipients. |
| … cannot receive document | The recipient can't receive this type of document. | Check the recipient. See Verify recipients. |
| Customer … no longer has a delivery site. Document was not updated. | The delivery site was removed from the customer after the document was created. | Put the delivery site back on the customer or send the invoice another way. |
| No Report selected exists for usage … | A PDF of the invoice can't be created to send along, because there is no report selection for this document type. | Set up report selections for sales or service invoices and credit memos in BC and choose Recreate. |
| Only Sales Invoices/Credit Memos and Service Invoices/Credit Memos can be recreated. | Recreate only works on outgoing sales and service documents. | Nothing. Other documents can't be recreated. |
| eDoc … has already been sent and cannot be recreated. | The document has already been sent. A sent document is never recreated. | Nothing. If the recipient needs a correction, issue a credit memo or a new invoice. |
| eDoc … has already been converted to a BC document and cannot be recreated. | The document has already been converted to a document in BC. | Nothing. Work with the BC document instead. |
| Only outbound document copies can be exported | You tried to export a copy of a received document. | Use the original file of the received document instead. |
| File type not supported | The file you tried to attach is of a type that BII Standard doesn't allow. It isn't added. | Save the file as an allowed type, for example PDF, and try again. See Attachments on outgoing electronic documents. |
| Attachments cannot be added / Attachments can only be added to outgoing documents that have not been sent. … | The document is inbound or has the status Sent OK!. | Nothing. Attachments can only be added to outgoing documents that haven't been sent. |
| Attachment type not allowed in TS 236 / The attachment "…" on eDoc … has the MIME type "…", which TS 236 (PEPPOL BIS Billing 3.0) does not allow. … | BII Standard is TS236 and an attachment on the document is of a type TS 236 doesn't allow. The document isn't sent. | Choose Remove attachment in the error and send again, or fix the attachments on the source document and choose Recreate. See Attachments on outgoing electronic documents. |
| These eDocs have attachments that were added manually: … eDoc Recreate rebuilds attachments from the source document, so these attachments will be removed. Do you want to continue? | Recreate removes manually added attachments on documents that haven't been sent. | Answer Yes to recreate, or No to cancel. No document is then recreated. |
Receiving and checking documents
These errors come up when a received document is checked. The document gets the status Checked with Errors! and the errors are shown on the document. See Resolve errors.
| Message | Explanation | What to do |
|---|---|---|
| eDoc Setup has not been set up. Open the eDoc Setup page to create the setup, and then try again. | This appears when you check a received document before eDoc Setup has been created. A bulk check stops if setup is missing. | Open eDoc Setup, create the setup and check the document again. |
| eDoc … no longer exists. It may have been deleted or recreated by another process. Refresh the list and open the document again. | The eDoc was deleted or recreated by another process while it was being checked. | Refresh the eDoc Worksheet, open the document again and check it again. |
| Document standard … is not supported. | A document was received through a delivery site whose standard eDocs can't read. Supported standards are BII, NES and EDI. | Choose a supported standard on the delivery site. If you need a different standard, contact Rue de Net. See Delivery sites. |
| Unable to map party AccountingSupplier (…) to Vendor. | No vendor was found with the sender's registration number. Often Vendor SSN Field is still set to No. | Set Vendor SSN Field to the field holding the registration number, or register a vendor mapping. See Master data and Register mappings. |
| Unable to map party AccountingSupplier (…) to Vendor because vendor does not exist. | A mapping points to a vendor that doesn't exist. | Fix the mapping or create the vendor. See Register mappings. |
| Unable to map party Payee (…) to Vendor. | The payee on the document isn't mapped to a vendor. | Register a mapping for the payee. See Register mappings. |
| Unable to map party … (…) to Customer. / … to Customer because customer does not exist. | The sender of a received sales order isn't found as a customer. Often Customer SSN Field is still set to No. | Set Customer SSN Field to the field holding the registration number, or register a mapping. See Master data. |
| This document (AccountingCustomer=…) is not intended for this company (Reg.No=…)! | The payer's registration number on the document isn't the same as Registration No. in Company Information. | Check your company's registration number. If the document does belong to the company anyway, you can choose Skip Check Document For Us on the document. See Master data. |
| Unable to find the AccountingCustomer info! | The document doesn't state a payer. | Contact the sender. |
| Invoice type … not supported! | The received invoice is of another type than a normal invoice (380). | Contact the sender. |
| Referenced order … does not exist. | Check Order No. is set on the vendor and the order the invoice refers to isn't found. | Check the order number, or turn off Check Order No. on the vendor. See Receive a purchase invoice. |
| Unable to map UOM…for seller Item … | The unit of measure on the line isn't mapped. | Register a mapping for the unit of measure. See Units of measure and Register mappings. |
| Unable to map item … (…). No Item exists with matching Vendor Item No. | No item has a vendor item number matching the seller's item. | Register a mapping to an item or G/L account, or fill in the vendor item number on the item. See Register mappings. |
| Unable to map item … (…). No Item exists with matching No. | On a received sales order, no item has this number. | Register a mapping. See Register mappings. |
| Mismatch in VAT%. Incoming value is … instead of … | The VAT percentage on the line doesn't match the VAT setup of the item or G/L account it is mapped to. | Fix the mapping or the VAT posting groups. See Register mappings. |
| Unable to map additional document reference … to location. | The delivery location on the document isn't mapped to a location. | Register a mapping or the location's EAN code. See Location EAN codes. |
| No Data Exchange Definition for … | There is no data exchange definition for the type of the received file. | Choose Run Install Code Manually in eDoc Setup to install the definitions again. See Data exchange definitions. |
| No original file found / There is no Raw file available for this eDoc. | The original file isn't stored with the document. | If files are stored in Azure Blob Storage, check the connection. See Azure Blob Storage. |
| There are no details for this error | The error has no further description. | Read the error text itself. |
Converting and posting
| Message | Explanation | What to do |
|---|---|---|
| eDoc Setup has not been set up. Open the eDoc Setup page to create the setup, and then try again. | This appears when you convert a received document before eDoc Setup has been created. A bulk conversion stops if setup is missing. | Open eDoc Setup, create the setup and convert the document again. |
| eDoc … no longer exists. It may have been deleted or recreated by another process. Refresh the list and open the document again. | The eDoc was deleted or recreated by another process while conversion was in progress. | Refresh the eDoc Worksheet, open the document again and convert it again. |
| The conversion of eDoc … was cancelled or stopped without an error message. Check the eDoc and try converting it again. | The conversion stopped without a reason, for example because you cancelled a question during it. The message is added to the document's errors. | Check the document and convert it again. |
| Mapping is missing for eDoc Item: … | An item on the document isn't mapped when the document is converted to BC. | Register a mapping and check the document again. See Register mappings. |
| Item Unit of measure code … missing for item no … | The item in BC doesn't have the unit of measure the mapping gives. | Add the unit of measure to the item or fix the mapping. See Units of measure. |
| Invoice rounding of … is too much. | The difference between the document's amounts and the purchase document is more than Maximum Invoice Rounding Amnt. allows. | Check the amounts and VAT on the lines or raise the maximum. To skip the check on one document, choose Skip Invoice Rounding Check on it. See eDoc Setup. |
| Purchase header amount: … and eDocs amount: … differ, do you want to cancel the current action? | On posting, the amount on the purchase document isn't the same as on the electronic invoice. | Choose Yes to cancel and compare the amounts, or No to post anyway. See Convert a document to BC. |
| Sales Header amount: … and eDocs amount: … differ, do you want to cancel the current action? | The same check for sales orders converted from an electronic document. | As above. |
Delivery sites and connections
| Message | Explanation | What to do |
|---|---|---|
| Delivery Site … is missing credentials. / Credentials missing for Delivery Site …. Please set the missing credentials before proceeding | The username or password is missing on the delivery site. | Enter the username and password on the delivery site. See Delivery sites. |
| Connection could not be made to InExchange! | The connection to InExchange failed. | Check the username, password and network, and choose Test Connection. See Delivery sites. |
| Failed to connect to Sendill! | The connection to Unimaze (Sendill) failed. | As above. |
| Failed to connect to Deloitte! | The connection to Deloitte failed. | As above. |
| Unexpected status code …: … | Unimaze answered with an error. | Read the response in the message. If it is about access, check the username and password. Otherwise contact Rue de Net. |
| The HTTP request could not be sent. | BC couldn't reach Unimaze, for example because of a network problem or an outage. | Try again later. If it keeps happening, check the URL on the delivery site and choose Test Connection. See Delivery sites. |
| Invalid request URI: … | The Unimaze URL on the delivery site is invalid. | Fix the URL on the delivery site. See Delivery sites. |
| … Site is only supported when using Edocs Exchange. Would you like to use Edocs Exchange? | A delivery site of type FTP File Transfer or Simple File Moving only works with eDocs Exchange. | Choose Yes if eDocs Exchange is set up, otherwise choose another type. See Delivery sites. |
| Delivery site type … is not supported by the service resolver. | The action doesn't exist for this delivery site type. | Use a delivery site with Unimaze or InExchange for this action. |
| You must assign a eDoc Default Standard before uploading a file directly to the Delivery Site! | To upload a file directly, the delivery site needs a standard. | Choose a standard on the delivery site. See Delivery sites. |
| No delivery site with recipient verification support was found. | Recipient verification only works with delivery sites at Unimaze or InExchange. | Set up a delivery site at Unimaze or InExchange. See Verify recipients. |
| Customer identifier is missing (no valid GLN or kennitala found). | The customer has neither a valid GLN nor a valid registration number. | Fill in the registration number or GLN. See Master data. |
| Customer identifier is duplicated and cannot be verified uniquely. | More than one customer has the same identifier. | Fix the duplicate registration number or GLN. See Verify recipients. |
| Unimaze processing timed out. Try again later using Refresh Pending. | Unimaze didn't answer in time. | Try again later. See Verify recipients. |
| ✖ No delivery site created. Please choose atleast one delivery site | Summary in the assisted setup: no delivery site has been created. | Go back and create a delivery site. See Assisted setup of Electronic Documents. |
| ✖ One or more delivery sites not tested or failed connection test / ⚊ Delivery sites not tested | Summary in the assisted setup: the connection hasn't been tested or the test failed. | Choose Test Connection and fix the credentials. |
Setup and master data
| Message | Explanation | What to do |
|---|---|---|
| The following tax categories are missing exemption reasons for standard TS236: … Do you want to set them up now? | With the TS236 standard, tax categories with 0% tax need an exemption reason. | Choose Yes and fill in the reason. See Tax categories. |
| This category does not require an exemption reason and/or exemption reason code. Do you want to clear those values now? / Category … does not require … Filling them in might result in a validation error from message broker. | An exemption reason only applies to tax categories that need one. | Clear the values. See Tax categories. |
| ✖ eDoc setup not finished / ✖ eDoc setup not finished - Missing EDI fields | Summary in the assisted setup: fields are missing in the setup. | Fill in the fields in eDoc Setup. See eDoc Setup. |
| It is not allowed to delete System Setup entries. / It is not possible to modify System Setup entries. (not translated) | System posting texts, such as STANDARD, can't be deleted or changed. | Create a new posting text if you need a different one. See Posting text setup. |
| Are you sure the Vendor has identical Item Nos. | Confirmation when you state that a vendor uses the same item numbers as your company. | Choose Yes only if the vendor's item numbers are the same as in BC. See Vendor eDoc settings. |
| Warning: selected code is not part of the Peppol BIS Billing 3.0 unit of measure code list (UNECERec20). See "https://docs.peppol.eu/poacc/billing/3.0/codelist/UNECERec20/" for available codes. / Warning: selected code is not part of common Icelandic EDI units of Measure. See "Handbók fyrir EDI í verslun - Icepro: https://www.stjornarradid.is/library/?itemid=9c8382f7-3d9e-11e8-9427-005056bc4d74" for reference. | The code you chose for a unit of measure isn't on the standard list. | Choose a code from the list. See Units of measure. |
| The data in this page is no longer used and the page will be removed in an upcoming release. Please use … to control outgoing Units of Measure. Open page … instead? | The old unit of measure page is no longer used. | Choose Yes to open the page that is used now. See Units of measure. |
Mappings
| Message | Explanation | What to do |
|---|---|---|
| No mappings found for this vendor. | The vendor has no mappings. | Register mappings or choose Create mappings. See Register mappings. |
| Customer mapping for edoc partner '…' does not exist. | The party on the document isn't mapped to a customer. | Register the mapping. See Register mappings. |
| (External Dimensions) … … has an empty BC Dimension value. Please specify what BC Dimension to map the external dimension … to. | An external dimension isn't linked to a dimension in BC. | Choose a BC dimension for the external dimension. See External dimensions. |
| (External Dimensions) … does not exist for External Dimension Code … | The value on the document doesn't exist for the external dimension. | Register the value. See External dimensions. |
| (External Dimensions) Dimension … does not exist in BC. / (External Dimensions) Dimension Value with Code … and Value … does not exist in BC. | The dimension or dimension value the external dimension points to doesn't exist in BC. | Create the dimension or value in BC or fix the link. See External dimensions. |
| Only dimensions 1 and 2 can be mapped. (not translated) | Only dimensions 1 and 2 can be mapped on the document header. | Use dimension 1 or 2, or external dimensions. See Register multiple dimensions in mappings. |
| VAT posting setup does not exist for VAT business posting group … and VAT product posting group … on G/L account …. | You turned on Post VAT on BC Id 1, but there is no VAT posting setup for the posting groups on the G/L account. | Create the VAT posting setup, or fix the posting groups on the G/L account. |
| … is only allowed for G/L accounts without VAT. G/L account … has …… VAT. | Post VAT on BC Id 1 only works when the G/L account in the mapping has 0% VAT. | Map to a G/L account without VAT, or leave the field off. |
| G/L Account … does not exist in BC | A Unimaze approval mapping points to a G/L account that doesn't exist. | Fix the mapping. See Unimaze approval support. |
| Unimaze Approval mapping from eDoc Item … to G/L Account … does not match Accounting Cost on eDoc header (…) or eDoc Line (…) | The G/L account in the mapping doesn't match the accounting information Unimaze sent. | Fix the mapping. See Unimaze approval support. |
Storage and cleanup
| Message | Explanation | What to do |
|---|---|---|
| Azure Blob Storage is selected as the storage provider but has not been configured fully yet. … / Azure Blob Storage configuration is incomplete. Please set up … in eDoc Setup. | Fields are missing in the Azure Blob Storage setup. | Fill in the storage account name, container name and the key or SAS token. See Azure Blob Storage. |
| Connection test failed: … | The connection test to Azure failed. | Check the names and the key. See Azure Blob Storage. |
| Azure Blob Storage operation failed for blob "…": … | A file couldn't be read from or written to Azure. | Check the connection and the access. See Azure Blob Storage. |
| You can only use this field to delete the key by unchecking it, not to set a new key. To set a new key, enter it in the "Shared Access Key" field above. / You can only use this field to delete the token by unchecking it, not to set a new token. To set a new token, enter it in the "SAS Token" field above. | The field only shows whether a key or token is stored. | Enter the new key or token in the field above. See Azure Blob Storage. |
| The storage location has changed since this deletion was logged (logged: "…", current: "…"), so the content was not deleted. Delete the content manually in the logged location, or restore the original storage settings and reset the attempt count. | Files were waiting to be deleted from external storage, but the storage settings changed in the meantime. eDocs doesn't delete anything from the new location. The message is shown on the entry in eDoc External Content Deletions. | Delete the files manually in the logged location. Or restore the old storage settings and choose Reset Attempt Count on the entry. See Azure Blob Storage. |
| The storage provider … is not a known storage provider. | The storage provider that holds the files isn't installed or isn't registered. | Contact Rue de Net. |
| Source and target storage providers cannot be the same (both are …). | You tried to move data to the storage it is already in. | Choose another storage as the target. See Azure Blob Storage. |
| The migration job queue entry was created but could not be scheduled, likely because of missing permissions. The entry has to be restarted by an administrator for it to be scheduled properly. Do you want to view the job queue entry now? | You don't have permission to start job queue entries. | Ask an administrator to start the entry. |
| The clean up job queue entry was created but could not be scheduled, likely because of missing permissions. … | The same for the clean-up job. | Ask an administrator to start the entry. See Automatic data clean-up. |
| Please note that nothing will be deleted with the current Clearance Job settings. | The clean-up job's settings don't cover any document. | Fix the settings. See Automatic data clean-up. |
Job queue
| Message | Explanation | What to do |
|---|---|---|
| Invalid parameter: …. Supported parameters are: fetch, send, unimazestatus. The Parameter is case-insensitive … | The parameter on the job queue entry isn't one of the supported ones. | Leave the parameter blank or use fetch, send or unimazestatus. See Job queue entry. |
| One or more errors occured during fetching from all delivery sites: … | Documents were fetched from several delivery sites and an error came up on at least one. | Read the errors and fix the delivery sites. See Delivery sites and connections. |
| … errors found in eDocs (email subject) | The job queue sends an email with errors when Send Error Email is on. | Read the errors in the email and fix them. See Resolve errors. |
Problems without a message
| Symptom | Explanation | What to do |
|---|---|---|
| No electronic document was created when the invoice was posted, and no error came. | The invoice's bill-to customer has no Delivery Site. Without it no document is created on posting. | Fill in Delivery Site on the customer and create the document afterwards. See Create an electronic document from an invoice. |
| The invoice was posted but no electronic document was created, and only a message was shown. | The user doesn't have the EDOCS permission set. | Assign EDOCS and create the document afterwards. See Getting started. |
| No received invoice finds its vendor, even though the registration number is filled in. | Vendor SSN Field is still the default field 1 (No.), so the registration number is looked up in the vendor number. | Set the field to the one holding the registration number, for example 25. See Master data. |
| The job queue neither fetches nor sends documents. | There is no job queue entry, or Automatic Processing is off on the delivery site. The job queue only handles delivery sites with Automatic Processing. | Set up the entry and turn on Automatic Processing. See Job queue entry. |
| BC stops with an error that Registration No. must have a value in Company Information. | Electronic Documents needs your company's registration number to send and check documents. | Fill in Registration No. in Company Information. See Master data. |
| The connection stopped working after the delivery site's credentials dialog was closed. | If the username or password is blank when the dialog is closed with OK, the stored value is deleted. | Enter both username and password again and choose Test Connection. See Delivery sites. |
| After the extension is installed, Def. Vendor Posting Text is blank and there are no delivery sites. | The extension doesn't fill in the setup by itself. Assisted setup does. | Select STANDARD in Def. Vendor Posting Text and set up delivery sites and tax categories. See Getting started. |