FORM-2
THE PATENTS ACT, 1970
(39 OF 1970)
&
The Patents Rules, 2003
COMPLETE SPECIFICATION
[See section 10 and rule 13]
"A DISTRIBUTED COMPUTER SYSTEM FOR PROCESSING OF INVOICES AND/OR DOCUMENTS AND A METHOD IMPLEMENTED THEREIN"
INTELENET GLOBAL SERVICES PVT. LTD., an Indian company, of Intelenet Towers, 1406-A/28, Mindspace, Malad (West), Mumbai - 400 064;
The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF INVENTION
This invention relates to data processing systems, and more particularly to a system and method for processing of invoices and/or documents.
BACKGROUND
An organization generally requires various vendors / service providers to provide them with different supplies and services. The vendors after providing the supplies or rendering the required services raise invoices in that respect. Conventionally, invoices are raised in paper form. These paper invoices are sent to the organization for processing by the accounts payable department thereof. Particularly, upon receipt of such invoices in the accounts payable department, the same are directed to a concerned person within the organization who is authorized for approving and processing payments. The concerned person, after scrutiny of the invoices, approves and forwards the same to the accounts department for processing payment. Upon finding any discrepancies in the invoices, the same are sent to the vendor for clarification or rectification. It is observed that the conventional process is generally very slow due to considerable dependence on the efficiency of persons involved in the processing of invoices and also due to the use of physical delivery systems, like postage systems, courier and the like, for delivery of invoices. Moreover, such conventional systems are also prone to errors caused by humans in the processing chain.
Further, in the event such a system is required to handle a large volume of invoices, the probability of mistakes and delays in processing may increase considerably. Also, in such conventional systems, it is at times difficult for vendors or concerned persons of the organization to track the invoices since the current physical location of the invoices or details regarding the processing thereof may not be known to each concerned person in the processing chain at a particular time.

Similar problems persist in conventional systems with regard to processing of documents submitted by vendors.
Accordingly, there persists a need for an improved system for processing invoices and documents such that the system enables speedier and error free processing of the invoices/documents.
There further persists a need for an improved system for processing invoices and documents in which human involvement is reduced to the minimum to avoid dependence on human efficiency.
There further persists a need for an improved system for processing invoices and/or documents such that the system enables easy tracking of the invoice/document.
OBJECTS OF THE INVENTION:
In view of the foregoing disadvantages inherent in the prior art, the general purpose of the present invention is to provide an improved system and method for processing of invoices and/or documents that helps in faster, simpler and efficient processing of invoices/documents.
Accordingly, an object of the present invention is to obviate the above and other disadvantages from the existing art and to provide a system and method for processing invoices and/or documents that enables vendors to submit their invoices electronically irrespective of their geographical location.
Further, another object of the present invention to provide a system and method for processing invoices and/or documents in which the invoices and/or documents are verified according to a pre-determined logic and the invoices/documents are escalated thereafter to an appropriate person for processing thereof.

Yet another object of the present invention is to provide a system and method for processing invoice and documents that keeps track of the invoice/documents.
These and other objects and advantages of the invention will be clear from the ensuing description.
SUMMARY:
In light of the above objects, a distributed computer processing system for processing of invoices and/or documents is disclosed. The distributed computer processing system comprisis at least one server, a database communicably coupled to the server and at least one external user terminal and at least one internal user terminal communicably coupled to the at least one server wherein the at least one server is adapted to receive invoices and/or documents from any of the at least one external user terminal and the at least one internal user terminal, verify the received invoices and/or documents based on predetermined conditions, escalate the invoices and/or documents electronically to any of the at least one external user terminal and the at least one internal user terminal based on the verification and to keep track of the escalated invoice and/or documents until processing thereof is complete and wherein the escalation is accompanied by an identifier defining an action to be taken for processing of the invoices and/or documents.
In another embodiment of the present invention, the at least one internal user terminal is a part of local domain of the distributed computer system.
In yet another embodiment of the present invention, the at least one external user terminal are external to the local domain of the distributed computer system and are communicably coupled to the server through internet or a dedicated communication channel.

