WO2021144441A1

WO2021144441A1 - Nfc-based transactional transfer of transactional details and control method of a transaction

Info

Publication number: WO2021144441A1
Application number: PCT/EP2021/050843
Authority: WO
Inventors: Henrik HVILSHØJ; Thomas Kjær PALLESEN
Original assignee: Deviking License Aps
Priority date: 2020-01-16
Filing date: 2021-01-15
Publication date: 2021-07-22

Abstract

A method and system for monitoring and controlling a transaction between a provider and a receiver comprising an provider's and receiver's NFC system, comprising an NFC reader/writer and an app, the NFC reader/writer having reading and writing capabilities to a NFC tag and is in communication with NFC app, a provider's and/or receiver's tag, comprising memory, transferring capacities to an NFC system and a encoded unique identification number, wherein a data communication occurs when the NFC tag is "tapped" with a NFC reader/writer of a NFC system transferring order and transaction details between the receiver and the loader.

Description

NFC-based transactional transfer of transactional details and control method of a transaction

FIELD OF THE INVENTION The present invention relates to a method and system for transferring, controlling, and monitoring of transactional details using a NFC system and one or more NFC tags.

BACKGROUND OF THE INVENTION The present invention relates to the control, transfer, and monitoring of transactional details.

Transaction tracking is an important aspect in many industries, especially in the delivering and carrier industry, such as in quarries and building material deliveries, wherein a delivery driver is assign to pick up a product on behalf of a customer. A delivery driver can be assign multiple customers and drivers may not be assigned to a fixed truck. Critical transactional details will therefore change throughout the day and the driver is responsible for keeping track of the changes in information.

Today's systems relies on physical copies of weight slips, which is manually filled out at the site by the person loading the goods. The receiving person will take a picture of the weighing slip for record keeping and send it to his/her own company. This creates additional problems in the process, since the picture is often of poor quality and each of the provider's and receiver's companies will have to perform additional administrative tasks in order to monitor and control the transaction.

Further, the provider of the products and goods might mistake the identity of the trucks, such that the invoice will contain the wrong identification information, resulting in the invoice being sent to the wrong customer or additional checks are needed to ensure that the correct customer is identified. This is further enhanced since most delivery drivers will drive for multiple customers and the driver might change trucks at the last minutes further increasing the confusion relating to the identity of the delivery drivers and what goods or products have been transacted. These normal transaction details are also carried out by handwriting the order transaction details and identification information onto the order sheet or weight slip, creating many possibilities for the provider and the delivery driver to make mistakes, misspell and/or misinterpreting information.

US 5,848,368 discloses a method for controllably loading a haul vehicle, with a payload material desired by a customer, using a mobile loading machine. An identification tag, located on the haul vehicle, is read by an identification tag reader, located on the mobile loading machine. A haul vehicle identification signal is produced from the reading, and compared to customer data files. A load command signal, containing selected information from the customer data file that corresponds with the haul vehicle identification signal, is produced.

However, such a method disclosed in US 5,848,368 does not allow any flexibility in the loading schedule of the haul vehicle, as a specific pre-determined haul vehicle is required nor does it allow a different haul vehicle to arrive in the case of breakdowns. Further, a customer of the haul vehicle does not obtain any information about the loading process.

Hence, an improved transaction controlling, transferring, and monitoring method and system would be advantageous.

OBJECT OF THE INVENTION

It is a further object of the present invention to provide an alternative to the prior art.

In particular, it may be seen as an object of the present invention to provide a method and system that solves the above mentioned problems of the prior art of errors in mistaking the transaction details and identification information. SUMMARY OF THE INVENTION

Thus, the above-described object and several other objects are intended to be obtained in a first aspect of the invention by providing a method for monitoring and/or controlling a transaction between a provider and a receiver, the method preferable comprises the steps of providing the provider with a NFC system, the NFC system may comprise a NFC reader/writer and an NFC app in connection with the NFC reader/writer, providing the receiver with a NFC system, the NFC system may comprise a NFC reader/writer and an NFC app in connection with the NFC reader/writer, providing the receiver and/or the provider with an NFC tag with an encoded tag identification number associated with a unique receiver or provider, wherein the NFC system and the NFC tag(s) may provide a first communication channel by transferring data pertaining to the transaction, including the encoded tag identification number, inputted into one of the NFC app's to the other NFC app by use of a NFC tag and the NFC reader/writers, inputting by the provider into the provider's app the transaction details, such as the quantity and type of goods that has been transacted, transferring the transaction details from the provider's NFC system to the receiver's NFC system by use of the first communication channel using either the receiver's or provider's NFC tag.

By provider and receiver is preferable meant the person or the entity responsible for the action of either providing a product or receiving, such that the provider and receiver may be a truck, the person driving the truck or the end-customer.

In another aspect of the invention, a method for transferring, monitoring and/or controlling a transaction, including transactional details between a provider, such as a provider company, and a receiver, such as a receiver company, such as a customer, the method may comprise the steps of providing an entity associated with the provider, such as an employee or loading vehicle or weighing station, with a NFC system, the NFC system may comprise a NFC reader/writer and an NFC app in connection with the NFC reader/writer, providing an entity associated with the receiver, such as the delivery truck, with a NFC system, the NFC system may comprise a NFC reader/writer and an NFC app in connection with the NFC reader/ writer, providing an NFC tag associated with the receiver's entity, the NFC tag may comprise an encoded tag identification number uniquely identifying the entity, wherein the NFC system and the NFC tag provides a first communication channel by transferring data using the NFC tag and NFC readers/writers, where the encoded tag identification number identifying the entity on the NFC tag will always be transferred to the NFC reader/writer, from one of the NFC app's to the other NFC app, the transferring includes

- recording, preferable after completion of the transaction, such as after loading of the required material, in the provider's entity NFC app transactional details, such as loading details, which could be information normally present in a weighing slip, such as the quantity and type of goods that has been transacted, details about the provider etc.,

- transferring the transactional details, using the first communication channel from the provider's entity NFC app to the receiver's entity NFC app, the transferring may comprise o transferring the transactional details on the provider's entity app to the receiver's entity NFC tag using the provider's entity NFC reader/writer and transferring the encoded tag identification number identifying the receiver's entity to the provider's entity app, such that the provider's entity app will contain information identifying the receiver's entity, o transferring the transactional details on the NFC tag to the receiver's NFC app using the receiver's NFC reader/writer, where the receiver's entity app after the transfer will contain the transactional details and the provider's entity will have information on the entity responsible for the transaction of the receiver, such that both the provider's and receiver's companies may have the required transactional information.

An entity associated to a provider could be a bulldozer, a wheel loader, a combine harvester, a suction dredger, etc. An entity associated to a receiver could be a truck, a third-party hauler, a tractor with trailer, a barge, a landfill and environmental centre.

A receiver could be a delivery company, a person off-loading materials at a landfill or environmental centre. The receiver and entity of the receiver could be different companies and entities or could be the same entity.

A provide could be a quarry, an environmental centre etc.

Having a system wherein a data transfer transfers identification information of the receiver to the provider and transactional details from the provider to the receiver may be beneficial, since both the receiver and the provider may have the information required to update their internal systems and send invoices and complete internal procedures.

