Managed Document Transfer - Redwave Commerce

By: Redwave Commerce  09-12-2011

For example:

  • All participants should have an audit history of data that they have sent or received.
  • The sender should be able to tell whether the recipient has retrieved the data that they have sent to them.
  • For some data types, users should be able to enter and view information via forms on a browser.
  • Users should be able to send a file and attach meta data to it. This can be fields of data that describe the file or key fields taken from the file. Meta data is used by recipients to route the file, create an index with search keys for later retrieval or collect required information into a data base without their having to view the file and key the data themselves.
  • There should be integrated workflow to manage the process. The recipient should be notified when there is data available for them and be reminded when they don’t retrieve or send data according to a defined schedule.
  • There should be the ability to parse and translate data between formats when the sender and recipient don’t use the same one.
  • When applicable, the data should be validated for syntax and semantics, notifying the sender of errors.

Redwave’s Managed Document Transfer service provides a managed portal based environment for companies to exchange data. Inexpensive and easy to use, companies can participate in the exchange without buying additional software or writing computer code or scripts.

Features of the service include:

  • A central portal provides an interface for participants to access and manage their account plus documents and files sent and received.
  • Files are securely routed between the sender and recipient(s). The sender can specify the recipient when they upload the file or the routing can be established according to data content and business rules.
  • Files can be parsed and data collected for use in validation, routing, process logic or presentation in reports.
  • Document transfers can be a standalone event, such as sending a weekly report, or an integrated business process. For example the process can include receiving a request for information, automatically creating a response form from the request where the recipient enters information, validating the data, attaching a file to the form, and submitting it back to the requester.
  • Management consoles let the companies see how the exchange is operating and compare performances.

Contact Redwave Commerce

Email - none provided

Print this page

Other products and services from Redwave Commerce


Contract Invoicing - Redwave Commerce

Any required business rules are applied to the data entered, such as a check for mandatory fields, test the validity of the contract number, test whether the invoice amount exceeds that specified in the contract, check if it is a duplicate invoice, etc.


Logistics - Redwave Commerce

The challenge facing the vendor is that they want to provide their customer with a consistent level of service regardless of the logistics model, recognizing that any issues that arise with fulfillment will reflect on them and potentially impact the existing and future sales.


Web Commerce Solutions - Redwave Commerce

The challenge with creating intercompany applications is the diversity in the partner community and the variation in effort and cost that they are prepared to endure in order to participate in the project. Solutions cover a range of B2B processes, including EDI based orders and invoices, drop shipments, contract invoices for services, shipment scheduling collaboration and more.


Other Web Commerce Solutions - Redwave Commerce

Redwave has worked with these customers to build what they require covering a range of processes, including vendor managed inventory, electronic catalogue integration, dental claims brokering, requests for quotes and delivery schedule collaboration.


Web Commerce - Redwave Commerce

Even for those partners that send and receive EDI documents, many implement a “rip-and-read” form of EDI, where they use a generic EDI package manually, printing off the inbound documents and keying in the outbound. As you expand your program to support less commonly used documents and smaller partners, you need to modify your approach to make it easier for your partners to participate.