In yet another embodiment of the present invention, the at least one internal user terminal and the at least one external user terminal comprises a desktop computer, a laptop, a personal digital assistant (PDA), a mobile phone, a palm top device and the like.
In yet another embodiment of the present invention, the server is adapted to retrieve relevant details from the received invoices and/or documents and save the same in the database by indexing the relevant details.
In yet another embodiment of the present invention, the predetermined conditions utilized by the server comprise information associated with approved prices, valid reference number of the invoices and/or documents, information associated with particular fields in the invoices and/or documents, and any combination thereof.
In yet another embodiment of the present invention, the server, to escalate the invoices and/or documents, transmits the same to an approving user terminal, selected from at least one internal user terminal, for completing processing thereof upon the invoices and/or documents being identified as confirming to the pre-determined conditions.
In yet another embodiment of the present invention, the server, to escalate the invoices and/or documents, transmits the same to the at least one external user terminal, for correction of the invoices and/or documents, upon the invoices and/or documents being identified as not confirming to the pre-determined conditions, the correction required to be carried out in accordance with the identifiers.
In yet another embodiment of the present invention, the server is adapted to store information associated with escalation in the database for tracking the escalated invoice and/or document.

In yet another embodiment of the present invention, the at least one server is adapted to send periodic reminders to any of the at least one external user terminal and the at least one internal user terminal, to whom the invoices and/or documents have been escalated, based on the stored information associated with escalation, until processing thereof is complete.
In yet another embodiment of the present invention, the at least one server is adapted to generate reports regarding invoices and/or documents escalated and those for which processing is complete.
In yet another embodiment of the present invention, a method for processing of invoices and/or documents in a distributed computer processing system is disclosed. The processing system comprising at least one server, and a database, at least one external user terminal and at least one internal user terminal communicably coupled to the server, the method comprises receiving invoices and/or documents at the at least one server from any of external user terminal and internal user terminal, verifying the received invoices and/or documents at the at least one server based on pre-determined conditions escalating the invoices and/or documents electronically to any of the at least one external user terminal and the at least one internal user terminal based on the verification thereof by the at least one server along with an identifier defining an action to be taken for processing of the invoices and/or documents and tracking the escalated invoice and/or documents until processing thereof is complete.
In yet another embodiment of the present invention, the relevant details are retrieved from the invoices and/or documents and saved in the database by indexing the relevant details.
In yet another embodiment of the present invention, the pre-determined conditions comprise information associated with approved prices, valid reference number of the invoices and/or documents, information associated with particular fields in the invoices and/or documents, and any combination thereof.

In yet another embodiment of the present invention, the escalating the invoices and/or documents comprises transmitting the same to an approving user terminal, selected from the at least one internal user terminal, for completing processing thereof upon the invoices and/or documents being identified as confirming to the pre-determined conditions.
In yet another embodiment of the present invention, the escalating the invoices and/or documents comprises transmitting the same to the at least one external user terminal, for correction of the invoices and/or documents, upon the invoices and/or documents being identified as not confirming to the pre-determined conditions, the correction required to be carried out in accordance with the identifiers.
In yet another embodiment of the present invention, the tracking the escalated invoice and/or document comprises storing information associated with escalation in the database.
In yet another embodiment of the present invention, tracking the escalated invoice and/or document comprises sending periodic reminders to any of the at least one external user terminal and the at least one internal user terminal, to whom the invoices and/or documents have been escalated, based on the stored information associated with escalation, until processing thereof is complete.
In yet another embodiment of the present invention, the tracking the escalated invoice and/or document comprises generating reports regarding invoices and/or documents escalated and those for which processing is complete.
These aspects together with other aspects of the present invention, along with the various features of novelty that characterize the present invention, are pointed out with particularity in the claims annexed hereto and form a part of this present invention. For a better understanding of the present invention, its operating advantages, and the specific

objects attained by its uses, reference should be made to the accompanying drawing and descriptive matter in which there is illustrated an exemplary embodiment of the present invention.
BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS:
The advantages and features of the present invention will become better understood with reference to the following detailed description and claims taken in conjunction with the accompanying drawings, in which:
Fig. 1 illustrates a distributed computer processing system for processing of invoices and/or documents, in accordance with an embodiment of the present invention.
Fig. 2 illustrates a flow chart depicting a method for processing of invoices and/or documents as implemented in the system of Fig. 1, in accordance with an embodiment of the present invention.
DETAILED DESCRIPTION OF INVENTION WITH REFERENCE TO DRAWINGS:
The exemplary embodiments described herein detail for illustrative purposes are subject to many variations in structure and design. It should be emphasized, however, that the present invention is not limited to a particular distributed computer processing system and a method for processing invoices/documents as shown and described. It is understood that various omissions and substitutions of equivalents are contemplated as circumstances may suggest or render expedient, but these are intended to cover the application or implementation without departing from the spirit or scope of the claims of the present invention.
The terms "a" and "an" herein do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item. Further, the terms "first," "second," and

