Description:TECHNICAL FIELD
[0001] The present disclosure relates generally to accounting methods and systems, and, more particularly, to remote invoicing methods and systems using an accounts automation application.

BACKGROUND
[0002] Traditional accounting processes involve manual entry and verification of financial transactions. These tasks are time-consuming, error-prone, and resource-intensive. To streamline these operations, various software tools or applications have been developed to automate invoice generation, voucher creation, and related accounting tasks. However, existing accounts automation tools suffer from several drawbacks. Most of the conventional accounts automation tools require extensive configuration to adapt to an organization’s specific accounting practices and customization options available are often convoluted, leading to confusion and suboptimal setups. The predefined workflows in the conventional accounts automation tools may not align with the unique processes of different businesses and modification or extension of workflows becomes difficult. Further, the conventional accounts automation tool lack seamless integration with other enterprise systems, such as enterprise resource planning (ERP) applications due to which efficient data exchange between different modules is hindered. Automated data extraction from source documents (e.g., scanned invoices) can be error-prone. Inaccuracies lead to incorrect financial records and reconciliation issues. As transaction volumes increase, the conventional account automation tools struggle to handle the load efficiently.
[0003] In light of the foregoing, there exists a need to provide a technical solution to overcome the problems of conventional accounts automation tools.

SUMMARY
[0004] According to an aspect of the present disclosure, a remote invoicing method is disclosed. The remote invoicing method includes generating a first sub-user account for an accounts automation application, receiving a set of inputs by the first sub-user account to generate a sales invoice, and generating the sales invoice based on the received set of inputs. Further, the remote invoicing method includes automatically generating a sales voucher corresponding to the sales invoice and storing the sales voucher. Characterized in that, the remote invoicing method includes automatically exporting the stored sales voucher to an enterprise resource planning (ERP) application communicatively coupled with the accounts automation application when an account on the ERP application associated with the first sub-user account is initiated on the ERP application.
[0005] Additionally, or optionally, the remote invoicing method includes generating a user account for the accounts automation application based on a purchase of a subscription license of the accounts automation application and receiving the request from the user account to generate the first sub-user account with unique credentials. The first sub-user account is generated based on the request received from the user account of the accounts automation application.
[0006] Additionally, or optionally, the remote invoicing method includes authorizing the first sub-user account based on a log-in request with the unique credentials.
[0007] Additionally, or optionally, the remote invoicing method includes receiving an indication to automatically generate the sales voucher after generation of the sales invoice. The sales voucher comprises at least one of product details and service details.
[0008] Additionally, or optionally, the remote invoicing method incudes downloading the stored sales voucher in a file and importing the file in the ERP application when the account on the ERP application associated with the first sub-user account is initiated on the ERP application.
[0009] Additionally, or optionally, the remote invoicing method includes providing a machine-readable optical label in the generated sales invoice, generate a purchase voucher corresponding to the sales voucher, scanning the machine-readable optical label by a computing device to download at least one of the sales voucher and the purchase voucher when the accounts automation application is active on the computing device, and scanning the machine-readable optical label by the computing device to link to a webpage to activate the accounts automation application and download at least one of the sales voucher and the purchase voucher when the accounts automation application is inactive on the computing device.
[0010] Additionally, or optionally, the remote invoicing method includes detecting whether a second sub-user account is generated on the accounts automation application based on a unique identifier when the sales invoice is generated for the second sub-user account, generating a purchase invoice corresponding to the sales invoice, requesting permission from the first sub-user account to send the purchase invoice to the second sub-user account based on the detection whether the second sub-user account is generated on the accounts automation application, notifying the second sub-user account to accept the purchase invoice after generation of the sales invoice and the sales voucher, and sending the purchase invoice to the second sub-user account when the second sub-user account accepts the purchase invoice. Further, the remote invoicing method includes automatically generating a purchase voucher corresponding to the purchase invoice, storing the purchase voucher, and automatically exporting the stored purchase voucher to another ERP application communicatively coupled with the accounts automation application when an account on the other ERP application associated with the second sub-user account is initiated on the other ERP application.
[0011] Additionally, or optionally, the remote invoicing method includes downloading the stored purchase voucher in a file and importing the file in the other ERP application when the account on the other ERP application associated with the second sub-user account is initiated on the other ERP application.
[0012] Additionally, or optionally, the remote invoicing method includes generating a second sub-user account for the accounts automation application based on a request received from another user account of the accounts automation application, automatically generating a purchase invoice corresponding to the sales invoice and a purchase voucher based on the purchase invoice, and storing the purchase invoice and the purchase voucher. Further, the remote invoicing method includes automatically exporting the stored purchase voucher to another ERP application communicatively coupled with the accounts automation application when an account on the other ERP application associated with the second sub-user account is initiated on the other ERP application and automatically sending the purchase invoice to the second sub-user account after exporting the stored purchase voucher.
[0013] According to another aspect of the present disclosure, a remote invoicing system comprises at least one hardware-based processor and memory. The memory comprises processor-executable instructions encoded on a non-transient processor-readable media. The processor-executable instructions, when executed by the processor, configure the remote invoicing system to generate a sub-user account for an accounts automation application, receive a set of inputs by the sub-user account to generate a sales invoice, generate the sales invoice based on the received set of inputs, automatically generate a sales voucher corresponding to the sales invoice, store the sales voucher, and characterized in that: automatically export the stored sales voucher to an enterprise resource planning (ERP) application communicatively coupled with the accounts automation application when an account on the ERP application associated with the sub-user account is initiated on the ERP application.
[0014] The remote invoicing system and method utilizing the accounts automation application facilitate simple configuration and customization, allowing users to adapt it to their specific accounting practices effortlessly. Further, the accounts automation application provides flexible workflows, seamless integration with other enterprise systems, such as ERP, accurate data extraction, and improved scalability. Thus, remote invoicing system and method utilizing the accounts automation application may help to enhance productivity, accuracy, and overall financial management for an organization or individual.

BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The illustrated embodiments of the subject matter will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. The following description is intended only by way of example, and simply illustrates certain selected embodiments of devices, systems, and processes that are consistent with the subject matter as claimed herein.
[0016] FIG. 1 is a block diagram of a remote invoicing system in accordance with an exemplary embodiment of the disclosure;
[0017] FIG. 2 is a block diagram that illustrates an accounts automation application of the remote invoicing system of FIG. 1 in accordance with an exemplary embodiment of the disclosure; and
[0018] FIGS. 3A-3E, collectively, represent a flow chart illustrating a remote invoicing method in accordance with an exemplary embodiment of the disclosure.

DETAILED DESCRIPTION
[0019] Example apparatus are described herein. Other example embodiments or features may further be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented herein. In the following detailed description, reference is made to the accompanying drawings, which form a part thereof.
[0020] The example embodiments described herein are not meant to be limiting. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the drawings, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein.
[0021] FIG. 1 is a block diagram of a remote invoicing system 100 in accordance with an exemplary embodiment of the disclosure. The remote invoicing system 100 may utilize an accounts automation application or tool for remote invoicing. An accounts automation application for remote invoicing streamlines the entire invoicing process from generation of the invoices to generation of vouchers and importing of vouchers in an enterprise resource planning (ERP) application for accounting purposes. The accounts automation application may enable users to generate, send, and manage invoices and vouchers digitally through the accounts automation application, regardless of their location.
[0022] The remote invoicing system 100 includes computing devices 102 of users 104, first and second users 104a and 104b, computing devices 106 of sub-users 108, first and second sub-users 108a and 108b, an accounts automation application 110, a database server 112, and an ERP application 114. The computing devices 102 and 106, the accounts automation application 110, the database server 112, and the ERP application 114 may be coupled to each other via a communication network 116.
[0023] The users 104, such as the first user 104a and the second user 104b, may be an individual who may be a financial professional, such as an accountant or a chartered accountant, who provides expertise in various areas of accounting and finance, for example, auditing financial statements, filing tax returns, offering advisory services, and the like. The users 104 may perform various activities related to accounting and finance, by utilizing a service application running on the computing devices 102. In an alternate embodiment, the users 104 may be a firm, an organization, an entity, or a company who may be a professional organization that provides accounting, financial, and advisory services and may be staffed by qualified CAs who assist businesses, individuals, and organizations with their financial needs.
[0024] The computing devices 102, such as a computing device 102a of the first user 104a and a computing device 102b of the second user 104b, may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform one or more operations. The one or more operations may be performed by utilizing the service application running on the computing devices 102. The computing devices 102 may correspond to a device of the users 104. Thus, in some embodiments, the computing devices 102 may be utilized, by the users 104, to perform the one or more operations. For example, the computing device 102a may be utilized by the first user 104a, for purchasing of a subscription license of the accounts automation application and sending a request to generate a user account on the accounts automation application for the first user 104a. Similarly, the computing device 102b may be utilized by the second user 104b, for purchasing of a subscription license of the accounts automation application and sending a request to generate a user account on the accounts automation application for the second user 104b.
[0025] Further, the computing device 102a may be utilized by the first user 104a, for sending a request to generate a first sub-user account on the accounts automation application for the first sub-user 108a. Similarly, the computing device 102b may be utilized by the second user 104b, for sending a request to generate a second sub-user account on the accounts automation application for the second sub-user 108b. Examples of the computing devices 102 may include, but are not limited to, a personal computer, a laptop, a smartphone, and a tablet computer.
[0026] In an embodiment, the computing devices 102 may be configured to receive from the accounts automation application 110 via the communication network 116, one or more user interfaces that enable the users 104 to interact with one or more computing devices, servers, or applications for performing the one or more operations. The one or more user interfaces may be received in response to the purchase of the subscription license and the request sent by the users 104 to generate an account on the accounts automation application. Further, the computing devices 102 may be utilized, by the users 104, to view and interact with the one or more user interfaces (one at a time) rendered by the accounts automation application 110.
[0027] The sub-users 108, such as the first sub-user 108a and the second sub-user 108b, may be an individual who may be an employee, a director, a partner, or an owner of a firm, an organization, an entity, or a company in requirement of expertise in various areas of accounting and finance, for example, auditing financial statements, filing tax returns, offering advisory services, and the like. The sub-users 108 may perform various activities related to accounting and finance, by utilizing a service application running on the computing devices 106. In an alternate embodiment, the sub-users 108 may be a firm, an organization, an entity, or a company who may be in requirement of expertise in various areas of accounting and finance, for example, auditing financial statements, filing tax returns, offering advisory services, and the like.
[0028] The computing devices 106, such as a computing device 106a of the first sub-user 108a and a computing device 106b of the second sub-user 108b, may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform one or more operations. The one or more operations may be performed by utilizing the service application running on the computing devices 106. The computing devices 106 may correspond to a device of the sub-users 108. Thus, in some embodiments, the computing devices 106 may be utilized, by the sub-users 108, to perform the one or more operations. For example, the computing device 106a may be utilized by the first sub-user 108a, for purchasing of a subscription license of the accounts automation application and sending a request to generate a user account on the accounts automation application for the first sub-user 108a. Similarly, the computing device 106b may be utilized by the second sub-user 108b, for purchasing of a subscription license of the accounts automation application and sending a request to generate a user account on the accounts automation application for the second sub-user 108b.
[0029] Further, the computing device 106a may be utilized by the first sub-user 108a, for logging in a first sub-user account on the accounts automation application for the first sub-user 108a. In one embodiment, the first sub-user account may be generated on the accounts automation application based on the request sent by the first sub-user 108a via the computing device 106a. In another embodiment, the first sub-user account may be generated on the accounts automation application based on the request sent by the first user 104a via the computing device 102a. Similarly, the computing device 106b may be utilized by the second sub-user 108b, for logging in a second sub-user account on the accounts automation application for the second sub-user 108b. In one embodiment, the second sub-user account may be generated on the accounts automation application based on the request sent by the second sub-user 108b via the computing device 106b. In another embodiment, the second sub-user account may be generated on the accounts automation application based on the request sent by the second user 104b via the computing device 102b. Examples of the computing devices 106 may include, but are not limited to, a personal computer, a laptop, a smartphone, and a tablet computer.
[0030] Furthermore, the computing device 106a may be utilized by the first sub-user 108a, for providing a set of inputs to generate invoices on the accounts automation application 110 and providing confirmation to generate vouchers and send invoices or vouchers to other users or sub-users. Similarly, the computing device 106b may be utilized by the second sub-user 108b, for providing a set of inputs to generate invoices on the accounts automation application 110 and providing confirmation to generate invoices or vouchers and send vouchers to other users or sub-users.
[0031] In an embodiment, the computing devices 106 may be configured to receive from the accounts automation application 110 via the communication network 116, one or more user interfaces that enable the sub-users 108 to interact with one or more computing devices, servers, or applications for performing the one or more operations. The one or more user interfaces may be received in response to the purchase of the subscription license and the request sent by the users 104 or the sub-users 108 to generate an account on the accounts automation application. Further, the computing devices 106 may be utilized, by the users 108, to view and interact with the one or more user interfaces (one at a time) rendered by the accounts automation application 110.
[0032] In one embodiment, the sub-users 108 may avail financial services from one of the users 104. In the embodiment, one of the users 108, for example, the first user 104a may be associated with the first sub-users 108a and may send a request to generate the first sub-user account of the first sub-user 108a under the user account of the first user 104a on the accounts automation application 110, by utilizing a service application running on the computing device 102a. In another embodiment, the sub-users 108 may send a request directly to generate the first sub-user account of the first sub-user 108a on the accounts automation application 110, by utilizing a service application running on the computing device 106a.
[0033] The accounts automation application 110 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform one or more operations for remote invoicing. The accounts automation application 110 may be a computing device, which may include a software framework, that may be configured to create the application server implementation and perform the various operations associated with remote invoicing. The accounts automation application 110 may be realized through various web-based technologies, such as, but are not limited to, a Java web-framework, a .NET framework, a PHP framework, a python framework, or any other web-application framework. The accounts automation application 110 may also be realized as a machine-learning model that implements any suitable machine-learning techniques, statistical techniques, or probabilistic techniques. Examples of such techniques may include expert systems, fuzzy logic, support vector machines (SVM), Hidden Markov models (HMMs), greedy search algorithms, rule-based systems, Bayesian models (e.g., Bayesian networks), neural networks, decision tree learning methods, other non-linear training techniques, data fusion, utility-based analytical systems, or the like. Examples of the accounts automation application 110 may include, but are not limited to, a personal computer, a laptop, or a network of computer systems.
[0034] In an embodiment, the accounts automation application 110 may be configured to process, control, and manage various functionalities and operations such as account generation, invoice generation, voucher generation, voucher exporting, and the like. For example, the accounts automation application 110 may be further configured to generate a first sub-user account for the accounts automation application 110. In one embodiment, the first sub-user account is generated with unique credentials based on the request received from the user account of the accounts automation application 110 by the first user 104a via the computing device 102a or based on the purchase of the subscription license of the accounts automation application 110 by the first sub-user 108a via the computing device 106a. The subscription licenses may grant a user, such as the first sub-user 108a, the right to use specific software, for example, the accounts automation application or software, through a one-time upfront fee or may involve recurring payments for access to software features or services. The accounts automation application 110 may be further configured to authorize the first sub-user account based on a log-in request with the unique credentials. Examples of the unique credentials may include, but not limited to, a unique identifier, a password, an email id, a code, and a personal identification number. In one embodiment, each user and sub-user is uniquely identified by way of the unique identifier of the corresponding user or sub-user provided by the accounts automation application 110.
[0035] After the authorization of the user account, the accounts automation application 110 may be configured to receive a set of inputs by the first sub-user account to generate a sales invoice and generate the sales invoice based on the received set of inputs. The sales invoice may be a document that records details of products or services provided, transaction dates, amounts owed, taxes, and payment terms. The sales invoice may serve as a foundation for accurate bookkeeping, aids in tax returns, helps manage inventory, and provides legal protections for business. In one embodiment of the present disclosure, the accounts automation application 110 may be configured to render a user interface on the computing device 106a of the first sub-user 108a presenting various fields required to generate the sale invoice.
[0036] Once the sales invoice is generated, the accounts automation application 110 may be configured to receive an indication from the first sub-user account of the first sub-user 108a via the computing device 106a to automatically generate a sales voucher. The sales voucher may include at least one of product details and service details. The sales voucher is a record of a sales transaction and served as a carbon copy of the sales invoice given to a customer. The sales voucher may be generated for providing real-time information, aiding commission payments, facilitating credit and billing, and serving as documentation for dispute resolution. Based on the received indication, the accounts automation application 110 may be configured to automatically generate the sales voucher corresponding to the sales invoice and store the sales voucher in a database. In one embodiment, the database may be in the accounts automation application 110. In alternate embodiment, the database may be in the database server 112.
[0037] The accounts automation application 110 may be configured to automatically export the stored sales voucher to the ERP application 114 communicatively coupled with the accounts automation application 110 when an account on the ERP application 114 associated with the first sub-user account is initiated on the ERP application 114. In an embodiment, when the ERP application 114 is integrated with the accounts automation application 110, the stored sales voucher may be directly exported to the ERP application 114 from the accounts automation application 110. In another embodiment, when the ERP application 114 is not integrated with the accounts automation application 110, the stored sales voucher may be downloaded in a file and the file may be imported in to the ERP application 114 when the account on the ERP application 114 associated with the first sub-user account is initiated on the ERP application 114. Various operations and functionalities of the accounts automation application 110 have been described in detail in conjunction with FIGS. 2 and 3A-3E.
[0038] The database server 112 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform one or more database operations, such as receiving, storing, processing, and transmitting queries, data, or content. The database server 112 may be a data management and storage computing device that is communicatively coupled to the computing devices 102, the computing devices 106, the accounts automation application 110, and the ERP application 114 via the communication network 116 to perform the one or more database operations. Examples of the database server 112 may include, but are not limited to, a personal computer, a laptop, or a network of computer systems.
[0039] In an embodiment, the database server 112 may be configured to manage and store historical data of various invoices and vouchers generated by each user or sub-user. The historical data of each invoice and voucher may include data of user account or the sub-user account associated with the respective invoice and voucher. In an exemplary embodiment, the historical transaction data of each invoice and voucher may include at least the data associated with the product or the service, data of users or sub-users on whose account the invoices or vouchers may be generated, such as the first and second sub-users 108a and 108b, a unique identifier of the users or sub-users, and a value of each of invoices and vouchers. The database server 112 may be configured to obtain the historical transaction data from at least one of the computing devices (such as the computing devices 102 and the computing devices 106), the accounts automation application 110, or the ERP application 114. In an embodiment, the database server 112 may be further configured to manage and store historical invoices and vouchers generated on the accounts automation application 110.
[0040] In an embodiment, the database server 112 may be further configured to manage and store the unique credentials of each user and sub-user. The database server 112 may be further configured to generate a data structure including one or more rows and columns for storing the plurality of invoices and vouchers. For example, each row may be associated with a user or sub-user identifier, and one or more columns corresponding to each row may indicate a product or service name, a product or service ID, an identity of the user or sub-user, an identity of the user of one of the product and the service, and/or the like. Further, the database server 112 may be configured to manage and store the data associated with association of the sub-user accounts with the user accounts, such as the association of the first sub-user account of the first sub-user 108a with the user account of the first user 104a when the first user 104a creates and account of the first sub-user 108a on the accounts automation application 110.
[0041] In an embodiment, the database server 112 may be further configured to receive a query from the accounts automation application 110 via the communication network 116. The query may be an encrypted message that is decoded by the database server 112 to determine one or more requests for retrieving requisite information (such as the invoices and the voucher, the data associated with the associations of the users and sub-users, or any combination thereof). In response to the determined one or more requests, the database server 112 may be configured to retrieve and communicate the requested information to the accounts automation application 110 via the communication network 116.
[0042] The ERP application 114 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform one or more operations for remote invoicing. The ERP application 114 may be a computing device, which may include a software framework, that may be configured to create the ERP application implementation and perform the various operations associated with remote invoicing. In one embodiment, the ERP application 114 may be a software system designed to integrate and manage various core business processes within an organization and may be configured to provide a centralized platform for automating and streamlining operations across functions such as finance, human resources, procurement, distribution, and supply chain and act as the “central nervous system” of an enterprise, ensuring efficient day-to-day business operations and providing a single source of truth for data across the organization. Modern ERP systems, delivered via the cloud, utilize technologies like artificial intelligence and machine learning to enhance efficiency and collaboration, connecting internal operations with global business networks. In one example, the ERP may be Tally® ERP which is a powerful and trusted business management software solution that integrates accounting, auditing, invoicing, iTax, sale purchase management, and the like.
[0043] The communication network 116 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to transmit queries, messages, and requests between various entities, such as the computing devices 102 and 106, the accounts automation application 110, the database server 112, and/or the ERP application 114. Examples of the communication network 116 include, but are not limited to, a wireless fidelity (Wi-Fi) network, a light fidelity (Li-Fi) network, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a satellite network, the Internet, a fiber optic network, a coaxial cable network, an infrared (IR) network, a radio frequency (RF) network, and a combination thereof. Various entities in the system 100 may connect to the communication network 116 in accordance with various wired and wireless communication protocols, such as Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Long Term Evolution (LTE) communication protocols, or any combination thereof.
[0044] FIG. 2 is a block diagram 200 that illustrates the accounts automation application 110, in accordance with an exemplary embodiment of the disclosure. The accounts automation application 110 includes circuitry such as a processor 202, a memory 204, a transceiver 206, and an input/output (I/O) port 208 that communicate with each other by way of a first communication bus 210.
[0045] The processor 202 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform one or more operations associated with the automated patent evaluation and infringement management. Examples of the processor 202 may include, but are not limited to, an application-specific integrated circuit (ASIC) processor, a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, and a field-programmable gate array (FPGA). It will be apparent to a person of ordinary skill in the art that the processor 202 may be compatible with multiple operating systems.
[0046] In an embodiment, the processor 202 may be configured to control and manage various functionalities and operations such as account generation, invoice generation, voucher generation, voucher exporting, and the like. The various functionalities and operations may be controlled and managed by one or more internal components of the processor 202, such as an account generation engine 202a, an invoice generation engine 202b, a voucher generation engine 202c, and a voucher exporting engine 202d, that communicate with each other. In some embodiments, the processor 202 may operate as a master processing unit, and the account generation engine 202a, the invoice generation engine 202b, the voucher generation engine 202c, and the voucher exporting engine 202d may operate as slave processing units. In such a scenario, the processor 202 may be configured to instruct the account generation engine 202a, the invoice generation engine 202b, the voucher generation engine 202c, and the voucher exporting engine 202d to perform their corresponding operations either independently or in conjunction with each other.
[0047] The account generation engine 202a may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform the one or more operations for account generation. The account generation engine 202a may be implemented by one or more processors, such as, but are not limited to, an ASIC processor, a RISC processor, a CISC processor, and an FPGA processor.
[0048] The invoice generation engine 202b may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform the one or more operations for invoice generation. The invoice generation engine 202b may be implemented by one or more processors, such as, but are not limited to, an ASIC processor, a RISC processor, a CISC processor, and an FPGA processor.
[0049] The voucher generation engine 202c may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform the one or more operations for voucher generation. The voucher generation engine 202c may be implemented by one or more processors, such as, but are not limited to, an ASIC processor, a RISC processor, a CISC processor, and an FPGA processor.
[0050] The voucher exporting engine 202d may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform the one or more operations for voucher generation. The voucher exporting engine 202d may be implemented by one or more processors, such as, but are not limited to, an ASIC processor, a RISC processor, a CISC processor, and an FPGA processor.
[0051] In operation, the user 104a, such as a chartered accountant, may purchase the subscription license of the accounts automation application 110 utilizing the computing device 102a. Upon purchase of the subscription license, the account generation engine 202a may be configured to generate the user account for the accounts automation application 110. The user 104a may create a sub-user account for a client on the accounts automation application 110. The account generation engine 202a may thus be configured to receive the request from the user account to generate the first sub-user account with unique credentials for the first sub-user 108a from the computing device 102a. In an alternate embodiment, the first sub-user 108a may directly purchase the subscription license for the accounts automation application 110. Based on one of the request from the user account to generate the first sub-user account and purchase the subscription license for the accounts automation application 110 by the first sub-user 108a, the account generation engine 202a may be further configured to generate the first sub-user account of the first sub-user 108a for the accounts automation application 110 with the unique credentials. In one embodiment, the first sub-user account is generated with unique credentials based on the request received from the user account of the accounts automation application 110 by the first user 104a via the computing device 102a or based on the purchase of the subscription license of the accounts automation application 110 by the first sub-user 108a via the computing device 106a.
[0052] After the generation of the first sub-user account, the account generation engine 202a may render a first user interface on the computing device 106a presenting a login page to the first sub-user 108a. The first sub-user 108a may attempt to login on the accounts automation application 110 by way of the computing device 106a by interacting with the first user interface and providing the unique credentials as an input. The account generation engine 202a may be further configured to authorize the first sub-user account based on a log-in request with the unique credentials received from the computing device 106a.
[0053] After the authorization of the first sub-user account, the invoice generation engine 202b may render a second user interface on the computing device 106a presenting an invoice creation page to the first sub-user 108a. The first sub-user 108a may provide the set of inputs for generating the sales invoice by way of the computing device 106a by interacting with the second user interface. In one embodiment, the set of inputs may include, but not limited to, one of product and service details, information regarding entity to which product or service provided, information regarding the unique identifier of the entity, a date of the sales invoice, and an amount of the sales invoice. The invoice generation engine 202b may be configured to receive the set of inputs by the first sub-user account to generate the sales invoice. Based on the received set of inputs, the invoice generation engine 202b may be configured to generate the sales invoice. In one embodiment, the first sub-user 108a may be able to download the sales invoice.
[0054] Once the sales invoice is generated, the voucher generation engine 202c may be configured to render a notification on the computing device 106a of the first sub-user 108a to confirm whether the sales voucher corresponding to the sales invoice is to be generated. In response to the notification, the first sub-user 108a may utilize the computing device 106a to provide the indication for automatic generation of the sales voucher. The voucher generation engine 202c may thus be configured to receive the indication from the first sub-user account of the first sub-user 108a via the computing device 106a to automatically generate the sales voucher. The sales voucher may include at least one of product details and service details. Based on the received indication, the voucher generation engine 202c may be configured to automatically generate the sales voucher corresponding to the sales invoice and store the sales voucher in the database. In one embodiment, the database may be in the accounts automation application 110. In alternate embodiment, the database may be in the database server 112. It will be apparent to a person skilled in the art that multiple such sales vouchers corresponding to multiple sales invoices may be stored in the database.
[0055] In one scenario, when the accounts automation application 110 is integrated with the ERP application 114, the first user 104a may be able to directly import the stored sales voucher when the first user 104a, by way of the computing device 102a, initiates an account on the ERP application 114 that is associated with the first sub-user account of the first sub-user 108a. The voucher exporting engine 202d may be configured to automatically export the stored sales voucher to the ERP application 114 that is communicatively coupled with the accounts automation application 110 when the account on the ERP application 114 associated with the first sub-user account is initiated on the ERP application 114.
[0056] In another scenario, when the accounts automation application 110 is not integrated with the ERP application 114, the user 104a may not be able to directly import the stored sales voucher when the first user 104a, by way of the computing device 102a, initiates an account on the ERP application 114 that is associated with the first sub-user account of the first sub-user 108a. In this scenario, the voucher exporting engine 202d may be configured to export the stored sales voucher in a file. The stored sales voucher may thus be downloaded in the file by the first user 104a utilizing the computing device 102a and the file may be imported in to the ERP application 114 when the account on the ERP application 114 associated with the first sub-user account is initiated on the ERP application 114 by the first user 104a by utilizing the computing device 102a. Examples of the file include, but not limited to, an excel file (i.e., .xls or .xlsx file) and a comma separated value file (i.e., .csv file). It will be apparent to a person skilled in the art that the file may correspond to any suitable file type without deviating from the scope of the present disclosure.
[0057] In one embodiment, the invoice generation engine 202b may be further configured to generate a purchase invoice corresponding to the sales invoice upon generation of the sales invoice. The purchase invoice, also known as a supplier invoice or bill, may be a document that records the purchase of goods or services and serves as proof of the transaction for both the buyer and the vendor, detailing essential information such as the quantity, price, taxes, and payment term. Further, the invoice generation engine 202b may be configured to provide a machine-readable optical label in the generated sales invoice and the generated purchase invoice. In one embodiment, the machine-readable optical label may correspond to a quick-response (QR) code. It will be apparent to a person skilled in the art that in alternate embodiments, the machine-readable optical label may correspond to any suitable code, such as a bar code, with deviating from the scope of the present disclosure.
[0058] Further, upon generation of the sales voucher, the voucher generation engine 202c may be configured to generate a purchase voucher corresponding to the sales voucher. The purchase voucher may be used to document purchases made by an individual or a company and includes details such as the supplier’s information, purchase date, item descriptions, quantities, unit prices, and the total amount. The purchase vouchers help businesses track expenses, manage inventory, and verify supplier invoices.
[0059] In one embodiment, when the accounts automation application is active (i.e., downloaded and running) on the computing devices 102 or 106, the users 104 or the sub-users 108 may utilize the computing devices 102 or the computing devices 106, respectively, to scan the machine-readable optical label to download at least one of the sales voucher and the purchase voucher. In another embodiment, when the accounts automation application is inactive (i.e., not downloaded and not running) on the computing devices 102 or 106, the users 104 or the sub-users 108 may utilize the computing devices 102 or the computing devices 106, respectively, to scan the machine-readable optical label to get linked to a webpage for activation (i.e., downloading and running) of the accounts automation application 110 on the computing devices 102 or 106 and download at least one of the sales voucher and the purchase voucher upon activation of the accounts automation application 110. Thus, the machine-readable optical label does not store the sales voucher or the purchase voucher, instead, store a link to the sales voucher or the purchase voucher or a link to initiate the process of registering on the accounts automation application 110 and downloading the sales voucher and the purchase voucher. As a result, the accounts automation application 110 facilitates security of confidential information.
[0060] In one embodiment, when the first sub-user 108a generates the sales invoice utilizing the computing device 106a for the second sub-user 108b who has an account, such as a second sub-user account, on the accounts automation application 110, the accounts generation engine 202a may be configured to detect whether the second sub-user account is generated on the accounts automation application based on a unique identifier when the sales invoice is generated for the second sub-user account. In one embodiment, the unique identifier of the second sub-user account of the second sub-user 108b may be utilized to detect that the second sub-user account is generated on the accounts automation application 110. In one example, the unique identifier is an email id of the second sub-user 108b. In the embodiment, it will be understood by a person skilled in the art that the first sub-user 108a and the second sub-user 108b may be primary users of the accounts automation application 110 and may not be sub-users and may have direct access to the ERP application 114. The invoice generation engine 202b may be configured to generate the purchase invoice corresponding to the sales invoice. Upon generation of the purchase invoice, the voucher generation engine 202c may be configured to request permission from the first sub-user account to send the purchase invoice to the second sub-user account based on the detection whether the second sub-user account is generated on the accounts automation application 110. Further, the voucher generation engine 202c may be configured to notify the second sub-user account to accept the purchase invoice after generation of the sales invoice and the sales voucher. In one embodiment, the voucher generation engine 202c may be configured to render a third user interface to present a notification page on the computing device 106b of the second sub-user 108b for accepting the purchase invoice.
[0061] When the second sub-user 108b accepts the purchase invoice by interacting with the third user interface by utilizing the computing device 106b, the invoice generation engine 202b may be configured to send the purchase invoice to the second sub-user account. The voucher generation engine 202c may be configured to automatically generate the purchase voucher corresponding to the purchase invoice and store the purchase voucher in the database. In one scenario, when the accounts automation application 110 is integrated with the ERP application 114, the second user 104b may be able to directly import the stored purchase voucher when the second user 104b, by way of the computing device 102b, initiates an account on the ERP application 114 that is associated with the second sub-user account of the second sub-user 108b. The voucher exporting engine 202d may be configured to automatically export the stored purchase voucher to the ERP application 114 that is communicatively coupled with the accounts automation application 110 when the account on the ERP application 114 associated with the second sub-user account is initiated on the ERP application 114.
[0062] In another scenario, when the accounts automation application 110 is not integrated with the ERP application 114, the second user 104b may not be able to directly import the stored purchase voucher when the second user 104b, by way of the computing device 102b, initiates an account on the ERP application 114 that is associated with the second sub-user account of the second sub-user 108b. In this scenario, the voucher exporting engine 202d may be configured to export the stored purchase voucher in a file. The stored purchase voucher may thus be downloaded in the file by the second user 104b utilizing the computing device 102b and the file may be imported in to the ERP application 114 when the account on the ERP application 114 associated with the second sub-user account is initiated on the ERP application 114 by the second user 104b by utilizing the computing device 102b. Examples of the file include, but not limited to, an excel file (i.e., .xls or .xlsx file) and a comma separated value file (i.e., .csv file). It will be apparent to a person skilled in the art that the file may correspond to any suitable file type without deviating from the scope of the present disclosure.
[0063] It will be understood by a person skilled in the art that though in the current embodiment, the first user 104a has created an account for the first sub-user 108a and the second user 104b has created an account for the second sub-user 108b on the accounts automation application 110, that is, the chartered accountant of the first and second sub-users 108a and 108b are different, the scope of the present disclosure is not limited to it. In various other embodiments, the first user 104a may create an account for the first sub-user 108a and the second sub-user 108b on the accounts automation application 110, that is, the chartered accountant for the first and second sub-users 108a and 108b is the same, without deviating from the scope of the present disclosure.
[0064] In one scenario, when the first user 104a generates the first sub-user account for the first sub-user 108a and the second user 104b generates the second sub-user account for the second sub-user 108b on the accounts automation application, the account generation engine 202a may be configured to generate the second sub-user account for the accounts automation application 110 based on a request received from the second user account of the accounts automation application 110 by the second user 104b utilizing the computing device 102b. Upon generation of the sales invoice by the first sub-user 108a for the second sub-user 108b, the invoice generation engine 202b and the voucher generation engine 202c may be configured to automatically generate the purchase invoice corresponding to the sales invoice and the purchase voucher based on the purchase invoice and store the purchase invoice and the purchase voucher in the database.
[0065] When an account on the ERP application 114 associated with the second sub-user account is initiated on the ERP application 114 by the second user 104b utilizing the computing device 102b, the voucher exporting engine 202d may be further configured to automatically export the stored purchase voucher to the ERP application 114 that is communicatively coupled with the accounts automation application 110. In one embodiment, the ERP application 114 associated with the first sub-user account and the second sub-user account may be different or same. Further, the invoice generation engine 202b may be configured to automatically send the purchase invoice to the second sub-user account after exporting the stored purchase voucher.
[0066] The memory 204 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to store one or more instructions that are executed by the processor 202, the account generation engine 202a, the invoice generation engine 202b, the voucher generation engine 202c, the voucher exporting engine 202d, the transceiver 206, and the I/O port 208 to perform their operations. In an exemplary embodiment, the memory 204 may be configured to temporarily store the generated sales invoices, purchase invoices, sales vouchers, and the purchase vouchers. The memory 204 may be further configured to temporarily store the user credentials of each user and sub-user for authorization operations. Examples of the memory 204 may include, but are not limited to, a random-access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), and an erasable PROM (EPROM).
[0067] The transceiver 206 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to transmit (or receive) data to (or from) various servers or devices, such as the computing devices 102 and 106, the database server 112, or the ERP application 114. Examples of the transceiver 206 may include, but are not limited to, an antenna, a radio frequency transceiver, a wireless transceiver, and a Bluetooth transceiver. The transceiver 206 may be configured to communicate with the computing devices 102 and 106, the database server 112, or the ERP application 114 using various wired and wireless communication protocols, such as TCP/IP, UDP, LTE communication protocols, or any combination thereof.
[0068] The I/O port 208 may include suitable logic, circuitry, interfaces, and/or code, executable by the circuitry, that may be configured to perform the one or more operations related to input or output features facilitated to the one or more users and the sub-users. The I/O port 208 may include interface to various input and output devices that are configured to communicate with the processor 202, the memory 204, and the transceiver 206. Examples of interface to the input devices may include interfaces to a keyboard, a mouse, a joystick, a touchscreen, a microphone, and the like. Examples of interface to the output devices may include interface to a display, a speaker, a headphone, and the like.
[0069] FIGS. 3A-3E, collectively, represent a flow chart illustrating a remote invoicing method 300 in accordance with an exemplary embodiment of the disclosure.
[0070] At 302, the accounts automation application 110 generates the user account for the accounts automation application 110 based on the purchase of the subscription license of the accounts automation application 110 by the first user 104a by way of the computing device 102a. At 304, the accounts automation application 110 receives the request from the user account to generate the first sub-user account with unique credentials for the first sub-user 108a utilizing the computing device 102a. At 306, the accounts automation application 110 generates the first sub-user account of the first sub-user 108a for the accounts automation application 110. At 308, the accounts automation application 110 generates the second sub-user account of the second sub-user 108b for the accounts automation application 110 based on a request received from user account of the second user 104b of the accounts automation application.
[0071] At 310, the accounts automation application 110 authorizes the first sub-user account based on a log-in request with the unique credentials. At 312, the accounts automation application 110 receives the set of inputs by the first sub-user account to generate the sales invoice. At 314, accounts automation application 110 generates the sales invoice based on the received set of inputs. At 316, the accounts automation application 110 provides the machine-readable optical label in the generated sales invoice. At 318, the accounts automation application 110 receives the indication to automatically generate the sales voucher after generation of the sales invoice. At 320, the accounts automation application 110 automatically generates the sales voucher corresponding to the sales invoice. At 322, the accounts automation application 110 stores the sales voucher in the database.
[0072] At 324, the accounts automation application 110 determines whether the accounts automation application 110 is integrated with the ERP application 114. If at 324, the accounts automation application 110 determines that the accounts automation application 110 is integrated with the ERP application 114, 326 is executed. At 326, the accounts automation application 110 automatically exports the stored sales voucher to the ERP application 114 that is communicatively coupled with the accounts automation application 110 when an account on the ERP application 114 associated with the first sub-user account is initiated on the ERP application 114.
[0073] If at 324, the accounts automation application 110 determines that the accounts automation application 110 is not integrated with the ERP application 114, 328 is executed. At 328, the computing device 102a downloads the stored sales voucher in the file. At 330, the ERP application 114 imports the file in the ERP application 114 when the account on the ERP application 114 associated with the first sub-user account is initiated.
[0074] At 332, the accounts automation application 110 generates the purchase voucher corresponding to the sales voucher. At 334, the accounts automation application 110 determines whether the accounts automation application 110 is active on the computing device 102 or 106. If at 334, the accounts automation application 110 determines that the accounts automation application 110 is active on the computing device 102 or 106, 336 is executed. At 336, the computing device 102 or 106 scans the machine-readable optical label to download at least one of the sales voucher and the purchase voucher.
[0075] If at 334, the accounts automation application 110 determines that the accounts automation application 110 is inactive on the computing device 102 or 106, 338 is executed. At 338, the computing device 102 or 106 scans the machine-readable optical label to link to the webpage to activate the accounts automation application 110 and download at least one of the sales voucher and the purchase voucher.
[0076] At 340, the accounts automation application 110 detects whether the second sub-user account is generated on the accounts automation application 110 based on the unique identifier. If at 340, the accounts automation application 110 detects that the second sub-user account is generated on the accounts automation application 110 based on the unique identifier, 342-360 or 362-368 are executed.
[0077] At 342, the accounts automation application 110 generates the purchase invoice corresponding to the sales invoice. At 344, the accounts automation application 110 requests permission from the first sub-user account to send the purchase invoice to the second sub-user account. At 346, the accounts automation application 110 notifies the second sub-user account to accept the purchase invoice. At 348, the accounts automation application 110 sends the purchase invoice to the second sub-user account upon acceptance of the purchase invoice by the second sub-user account.
[0078] At 350, the accounts automation application 110 automatically generates the purchase voucher corresponding to the purchase invoice. At 352, the accounts automation application 110 stores the purchase voucher in the database.
[0079] At 354, the accounts automation application 110 determines whether the accounts automation application 110 is integrated with the ERP application 114. If at 354, the accounts automation application 110 determines that the accounts automation application 110 is integrated with the ERP application 114, 356 is executed. At 356, the accounts automation application 110 automatically exports the stored purchase voucher to the ERP application 114 that is communicatively coupled with the accounts automation application 110 when an account on the ERP application 114 associated with the second sub-user account is initiated on the ERP application 114.
[0080] If at 354, the accounts automation application 110 determines that the accounts automation application 110 is not integrated with the ERP application 114, 358 is executed. At 358, the computing device 102b downloads the stored purchase voucher in the file. At 360, the ERP application 114 imports the file in the ERP application 114 when the account on the ERP application 114 associated with the second sub-user account is initiated.
[0081] At 362, the accounts automation application 110 automatically generates the purchase invoice corresponding to the sales invoice and the purchase voucher based on the purchase invoice. At 364, the accounts automation application 110 stores the purchase invoice and the purchase voucher in the database. At 366, the accounts automation application 110 automatically exports the stored purchase voucher to another ERP application communicatively coupled with the accounts automation application 110 when an account on the other ERP application associated with the second sub-user account is initiated on the other ERP application. At 368, the accounts automation application 110 automatically sends the purchase invoice to the second sub-user account after exporting the stored purchase voucher.
[0082] The present disclosure facilitates the remote invoicing system 100 and the remote invoicing method 300 utilizing the accounts automation application 110 to facilitate simple configuration and customization, allowing users to adapt it to their specific accounting practices effortlessly. Further, the accounts automation application 110 provides flexible workflows, seamless integration with other enterprise systems, such as ERP application 114, accurate data extraction, and improved scalability. Thus, remote invoicing system and method utilizing the accounts automation application may help to enhance productivity, accuracy, and overall financial management for an organization or individual.
[0083] A person of ordinary skill in the art will appreciate that embodiments and exemplary scenarios of the disclosed subject matter may be practiced with various computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, as well as pervasive or miniature computers that may be embedded into virtually any device. Further, the operations may be described as a sequential process, however some of the operations may in fact be performed in parallel, concurrently, and/or in a distributed environment, and with program code stored locally or remotely for access by single or multiprocessor machines. In addition, in some embodiments, the order of operations may be rearranged without departing from the spirit of the disclosed subject matter.
[0084] Techniques consistent with the disclosure provide, among other features, systems and methods for automated patent evaluation and infringement management. While various exemplary embodiments of the disclosed systems and methods have been described above, it should be understood that they have been presented for purposes of example only, and not limitations. It is not exhaustive and does not limit the disclosure to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the disclosure, without departing from the breadth or scope.
[0085] While various embodiments of the disclosure have been illustrated and described, it will be clear that the disclosure is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions, and equivalents will be apparent to those skilled in the art, without departing from the spirit and scope of the disclosure, as described in the claims.
[0086] Although the disclosure is described herein with reference to specific embodiments, various modifications and changes can be made without departing from the scope of the present disclosure as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present disclosure. Any benefits, advantages, or solutions to problems that are described herein with regard to specific embodiments are not intended to be construed as a critical, required, or essential feature or element of any or all the claims.
[0087] The term “coupled,” as used herein, is not intended to be limited to a direct coupling or a mechanical coupling.
[0088] Furthermore, the terms “a” or “an,” as used herein, are defined as one or more than one. Also, the use of introductory phrases such as “at least one” and “one or more” in the claims should not be construed to imply that the introduction of another claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to disclosures containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an.” The same holds true for the use of definite articles.
[0089] Unless stated otherwise, terms such as “first” and “second” are used to arbitrarily distinguish between the elements such terms describe. Thus, these terms are not necessarily intended to indicate temporal or other prioritization of such elements.
[0090] Unless otherwise stated, conditional languages such as "can", "could", "will", "might", or "may" are understood within the context as used in general to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional languages are not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
[0091] It will be understood by those within the art that, in general, terms used herein, are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.).
, Claims:We Claim:
1. A remote invoicing method (300), comprising:
generating a first sub-user account for an accounts automation application (110);
receiving a set of inputs by the first sub-user account to generate a sales invoice;
generating the sales invoice based on the received set of inputs;
automatically generating a sales voucher corresponding to the sales invoice;
storing the sales voucher; and
characterized in that:
automatically exporting the stored sales voucher to an enterprise resource planning (ERP) application (114) communicatively coupled with the accounts automation application (110) when an account on the ERP application (114) associated with the first sub-user account is initiated on the ERP application (114).

