EP2248047A1

EP2248047A1 - Device for exchanging documents between two parties through a network

Info

Publication number: EP2248047A1
Application number: EP09713036A
Authority: EP
Inventors: Philip Mathuis; Philippe Geleyn
Original assignee: B2boostcom
Current assignee: B2boostcom
Priority date: 2008-02-19
Filing date: 2009-02-17
Publication date: 2010-11-10
Also published as: FR2927711A1; WO2009104098A1; FR2927711B1; US20110035450A1

Abstract

The invention relates to a device for exchanging documents between two parties through a network that includes: an interface (13) arranged for receiving transmitter document data (16) from a network and including at least one transmitter identifier and one addressee identifier, a converter (15) capable of converting the transmitter document data (16) into intermediate document data (18) on the basis of a transmitter model associated with the transmitter identifier of the transmitter document data (16) while preserving the transmitter identifier and the addressee identifier, a generator (20) capable of converting the intermediate document data (18) into addressee document data (22) on the basis of an addressee model associated with the addressee identifier of the intermediate document data (18) on the one hand, and into archive document data (24) on the other hand, and a controller (14) arranged for calling the converter (15) with transmitter document data (16) received by the interface, for calling the generator (20) with the resulting intermediate document data, and for storing the resulting archive document data for further access by the transmitter or the addressee.

Description

Device for exchanging documents between two parties through a network

The invention relates to the communication of documents between parties connected by a wide area network such as the Internet.

In transactions, parties often need to share a transaction document with each other. In general, these parties each have their own computer system, and these systems are incompatible with one another.

To remedy this, it is therefore necessary to print the document, send it by mail or fax, and re-enter relevant information on each side in the respective computer systems.

This method is inefficient, slow, less secure than electronic network transport, and imposes significant logistics, the financial and environmental consequences of which are worrying for modern businesses.

The invention improves the situation.

For this purpose, the invention proposes a device for exchanging documents between two parties through a network, which comprises an interface arranged to receive transmitter document data from the network and comprising at least one transmitter identifier. and a recipient identifier.

The device also includes a converter, capable of converting issuer document data to intermediate document data, based on an issuer model associated with the issuer identifier of the issuer document data, and retaining the sender ID and the recipient ID.

It further comprises a generator, capable of converting intermediate document data on the one hand to recipient document data on the basis of a recipient template associated with the recipient identifier of the intermediate document data, and on the other hand archival document data.

Finally, this device comprises a controller, arranged to call the converter with transmitter document data received by the interface, to call the generator with the resulting intermediate document data, and to store the resulting archive document data. for subsequent access by the sender or recipient.

Such a device is particularly interesting because it allows secure and efficient management of document exchanges between parties with computer systems and formats that are not or not compatible.

This management is completely electronic, which is faster, cheaper and more environmentally friendly than paper-based and data capture solutions.

In addition, the recipient document data can be adapted to be directly processed by the information system of the receiving party. This is more efficient in logistical and organizational terms.

Finally, in the context of financial transaction documents, the operation of the device by a trusted third party can improve the resolution of conflicts, in particular by virtue of archiving document data.

The invention also relates to a method for exchanging documents between two parties over a network, which comprises:

a) sending a part of transmitter document data on the network to an exchange device, b) receiving in the exchange device issuer document data, which includes at least one issuer identifier and one recipient identifier,

c) converting in the exchange device the issuer document data to the intermediate document data, based on an issuer model associated with the issuer identifier of the issuer document data, and retaining the sender ID and the recipient ID,

d) converting the intermediate document data to the recipient document data in the exchange device based on a recipient template associated with the recipient identifier of the intermediate document data, the recipient document data at the destination document recipient, and

e) converting the intermediate document data to the archiving document data in the exchange device, and storing the archiving document data in the exchange device, and

f) the sending by the exchange device to the recipient of the recipient document data.