the like, herein do not denote any order, quantity, or importance, but rather are used to distinguish one element from another.
Fig. 1 illustrates a distributed computer processing system 100 used for processing of invoices and/or documents, in accordance with an embodiment of the present invention. The distributed computer processing system 100 (hereinafter referred to as "system 100") includes at least one server 102. The server 102 is configured to have a database 104. In an embodiment of the present invention, the database 104 may be configured on a separate database server. In another embodiment, the database 104 may exist on the server 102 itself such that the server 102 also performs the additional role of a database server. Further, the system 100 includes at least one internal external user 106 and at least one internal user 108 communicably coupled to the server 102. As shown in Fig. 1, the at least one internal user 108 and at least one external user 106 may include a plurality of users communicating with the server 102, however, for sake of simplicity of description, the present invention shall be explained with reference to a single internal user 108 and single external user 106. Further, in an embodiment of the present invention, the at least one internal user 108 may be a part of a local domain of the system 100 that is configured with the server 102 as the domain controller. For instance, the system 100 may include a network configuration of a large enterprise with a local domain configured therein such that the server 102 is the domain controller and the at least one internal user 108 is a member of the local domain. The at least one external user 106 is external to the local domain 106 and may be communicably coupled to the server 102 through internet or a dedicated communication channel. It will be evident that the communication between the server 102 and the at least one external user 106 is configured through a firewall (not shown) of the enterprise network and various other network devices, such as routers, switches etc, that enable communication over a network. In an embodiment of the present invention, the at least one external user 106 and the at least one internal user 108 include a user accessing the server 102 through a desktop, a laptop, a personal digital assistant (PDA), a mobile phone, a palm top device and the like.

Further, the at least one external user 106 or the at least one internal user 108 are adapted to electronically transmit invoices and/or documents to the server 102 for processing thereof. The at least one external user 106 thus preferably represents vendors who provide supplies and/or services to the enterprise. The invoices pertain to the supplies and/or services already provided to the enterprise. Further, the documents may pertain to Performa invoices, brochures, product catalogues and the like for the purpose of providing supplies and/or services in the future. Also, the at least one internal user 108 includes various personnel of the enterprise who are responsible for aiding in the processing of the invoice and/or documents. For instance, the internal user 108 may include a data entry operator, accounts personnel, a stores in-charge, a manager having sanctioning authority and the like. One of the internal user 108, such as the accounts manager, may transmit a partially processed invoice/document to an approving internal user 108A, such as a manager having sanctioning authority, for obtaining final approval on the invoice/document for final processing. The working of the system 100 to process the received invoices and/or documents shall be explained further in detail in conjunction with Fig. 2. It is to be noted that the method 200 may be used for serving the requirements of external users 106 as well as internal users 108 and thus the method 200 shall be explained in context with its application to both the external users 106 and the internal users 108, as will be evident from the ensuing description.
Particularly, Fig. 2 illustrates a flowchart depicting a method 200 for processing invoices and/or documents. The method 200 is implemented in the system 100, as will be evident from the ensuing description. Further, while describing the method 200 references shall be made to the system 100 of Fig. 1 wherever required to explain the method 200 elaborately.
The method 200 has applicability to both the internal user 108 and the external user 106. In a first example, the method 200 is being explained in context with the applicability to the external user 106. The method 200 begins at 202 when the invoices and/or documents are received from the external user 106 at the server 102. Particularly, in one particular