The method may further allow for an automatic loading process, wherein the provider's NFC system is located on a platform at the loading place or at the entry to the site, such that no manually interchange of information is required. This will ensure that data errors are minimalised both on the receiver's and provider's side of the transaction.

In an embodiment, the method may further comprise encoding pre-transactional order details, respectively, into the receiver's entity and/or the provider's entity app, such as customer information, case information, billing information, etc., before the transaction and may further comprise merging them with the transactional details after the transaction.

In the following description, receiver's entity XX and receiver's XX is used interchangeable, such that receiver's entity NFC and receiver's NFC refers to the receiver's entity.

The pre-transactional order details may be different from the provider and receiver, since these data may originate from different systems. The receiver may have more detailed information on the final customer, such as in the case of a delivery driver, which may have additional information on the delivery address, and the provider may only have information needed for invoices, which could also come from recording the transactional information into the app.

In an embodiment, the method may comprise merging the transactional details with the pre-transactional order details in the receiver's entity NFC app and/or merging the identification of the receiver with the pre-transactional order details in the provider's entity NFC app.

In an embodiment, the method may comprise sending the transactional details from the receiver's entity NFC app to the receiver. This could be accomplished by a server or the likes connected and accessible by the receiver.

In an embodiment, the method may comprise providing the provider's entity with a printer connected to the NFC system and may include the transactional details, such as a receipt or weighing slip, being printed after the transferring of the transactional details to the receiver's NFC tag and receiver's identification to the provider entity.

In an embodiment, the method may comprise printing the transactional details at a third NFC system, preferable associated with the provider, and connected to the printer.

In such a step, the pre-transactional details may be information on the receiver id, which is ideal in the case of a generic delivery driver picking up goods from a provider, such that the transfer of information also includes information on the customer, here the receiver.

The receiver may therefore be a customer and an entity associated with the receiver may be an independent delivery driver. The receiver may also be a transportation company employing the delivery driver.

After the transfer, the delivery driver will have the required information to document the transaction to the customer and the provider will have enough information to send the invoice either to the delivery driver or the customer. This information on the customer could also be tied to the pre-transaction order details in the provider's app to a specific transaction based on the delivery driver, here the entity associated with the provider. Such that the invoice information from a customer is found based on the identification of the delivery encoded tag identification number.

In an embodiment, the method may further comprise transferring identification information about the receiver's entity and/or receiver to the provider's entity or provider via the first communication channel in a separate step before the transferring of the transactional details.

In an embodiment, the method may comprise supplying a second NFC reader/writer associated with the provider, wherein the transferring of identification information, preferably of the receiver, is completed at the second NFC reader/writer.

This is advantageous, since then at the entry to a site, such as a quarry, the receiver entity may transfer the information identifying him. After completion of the transaction, which could be loading of gravel to a truck, the weighing details could be transfer at another stand containing the provider's first NFC system. Both of the NFC systems associated with the provider could then be connected to a local server, where the information needed for the invoicing will be collected and merged.

In an embodiment, the method may comprise deleting the loading details on the receiver's entity NFC tag when transferring the transactional details. This will ensure that the NFC tag is ready for the next transaction.

In an embodiment, the method may further comprise the step of transferring further unique identification information to the receiver's and/or provider's NFC tag by use of the NFC systems.

This is advantageous when one wants to identify the specific person of the provider and receiver or the specific customer, since a unique tag to that person may be assigned irrespectively of the physical NFC tag provided. Further, multiple persons may have multiple tags and further unique identification information may help in identifying the person across different tags, or when a tag is shared among multiple person. This further unique identification information may be transferred from the NFC app to the NFC tag.

In an embodiment, the method may further comprise the step of always transferring the further unique identification information encoded in the NFC tags when using the first communication channel.

In an embodiment, a Commodity ID is transferred to the app and to the tag of the receiver, wherein the Commodity ID identifies the product to be transacted. This information may be transferred at the second NFC system, such that the provider's entity may know what product to the transacted.

In an embodiment, the method may further comprise the step of communicating pre-transactional order details, from the receiver to the provider using a second communication channel or the first communication channel, such as indicating the quantity and type of the goods to be received before the transaction.

This is advantageous, since in such embodiments all of the details required in the transaction may be communicated using the first communication channel and mistakes, misspelling and misinformation may be eliminated.

In an embodiment, the step of transferring the further unique identification information to the NFC tag of the provider or receiver may occur when transferring, respectively, the transactional details or pre-transactional order details.

This is advantageous in situations, wherein the tag is associated to a non-human entity in the transaction, such as the truck or the excavator, such that the driver of the entity may transfer identifying information to the tag identifying the driver when transferring the relevant details. The tag may in such embodiments also convey the information of the human entity in the transaction process. In an embodiment, the method may further comprise the step of connecting the provider's and receiver's NFC systems to, respectively, a provider's server and a receiver's server.

In an further embodiment the method may further comprise the step of connecting the receiver's and provider's server to one or more main system(s), that may be accessible by one or more user(s), which may read and write to the receiver's and provider's servers using the main system(s), the main system(s) may comprise identification information relating to the one or more user(s), the main system may further be connected to each other by an API.

This is advantageous, since in some embodiments, as all the information, both the pre-transactional order details and transactional details, used in process may be communicated via the first communication channel, such that both the provider and receiver will have completed transaction details, which may be sent to their respective companies and accounting divisions. The transaction monitoring may therefore from the view of the provider and the receiver be viewed as automatic.

In an embodiment the NFC tag's encoded tag number, may be, respectively, matched with the provider or receiver in the main system(s).

In an further embodiment, the method may further comprise the step of transferring from the receiver's server the further unique identification information of the user and/or receiver to the receiver's NFC system(s) for transferring to the NFC tag(s). This further unique identification information may also be matched with a provider or receiver or user in the main system.

In a further embodiment the method may further comprise the step of displaying on the receiver's app an order information list obtained by an external application, which may be in communication with the receiver's server or main system.

In an further embodiment the step of sending the transaction details, pre transactional order details, and/or the identification information to the provider's server and/or receiver's server may be delayed until a stable connection is achieved and/or done by the provider and/or receiver by instructing the provider's and/or receiver's app to commence the transfer.

In an embodiment, the transaction process may occur in a quarry, building supply distributor, and environmental centre transaction process.

In an embodiment, the identification information relating to the specific user may be transferred to the receiver's NFC system according to the selected order, preferable from the booking and ordering application. This information will, in some embodiments, be part of the pre-transactional order details that may be changed according to the specific transaction.

In an embodiment, the identification information and the pre-transactional order details may be matched in the main system with a user. This user may be the companies or customer behind the transaction.

In an embodiment, the method may further comprise a step of transferring the goods from the provider to the receiver and confirm the transfer using the provider's and/or receiver's app, and may send a confirmation to the provider's and/or receiver's server.

In an embodiment, the provider's NFC app may specify what types of pre transactional order details, the provider can input, such as a dropdown menu of the available goods.

In an embodiment, the interface may be configured such that a user can read and write to the servers.

In an embodiment, the connection between the provider's and receiver's app and the NFC reader/writer may be a closed connection, such as Bluetooth, cable connection etc., and the connection between the provider's and receiver's app and the main server may be an open connection, such as an internet connection. In an embodiment, the receiver's server may be configured to be in data connection with an external application, such as a booking and ordering application for receiving an order list.