Other characteristics and advantages of the invention will appear better on reading the description which follows, taken from examples given by way of nonlimiting illustration from the drawings in which:

- Figure 1 shows a schematic view of a device according to the invention, and an exemplary data stream between two parts;

FIG. 2 represents an implementation diagram of the device of FIG. 1; FIG. 3 represents a particular implementation of a first operation of FIG. 2;

FIG. 4 represents a part of a particular implementation of a second operation of FIG. 2;

- Figure 5 shows another part of a particular implementation of the second operation of Figure 2; and

- Figure 6 shows a particular implementation of a third operation of Figure 2.

The drawings and the description below contain, for the most part, elements of a certain character. They can therefore not only serve to better understand the present invention, but also contribute to its definition, if any.

In modern enterprises, different departments such as production, sales, purchasing, accounting and others are linked through computer programs generally referred to as the information system.

As a result, the management of the activity and the day-to-day operation of these companies is based on these systems and their reliability. In the context of sales and purchasing operations, many difficulties arise because of the number of distinct information systems between parties, and their lack or lack of interoperability.

For this, it is often necessary to re-enter entire documents such as invoices or purchase orders, which results in significant losses of time and resources. On the other hand, the problems mentioned above arise even more acute for transactions in which a paper version and / or authentication are necessary to ensure the validity of the transaction.

In such cases, information systems are usually powerless to receive a third party document and provide the necessary authentication. Although there may be developments to allow such exchanges, these developments are extremely limited, and circumscribed only to the situations for which they were made.

Figure 1 shows an environment 2 in which an issuer and a recipient exchange transaction documents, such as orders or invoices.

The environment 2 comprises a transmitter system 4, an exchange device 6 and a destination system 8 which communicate with each other via a network 5.

The network 5 can be any type of known network, although the invention finds a particular application with an Internet type network.

Alternatively, the transmitter system 4 and the exchange device 6 may be connected by a first type of network, and the exchange device 6 and the destination system 8 may be connected by another type of network.

The transmitter system 4 is a computer system disposed at the party participating in the transactions that issues the documents to be exchanged. The transmitter system 4 may be a terminal connected to the information system of the transmitter, or it may be a single station decoupled from the other computer components at the transmitter.

The transmitter system 4 may comprise software that is run natively on a computer, or a web application that is executed remotely by the issuer, or any other type of application that generates a document that the issuer wishes to exchange with the recipient.

In general, it should be understood that the transmitter system 4 is a software or hardware computer component that is arranged to produce a document that the issuer wishes to exchange under a specific type and format.

The transmitter system 4 includes a network interface that allows it to connect to the Internet or any other network that will be adapted for communication between the transmitter system 4, the exchange device 6 and the destination system 8.

The recipient system 8 is functionally very similar to the transmitter system 4, in that it can be performed in substantially the same manner.

The main difference between the sending system 4 and the receiving system 8 lies in their role in the exchange, that is to say that one is at the origin of the exchange (the transmitter system 4), and the other is on receipt of the exchange (the recipient system 8).

However, these roles can be reversed depending on the exchange that is considered:

in the context of an order, a party that wants to receive products will be the sending system 4, and the other party that will produce them will be the recipient system 8;

- In the context of a billing, the party previously sending system may this time be the recipient system, and vice versa.

Due to the high integration of computer components in modern information systems, the exchange device 6 thus makes it possible to create a strong link route between parties who exchange products or services regularly, by simplifying and automating the processes. processes that are associated with these exchanges. The device 6 has two main parts:

a portal 10 whose role will be explained below; and

- an exchange processing unit 12.

The exchange processing unit 12 comprises a network interface 13 which enables it to communicate with the sending system 4 and the receiving system 8 as defined above.

The network interface is connected as input to a controller 14. The controller 14 manages the flow of data in the exchange unit 12, and calls a converter 15 when receiving a transmitter document 16 from the transmitter system 4.