embodiment of the present invention, it is envisaged that the external user 106 may transmit the invoice and/or document electronically to the server 102 by using various electronic communication schemes such as emails, by using file transfer protocol (FTP), uploading on a file sharing portal and the like. In the described embodiment, the invoice and/or document may be a generated by a computer in any particular format such as word processor format, spreadsheet format, portable document format and the like. The server includes a text capturing means configured therein which retrieves relevant information from the invoice and/or document and stores the information in the database 104. The relevant information could include details that are helpful in identifying the vendor, the services or supplies provided, details regarding costs of services/supplies and the like. In another embodiment of the present invention, the invoice and/or document may be prepared by using a computer but submitted by physical delivery at the enterprise for processing thereof. In the described embodiment, the relevant information from the invoice and/or document is manually retrieved by the internal user 108 and manually entered in the database 104 through application software. A scanned copy of the invoice/document may also be saved in the database 104 along with the relevant information for future reference. Further, the server 102 is adapted to index the relevant information being stored in the database 104 for enabling easy retrieval thereof at a later stage.
Furthermore, at 204, the received invoices and/or documents are verified at the server 102 based on pre-determined conditions. Particularly, the present invention envisages that the relevant information retrieved from the received invoice and/or document is compared by the server 102 with the stored pre-determined conditions. In an embodiment of the present invention, the pre-determined conditions may pertain to stored information associated with pre-approved prices of a supply or services from being provided by vendors, valid reference numbers of the invoices and/or documents, valid purchase order numbers issued by the enterprise for availing the services or receiving supplies, or any other relevant information contained in the invoice/document, such as date, details of the vendor's bank in which payment is to be made, signatures of an approving authority and

the like. It is to be noted that the pre-determined conditions are not limited to the information as mentioned herein and it may include varied information that may be required by an enterprise in carrying out its vendor management and purchasing activities. Further, the pre-determined conditions may be stored in the database 104.
For instance, the information regarding the purchase order, against which the services have been provided by the vendor and an invoice has been raised, retrieved from the received invoice is compared with the valid list of purchase orders stored in the database 104 to determine whether a match exists or not. In another example, a document, such as a Performa invoice from a new vendor, relevant information may be retrieved from the document and compared with pre-determined conditions that may relate to a required format in which the enterprise requires the information is represented in the Performa invoice, the tax rates as applicable to the enterprise, payment conditions and the like.
Further, based on the verification carried out at 204, the server 102 escalates the invoice and/or document (stored in the database 104 at step 202) to any of the external user 106 or the internal user 108 along with an identifier that defines an action to be taken for enabling processing of the invoice/document. In this regard, it is to be noted that the term "escalation" as referred herein refers to intimating details of an action required to be taken for processing of the invoice/document to a concerned person or concerned authority.
Further, as shown in Fig. 2, in the event, the verification step indicates that the invoice/document does not conform to the pre-determined conditions (i.e. the retrieved information from the invoice/document does not match the pre-determined conditions), then at 206, the stored copy of invoice/document is electronically transmitted to the external user 106 who generated the invoice/document. The stored copy is transmitted along with the identifier that includes information regarding the changes required to be made to the invoice/document to conform the same to the pre-determined conditions. For instance, in the event the purchase order number on the invoice does not conform to that a valid purchase order existing in the database 104, the invoice is escalated to the vendor

indicating the error in the purchase order number. Information regarding the correct purchase order number may also be provided for enabling the vendor to correct the invoice and re-submit for processing. Further, at 210, an entry regarding the escalation is made in the database 104 for enabling tracking of the invoice/document. Particularly, the information associated with escalation, such as the details of the external user 106 to whom the invoice is escalated, details of the discrepancy in the invoice/document, and the like, is stored in the database against the relevant entry for the said invoice/document. The server 102 may periodically retrieve the details of all escalated invoices/documents to send reminders to the concerned external users 108 to expeditiously correct the discrepancy and return for processing thereof.
The vendor after correcting the discrepancy in the invoice/document may transmit the corrected invoice/document to the server 102 and the steps 202, 204, 206 and 210 are repeated until the invoice/document conforms to the pre-determined conditions.
Upon determining at 204 that the invoice/document conforms to the pre-determined conditions, the invoice/document is escalated by the server 102, at 208, to an approving user terminal 108A. As shown in Fig. 1, the approving user terminal 108A may be selected from the at least one internal users and has an authority to approve the invoice/document. Particularly, the approving user terminal 108A may pertain to a Chief Financial Officer (CFO), an accounts manager, a senior management person, and the like. Further, the server 102 may preferably escalate the invoice/document through electronic mail. The invoice/document is transmitted along with an identifier that may include a brief background of the invoice/document and the actions required to be taken. Upon receiving the approval of the approving user terminal 108A, the server 102 may take necessary steps to process the invoice/document to finally process the invoice/document at 212, thereby concluding the method 200. In a working example, a verified invoice may be escalated by the server 102 to the CFO for his approval at 208. Upon receiving the CFO's approval, an electronic intimation may be sent to the bank for releasing the