In an embodiment, the NFC system may be implemented on a handheld device, e.g. a telephone, tablet etc.

In a second aspect of the present invention a system for controlling and monitoring a transaction is provided, wherein the system may comprise an provider's and receiver's NFC system, comprising an NFC reader/writer and an app, the NFC reader/writer may have reading and writing capabilities to a NFC tag and may be communication with NFC app, a provider's and/or receiver's tag, comprising a memory, transferring capacities to an NFC system and may have encoded tag identification number, wherein a data communication may occur when the NFC tag is "tapped" with a NFC reader/writer of a NFC system.

In an embodiment, the system may further comprise a server in connection with the provider's NFC system and a server in connection with the receiver's NFC system.

In an embodiment, the provider's and/or receiver's server may be connected to one or more main system(s), which may accessible by a user of the receiver and/or the provider.

Preferable, by NFC tag is meant a passive physically or virtually implemented device capable of storing information and sending and receiving information by use of the NFC reader/writer.

Preferably, by NFC reader/writer is meant an active device capable of writing and reading information on the NFC tag.

By pre-transactional order details are preferable meant data that can be inputted before the transaction and this information could be different from the provider and receiver and could be missing in some embodiments. This data is also normally referred to as order details. These data could be customer case number, a desired quantity, the name of the customer and the type of goods to be received, driver name, vehicle registration number (number plate), case number, Commodity ID information or a sub-set of the above.

By transactional details is preferable meant details originating from the provider, such as details normally found on weight slips, or transaction receipt, i.e. receipt number, provider name, type of goods, quantity, customer name, customer case number, vehicle registration number (number plate), drivers name, remarks, etc. These data are the actual transferred amount and type.

There could be common entries in the transactional and pre-transactional details and the terms should not be construed to mean separate data entries, as the data entries could be the same. The terms are preferable used to indicate time steps in the transactional process.

By tap is preferable meant physically moving the passive NFC tag towards an NFC reader/writer, such that an induced voltage field, resulting from the magnetic field of the NFC reader/writer, can power the passive NFC tag and either transfer and store data on the tag or transfer and read data stored on the tag.

The individual aspects of the present invention may each be combined with any of the other aspects. These and other aspects of the invention will be apparent from the following description with reference to the described embodiments.

BRIEF DESCRIPTION OF THE FIGURES

The system and method according to the invention will now be described in more detail with regard to the accompanying figures. The figures show one way of implementing the present invention and is not to be construed as being limiting to other possible embodiments falling within the scope of the attached claim set.

Figure 1 illustrates an exemplary embodiment of the invention,

Figure 2 illustrates an embodiment of system configurations,

Figure 3 illustrates a further embodiment of a system configuration, Figure 4 illustrates an embodiment wherein the transaction and identification information is transferred,

Figure 5 illustrates the data flow in an embodiment,

Figure 6 illustrates the steps involved in an embodiment of invention,

Figure 7 illustrates the input into the customer files related to an embodiment of the invention,

Figure 8 illustrates an embodiment different modules of the invention in a quarry situation and

Figure 9 illustrates an embodiment of an IWLAN configuration.

DETAILED DESCRIPTION OF AN EMBODIMENT

In the following, the invention will be described in relation to specific embodiments.

Referring to figure 1, an exemplary embodiment of the invention is shown. In this embodiment, a method for monitoring and/or controlling a transaction between a provider 1 and a receiver 2 is shown. Such a transaction could either be the transfer of goods between the provider 1 and the receiver 2, such as in the case of a quarry or it could be a transfer from the receiver 2 to the provider 1, in the case where the provider 1 offers a service, such as in recycling plants or dump sites. The receiver and provider is represented by an entity 1, 2 associated with the receiver or provider.

In a first step of the method, an NFC system, respectively 3 and 4, is provided to the provider 1 and the receiver 2. The NFC systems 3 and 4 being distinct from each other, such as both physically and functionally distinct.

In an embodiment, the NFC systems will, respectively, comprise an NFC reader/writer, 6 and 8, and an app, 5 and 7. Each of the components in the NFC system can be physically and spatially separated, such that the app is implemented on a mobile phone or tablet and the reader/writer is a separate device or it could be implemented in a single tablet or mobile phone. The NFC reader/writer is adapted to read and write data on/to an NFC tag. Further, an NFC tag, 17 and 18, is provide to either an entity associated to the provider or the receiver or both. In the following provider NFC tag, NFC system etc. is referring to an entity associated with the provider. The same applies to the receiver. In a preferred embodiment, the receiver will always possess a NFC tag 17. Each of the NFC tags have inbuilt tag identification number, system-id, encoded into the tag 17, 18. The NFC tag(s) 17, 18 further comprises memory for storing data, as well as being able to establish a data transfer connection between the NFC reader/writer 6, 8.

In some embodiments, each identification number is associated to a single entity associated with a provider or receiver, such that they are identifiable by their NFC tag's identification number. In most embodiments, the identification number is always transferred and registered with the NFC system both when data is read from the tag and when data is written to the tag. The will in some embodiments be contained in a log file of the data transfer, which can be accessed by the NFC apps.

In some embodiments, a single tag is shared between the provider and receiver, such that each NFC reader/writer can overwrite information on the tag. In another embodiment, the NFC reader/writer can read both the provider's and receiver's tag, but can only write to the tag associated with their system. This is useful when tags are company based.

It is possible to implement the NFC system and the NFC tag in a single device, in such cases the NFC tag is a virtually tag implemented in the NFC app. This occurs in NFC peer-to-peer transfers processes. This could for example be the case if smart phones are used. Further the systems could be implemented in a tablet, a screen etc.

The NFC systems will provide a first communication channel 9. This communication channel consist of transferring data from one NFC system to the other NFC system by the intermediate use of a NFC tag. The transfer occurs by transferring data to a NFC tag, storing the data on the NFC tag's memory, by use of the write functionality of the NFC reader/writer and transferring the data on the NFC tag to the other NFC system by use of the read functionality of the other NFC reader/writer. In the transfer of data, the tag identification number of the used tag is transferred as well. The data is typically commenced by "tapping" the tag on the NFC reader/writer transferring the data. In the first communication channel 9 at least two taps with the NFC tag are therefore needed.

When the transfer occurs from the provider to the receiver using the receiver's NFC tag, the provider will therefore receive the encoded tag identification information of the receiver's tag, as well as further identification information on the NFC tag if such information are transferred to the tag.

In a second step, the provider will input into the app 5, the transactional details, such as the quantity and type of goods that has been transacted. These transaction details will depend on the transaction situation, but will be the actual amount received by the receiver, and in the case of a quarry will constitute the weighing details on the weighing slip. It could include price, price pr. Kilo, transaction number Etc., end-customer,

In a third step, the transactional details will be transferred to the receiver by use of the first communication channel 9. This transactional details data will be transferred to an NFC tag 17, 18, which will be used to transfer the data to receiver's NFC system. In a preferred embodiment, the NFC tag, is in this step the receiver's NFC tag 17, such that the identification number of the receiver entity is received by the provider in the first tap. This will ensure that the provider will have information on the entity completing the transaction. The transaction details will, in some embodiments, also contain data identifying the provider's as well as information relating to the transaction, such as Commodity ID information.