The converter 15 has the function of receiving the transmitter document 16 as a result of an operation by the transmitter system 4, and of transforming it into an intermediate document 18 whose structure is specific to the exchange device 6.

The converter 15 operates on the basis of a storage 19 which contains description data of the transmitter documents 16. The storage 19 will be described in more detail below.

Intermediate document 18 can be saved in XML format. This format allows for increased integration into modern networks. Other formats can of course be considered.

Once the issuer document 16 has been converted into an intermediate document 18, the controller 14 transmits it to a generator 20. The function of the generator 20 is to generate several documents, including a recipient document 22 and an archiving document 24. Generator 20 operates on the basis of storages 26 and 28 which contain recipient document description data 22 and archival documents 24. Storages 26 and 28 will be described in more detail below.

The converter 15 and the generator 20 may be implemented in the form of locally or remotely executed programs, or in the form of dedicated circuits such as ASICs, or with other suitable integrated circuits.

In an advantageous embodiment, the generator 20 comprises a signature module that provides authentication to the archiving document 24 for archiving in a storage 30.

The signature can be made by any means known to those skilled in the art, whether in software or hardware. An example is a time stamp of the document.

Storages 19, 26, 28 and 30 can be made in the form of tables or databases that can be physically stored on the same support, or in different locations and supports. These storages can also be distributed, and be wholly or partly deported to remote storages.

Although they have been shown in the same frame 12 in FIG. 1, it will be understood that the controller 14, the converter 15 and the generator 20 can be made on separate computers joined together in the exchange unit 12, or on one machine.

Figure 2 shows a general diagram of the use of the exchange device 6 in the environment 2.

The implementation of the exchange device 6 comprises two main operations: in an operation 200, the exchange between the recipient and the transmitter begins with a preparation operation,

in an operation 300, the recipient and the transmitter use the exchange device 6 to exchange documents.

The operation 200 comprises an operation 210, in which the recipient prepares the portal 10. The portal 10 serves as a tool for the registration of transmitters in relation to the recipient, as well as for the management of exchanges.

The portal 10 can be customized to correspond to the graphic themes of the recipient, as well as to contain information elements on the recipient and on the operation of document exchanges with the exchange device 6 for new issuers.

Then, an operation 220 is performed, in which the recipient invites issuers to exchange documents with him via the exchange device 6.

In the embodiment described here, operation 220 comprises:

a registration operation, in which a new issuer or an existing issuer registers on the portal 10 to be linked with the addressee and to be able to send him documents. This operation is shown as an example in FIG. 4.

- An installation operation, in which an issuer installs a software element for connection to the exchange device 6, and performs a series of actions to adjust its exchange with the recipient. This operation is shown as an example in FIG. Operation 300 includes a document sending operation 310, and an archiving consultation and account maintenance operation 320. These two operations can be performed in parallel and are complementary.

The operation 310 is shown as an example in FIG. 6. The operation 320 is a generic operation that enables the recipient and the issuer to modify details of their accounts, to obtain exchange credits when they are it is necessary, and to consult the exchanges which concern them. Other typical account management / maintenance functions may be associated with the operation 320.

FIG. 3 illustrates a particular embodiment of the operation 210. The operation 210 can be performed by the combination of an operation 2100 and an operation 2200. The operations 2100 and 2200 can be performed sequentially or in parallel, as will be appreciated by those skilled in the art.

In operation 2100, the recipient defines a recipient document format. The recipient document format forms a template that is stored in the storage 26 and is used by the generator 20 to establish the recipient document 22.

Among other things, this template can be chosen to match the format of the recipient's information system, so that the recipient system information system 8 can directly integrate and use the recipient's document 26.

Optionally, the recipient can also define in the model information that he considers necessary for the exchange. As we will see below, in the absence of this information, the exchange can be blocked.

This makes it possible to improve the robustness of the device of the invention, since it is thus guaranteed that a certain number of data critical to the characterization of the exchange are well transmitted. Examples of such information may be recipient-specific codes for linking to its information system, recipient-specific or sender-specific data, and so on.

