eDoc Parties
eDoc Parties shows the companies on one electronic document: the seller, the buyer, the payee and others. The system uses the parties to find the document's vendor or customer in BC.
Overview
The list opens when you select the Parties field on the eDoc card. Each party is one line. The fields are read from the document, or filled from BC when an outbound document is created, and aren't meant to be changed.

Party types
The Party field tells you the role the party plays on the document.
| Party | What it is | How the system uses it |
|---|---|---|
AccountingSupplier | The seller that issues the invoice. | On purchase invoices its Legal Entity Company ID is mapped to a vendor. |
AccountingCustomer | The buyer the invoice is addressed to. | On sales invoices this is the customer. On inbound documents its Legal Entity Company ID is compared with your company's registration number. |
Payee | The party that receives payment, if different from the seller. | On orders from a customer it's used to find the customer. |
BuyerCustomer | The buyer that places the order. | On orders from a customer it's used if there's no Payee on the document. |
Documents can also have the parties DeliveryLocation (delivery location), SellerSupplier (the seller on outbound purchase orders), DP_Party and OriginatorCustomer.
Fields
| Field | What it does | When to change it | Default |
|---|---|---|---|
| Party | The party's role; see Party types. | Never. | From the document |
| ID | The party's identifier in the document. Selecting the field opens the customer card (AccountingCustomer), the vendor card (AccountingSupplier) or Company Information if the ID is your own company's. | Never. | From the document |
| Legal Entity Company ID | The party's company registration number (kennitala). Mappings of type Vendor and Customer match on it. | Never. | From the document |
| Name | The party's name. | Never. | From the document |
| Endpoint | The party's electronic address the document is sent to: a GLN (scheme 0088) or a kennitala (scheme 0196). See Endpoint. | Never. | From the document or BC |
| Address Postbox, Address Street Name, Address Street Name 2, Address Building Number, Address Postal Zone, Address City Name, Address Department | The party's address. | Never. | From the document |
| Address ID | The address identifier, for example the GLN of a delivery location. | Never. | From the document |
| Address Line | An extra address line. Mappings of type Address Line match on it. | Never. | From the document |
| Address Country | The party's country. | Never. | From the document |
| Tax Scheme ID / Tax Scheme Company ID | The tax scheme and the party's VAT number. | Never. | From the document |
| Registration Name, Registration City Name, Registration Country Subentity, Registration Country ID Code | The company's registered name and place of registration. | Never. | From the document |
| Contact Name, Contact Telephone, Contact Telefax, Contact Email | The party's contact. | Never. | From the document |
| Fallback E-Mail | The email address Unimaze uses if the document can't be delivered electronically. Only supported when the delivery site's Unimaze Transfer Mode is JSON Metadata (REST), see JSON metadata. Taken from the customer or vendor. | Never. | From BC |
| First Name, Middle Name, Family Name, Title | Name and title of a person, if the party is an individual. | Never. | From the document |
Endpoint
Endpoint is the electronic address a document is sent to and fetched by.
- Outbound sales invoices: the customer's kennitala is used, unless Use GLN as Default Identifier is selected on the Customer Card. Then the customer's GLN is sent.
- Outbound purchase orders: the vendor's EAN ID on the Vendor Card, or the EAN ID of the order address.
- Inbound purchase documents: the buyer's ID, its endpoint and the delivery location ID are matched against mappings of type Address Line to Location, and then against Location EAN IDs, to pick the location. Empty mappings are created automatically so you can fill them in.
- Inbound orders: the seller's endpoint is matched against location EAN IDs to pick the location.
How the vendor is found
If there's no mapping of type Vendor for the seller's Legal Entity Company ID, the system looks for a vendor whose number is the kennitala, with or without a hyphen, and then in the vendor's registration number field. If none is found and Create new Vendor is selected in eDoc Setup, the vendor is created. A mapping is created automatically when a vendor is found.
If that fails, you get an error such as "Unable to map party AccountingSupplier (kennitala) to Vendor." Register a mapping as described in Register mappings.