Community Integration
Integrating with your ERP
Unimarket Integration Middleware
-
Workato On Premise Agent (OPA)
Unimarket integrations use Workato as a SaaS based middleware for establishing the connections between Unimarket and customer Finance ERP, as well as other third party syst...
-
Unimarket Connector Platform
The buying organization can choose to integrate via standard Unimarket webservices or use the Unimarket Connector middleware. To manage data transformation with external sy...
File Automation sFTP
-
Unimarket File Automation (sFTP)
Unimarket File Automation provides a low-barrier alternative to full system integration by allowing customers to securely import and export data using simple CSV flat file...
-
sFTP File Processing Error
When your community receives an email notification with the error "Problem Processing File," it indicates that an automated or manual file upload was unsuccessful. Follow t...
-
sFTP Setup for File Automation
Unimarket uses Secure File Transfer Protocol (sFTP) to securely send and receive files. This functionality automates master data uploads (e.g., Users, Account Codes, and Ap...
-
Approval Data Uploads via sFTP
You can automate approval data uploads by sending CSV file templates to Unimarket via Secure File Transfer Protocol (sFTP). This functionality allows you to update your com...
-
User Data Uploads via sFTP
You can automate user data uploads by sending CSV file templates to Unimarket via Secure File Transfer Protocol (sFTP). This service removes the need to manually manage use...
-
Supplier Master Data Uploads via sFTP
Suppliers and their related details can be created and updated efficiently, using the bulk community Supplier Upload function. This service allows you to use a CSV template...
Master Data
-
Update Account Code Format Integration
The Update Account Code Format integration is an inbound process used to receive General Ledger (GL) or Project account code formats, values, and descriptions from an exter...
-
Validate Account Codes (Budget Check)
The Validate Account Code integration allows Unimarket to request real-time verification of accounting information (such as FOPAL or ledger data), from an external ERP or ...
-
Approval Request/Response Integration
The Approval Request / Response messages facilitate a two-way, real-time integration. That allows Unimarket to retrieve approver information directly from an external ERP o...
-
Approval Configuration Request Integration
The Approval Configuration Request is an inbound integration point used to synchronize approval hierarchies, groups, and financial delegations from an external ERP system i...
Transactions: Orders, Receipts, Invoices & More
-
Purchase Order Integration (OrderRequest) Overview
The OrderRequest integration is used to transmit Purchase Order (PO) details between Unimarket and external systems. It follows the cXML standard, ensuring compatibility ac...
-
Integration Options for Validate Account Code (Budget Check) Integration
The Validate Account Code (Budget Check) integration is a real-time, synchronous process that verifies financial data at the point of checkout. When a user clicks "Checkout...
-
cXML Order Integration - Change Orders
In Unimarket, change orders (edits to existing purchase orders) can be handled using two distinct logical configurations. The method chosen determines how integration messa...
-
Electronic Invoicing
eInvoicing is the direct, electronic exchange of invoice data between a supplier's accounting system and your Unimarket Community. Unlike PDF or paper invoices, eInvoices a...
-
Peppol eInvoicing in Australia & New Zealand
Peppol is the electronic invoicing standard adopted by the Australian and New Zealand governments to streamline business transactions. It allows your community to receive ...
-
Purchase Order (OrderRequest) Technical Documentation
This document defines the transport layer requirements for integrating Purchase Orders from Unimarket into a Community's receiving system (ERP/Financial System). Unimarket...
Authentication & Users
-
Authentication
Unimarket offers several authentication mechanisms to provide flexibility for different security and user management needs. These fall into two main categories: Username/P...
-
Setting up SAML SSO
To set up SAML Single Sign-On (SSO), Unimarket acts as the Service Provider (SP), and your organization acts as the Identity Provider (IdP). This three-step process establ...
-
User API (JSON)
The Unimarket User REST API allows for the real-time synchronization of user data between your internal systems (like an HRIS or ERP) and Unimarket. This interface supports...
-
User Detail Request (user-detail-request)
The User-Detail-Request and User-Detail-Response integration points, allow your organization to use an external system (such as Active Directory, an Identity Provider, or a...
Punchout
-
eMarketplace Punch-out (ERP to Unimarket)
Unimarket can be configured as a centralized eMarketplace that sits on top of your existing ERP system (such as Workday, PeopleSoft, Oracle, or TechnologyOne). In this set...
-
ERP Punchout to Unimarket (Technical Information)
The Punchout (Roundtrip) process is a standardized method for a user to leave their internal ERP system, shop within the Unimarket eMarketplace. And return a populated shop...
General & Technical
-
Email Authentication
Unimarket uses Postmark to manage email delivery, ensuring high security, reliable delivery rates, and professional bounce handling. To verify that emails sent by the syste...
-
Simplifying SPF Maintenance
An SPF (Sender Policy Framework) record is a type of DNS record, that identifies which mail servers are authorized to send email on behalf of your domain. This prevents "sp...
-
Webservice Integration Technical Documentation & Examples
Unimarket utilizes two primary messaging standards for integration: uXML (Unimarket XML) for proprietary platform functions and cXML (Commerce XML) for industry-standard p...
-
Sending POX (Plain Old XML) Messages to Unimarket
POX (Plain Old XML) is a simplified protocol used for communicating with Unimarket when full SOAP overhead is not required. It is primarily used for administrative and data...
-
Sending SOAP Messages to Unimarket
SOAP (Simple Object Access Protocol) is a highly structured protocol used, to exchange XML-based information when implementing Unimarket Web Services. Unlike the simpler PO...
Troubleshooting
-
Troubleshooting Ellucian/Colleague Timeout Errors
This document is designed to handle 30,000ms timeout errors, effectively. Integration Architecture Overview These errors typically occur when the Ethos API or the underl...
-
Unimarket-Banner Fiscal Year End Processes
Fiscal Year End (FYE) processes are essential for reporting revenue and expenses within their correct annual period. Because financial statement integrity is paramount, tra...
-
Troubleshooting Unimarket-to-Banner PO Integration Errors
This guide provides Functional Users in Procurement and Finance Offices with instructions for troubleshooting common errors encountered during the transmission of Purchase ...
-
Troubleshooting SSO Errors
SSO errors typically occur when there is a mismatch between your organization's Identity Provider (IdP) and Unimarket (the Service Provider). Most issues can be resolved by...
-
Troubleshooting Unimarket-to-Banner Invoice Integration Errors
This guide provides Functional Users in Accounts Payable and Finance Offices with instructions for troubleshooting common errors encountered during the transmission of Invo...
-
Troubleshooting: Unimarket-Banner Interface Error Emails
When the Unimarket-Banner interface encounters an error during document transmission (POs, Invoices, etc.), the Banner APIs generate error logs. These errors are stored in ...