2. The remote invoicing method (300) as claimed in claim 1, comprising:
generating a user account for the accounts automation application (110) based on a purchase of a subscription license of the accounts automation application (110); and
receiving the request from the user account to generate the first sub-user account with unique credentials, wherein the first sub-user account is generated based on the request received from the user account of the accounts automation application (110).

3. The remote invoicing method (300) as claimed in claim 2, comprising:
authorizing the first sub-user account based on a log-in request with the unique credentials.

4. The remote invoicing method (300) as claimed in claim 1, comprising:
receiving an indication to automatically generate the sales voucher after generation of the sales invoice, wherein the sales voucher comprises at least one of product details and service details.

5. The remote invoicing method (300) as claimed in claim 1, comprising:
downloading the stored sales voucher in a file; and
importing the file in the ERP application (114) when the account on the ERP application (114) associated with the first sub-user account is initiated on the ERP application (114).

6. The remote invoicing method (300) as claimed in claim 1, comprising:
providing a machine-readable optical label in the generated sales invoice;
generate a purchase voucher corresponding to the sales voucher;
scanning the machine-readable optical label by a computing device (102 or 106) to download at least one of the sales voucher and the purchase voucher when the accounts automation application (110) is active on the computing device (102 or 106); and
scanning the machine-readable optical label by the computing device (102 or 106) to link to a webpage to activate the accounts automation application (110) and download at least one of the sales voucher and the purchase voucher when the accounts automation application (110) is inactive on the computing device (102 or 106).

