Setting Up a Webservice User Account
Introduction
Before your Coins environment can send or receive transmissions via the ECESB001 webservice, a dedicated webservice user account must be created. This user account is used to authenticate all inbound and outbound eCommerce transmissions.
Before You Start
Ensure that the following criteria are met before getting started:
You have been upgraded to Coins ERP+ v12.06
The %ECESB licence is active on your environment (confirm with Access Coins support)
You have system administrator access to your Coins environment
You have the webservice endpoint URL ready (provided by Access Coins support)
If you do not have administrator access, please ask your Coins system administrator or contact the Access Coins support team.
Create the Webservice User
Log in to your COINS environment as a system administrator.
Select Add New User.
Complete the fields as follows:
Field | Value |
Username | A dedicated name e.g. ECUSER or WSUSER |
Full Name | e.g. eCommerce Webservice User |
Password | Set a strong password — this will be shared with your HUB/provider |
User Type | Named User |
Status | Active |
4. Assign the standard WMANDATORY group, or a blank/empty group created specifically for webservice users.
5. Do not use a personal user account for the webservice. A dedicated account ensures transmissions are not affected if a staff member leaves or changes their password.
Communicate Credentials to Your Provider
Once the user has been created, share the following details with your eInvoicing HUB or supplier First B2B:
Detail | Description |
Username | The webservice username created in Step 3 above |
Password | The password set in Step 3 above |
Webservice Endpoint URL | Your ECESB001 endpoint — provided by Coins Administrator |
The ECESB001 API can be located by adding “/wouesb.p” to the end of the environment URL, for example:
ukdemo.coins-global.com/env/demo2/wouesb.p
Test the Connection
Ask your provider to send a test transmission to the endpoint.
Navigate to eCommerce → eCommerce Message Receiver in Coins.
Confirm the test transmission appears and shows a status of Processed.
If the transmission fails, check the user has the eCommerce Services role assigned and that the correct endpoint URL was used.
Common Issues
Issue | Likely Cause | Resolution |
Authentication error from provider | Incorrect username/password shared | Reset password and re-share credentials |
Transmission not in Message Receiver | eCommerce Services role not assigned | Assign the role and retry |
User cannot log in to Coins | User status set to Inactive | Set user status to Active |
Transmission rejected | %ECESB licence not active | Contact Access Coins support to confirm licence |
Receiving eInvoices via Webservice
Introduction
This section explains how to configure your Coins 12.06 environment to receive supplier invoices transmitted via the ECESB001 webservice.
Your suppliers or eInvoicing HUB providers (e.g. Adaptris/OpenECX, Tradex, Adflex) will submit invoice XML files directly to your Coins webservice endpoint. Coins will then process these automatically via the eCommerce receiver (ecu003) and router (ecu004) programs.
Before You Start
Ensure that the following criteria are met before getting started:
You have been upgraded to Coins ERP+ v12.06
The %ECESB licence is active on your environment (confirm with Access Coins support)
A webservice user has been created and assigned the eCommerce Services role (see above section)
The user has been granted access to at least one company (kco)
You have the webservice endpoint URL ready (provided by Access Coins support)
Your Webservice Endpoint
Your suppliers or HUB provider will need the endpoint URL to submit invoices to your Coins environment. The URL will look something like this:
Your actual endpoint URL will be specific to your environment. The above is an example — your Coins support contact will provide your exact URL.
Share the following with your eInvoicing provider:
The webservice endpoint URL
The webservice username and password (set up by Access Coins support)
How Invoices Are Received
Your supplier or HUB submits an invoice XML file to your ECESB001 endpoint.
Coins places the XML into the ECDir/LOAD folder.
The eCommerce Receiver (ecu003) picks up and validates the file.
The eCommerce Router (ecu004) routes it for processing within Coins.
The invoice appears in Coins for matching and approval.
Verifying Received Invoices
Log in to your Coins environment.
Navigate to eCommerce → eCommerce Message Receiver.
Review the list of inbound transmissions - confirmed receipts will show a status of 'Processed'.
If a transmission has failed, the status and error detail will be shown here.
eInvoicing Provider Reference
Provider | Method for v12.06 Hosted Customers |
Adaptris (OpenECX) | ECESB001 webservice API |
Tradex (hosted) | ECESB001 webservice API |
Adflex (PCard) | ECESB001 webservice API |
FirstB2B | Migrating from AS2 → ECESB001 webservice |
Tradex (non-hosted) | May still use sFTP - confirm with your provider |
Testing the Connection
Ask your provider to send a test invoice transmission.
Navigate to eCommerce → eCommerce Message Receiver to confirm receipt.
Check the transmission status shows 'Processed'.
Contact Access Coins support if the transmission does not appear within a reasonable timeframe.
Sending Purchase Orders via ESB Service
Introduction
This section explains how to configure your Coins ERP v12.06 environment to send purchase order (PO) XML files to your suppliers or eInvoicing HUB via the Coins ESB (Enterprise Service Bus) service.
In Coins ERP+ v12.06, purchase orders are transmitted using XmtMethod = ESB rather than directly via the webservice. The ESB service manages the queuing and delivery of PO XML to the configured endpoint (e.g. FirstB2B). This provides a more robust and managed transmission process.
The PO is sent using the ESB service — not directly via the ECESB001 webservice endpoint. The ESB queue (e.g. B2B) must be configured in Background Process Configuration before POs can be transmitted.
Before You Start
Ensure that the following criteria are met before getting started:
You have been upgraded to Coins ERP+ v12.06
The %ECESB licence is active on your environment (confirm with Access Coins support)
A webservice user has been created and assigned the eCommerce Services role (see first section)
You have your company code (kco) to hand
The ESB Send queue (e.g. B2B) has been configured in Background Process Configuration
Your supplier or HUB provider (e.g. FirstB2B) is ready to receive transmissions
If any of the above are not in place, please contact the Access Coins support team before proceeding.
Configure the ESB Send Queue
The ESB Send queue must be set up in Coins ERP+ before POs can be transmitted. This is typically configured by the Access Coins support team.
Navigate to System → Background Process Configuration.
Select the ESB Send tab.
Confirm a queue entry exists (e.g. ID: B2B, Description: First B2B, Endpoint: FirstB2B).
If no entry exists, contact the Access Coins support team to set this up.
The ESB Send queue configuration shown in Background Process Configuration must match the ESBQueue value in the PORD document type XML (e.g. <ESBQueue>B2B</ESBQueue>).
Apply the PORD Configuration
A sample configuration file (PORD_webservice_sample.xml) will provided by support. Open it in a text editor and confirm/update the following key fields:
Field | Value | Description |
<XmtMethod> | ESB | Tells Coins to use the ESB service for transmission |
<ESBQueue> | B2B | The ESB queue name - must match the Background Process Configuration entry |
<FileFormat> | eBis-XML_V3 | XML format for the PO document |
<Envelope> | BizTalk_1 | Envelope format used for transmission |
<Company kco=""> | Your kco | Your company code |
Do not change SendXMLRules or MajorType sections unless specifically advised by your Access Coins support contact.
To apply the configuration in Coins:
Log in to your Coins environment.
Navigate to eCommerce → eCommerce Organisation Setup.
Locate the PORD document type row for your organisation.
Select 'Import' and upload the updated PORD_webservice_sample.xml file.
Confirm the settings have been applied by reviewing the record on screen.
How PO Transmission Works via ESB
Once configured, the process works as follows:
A purchase order is raised and approved in Coins ERP+.
Coins generates the PO XML in eBis-XML V3 format.
The XML is placed into the ESB Send queue (e.g. B2B).
The ESB service picks up the queued message and transmits it to the configured endpoint (e.g. FirstB2B).
A confirmation response is returned and logged in Coins ERP+.
The transmission can be monitored via eCommerce → Inbound/Outbound Message Status.
Testing the Connection
Raise a test purchase order in Coins ERP+.
Transmit it via the eCommerce module.
Navigate to eCommerce → Inbound/Outbound Message Status to confirm the transmission shows as Sent.
Check the ESB Send queue in Background Process Configuration - the Log column can be used to review transmission activity.
Ask your supplier or HUB provider (e.g. FirstB2B) to confirm receipt on their side.
Contact Access Coins support if the transmission does not appear or shows an error.
Summary of Key Configuration Fields
Field | Previous (AS2/Folder) | New (ESB Service) |
Transmission Method | AS2 protocol via OpenAS2 / Folder drop | ESB service queue |
XmtMethod field | Folder | ESB |
Queue/Endpoint Config | AS2 server / file path | ESBQueue = B2B (Background Process Config) |
Visibility | Separate MDN log files | eCommerce Inbound/Outbound Message Status |
Certificate Management | Ongoing AS2 certificate maintenance | Handled within Coins ESB configuration |
Support | AS2 specialist required | Standard Coins support |