In the operation 2150, the recipient defines the portal 10 as mentioned above. Once the portal 10 is defined, the recipient can send invitations to the issuers with whom he wishes to exchange documents, by email or by any other appropriate means of communication.

At the end of the operation 2150, the storage 28 is modified to take account of the previous operations, so that a transmitter can be subsequently associated with the recipient.

Figure 4 shows a particular embodiment of the write operation of operation 220.

In this embodiment, a transmitter starts in 2200 an invitation received from the recipient. This invitation may have been sent by email or any other means of communication, in connection with Portal 10 or not.

The invitation 2200 is concretized by a visit in 2210 of the portal 10. This visit can be carried out by consulting a web page associated with the portal 10, or by connecting to any site or other media in connection with the portal 10 which allows the issuer to register a relationship with the recipient.

If the issuer has never used the exchange device 6, the registration starts with the entry of several details about his business, such as the name, the direct debit, the VAT number, the RCS number, other specific mentions related to the recipient etc. (operation 2220) Then, or in the case where the issuer has already used the exchange device 6, it is sufficient for him to enter his account credentials, and the issuer is directed to a subscription transaction 2230.

The purpose of the subscription transaction 2230 is to record the subscription of the issuer and the recipient to the terms of exchange of documents between them. This operation, although optional in certain applications of the invention, makes it possible to satisfy legal conditions that make it possible to certify some of the document exchanges between the sender and the recipient.

This operation can be carried out in a conventional manner by the use of a "Click-Wrap" form, that is to say that the issuer ticks a box pre-ticked for the recipient, which implies acceptance of the conditions defined by the text associated with this box. Other methods can also be considered.

Once these operations are completed, the registration of the transmitter on the portal 10 ends in 2240, with the provision of an application that will allow integration with the transmitter system 6.

The supply of the application in 2240 can preferably be performed by providing a hypertext link that allows downloading this application, or by sending an email containing such a link, or by any other means.

In the embodiment described, the application in question is a virtual print driver that will allow the sender to send a document from a software on the sender system 6 to the exchange unit 12.

This is especially useful because almost all computer programs have a print option, regardless of the operating system. Therefore, the implementation by a virtual printer driver allows a slight integration and no need for special development for each software.

The operation of this virtual print driver is as follows. In the desired software, the issuer creates the document he wants to exchange, and prints it with the virtual print driver.

This driver, instead of trying to print on a physical printer, transmits the print data stream to the receiving interface of the exchange unit 12 for processing by it.

In a first variant, the transmission of the data by the virtual printer is direct, that is to say that the print driver contains the physical address (URL) of the exchange unit 12, as well as identification codes when necessary.

In another variant, the virtual printer driver communicates with a web service which is secure, and which is responsible for transmitting the transmitter document data 16 to the exchange unit 12. This second variant makes it possible to increase security of communications by imposing an intermediary between the transmitter system 4 and the exchange unit 12.

Although the embodiment described above has a "direct" communication between the transmitter system 4 and the exchange device 6, other variants are possible in which an intermediate is placed between the two.

In addition, in other embodiments, specific integration means are generated and managed by the installed application, such as creating a network directory that corresponds to the exchange unit 12 or the like.

Thus, in the case where the transmitter uses a remote EDI system, the transmitter transmits data to this remote system, and this system converts them into EDI data. as desired by the transmitter. Therefore, the transmitter can configure the EDI system to transfer the generated EDI data to the device 6 instead of a direct transfer.

Alternatively, modules (or "plug-ins") may be developed to be integrated with the software for which the exchange is desired, or modules may be developed for the operating systems of the sending systems to initiate communication on pressing a key combination or a specific icon.

FIG. 5 represents a particular implementation of the operation of installation of the operation 2200. The transmitter starts in 2250 from the reception of the application of the step 2240, with the installation of this on the transmitter system 4.