If the provider's NFC tag is used, the receiver will receive the identification number of the provider, but this information could be part of the transactional details and could be used if the receiver loses his/hers tag. In both cases, a monitoring of the transaction is possible, as either the receiver or the provider will have information identifying all the transaction partners. Further, the transactional details may contain identifying information of the provider, such as the company the provider works at. In some embodiments, parts of the transactional details could stem from the receiver and a transfer from the receiver to the provider.

In some embodiments, further unique identification information is encoded in the NFC tag 17, 18. This will be encoded in the free writeable memory of the NFC tag. This further identification information could, in some embodiments, be the billing and company information of a customer of the receiver, but may be any other information identifying the receiver and/or other important identification information of the transaction. If the tag is associated to a truck, this further unique identification information may be information identifying the person completing the transaction or driving the truck. This is advantageous in applications where the provider needs additional information about the receiver in order to create an invoice or complete the monitoring of the transaction. This information could be pre-selected from a list interlink with the transaction type.

It could also be information relating to a customer of the receiver or associated company of the provider. In the case of a quarry, such information identifying the provider could be information relating to the quarry and subsection, such as department within the quarry, bay number or transaction number. In the case of a receiver, this further identification information could be information identifying a customer or order number. This information could also be transferred by the second communication channel 10.

The information, in the embodiments wherein the receiver's NFC tag 17 is used, could be information identifying the specific provider, such that the receiver will always receive identifying information of the specific provider. This enables the receiver to have complete information about the transaction.

Therefore, in an optional step of the method the receiver's identification information are registered with the receiver's NFC system 3, preferable in the app associated to the receiver. The identification information are typically the billing and company information of the receiver's, but may be any information identifying the receiver. This information is transferred to NFC tags before the transaction and will constitute the further identification information. This information could also be transferred by a second communication channel 10, wherein the second communication, in some embodiments, is verbal.

Since the identification information of the receiver or provider may be provided for in individual physical NFC tags, such that each NFC tag is unique for a specific receiver, the provider or receiver does not need to input or actively record this identifying information during a working day. This is especially useful when further identification information is transferred to the tag, as it streamlines the transaction process. For example, some trucks may have an NFC reader/writer integrated in the dashboard. These trucks might be shared between multiple chauffeurs and jobs. Each chauffeur will receive a unique NFC tag, which identifies him or her. The chauffeur will then be able to change trucks, without needing to notify the provider about the change, as all of the identification information is on the individual tag. In the case of a truck change, the identification information is transferred with the chauffeur. Further, the receiver might give the wrong customer information for an order, if done manually or by the truck driver. Misidentification will therefore be minimized, as the transfer will be automatic.

Before the transaction pre-transactional order details may be encoded within the apps (5, 7), such as customer information, case information, billing information, etc. These data could be different from transaction to transaction and different from provider to receiver. The receiver could in some embodiments not have any pre-transactional data encoded and will in this case get all the information from the provider.

In some embodiments, the further identification information is always transfer during a data transfer between a NFC reader/writer and the tap.

In some embodiments, the further identification information is transferred to the NFC tag alongside the transactional order details, such the further identification information relating to the provider is part of the data packet of the transaction details.

Further, in an embodiment the pre-transactional order details are communicated from the receiver of the goods to the provider of the goods using a second communication channel 10 or the first communication channel 9, indicating the quantity and type of the goods to be received or other relevant information, such as Commodity ID.

Using the first communication channel to also exchange the pre-transactional order details, ensures that spelling error, miscommunication and other things prone to errors is eliminated.

This second communication channel 10 can, in an embodiment, be verbal, written, and/or non-electronic electronic. The main point is that the second communication channel is distinct from the first communication channel, and gives the receiver a flexibility to change his/her order, such as if last-minute changes requires a different quantity or if a receiver has called in sick and a replacement is sent, such that the communication channel is only reliant on the receiver. This eliminates the potential problem of old information or inflexible loading sequences being used in the transaction/loading process; since the receiver or the receiver system always has the most up-to-date information, pertaining to which goods needs to be transferred/loaded.

The first and second communication channel 10 will only depend on the NFC tags. The first and second communication channel is, in an embodiment, not dependent on an internet connection or a connection to a server. This has the effect that a transaction can always occur irrespectively of a connection to a server. This is especially useful in deep quarries and loading places with no/bad internet connectivity.

In some embodiments, the pre-transactional order details will contain information coming from a customer, such as desired quantity, type, delivery place, pick-up place. Not all of these information are necessarily being transferred using the first communication channel and is based on the specific transaction.

After the order has been received by the provider, in an embodiment, the NFC's systems will transfer from the receiver's NFC system 3 to the provider's NFC system 4, the receiver's identification information. This transfer of data is an automatic process by the NFC systems, such that misinformation and miscommunication relating to the receiver's identity and affiliation is avoided. In an embodiment, the receiver will tap his/her tag on the provider's NFC reader/writer, transferring the data to the provider's NFC system and app. This can, in an embodiment, occur as a separate process in the case of the pre transactional order details being communicated using the second communication channel 10 or in the same process as when the pre-transactional order details are communicated using the first communication channel 9. This could be also completed at a second NFC system 29 associated with the provider.

Miscommunications between the provider and receiver are frequent in transactions processes, such as in the case of a provider mistaking the identity of a truck in a truck sequence, since different companies may use the same delivery services and different trucks may have the same appearance. By using a tag with pre-transactional information on it, such problems are overcome.

The identification information are used as input in the provider's app 5. This transfer process is typically done by a NFC tap, which is a local transfer of information. The tap could occur at the loading zone with the NFC system of the provider being placed at a fixed place or by the provider and receiver meeting and tapping their systems together. The NFC tag does not necessary form a physical unit with the NFC app and NFC reader/writer.

By having two distinct communication channel, one for communicating order and transactions details and one for communicating identification information, the process becomes more flexible, such that the trucks are not required to arrive in a particular order nor in a designated vehicle. The method further does not require an internet connection. Manual inputting at the transaction location is also minimized using the first communication channel, minimizing errors.

When the identification information has been transferred or before the identification information of the receiver has been transferred, the provider will input into his/her app the transaction details of the order. The transactional details could either be information relating to the goods that has been received or loaded by the provider. This information is matched with the identification information of the receiver, preferably at the transfer step, such that an entry in the provider's app is both the transactional details and the corresponding identification information of the receiver. The provider will provide the transaction details and the receiver will provide the identification information. This will provide the receiver and provider with the required information about the transaction.

Referring to figure 2, different embodiments of the invention are shown. In a first embodiment, the NFC systems of the receiver and the provider may be connected to the provider's 11 and receiver's server 12, such that the NFC app 5 and 7 can transfer the inputted information, such as the pre-transactional order information and the receiver's identification information to the servers.

The receiver's server may provide the identification information for the receiver's NFC system 3, such that the NFC system 3 downloads the relevant information from the receiver's server 12.

In an embodiment, a main system 13 may further be connected to the receiver's and provider's server and accessible by a number of users 14, 19, the users being able to access and input information into the main system. The main system may be a web interface connected to the servers. This allows a user distinct from the provider and receiver to access the transaction details, such that they can monitor, receive receipts and approve invoices in the main system interface.

