Set up delivery sites
An administrator sets up delivery sites to connect BC to a message broker so documents can be exchanged.
Purpose
A delivery site is the connection to a message broker or a file folder. It holds the connection type, URLs, credentials and the default standard (BII, NES or EDI). Every customer and vendor that exchanges electronic documents gets a delivery site, and the site's standard decides the document format. The job queue entry only fetches and sends documents through delivery sites where Automatic Processing is selected.
Prerequisites
- A username and password from the message broker.
- For FTP File Transfer and Simple File Moving: access to eDocs Exchange.
Permissions
The user needs the EDOCS permission set.
Steps
Create a delivery site
You can create a delivery site in three ways. The first two open the eDoc Delivery Site Auth. dialog:
- in assisted setup with Create New Delivery Site;
- in eDoc Delivery Sites with Quick Create;
- by creating a new record in the list, filling in the Delivery Site card and then choosing Update Credentials.
- Search for eDoc Delivery Sites and choose Quick Create.
- Choose the Type. The Code gets a default value based on the type, and you can change it.
- Choose the eDoc Default Standard: BII, NES, EDI or Custom.
- Enter the Username and Password and choose OK.
- For Unimaze, InExchange and Deloitte, you're asked "Do you want to test the connection now?". Choose Yes. If the connection succeeds, the delivery site is marked Authenticated.
- Open the card and go through the fields below.
Example: Dæmi ehf. creates a delivery site of type Unimaze WS, chooses REST API and the BII standard, enters the credentials from Unimaze and tests the connection. The company then chooses the delivery site for Prófun hf. in the customer settings.
Types
| Type | Effect |
|---|---|
| Unimaze WS | You're asked "Select API Type". REST API sets the URL https://mapi.sendill.is and Unimaze Transfer Mode = Document Payload (REST). SOAP sets the URLs to gateway.sendill.is and SOAP (Legacy). TEST sets the URLs to TEST, which returns dummy data without a connection. |
| InExchange WS | The default type. The URLs are set to ws.inexchange.is. |
| Deloitte | The URLs are set to edi.staki.is. |
| FTP File Transfer, Simple File Moving | The URLs are cleared. If Use eDocs Exchange isn't selected, you're asked "%1 Site is only supported when using Edocs Exchange. Would you like to use Edocs Exchange?". Yes selects Use eDocs Exchange. |
| Custom | The URLs are cleared. Used with Custom Write/Load Codeunit. |
The Delivery Site card
General
| Field | Effect |
|---|---|
| Code, Type | The delivery site's identifier and type. |
| eDoc Default Standard | The standard of documents through this delivery site. It's copied to eDoc Standard on customers and vendors that get the delivery site. When a standard is chosen, rows are created in units of measure for all units. |
| Unimaze Transfer Mode | Unimaze only: Document Payload (REST), JSON Metadata (REST) or SOAP (Legacy). See JSON metadata. |
| Ignore Billing Accuracy | JSON metadata only. |
| Fallback E-Mail | Shows Required for JSON metadata, otherwise Not Supported. When required, the customer needs a Fallback E-Mail or an email address. |
| InExchange Transfer Mode | InExchange only. |
| XSLT To Use | The XSLT transformation applied to received documents. |
| Send Attachments | Attachments are sent with outgoing documents. Selected by default. |
| Automatic Processing | The job queue entry fetches and sends through this delivery site. Selected by default. |
| Offset | Only for incoming EDI documents. Otherwise you get "This function is only for incoming EDI files". |
| Custom Write/Load Codeunit | Only for the Custom standard. |
| Use eDocs Exchange | Communication goes through eDocs Exchange. eDoc WS URL and Delivery Codeunit ID then appear. |
Web Service: Incoming Documents URL, Outgoing Documents URL, URL 3, Receiver Party ID (sent to InExchange), Username Stored and Password Stored.
FTP Settings: Remote Directory (Inbox), Remote Directory (Outbox), Prefix for Fetched Files and FTP Mode (Active or Passive).
File Moving: Local Directory (in), Local Directory (in) - Read, Local Directory (out) and Local Directory (In) - OnError.
The eDoc Delivery Sites list
The list shows Automatic Processing, Code, Type, Incoming Documents URL, Remote Directory (fetch), Username Stored, Password Stored, FTP Mode, Verify XML, Prefix for Fetched Files and Local Directory (in). The username and password themselves are never shown.

Update or delete credentials
- Update Credentials opens eDoc Delivery Site Auth. with only Username and Password.
- Delete Credentials asks "Are you sure you want to delete the stored credentials for this delivery site?" and then deletes both the username and the password.
Warning
If you leave Username or Password blank in Update Credentials and choose OK, the stored value is deleted. Always enter both values.
Other actions on the card
| Action | Effect |
|---|---|
| Test Connection | Tests the connection for Unimaze, InExchange and Deloitte. |
| Fetch Files | Fetches documents. Message: "Operation was successful, %1 eDocs were added." |
| Convert to BC Documents | Creates BC documents from fetched documents. |
| Send Files | Sends ready documents. Message: "Operation was successful, %1 eDocs were sent." |
| Verify Recipients | Checks whether customers with this delivery site can receive documents. See below. |
| Visit Web Portal | Opens the message broker's web portal. |
| Import file directly | Imports a file from disk. Requires an eDoc Default Standard. |
Verify recipients
Verify Recipients only works for delivery sites of type Unimaze WS with Unimaze Transfer Mode = Document Payload (REST) or JSON Metadata (REST) and a standard other than EDI. There's no check for InExchange or other types. See verify recipients.
Verify
- In eDoc Delivery Sites, Username Stored and Password Stored are selected, and Authenticated is selected after a connection test.
- Test Connection succeeds.
- For Unimaze REST: Verify Recipients shows the customers that use the delivery site. If no customer has it, you get "No customers found using the specified delivery site and eDoc standard."