7. The remote invoicing method (300) as claimed in claim 1, comprising:
detecting whether a second sub-user account is generated on the accounts automation application (110) based on a unique identifier when the sales invoice is generated for the second sub-user account;
generating a purchase invoice corresponding to the sales invoice;
requesting permission from the first sub-user account to send the purchase invoice to the second sub-user account based on the detection whether the second sub-user account is generated on the accounts automation application (110);
notifying the second sub-user account to accept the purchase invoice after generation of the sales invoice and the sales voucher;
sending the purchase invoice to the second sub-user account when the second sub-user account accepts the purchase invoice;
automatically generating a purchase voucher corresponding to the purchase invoice;
storing the purchase voucher; and
automatically exporting the stored purchase voucher to another ERP application communicatively coupled with the accounts automation application (110) when an account on the other ERP application associated with the second sub-user account is initiated on the other ERP application.

8. The remote invoicing method (300) as claimed in claim 7, comprising:
downloading the stored purchase voucher in a file; and
importing the file in the other ERP application when the account on the other ERP application associated with the second sub-user account is initiated on the other ERP application.

9. The remote invoicing method (300) as claimed in claim 1, comprising:
generating a second sub-user account for the accounts automation application (110) based on a request received from another user account of the accounts automation application (110);
automatically generating a purchase invoice corresponding to the sales invoice and a purchase voucher based on the purchase invoice;
storing the purchase invoice and the purchase voucher;
automatically exporting the stored purchase voucher to another ERP application communicatively coupled with the accounts automation application (110) when an account on the other ERP application associated with the second sub-user account is initiated on the other ERP application; and
automatically sending the purchase invoice to the second sub-user account after exporting the stored purchase voucher.

10. A remote invoicing system (100), comprising:
at least one hardware-based processor and memory, wherein the memory comprises processor-executable instructions encoded on a non-transient processor-readable media, wherein the processor-executable instructions, when executed by the processor, configure the remote invoicing system to:
generate a sub-user account for an accounts automation application (110);
receive a set of inputs by the sub-user account to generate a sales invoice;
generate the sales invoice based on the received set of inputs;
automatically generate a sales voucher corresponding to the sales invoice;
store the sales voucher; and
characterized in that:
automatically export the stored sales voucher to an enterprise resource planning (ERP) application (114) communicatively coupled with the accounts automation application (110) when an account on the ERP application (114) associated with the sub-user account is initiated on the ERP application (114).