Once the application is installed, or when the issuer was already registered and therefore had already installed the application, the installation program prompts the sender to open the software that generates the documents he wishes to exchange with the recipient. 2260.

It should be understood here that the invention is directed to any type of software that is contemplated for the exchange of transactional documents.

A loop begins then in which the transmitter will send to the exchange unit a number of standard documents which will serve as templates for the conversion of subsequent documents.

This loop starts in 2270 with the selection and printing of a test document on the virtual printer in the application.

In 2280, the exchange unit 12 receives the data stream from the sender model document, and seeks to associate it with other sender document models in the storage 19. When such a document is found, a return page appears to validate the correspondence with the existing model. The transmitter can then validate this correspondence in 2290.

As a variant, the validation of step 2290 can be carried out by an operator on the side of the exchange unit 12.

If no corresponding model document is found, or if the correspondence with the model is incomplete, feedback from the issuer is made in 2300 to create a new model that better corresponds to the standard document. The loop then resumes in 2270 to test the new model established.

Once the associated model document validated in 2290, the latter is stored in the storage 19 in correspondence of an identifier of the issuer, for example its account identifier established on the portal 10, or another identifier connected thereto.

Then, the issuer indicates in an operation 2310 if there remain standard documents to integrate. If this is the case, the loop resumes in 2270 with one of these documents.

Otherwise, the storage 28 is updated to indicate that the sender is now associated with the recipient (e.g., through a link in a database table), in an operation 2320, and the installation is completed at 2330.

In the event that the exchange of documents is conditioned by the purchase of credits by the issuer and / or the recipient, the installation of the application may include the offer to sell credits and / or the supply of credits. free to start.

Figure 6 shows an exemplary embodiment of the operation 310, that is to say the exchange of a document between an issuer and a recipient.

The exchange begins in 3100 with the printing in the sending system of a document to be exchanged on the virtual printer associated with the exchange device 6. The data stream is transmitted by the web service to the controller 14 via the network, and the latter transmits it to the converter 15, which analyzes in 3110 the contents of the stream to determine the recipient and the issuer.

This determination can be made on the basis of the analysis of the content of the flow or it can be based on the transmission of identifiers of the sender and the receiver which can be interpreted by the exchange unit 12.

Once these elements have been determined, the converter 15 interrogates the storage 28 to determine in 3120 whether there is a relationship in this storage between the sender and the receiver. Concretely, this corresponds to determining whether the operations described with the preceding figures have been carried out, and if there are accordingly models of issuer document and recipient document.

If there is no match, an error function is called in 3130 which can invite the recipient to register to exchange documents with remitter.

In case of correspondence, the converter 15 continues its analysis of the document received from the transmitter to determine the text fields it contains, and to classify them as 3140 based on the issuer document templates taken from the storage 19.

Then, in 3150, the converter 15 associates the fields determined in 3140 with mandatory fields prescribed when defining the recipient's needs.

In 3160, the converter 15 checks whether the fields are sufficient to appropriately define a document of exchange. If it is not, the error function 3130 is called to signal it.

If the mandatory fields are present, the converter 15 generates the intermediate document 18 which is transmitted by the controller 14 to the generator 20. The intermediate document 18 serves as an information vehicle for the processing by the controller. generator 20. The intermediate document 18 contains the issuer and recipient identifiers, which simplifies the rest.

The generator 20 calls at 3180 storage 26 to determine the format / pattern of the recipient, and generates and sends the recipient document 22 thus formatted at 3200.

Then, or in parallel, the generator also generates a control copy or archiving document 24 in accordance with what has been defined by the recipient in agreement with the remitter during the preparation and installation steps.

Optionally, the archival document 24 may be certified or otherwise authenticated prior to storage, for example by tagging. The format of the archiving document 24 may also be dictated in part at least by certification validity requirements.

It should be understood that the archival document 24 may further include several copies of documents that attest to the transaction. In the example described here, although reference is made to a single archival document 24, it actually includes a copy of the recipient document 22 and a copy of the issuer document 16.

