Orders should reach the ERP using your references
Administration needs orders with recognised customers, items and units. If staff complete incoming EDI data manually, integration needs to go further. Ediprism connects the exchange to an available ERP interface and defines required mappings. For contracting, specify the document created, handling of changes and response confirming registration. This distinguishes file delivery from a useful business-system connection.
Data needs to become a valid record
An incoming order needs to match ERP customers, items, units and conditions. The connection defines whether it creates a document, updates one or requires review. Correctly reading the EDI is only part of the work.
Use available interfaces
We review supported APIs, import and export options, permissions and restrictions. The connection uses an agreed, maintainable interface; it does not assume direct database access or compatibility with every version.
Handle duplicates and changes deliberately
Document identifiers and the treatment of retries, cancellations and amendments need agreement. Technical receipt is distinguished from actual document creation so a process still pending in the ERP is not marked complete.
What we need to assess the connection
Software identity and version, available interface documentation and an anonymised example exchange. Permissions, test environments and responsibilities are reviewed with the vendor or developer. Connectivity is confirmed by scope; brand compatibility is not claimed without verification.
Before you choose a provider
Does the system need changes?
It depends on available interfaces and the intended result. Configuring an import may be enough, or an interface may need adding. This is identified before agreeing the proposal.
How is it verified?
Through agreed creation, amendment, retry and error scenarios. Acceptance must confirm the destination-system result and any responses required by the partner.
What does my software need to connect?
An interface supporting required input or output, available permissions and documentation. The vendor confirms operations and necessary adaptations.
Does Ediprism directly modify the database?
That access is not assumed. Agree an appropriate interface with the system maintainer and document registration before implementation.
How is document registration confirmed?
Define destination responses or evidence. Distinguish file receipt from operational registration to detect pending work.
What about missing references or duplicates?
Agree retry detection, original-document references and incomplete-data handling, with update, rejection and intervention rules.
Who maintains the connection?
Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.
How much does integration cost?
Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.