In the main system, the provider's and receiver's entities NFC tag's encoded tag identification number is matched, respectively, with a provider and a receiver. As the tag(s) identification numbers are unique for each tag and each tag is preferably only used by one provider or receiver, the tags can be used as an identification tool. Every transfer will contain, in one embodiment, the identification number in the metadata of the transfer.

The main system further allows the receiver to receive further identification information relating to the user. The information of the user is the further identification information of the provider or receiver stored on the NFC tag in addition to the encoded unique system identification number. This further identification information is optional, while the encoded unique system identification number is always present on a NFC tag.

The main system and servers may then, in an embodiment, contain the metadata of the users associated to a receiver, which can be transferred to the tag 17, 18.

In the case of a receiver only having one user associated then they data might be the same.

The main system will be the connection between the users, e.g. between a haulier which is typically the receiver, and a customer of the transaction, which in the building industry might be a main contractor, such that the main contractor (the user) will receive the invoice directly from the main system 13 and have access to the transaction details, which has been uploaded to the receiver and/or provider server. The user may also be the company of the receiver.

As illustrated in figure 3, the main system may be spilt into two main systems.

One associated with the receiver and one with the provider. These main systems may then communicate by the use of an API.

The users 14, 19 are not necessary identical to the provider 1 or receiver 2, as the user might be a company which outsources its delivery services. A single user 14,19 may therefore in the server be associated to multiple provider's and/or receiver's NFC systems, such that multiple providers and receivers will download substantially the same user identification information. In order to track such transactions, the server will transfer the user identification information as the further identification information, and each receiver will further be assigned a unique tag with an associated identification number, such that the individual receiver is always identifiable by the NFC tag. This applies equally to the provider and to situations wherein a provider or receiver has multiple tags.

The receiver's server may therefore contain multiple user identification information, such that for each job a new user identification information is transferred to the tag of the receiver. The receiver and user identification may be the same; this would be in the case of the receiver being employed in a one-man company. In such situations, the receiver will before a job/transaction download the relevant user identification information, and in the case of the NFC tag being distinct, transfer the information to the tag by use of the NFC reader/writer. Such action will occur throughout the day whenever a new transaction occurs. A new transaction might be associated with a new user.

The pre-transactional order details can also be downloaded and transferred between the NFC systems, such as in the case of the user data. The provider's app will in such a situation be able to show the pre-transactional order details to the provider. This avoids miscommunication.

In an embodiment, when the provider has received the identification information from the receiver and inputted the transactional order details, the provider's app will send this information to the provider's server. This information may be accessible by the user associated with the provider and/or receiver using the main system(s). The receiver app could also upload the same information.

In an embodiment, the identification information and the transaction details are matched in the main system interface with a user, which will enable a user to monitor and control the transaction.

In another embodiment, the main system may send an order confirmation and/or receipt to the user of the main system, after the transaction has been matched with a user associated to the receiver. This will enable a streamlined billing process. The receipt can include the transaction details, provider's identification information, receiver's identification information, and/or the user's identification information, as well as time stamps. In the case of separate main system(s), the provider's main system will transmit the receipt to the receiver's or receiver's main system.

The receiver's app can further be connected to an external application 15, which can send an order list to the receiver's NFC system 3, such that the receiver will see a list of goods that needs to be transferred. This order list could contain Commodity ID information about the products. Such an application may be a booking and ordering system/application 16. External user not associated with the system may book through such a system, and these systems are preferable associated and managed by the receiver's main system.

Alternatively, an order list can be provided locally on the receiver's NFC system.

In these embodiments, the receiver would know exactly what needs picking up, and can optionally communicate this via the second communication channel 10 or first communication channel 9 to the provider 1.

Further, in an embodiment, a further step may be confirming that the transfer has been completed by either using the provider's and/or receiver's app. The information may be uploaded to the servers alongside the other information relating to the transaction.

As the first or second communication is not reliant on an internet or server connection, as these transfers are local communication, an internet connection does not need to be provided for a transaction to occur.

However, the transfer of the data to the receiver's and/or provider's server may need an open connection, such as an internet connection or connection to a server. This is, however, not possible in all situations, such as when the provider and/or receiver is in a quarry with poor reception.

In such a situation, the transfer of information to the servers may be delayed, as this is not a critical step in the transaction process and may be delayed without affecting the transferring process. The delay will occur until an internet connection can be establish or at a predetermined time or at the request of the provider and/or receiver. The receiver could in the app request that data should be transferred to the server at specific times or time intervals.

In order for avoiding errors in the billing process, the provider's app can in an embodiment specify what types of transaction details, the provider can input, such as by using a dropdown menu of the available goods. This information can be retrieved from the main system and be tailored for each provider and quarry. Referring to figure 4, an embodiment of the invention is shown, wherein a dotted line indicates an open connection and a solid line a closed connection.

Figure 5 indicates the data transfer scheme that may be implemented by figure 4. In such embodiments, a user, e.g. a customer, will in a first step create a profile in a main system, which is in communication with the receiver's and provider's server.

This user profile will include identification information relating to the user, such as the billing, company information and further containing matched details linking the encoded system identification numbers to providers and receivers. The users 14, 19 may provide and receive different information in the main server, as their data requirements may be different. The servers will send/transfer this information to the receiver's and provider's NFC systems, in order to create a local customer identification file (1) and (2), for respectively, the provider and receiver's NFC app, containing information or data entry spaces for all relevant transaction details.

By consulting figure 7, an example of an empty data file is shown each horizontal section defines a step and each arrow defines a transfer process shown in figure 5. The NFC reader/writer will in both the read and write mode read the unique encoded tag identification number and the further identification information. In the first transfer 22 from the receiver's server to the receiver's app, the customer file will be filled out according to figure 7. The information transferred will be data related to the receiver, such as identification information and pre-transactional order details. This step could be viewed as encoding pre-transactional order details into the app(s). The data entry may be related to data fields typically found in weighing slips. This information could also be transferred directly to the provider's app.

In an embodiment of the invention, the transfer of the identification files to the receiver's NFC system occurs when the receiver is within a predefined distance from the provider, such as when the receiver enters the quarry site. These files will be saved on the apps local databases, such that it can be access and changed at any time locally by the app. In an embodiment, further customer identification files can be saved and transferred to the provider's app, such that at the beginning of a workday the provider's app will download all the files relating to customers expected during that working day or other specified period. In a further embodiment, the app downloads all the customer files on the provider's server. This enables a receiver registered in the system to arrive at a non-specified time and date.

The identification information and pre-transactional order details will be sent 23 to the provider by use of the NFC system and preferable using the receiver's tag and used to update the file (1) 24. This is to ensure, that the provider's identification file (1) is up-to-date and, and optionally, transfer the unique tag number of the receiver, such that the file includes both the identification information relating to the user of the main system and for the specific receiver, both can be transferred by the NFC tag of the receiver. The user of the main system is in figure 7 the company name and the specific receiver is the receiver's tag id. In figure 7, the receiver nor the provider has a further unique identification information associated. The customer details is normally part of the pre-transactional order details.

This enables the user to see exactly which receiver has carried out the transaction and enable improved tracking. The identification information of the customer or the NFC tag number can also be used to ensure that the correct costumer file (1) is opened and used in the transaction process. The costumer file (1) may contain additional information not transferred through the first communication channel 9.