amount mentioned in the invoice to the vendor at 212, thereby completing the processing of the invoice.
In case of a document, such as a Performa invoice from a new vendor, the same may be escalated to a purchase manager at 208 who may, at 212, approve the details (such as price quotes) mentioned in the document for storage in the database 104 as predetermined conditions that are to be used for future transactions with the vendor. The processing of document is thus completed upon the approved details being stored.
Further, in one embodiment of the present invention, there may be more than one approving user terminal 108A representing various stages of approval in the enterprise. For instance, there may be two approving user terminal pertaining to an accounts manager and a CFO. In this case, the invoice may be first escalated to the accounts manager for conduction checks, such as ascertaining the signatures of receiver of the supplies/services provided by the vendor, to provide initial approval on the invoice. The partially approved invoice is thereafter escalated to the CFO for final approval to enable release of payment to the vendor.
In an alternate step, the details regarding escalation to the approving user terminal 108A may also be entered by the server 102 in the database 104 for enabling tracking of the invoice/document. Particularly, the information associated with escalation, such as the details of the approving user terminal 108A to whom the invoice/document is escalated by the server 102 is stored in the database 104 against the corresponding entries for the said invoice/document in the database 104. The server 102 may periodically retrieve the details of all escalated invoices/documents to send reminders to the approving user terminal 108A to expeditiously process the same.
Further, once the processing of the invoice/document is complete, the server 102 makes a relevant entry in the database 104 against the details of corresponding invoice/document. This also helps in keeping track of all pending invoices/documents that are due to be

processed and await action either from the external user 106 or the internal user 108. Also, the server 102 is capable of generating reports regarding the escalated invoices/documents, which are pending and processed invoices/documents.
In view of the foregoing, it shall be evident that the present invention envisages an improved system and method for processing of invoices/document which is significantly paper-less, simple and cost-effective. Moreover, the invoices/documents are largely transmitted electronically and therefore, the present invention helps in a faster processing of the invoices/documents. In addition, the system 100 of the present invention automatically keeps tab on the pendency of the unprocessed invoices/documents and sends periodic reminders to concerned users for enabling faster processing of the same. Also, the present invention envisages that pre-checks on the invoice/documents are carried out based on the pre-determined conditions, thereby requiring lesser human involvement, as compared to conventional systems, which also helps in expeditious processing of the invoices/documents. For instance, the discrepancies in an invoice may be determined by the system 100 and automatically transmitted to the vendor for correction, without requiring involvement of personnel from accounts department. Only when a correct invoice is received, that conforms to the pre-determined conditions, the invoice is escalated to accounts personnel for processing. This saves significant time of the accounts personnel since the steps of checking the invoice prior to approving payment is avoided.
Further, the present invention should not be construed to be limited to the embodiments, as described herein, and various modifications are possible. In an embodiment of the present invention, the entire log of transactions occurring from the receipt of the invoice/documents till the final processing thereof is maintained for future reference. Additionally, the log may be helpful in analysing the efficiency of the personnel assigned with the task of processing of invoice/documents since the time taken by the personnel to process invoices/documents may be easily determined. Further, though the present invention has been explained with reference to an accounts payable department, it may be equally applicable in other departments of an enterprise which involve exchange of

documents between a vendor/supplier and end users, whether internal or external to the enterprise. For instance, the present invention may be implemented in a manufacturing enterprise involving exchange of drawings between a tool design department and a tool manufacturing shop.
The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the present invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the present invention and its practical application, and to thereby enable others skilled in the art to best utilize the present invention and various embodiments with various modifications as are suited to the particular use contemplated. It is understood that various omissions and substitutions of equivalents are contemplated as circumstances may suggest or render expedient, but such omissions and substitutions are intended to cover the application or implementation without departing from the spirit or scope of the claims of the present invention.

We claim:
1. A distributed computer processing system for processing of invoices and/or
documents, the distributed computer processing system comprising:
at least one server;
a database communicably coupled to the server; and
at least one external user terminal and at least one internal user terminal communicably
coupled to the at least one server,
wherein the at least one server is adapted to receive invoices and/or documents from any of the at least one external user terminal and the at least one internal user terminal, verify the received invoices and/or documents based on pre-determined conditions, escalate the invoices and/or documents electronically to any of the at least one external user terminal and the at least one internal user terminal based on the verification and to keep track of the escalated invoice and/or documents until processing thereof is complete, and wherein the escalation is accompanied by an identifier defining an action to be taken for processing of the invoices and/or documents.
2. The distributed computer processing system for processing of invoices and/or
documents as claimed in claim 1, wherein the at least one internal user terminal is a part
of local domain of the distributed computer system.
3. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 1, wherein the at least one external user terminal are external to the local domain of the distributed computer system and are communicably coupled to the server through internet or a dedicated communication channel.
4. The distributed computer processing system for processing of invoices and/or documents as claimed in any of claims 2 or 3, wherein the at least one internal user