The archiving of the recipient document 22 and the issuer document 16 makes it possible to provide a simpler conflict situation management since it offers a copy of the documents received / issued by the parties from a trusted third party. In other embodiments, archiving can be done with other formats.

Finally, this operation ends in 3210, and a copy of the archiving document 24 is transmitted by the interface 13 to both parties to inform them that the transaction has been conducted. Alternatively, it is a message that can be sent.

The solution described above is particularly interesting because it offers a very strong decoupling of the document formats for the transmitter and recipient. Indeed, each party can respectively issue and receive a transaction document in a format of its own.

This is particularly advantageous in the context of international transactions, which may require great specificities on each side to be authenticated.

On the other hand, by releasing the parts of the format constraints related to the transactional documents they exchange, the invention makes it possible to offer a global exchange platform.

All the participants of the same industry can be found on this platform, whether distributors or sellers, without any adaptation being necessary at the level of their respective computer systems.

In the foregoing, it will be appreciated that all variants can be combined with each other to the extent of their compatibility. Although preferred modes have been presented, it goes without saying that the invention encompasses all of these variants and their combinations.

Claims

claims

A device for exchanging documents between two parties through a network, characterized in that it comprises: an interface (13) arranged to receive transmitter document data (16) from the network and comprising minus an issuer identifier and a recipient identifier, a converter (15), capable of converting issuer document data (16) to intermediate document data (18), based on an issuer model associated with the issuer identifier of the issuer document data (16), retaining the issuer identifier and the recipient identifier, a generator (20) capable of converting intermediate document data (18); ) on the one hand with recipient document data (22) on the basis of a recipient template associated with the recipient identifier of the intermediate document data (18), and on the other hand with document data of archiving (24), and a controller (14), arranged to call the converter (15) with transmitter document data (16) received by the interface, to call the generator (20) with the resulting intermediate document data, and to store the resulting archive document data for subsequent access by the sender or recipient.

2. Device according to claim 1, characterized in that it comprises means for marking the archiving document data (24).

The apparatus of claim 1 or 2, characterized in that the archival document data (24) comprises a copy of the issuer document data (16) and a copy of the recipient document data (22).

4. Device according to one of the preceding claims, characterized in that generator (20) is arranged to determine a correspondence between the issuer identifier and the recipient identifier.

Device according to claim 4, characterized in that the generator (20) is arranged to generate the recipient document data (22) and the archive document data (24) on the basis of the correspondence between the issuer ID and the recipient ID.

6. Device according to one of the preceding claims, characterized in that it comprises a transmitter model storage memory (19).

7. Device according to one of the preceding claims, characterized in that it comprises a storage memory (28) recipient template.

8. Device according to one of the preceding claims, characterized in that it further comprises a portal (10) associated with the destination system (8), and in that the gate (10) is arranged to provide an application to allow sending issuer document data (16).

9. Device according to claim 8, characterized in that said application is a virtual print driver.

A method of exchanging documents between two parties over a network, characterized in that it comprises: a) sending a part (4) of sender document data (16) on the network to a network exchange device (6), b) receiving in the exchange device (6) the issuer document data (16), which include at least one issuer identifier and one recipient identifier, c) the conversion in the exchange device (6) of the issuer document data (16) to document data intermediate (18), based on an issuer model associated with the issuer identifier of the issuer document data (16), retaining the issuer identifier and the recipient identifier,

D) converting in the interchange device (6) the intermediate document data (18) to the recipient document data (22) on the basis of a recipient template associated with the destination identifier of the data of the destination data; intermediate document (18), the document data from

Recipient (22) to the recipient, and e) converting the intermediate document data (18) into the interchange device (6) into archival document data (24), and storing the document data of the document archiving (24) in the exchange device (6), and

F) sending by the exchange device (6) to the recipient (8) the recipient document data (24).