The main system and servers may contain metadata on the user and/or receiver, such that costumer file (1) on the provider's app, before the identification information transfer, contains the user's information, but not the specific ID of the receiver, thereby the encoded unique tag id nor the further id. This is useful when the delivery company is known but not the specific driver or vehicle. A different driver or vehicle may be sent and recorded using such a method.

If the transfer occurs in a situation where no internet or server connection is available, e.g. no customer file has been downloaded to the provider, then the file (1) on the provider's system will be created at the NFC transfer step by use of the transferred information. The main reason why no customer file (1) exist is that the receiver has manually created the customer profile on the app before the server and provider's app has been updated or the provider's app has not updated due to lack of connectivity to the servers. This also means that the identification number is not matched with a receiver, but will be matched post-transaction. In such cases, the fields on the identification files are created from a standard template.

The transfer from the receiver to the provider 25 could also contain the pre transactional order details, such as the desired amount and type of goods. This information will be recorded in the provider's identification file or Commodity ID information.

The provider's app 5 will enable the entering of the transactional details relating to the transaction. The provider 1 will enter the transaction details relating to the transaction. The file (1) will be updated with the transaction details inputted by the provider, which is the actual transacted goods.

The updated file's (1) information will be transferred 25 to the receiver by use of the NFC first communication channel 9, such that file (2) is updated, see figure 7. The provider tag id and possible further unique identification information is further recorded in the provider's file upon written to the tag.

This ensures that both NFC system have all the relevant transaction information and file (1) and (2) contains the same information. The order and transaction details may not be the same, both could differ in quantity and type. The information is important in quality control tracking in building industry and will enable monitoring of loading errors.

The apps will send the updated files (1, 2) to the servers, where the users of the system can access the information, which can include both the user associated to the provider and the user associated to the receiver. This transfer of information to the server can be delayed to when a connection is established. Preferable, a receiver is always associated with a user registered centrally in the system, but can, in an embodiment, be locally registered in the receiver's app, which means that file (1) on the provider's does not exist and will created based on the transfer using the NFC system 4.

As all the information shared in the actual transaction process is local information, an internet connection is not needed. The transfer of the final files to the server can therefore be delayed to a time when an internet connection or connection to the server is possible.

Referring to figure 6, an embodiment of the actions of relating to implementation of an embodiment of the invention is shown. The method starts by matching into the main system the user identification information, which can be done globally, and providing the receiver with an NFC tag that identifies the specific receiver. An example of this is a delivery company registering it meta-data through the main system, such as its address etc., and providing the receiver with a NFC tag identifying him/her.

On the NFC app, the receiver will see an order list, which could come from the external booking and ordering application connected to the receiver's server. The receiver will choose the order that is to be executed and if the user is different or the receiver is associated to multiple users tap his/her tag on the NFC reader/writer transferring the identification information relating the specific user for the specific order to the tag.

This could also be a transfer of the customer identification information from the booking and ordering application, such that the tag now contains information about the specific receiver, the receiver's company and the customer from the booking and ordering app. This information could also be typed into the main system by the user, such that the user information also contained sub-profiles for each customer of the user. The user identification information could therefore also contain information pertaining to the user's customer or other information, important for the transaction. The information could also manually be inputted into the receiver's app. This means that for example, that job a and job b could differ by a change of information in a customer field but the user information being the same. A single user could therefore have multiple sub-user profiles for each customer.

The booking and ordering application could also provide the user identification information, such that job 1 and job 2 could identified different user based on information from external apps. This is advantageous because a delivery service could use the receiver's server to keep track of deliveries throughout the day, by the receiver choosing the relevant job he/she is about to commence, thereby eliminating user identification confusions. The receiver would do this for every job and transfer the new identification information for each job to his/her tag. The receiver would therefore not actively have to keep track of this information during the day, as the information is present on the tag based on the chosen job.

After this transfer, the receiver will tap his/her NFC tag on the provider's NFC reader/writer, commencing a transfer of the identification data. If information is missing, the provider will be able to manually input this information into his/her NFC app, such as specifying the customer or missing data entries, such as case number. The provider will input the transactional order details into the app, such as in the case of the transfer of goods the type and weight of the material.

This data will be transferred to the provider's NFC tag, by use of the receiver's NFC reader/writer, wherein the provider's or receiver's NFC tag will be "tapped" on the receiver's NFC reader/writer, transferring the data to receiver's NFC app. The receiver's and provider's app will locally store this information and, when a connection to the server is established, transfer the information to the server.

The provider's and receiver's server will then forward the information to external systems, such as the booking and ordering systems or external financial management systems, which could be associated to the user and/or a customer of the transaction. The receiver will not actively input in the process anything relating to his/her identity or identification.

The invention can be implemented by means of hardware, software, firmware or any combination of these. The invention or some of the features thereof can also be implemented as software running on one or more data processors and/or digital signal processors. Referring now to figure 8, five different modules (embodiments) of the current invention are shown. In the first illustration of figure 8, module 1 is shown.

Module 1 shows a method, where an entity 1 associated with the provider, here a weighing system and/or weighing station within a quarry site, is provided with a NFC system 4, the NFC system comprising a NFC reader/writer 6 and an NFC app 5 in connection with the NFC reader/writer 6. The NFC system being integrated within a tablet.

An entity 2 associated with the receiver, here a truck, is further provided, with a NFC system 3, here shown as a tablet/smartphone, the NFC system comprising a NFC reader/writer 8 and an NFC app 7 in connection with the NFC reader/writer 8, and is further provided with an NFC tag 17, the NFC tag 17 comprises an encoded tag identification number uniquely identifying the truck driver and optionally a Commodity ID, which uniquely identifies a commodity. This means that a tracking of the whole process is available.

As shown in the figure 8 module 1, an optional step could be to encode pre transactional order details into either or both of the receiver's and/or provider's entity NFC app(s) 5, 7. This information could be customer information, case information, billing information on a possible customer of the truck driver, etc. Shown in module 1 in a first step, each step is indicated by a number within a circle, data from the receiver's NFC system 3 is transferred to the NFC tag 17, this data would be the pre-transactional details, such as end-customer information.

The truck 2 will drive into the quarry as a second step as indicated by the solid lines and proceed to the loading place. A loading place will normally contain a weighing system or station. The truck will be loaded with the desired material and weighed at a weighing system, weighing station, loading station or off-loading station 1. The transactional details will be recorded at this station into the provider's entity NFC app and system 4, and could include information on the quarry site and person/machine loading the material, such as the weighing station id, time of loading, etc.

The truck driver 2 will take the NFC tag 17 and commence a data transfer with the provider entity 1 by tapping the NFC tag 17 with the provider's entity NFC system 4. This tap will transfer the transactional details to the tag 17, while transferring information of the receiver and/or receiver's entity from the tag 17 to the provider. After the transfer, the provider's entity 1 has all of the required information and a weighing slip could optionally be printed by a printer 26. The transfer could also transfer pre-transactional details from the tag 17 to the provider's app.

The receiver's entity 2 will take the NFC tag 17 back to the truck and tap with the receiver's entity own NFC system 3 and transfer the transactional details to the app, where it could be merged with the data already in the NFC app. The receiver entity will then drive out of the quarry. The receiver's entity and provider's entity will now have all the information they need in order to track and record the transaction and to make the necessary paperwork. The receiver entity could thereafter delete the loading details on the receiver's entity NFC tag 17 when transferring the transactional details.

