Are you curious about how ChainLink SRM would work with your existing business systems? Click the button below to schedule a call with one of our enterprise technology experts.
See current activities waiting for action as they relate to the original transaction document.
Effective B2B collaboration is about sharing business data with trading partners in a defined business process.
Track all actions related to a business document to easily produce an audit trail for B2B transactions.
Know exactly when important business documents are sent or received with verified document delivery timestamps for enforcing Just-In-Time delivery standards.
Attach files to any business document message, such as a reject notice or ASN.
Transfer, track, and deliver traditional EDI, XML, JSON, and other types of non-EDI standard format data type based documents, messages, and files.
Get multiple logins for ChainLink SRM so that everyone on your team that needs access has access.
Connect your in-house systems directly to ChainLink SRM. Fully automate the data connection between your systems and ChainLink SRM for unattended send and receive capability.
This basic workflow function allows routing documents between different user logins to facilitate the collection of information and actions on documents to support your business process.
Do you have a question about ChainLink SRM?
Chances are you’ll find the answer below.
ChainLink SRM does not replace your existing ERP or EDI system. Rather it provides a uniform interface for all of your supplier relationship management activities, including electronic document delivery for your ERP/EDI system to use for all of your suppliers. Once a document has left your back office system and entered ChainLink SRM, it will be delivered to the recipient via the most appropriate method.
For smaller paper-based suppliers, this means that it’s delivered to their ChainLink SRM inbox. Accessing, interacting with, and replying to your business documents requires nothing more than a computer and a modern web browser.
For larger suppliers with back office systems connected to ChainLink SRM, this means the document will be delivered all the way to their ERP or EDI system as if they were integrated via an EDI Direct Connection.
New documents and replies to existing documents from both large and small suppliers alike will be delivered to your ERP/EDI back office using that same uniform interface. You can treat all of your suppliers like electronic trading partners using the same protocol and document map.
For smaller suppliers, all you need is a computer with a modern web browser. You can view and take action on all documents delivered through ChainLink SRM using the web UI. Document forms are customized to match the originals and are presented in a clean and easy to use interface. All forms that require data entry have live data validation to help you fill out the forms with confidence.
Larger suppliers with back office systems can connect to ChainLink SRM using the TTPServices API. This SOAP-based API allows you to programmatically access ChainLink SRM functionality to poll for and retrieve newly delivered documents, take action on and reply to documents, submit new documents for delivery, and manage other facets of Supplier Relationship Management.
If neither of these connection options fits your needs, we will work with you to craft a custom connection solution for your back office system. ChainLink SRM supports post-delivery integrations for just such cases. This allows us to push documents to your systems as soon as they have been processed by ChainLink SRM using whatever method best supports you and your business. However the nature of these custom integrations requires more time and communication to establish and maintain than the web UI and TTPServices API.
ChainLink SRM is not intended to be a permanent cloud storage solution for EDI documents. Delivered items are temporarily stored on our servers to keep track of transaction sets and to allow users to view and interact with them using the web UI.
Once a transaction set has been closed, the documents it contains become eligible for deletion from ChainLink SRM’s database. This allows us to reclaim storage space from inactive documents, lowering our operating costs and allowing us to pass the savings on to you.
Inactive documents are deleted from ChainLink SRM’s database 60–120 days after being closed, dependent on the volume and size of documents being sent. Large or numerous documents would be cleaned out more frequently than small, sparse documents.
Note that active documents will never be deleted from ChainLink SRM, and there is no limit on the number of active documents or the length of time a document can remain active. Documents are closed and become inactive after needed action has been taken on all documents in the transaction set.
For example, a purchase order won’t be closed until after its transaction set has been completed by returning an advance ship notice, invoice, and remittance advice. At that point all four documents in the transaction set would close.
Not at the moment, but a number of users have requested this capability. We’re looking at designing and implementing this functionality to allow users to export their documents before they are deleted so that they may be permanently archived.
Yes. Using the document routing manager, you can specify which user a document should be sent to based on the community context and the document type.
Yes. All documents are converted to a proprietary data format before delivery, which allows ChainLink SRM to support a wide range of documents. Any number of fields and data types can be stored in a ChainLink SRM item. We just have to define a map for your data to the internal proprietary format. From there we will craft a custom form to display your document with any data validation rules and form actions it needs.
In addition, file attachments can be added to any item in ChainLink SRM. This allows it to facilitate managed file transfers of binary reports, images, CAD drawings, and other documents that aren’t suitable for storage in a text-based markup format.
Attachments are currently limited to 100MB per item action (create, update, reply, etc). This can be spread across any number of files—from a single 100MB file to twenty 5MB files.
There are no limitations on document transmissions by either count or kilocharacter.
In most cases, yes. We have engineered a number of custom solutions to parse and import data from binary reports and spreadsheets.
We’re all about moving data, so we’ll work with you to develop the best solution for getting data into ChainLink SRM from a back office system that doesn’t output EDI or XML.
Yes. Signatures are a form of authorization data that can be collected using the document forwarding capabilities of ChainLink SRM. Forwarded documents can be configured to capture a number of different data points during an authorization including reentry of user credentials, validation of a user-set pin, and digital signature using a mouse or touch-screen stylus.
Yes. Communities can be configured by the community sponsor to allow suppliers to send documents directly to other suppliers. This also allows ChainLink SRM to support multi-tier transaction sets.
Yes. We understand that your supply chain isn’t always a flat structure. Parts you order from one supplier may be used by another supplier to finish the final product that gets sent to you. ChainLink SRM supports the document trading workflow that results from this kind of structure with what we call 3 Dimensional Trading.
Here’s an example: Send a purchase order to Supplier B for parts needed by Supplier A to fulfill another PO. Supplier B returns an invoice to you and an ASN to Supplier A, and you can receive a carbon copy. If a part is defective, rejects and RMAs can be routed back down the supply chain to the origin of the defect.
Yes. ChainLink SRM allows community sponsors to pay for their trading partners’ subscriptions with a 3rd Party Payor Contract. You can set up a contract for 1, 2, or 4 quarters for any number of subscription activations. Volume discounts are automatically applied to contracts with high numbers of subscription activations.
Once paid for, you can activate subscriptions that last for the duration of the contract on any of your trading partners. You’ll also have the option to renew your contract and automatically extend your trading partners’ subscriptions.
Your monthly document quota is the number of documents that you can send in a month before incurring overage fees. Hubs and community sponsors have an unlimited document quota. Lifeline subscriptions have a base document quota of 0. And all other subscription options have a base document quota of 50.
Note that document quotas and overages apply only to the documents you send. Documents you receive from others do not count against your usage as they are covered by the trading partner that sent the document.
For more information about document quotas and overage fees for the different subscription options, see the Pricing page.
ChainLink SRM uses state-of-the-art technology to secure your account and business data.
Access to the internal web UI and TTPServices API requires an HTTPS connection using either TLS 1.1 or 1.2.
Passwords have minimum length and complexity requirements and are salted and hashed using an OWASP-recommended algorithm. The work factor is configured such that a single digest takes more than 300 milliseconds to compute on our hardware.
User sessions are limited to a single device at a time and automatically expire after 30 minutes of inactivity.
Password resets are protected by captcha and require knowledge of the account username, email, and security question. A reset token sent to the account email address must be entered to verify the user has access to the address.
We are certified PCI compliant by SecurityMetrics and utilize Authorize.Net to store and process credit card or bank account information.
If you have an urgent need, you can contact us directly using the contact page.