terminal and the at least one external user terminal comprises a desktop computer, a laptop, a personal digital assistant (PDA), a mobile phone, a palm top device and die like.
5. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 1, wherein the server is adapted to retrieve relevant details from the received invoices and/or documents and save the same in the database by indexing the relevant details.
6. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 1, wherein the pre-determined conditions utilized by the server comprise information associated with approved prices, valid reference number of the invoices and/or documents, information associated with particular fields in the invoices and/or documents, and any combination thereof.
7. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 1, wherein the server, to escalate the invoices and/or documents, transmits the same to an approving user terminal, selected from at least one internal user terminal, for completing processing thereof upon the invoices and/or documents being identified as confirming to the pre-determined conditions.
8. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 7, wherein the server, to escalate the invoices and/or documents, transmits the same to the at least one external user terminal, for correction of the invoices and/or documents, upon the invoices and/or documents being identified as not confirming to the pre-determined conditions, the correction required to be carried out in accordance with the identifiers.
9. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 1, wherein the server is adapted to store information

associated with escalation in the database for tracking the escalated invoice and/or document.
10. The distributed computer processing system for processing of invoices and/or
documents as claimed in claim 9, wherein the at least one server is adapted to send
periodic reminders to any of the at least one external user terminal and the at least one
internal user terminal, to whom the invoices and/or documents have been escalated, based
on the stored information associated with escalation, until processing thereof is complete.
11. The distributed computer processing system for processing of invoices and/or documents as claimed in claim 1, wherein the at least one server is adapted to generate reports regarding invoices and/or documents escalated and those for which processing is complete.
12. A method for processing of invoices and/or documents in a distributed computer processing system, the processing system comprising at least one server, and a database, at least one external user terminal and at least one internal user terminal communicably coupled to the server, the method comprising:
receiving invoices and/or documents at the at least one server from any of external user terminal and internal user terminal;
verifying the received invoices and/or documents at the at least one server based on predetermined conditions;
escalating the invoices and/or documents electronically to any of the at least one external user terminal and the at least one internal user terminal based on the verification thereof by the at least one server along with an identifier defining an action to be taken for processing of the invoices and/or documents; and

tracking the escalated invoice and/or documents until processing thereof is complete.
13. The method for processing of invoices and/or documents as claimed in claim 12, wherein relevant details are retrieved from the invoices and/or documents and saved in the database by indexing the relevant details.
14. The method for processing of invoices and/or documents as claimed in claim 12, wherein the pre-determined conditions comprise information associated with approved prices, valid reference number of the invoices and/or documents, information associated with particular fields in the invoices and/or documents, and any combination thereof.

15. The method for processing of invoices and/or documents as claimed in claim 12, wherein escalating the invoices and/or documents comprises transmitting the same to an approving user terminal, selected from the at least one internal user terminal, for completing processing thereof upon the invoices and/or documents being identified as confirming to the pre-determined conditions.
16. The method for processing of invoices and/or documents as claimed in claim 12, wherein escalating the invoices and/or documents comprises transmitting the same to the at least one external user terminal, for correction of the invoices and/or documents, upon the invoices and/or documents being identified as not confirming to the pre-determined conditions, the correction required to be carried out in accordance with the identifiers.
17. The method for processing of invoices and/or documents as claimed in claim 12, wherein tracking the escalated invoice and/or document comprises storing information associated with escalation in the database.
18. The method for processing of invoices and/or documents as claimed in claim 17, wherein tracking the escalated invoice and/or document comprises sending periodic reminders to any of the at least one external user terminal and the at least one internal

user terminal, to whom the invoices and/or documents have been escalated, based on the stored information associated with escalation, until processing thereof is complete.
19. The method for processing of invoices and/or documents as claimed in claim 18, wherein tracking the escalated invoice and/or document comprises generating reports regarding invoices and/or documents escalated and those for which processing is complete.