Module 2-5 in figure 8 shows additional embodiments of the invention with added features. In order to keep the illustrations simple reference signs have only been added for new features.

In module 2 shows that the provider's entity NFC system 4, as a tablet, is connected to a local server 32, which could be placed within a house and which could be connected to a cloud data 33 and with a wireless access point through an IWLAN 35. This allows the information from the provider's entity to be sent to provider and a bill or invoicing procedure to commence. Further module 2 shows that the receiver's entity app could be connected to an API with an inventory list from the provider. From this, the Commodity ID can be transferred to the NFC tag of the receiver's entity before the transaction. This means that the IWLAN makes it possible for the provider to complete the weighing directly at and in the localhost and/or cloud, if a cloud is available, if the receiver needs help

In module 3, a second NFC system 29 associated with the provider is provided. This allows the receiver entity 2 to tap the NFC tag 18 at this system before the loading. The system could advantageously be placed at the entrance of the site. This second NFC system is further connected to the local server 32 and cloud if possible. Further, if a new customer or entity associated with a receiver arrives without a tag, then means for identifying the entity could be provided in the screen 29, such that the provider knows who is reaching the good, what goods needs loading, etc. this could include transferring the Commodity ID to the screen and further to the provider entity responsible for the loading. This means that the provider knows the specific product that needs transferring.

In module 4, a third NFC system 30 associated with the provider is provided. This system could be connected to a printer 26, such that the receiver's entity could when exiting the site stop at (4) and print the weighing slip, thereby the transactional details. Further, if it is a new customer without a NFC tag, then the customer could complete the transaction at this third NFC system and optionally print the receipt.

In module 5, GPS location 34 of the receiver is gathered to ensure that it is the correct truck is at correct area of the site and could include an IWLAN extender for industrial Wi-Fi far away from the localhost at the house. The extender is further used, so the GPS location 34 works without an internet connection in the NFC system from the house localhost.

Figure 9 shows an overview of the IWLAN set-up, wherein a house contains a local access point and a wireless connection is established between multiple gravel pits.

The individual elements of an embodiment of the invention may be physically, functionally, and logically implemented in any suitable way such as in a single unit, in a plurality of units, or as part of separate functional units. The invention may be implemented in a single unit, or be both physically and functionally distributed between different units and processors.

Itemized list of preferred embodiments

Item 1. A method for monitoring and/or controlling a transaction between a provider (1) and a receiver (2), the method comprises the steps of providing the provider with a NFC system (4), the NFC system comprising a NFC reader/writer (6) and an NFC app (5) in connection with the NFC reader/writer (6), providing the receiver with a NFC system (3), the NFC system comprising a NFC reader/writer (8) and an NFC app (7) in connection with the NFC reader/writer (8), providing the receiver and/or the provider with an NFC tag (17, 18) with a encoded tag identification number associated with a unique receiver or provider, wherein the NFC system and the NFC tag(s) provides a first communication channel (9) by transferring data pertaining to the transaction, including the encoded tag identification number, inputted into one of the NFC app's (7, 5) to the other NFC app (5, 7) by using a NFC tag (17, 18) and the NFC reader/writers (6, 8), inputting by the provider (1) into the provider's app (5) the transaction details, such as the quantity and type of goods that has been transacted, transferring the transaction details from the provider's NFC system to the receiver's NFC system (3) by use of the first communication channel (9) using either the receiver's or provider's NFC tag (17, 18).

Item 2. A method according to item 1, further comprising the step of transferring further unique identification information to the receiver's and/or provider's NFC tag (17,18) by use of the NFC systems (3, 4).

Item 3. A method according to item 2, further comprising the step of always transferring the further unique identification information encoded in the NFC tags when using the first communication channel (9).

Item 4. A method according to item 1, further comprising the step of communicating order details, from the receiver to the provider using a second communication channel (10) or the first communication channel (9), such as indicating the quantity and type of the goods to be received. Item 5. A method according to any of the preceding items, wherein the step of transferring the further unique identification information to the NFC tag of the provider or receiver occurs when transferring, respectively, the transaction details or order details.

Item 6. A method according to any of the preceding items, further comprising the step of connecting the provider's and receiver's NFC systems (3, 4) to, respectively, a provider's server (11) and a receiver's server (12).

Item 7. A method according to item 3, further comprising the step of connecting the receiver's (12) and provider's server (11) to one or more main system(s) (13, 20), being accessible by one or more user(s) (14, 19) which can read and write to the receiver's and provider's servers (12, 11) using the main system(s) (13, 20), the main system(s) (13, 20) comprising identification information relating to the one or more user(s) (14, 19), the main system further being connected to each other by an API (21).

Item 8. A method according to item 7, wherein the NFC tags (17, 18) encoded unique system identification number are, respectively, matched with the provider or receiver in the main system(s) (13, 20).

Item 9. A method according to any of the preceding items, further comprising the step of transferring from the receiver's server the further unique identification information of the user and/or receiver to the receiver's NFC system(s) for transferring to the NFC tag(s) (17, 18).

Item 10. A method according to any of the preceding items, further comprising the step of displaying on the receiver's app an order information list obtained by an external application in communication with the receiver's server or main system.

Item 11. A method according to any of the preceding items 6-10, wherein the step of sending the transaction details, order details and the identification information to the provider's server and/or receiver's server is delayed until a stable connection is achieved and/or done by the provider and/or receiver by instructing the provider's and/or receiver's app to commence the transfer.

12. A method according to any of preceding items, wherein the transaction process occur in a quarry, building supply distributor, and environmental centre.

Item 13. A system for implementing the method detailed in items 1-12, wherein the system comprises a provider's and receiver's NFC system, comprising an NFC reader/writer and an app, the NFC reader/writer having reading and writing capabilities to a NFC tag and is in communication with NFC app, a provider's and/or receiver's tag, comprising memory, transferring capacities to an NFC system and an encoded unique identification number, wherein a data communication occurs when the NFC tag is "tapped" with a NFC reader/writer of a NFC system.

Item 14. A system according to item 13, further comprising a server in connection with the provider's NFC system and a server in connection with the receiver's NFC system.

Item 15. A system according to any of items 13-14, where in the provider's and/or receiver's server is connected to one or more main system(s), accessible by a user of the receiver and/or the provider.

Although the present invention has been described in connection with the specified embodiments, it should not be construed as being in any way limited to the presented examples. The scope of the present invention is to be interpreted in the light of the accompanying claim set. In the context of the claims, the terms "comprising" or "comprises" do not exclude other possible elements or steps. Also, the mentioning of references such as "a" or "an" etc. should not be construed as excluding a plurality. The use of reference signs in the claims with respect to elements indicated in the figures shall also not be construed as limiting the scope of the invention. Furthermore, individual features mentioned in different claims, may possibly be advantageously combined, and the mentioning of these features in different claims does not exclude that a combination of features is not possible and advantageous.

Reference list 1. Provider

2. Receiver

3. Receiver's NFC system

4. Provider's NFC system

5. Provider's NFC App 6. Provider's NFC reader/writer

7. Receiver's NFC App

8. Receiver's NFC reader/writer

9. First communication channel

10. Second communication channel 11. Provider's server

12. Receiver's server

13. Receiver's main system

14. Receiver's User

15. External application 16. Booking and ordering application

17. Receiver's NFC tag

18. Provider's NFC tag

19. Provider's user

20. Provider's main system 21. API

22. Update of receiver's file

23. Transfer of data to provider's file

24. Update of provider's file

25. Transfer of data to receiver's file 26. Printer

27. Express line

28. Truck

29. Second NFC system, reader and writer

30. Third NFC system, reader and writer 31. GPS system

32. Local server

Claims

1. A method for transferring, monitoring and/or controlling a transaction, including transaction details between a provider and a receiver, such as a customer, the method comprises the steps of providing an entity (1) associated with the provider, such as an employee or loading vehicle or weighing station, with a NFC system (4), the NFC system comprising a NFC reader/writer (6) and an NFC app (5) in connection with the NFC reader/writer (6), providing an entity (2) associated with the receiver, such as the delivery truck, with a NFC system (3), the NFC system comprising a NFC reader/writer

(8) and an NFC app (7) in connection with the NFC reader/writer (8), providing an NFC tag (18) associated with the receiver's entity (2), the NFC tag (18) comprises an encoded tag identification number uniquely identifying the entity (2), wherein the NFC system and the NFC tag provides a first communication channel (9) by transferring data using the NFC tag and NFC reader/writers (6, 8), where the encoded tag identification number identifying the entity on the NFC tag will always be transferred to the NFC reader/writer, from one of the NFC app's (7, 5) to the other NFC app (5, 7), the transferring includes

- recording, in the provider's entity NFC app (5) transactional details, such as loading details, which could be information normally present in a weighing slip, such as the quantity and type of goods that has been transacted, details about the provider etc.,

- transferring the transactional details, using the first communication channel

(9) from the provider's entity NFC app (5) to the receiver's entity NFC app (7), the transferring comprises o transferring the transactional details on the provider's entity app (5) to the receiver's entity NFC tag (18) using the provider's entity NFC reader/writer (6) and transferring the encoded tag identification number identifying the receiver's entity (2) to the provider's entity app(5), such that the provider's entity app (5) will contain information identifying the receiver's entity (1), o transferring the transactional details on the NFC tag (17) to the receiver's NFC app using the receiver's NFC reader/writer (8), where the receiver's entity (2) after the transfer will have the transactional details and the provider's entity (1) will have information on the receiver's entity (2) responsible for the transaction of the receiver, such that both the provider's and receiver's companies will have the required transactional information.

2. A method according claim 1, further comprising encoding pre-transactional order details, respectively, into receiver's entity and/or provider's entity app (5,

7), such as customer information, case information, billing information, etc., before the transaction and merging them with the transactional details after the transaction.

3. A method according to claim 1 or 2, further comprising merging the transactional details with the pre-transactional details in the receiver's entity NFC app (7) and/or merging the identification of the receiver with the pre-transactional details in the provider's entity (5) NFC app.

4. A method according any of the preceding claims, further comprising sending the transactional details from the receiver's entity NFC app (7) to the receiver.

5. A method according to any of the preceding claims, further comprising transferring to the receiver's entity NFC tag (17) pre-transactional details about the receiver's and receiver and/or the transaction, and transferring this information to the provider's entity app (5) in the step of transferring the transactional details from the provider's entity NFC app (5) to the receiver's entity NFC tag (17).

6. A method according to any of the preceding claims, further comprising transferring identification information about the receiver's entity and/or receiver to the provider's entity or provider via the first communication channel in a separate step before transferring of the transactional details.

7. A method according to any of preceding claims, further comprising providing the provider's entity with an NFC tag and using this tag for the transfer of transactional details from the provider to the receiver and details of the receiver to the provider.

8. A method according to any of preceding claims, further comprising supplying a second NFC reader/writer (29) associated with the provider and transferring identification information of the receiver and/or receiver's entity at the second NFC reader/writer (29), such as the encoded tag identification number.

9. A method according to any of the preceding claims, further comprising deleting the loading details on the receiver's entity NFC tag (17) when transferring the transactional details.

10. A method according to any of the preceding claims, further providing the provider entity with a printer connected to the NFC system and wherein the transactional details, such as a receipt or weighing slip, are printed after the transferring of the transactional details to the receiver's NFC tag and receiver's identification information to the provider entity.

11. A method according to any of the preceding claims, wherein the printing of the transactional details occurs at a third NFC system (30) associated with the provider (1) connected to the printer.

12. A method according to any of the preceding claims, further comprising the step of transferring further unique identification information to the NFC tags (17, 18) by use of the NFC systems (3, 4).

13. A method according to any of the preceding claims, further comprising the step of always transferring the further unique identification information encoded in the NFC tags when using the first communication channel (9).

14. A method according to any of the preceding claims, further comprising the step of communicating the pre-transactional order details, from the receiver to the provider using a second communication channel (10) different from the first communication channel or the first communication channel (9), such as indicating the quantity and type of the goods to be received, optionally at the second NFC reader/writer (29).

15. A method according to any of the preceding claims, further comprising the step of connecting the NFC systems (3, 4) to, respectively, a provider's server (11) and a receiver's server (12).

16. A method according to any of preceding claims, further comprising the step of connecting the receiver's (12) and provider's server (11) to one or more main system(s) (13, 20), being accessible by one or more user(s) (14, 19) which can read and write to the receiver's and provider's servers (12, 11) using the main system(s) (13, 20), the main system(s) (13, 20) comprising identification information relating to the one or more user(s) (14, 19), the main system further being connected to each other by an API (21).

17. A method according to claim 14, wherein the NFC tags (17, 18) encoded tag identification number and/or further unique identification information are, respectively, matched with the receiver in the main system(s) (13, 20).

18. A method according to any of the preceding claims, further comprising the step of transferring from the receiver's server the further unique identification information of the user and/or receiver to the receiver's entity NFC system(s) for transferring to the NFC tag(s) (17,18).

19. A method according to any of the preceding claims, further comprising the step of displaying on the receiver's app an order information list obtained by an external application in communication with the receiver's server or main system.

20. A method according to any of the preceding claims 13-17, wherein the step of sending the transactional details, pre-transactional order details and/or the identification information to the provider's server and/or receiver's server is delayed until a stable connection is achieved and/or done by the provider and/or receiver by instructing the provider's and/or receiver's app to commence the transfer.

21. A method according to any of preceding claims, wherein the transaction process occur in a quarry, building supply distributor, or environmental centre.

22. A method according to any of the preceding claims, wherein a Commodity ID is transferred to the NFC tag of the entity associated with the receiver and transferred to the provider.

23. A system for implementing the method of claims 1-22, wherein the system comprises a provider's and receiver's NFC system, comprising an NFC reader/writer and an app, the NFC reader/writer having reading and writing capabilities to a NFC tag and is in communication with NFC app, - a receiver's NFC tag, comprising memory, transferring capacities to an NFC system and an encoded unique identification number, wherein a data communication occurs when the NFC tag is "tapped" with a NFC reader/writer of a NFC system.

24. A system according to claim 23, further comprising a server in connection with the provider's NFC system and a server in connection with the receiver's NFC system.

25. A system according to any of claims 22-24, where in the provider's and/or receiver's server is connected to one or more main system(s), accessible by a user of the receiver and/or the provider.