On demand accrual system and method

BACKGROUND OF THE INVENTION

p-00021. Technical Field

p-0003The present invention relates generally to accounting systems, and more specifically relates to a system and method for performing on demand accrual in an enterprise resource planning (ERP) system.

p-00042. Related Art

p-0005Enterprise resource planning (ERP) systems, such as that sold by SAP™, allow many different facets of a business to be managed and integrated together with a comprehensive computing solution. Thus, ERP systems allow information to be processed and shared by and among different parts of the business, including product planning, parts purchasing, maintaining inventories, interacting with suppliers, providing customer service, tracking orders, accounting, finance, etc.

p-0006As businesses become more complex and competitive, the ability to provide “on-demand” information, i.e., a current snapshot of a business metric, remains an important challenge. One area where this challenge exists involves providing a daily gross profit analysis from an ERP system. In order to determine gross profit, revenue and cost data must be extracted for the ERP system. However, for any given accounting period, a significant portion of the revenue and cost must be “accrued.” Accrued revenue and cost is that portion of the total revenue and cost that cannot be recognized from an accounting perspective as “real revenue” or “real cost” because, e.g., the customer has not yet been billed.

p-0007Reasons for accruing revenue and cost generally fall into, but are not limited to, three categories: (1) Partial Deliveries: ordered items that have been partially delivered but remain unbilled; (2) Shipped But Unbilled Activities (SBU): ordered items that have been shipped, but not yet billed; and (3) Billed Not Accounted Activities: ordered items that have been billed to the client, but not yet posted to accounting due to some application error.

p-0008Standard accounting practices require accrued revenue and cost to be posted on the last day of the month and reversed at the first day of the following month when the new period is opened. This methodology allows the real revenue to be posted when the customer is billed. Unfortunately, this existing methodology does not allow a daily gross profit analysis to be generated. Accordingly, a need exists for a system and method that will allow on demand accrual calculations.

SUMMARY OF THE INVENTION

p-0009The present invention addresses the above-mentioned problems, as well as others, by providing an accrual system and method in which accruals are generated on a daily basis for those activity that are not already accrued, and which are reversed only when the customer has been billed and the “real revenue” can be posted, or when an item remains in accrual status for more than 30 days. Thus, while standard accounting methodologies perform a mass accrual/reversal at the end/beginning of each month, the daily net accrual process described herein accounts daily for activities that have not already been accrued, and reverses daily only those items previously accrued, which are eligible for reversal.

p-0010In a first aspect, the invention provides an on demand net accrual system for tracking accrued revenue and costs, comprising: an accrual system that causes each inputted accrual event to be posted at the same time that the accrual event was received; and a reversal system that, on demand, checks a set of reversal rules and reverses any accrual events that triggered a reversal rule.

p-0011In a second aspect, the invention provides a method for tracking accrued revenue and costs, comprising: receiving accrual events; posting each received accrual event at the same time that the accrual event was received; checking a set of reversal rules on demand; and reversing any accrual events that triggered a reversal rule.

p-0012In a third aspect, the invention provides a program product stored on a recordable medium for tracking accrued revenue and costs, comprising: means for receiving accrual events; means for posting each received accrual event at the same time that the accrual event was received; means for checking a set of reversal rules on demand; and means for reversing any accrual events that triggered a reversal rule.

BRIEF DESCRIPTION OF THE DRAWINGS

p-0013These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings in which:

p-0014<figref idrefs="DRAWINGS">FIG. 1</figref> depicts an on demand net accrual system in accordance with the present invention.

p-0015<figref idrefs="DRAWINGS">FIG. 2</figref> depicts an exemplary business scenario showing the operation of the present invention relative to the prior art.

p-0016<figref idrefs="DRAWINGS">FIG. 3</figref> depicts a flow chart depicting operation of the accrual process in accordance with the present invention.

p-0017<figref idrefs="DRAWINGS">FIG. 4</figref> depicts a flow chart depicting operation of the reversal process in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

p-0018Referring now to the drawings, <figref idrefs="DRAWINGS">FIG. 1</figref> depicts an on demand net accrual system <b>10</b> that analyzes events <b>22</b> obtained, e.g., from a supply chain <b>24</b>. System <b>10</b> includes an accrual system <b>12</b> capable of posting accruals at the same time they are received based on a set of accrual rules <b>13</b>, and a reversal system <b>14</b> capable of performing reversals at any time (i.e., “on demand”) based on a set of reversal rules <b>15</b>. In the exemplary embodiments described herein, accrual events are posted via a batch process on the same day they are received and reversal system <b>14</b> is run daily to check for and perform reversals. However, it should be noted that accruals could be posted immediately, or within some predefined window of time after they are received. Similarly, reversals could take place at any time interval (e.g., daily, weekly, as desired, etc.).

p-0019As noted above, in prior art accounting systems, accrual and reversal events were posted on the last day of the month and first day of the following month, respectively. However, in reality, accrual and reversal events occur on a regular basis. Accordingly, system <b>10</b> provides a system for tracking accrual and reversal events on a daily basis, thereby allowing executive information (EIS) system <b>20</b> to provide a daily gross profit analysis <b>26</b>. Daily gross profit analysis <b>26</b> may be defined as the breakdown of Revenue less Cost of Goods Sold for the units shipped that day. Typical profitability analysis breakdowns include: product family, sales geographical area, manufacturing, geographical area, etc.

p-0020Accrual system <b>12</b> utilizes accrual rules <b>13</b> to identify accrual scenarios from the inputted events <b>22</b>. Accrual events include, but are not limited to, e.g., (1) Partial Deliveries: ordered items that have been partially delivered but remain unbilled; (2) Shipped But Unbilled Activities (SBU): ordered items that have been shipped, but not yet billed; and (3) Billed Not Accounted (BNA) Activities: ordered items that have been billed to the client, but not yet posted to accounting due to some application error. When an accrual event occurs, accrual system <b>12</b> checks to see if the event has been previously accrued. If it has not been previously accrued, then accrual system <b>12</b> posts the accrual on that day. Accrual rules <b>13</b> may be modified as needed to define other possible accrual scenarios, e.g., concessions, service packs, try and buy, etc.

p-0021The accrual system <b>12</b> may generate accounting documents (e.g., Partial Delivery accrual, Shipped But Unbilled accrual, or Billed Not Accounted accrual) that post revenue, unbilled A/R, cost (where applicable) and field inventory (where applicable, field inventory typically represents a cost clearing account). To implement the concept of daily net accrual, accrual tracking table <b>16</b> may be implemented and be updated from accrual system <b>12</b> with relevant information of the accrual documents that has been created. Accrual tracking table may be implemented as any type of storage capable of holding data, e.g., a physical database, a data object, a data structure, RAM, etc.

p-0022The accrual tracking table <b>16</b> can store the following data for documents accrued and still not reversed (K for key fields): <ul><li id="ul0001-0001" num="0000"><ul><li id="ul0002-0001" num="0022">Client ID (K)</li><li id="ul0002-0002" num="0023">Sales organization (K)</li><li id="ul0002-0003" num="0024">Document number (K): used to store the delivery document number for SBU and partial deliveries accrual cases or the billing document number for billed not accounted accrual cases</li><li id="ul0002-0004" num="0025">Document item (K): used to store the delivery item number for SBU and partial deliveries accrual cases</li><li id="ul0002-0005" num="0026">Accounting document number (K): accrual accounting document number</li><li id="ul0002-0006" num="0027">Document category: used to identify the type of document, billing document or delivery document, which is stored in the “document number” field</li><li id="ul0002-0007" num="0028">Partially delivered indicator: used to distinguish partially deliveries accruals from SBU</li><li id="ul0002-0008" num="0029">Posting date: posting date of the accrual accounting document (shipping date for partial delivery and SBU, billing date for BNA)</li><li id="ul0002-0009" num="0030">Reference Quantity: picking quantity for partial delivery, or shipped quantity for SBU at the time of accrual</li><li id="ul0002-0010" num="0031">Base Unit: Unit of measure of the quantity field</li><li id="ul0002-0011" num="0032">Cost amount: cost amount for partial delivery, SBU and BNA at the time of accrual</li><li id="ul0002-0012" num="0033">Cost currency: currency key of cost amount</li></ul></li></ul>

p-0023Before creating an accounting document, the accrual system <b>12</b> will check the accrual tracking table <b>16</b>. For partial delivery and SBU events, accrual tracking table <b>16</b> will be used to prevent creating accrual accounting documents for the same combination of item and quantity. For a BNA event, accrual tracking table <b>16</b> will be used to prevent creating an accrual accounting document for the same billing document number.

p-0024An accrual history table <b>18</b> may be utilized to contain the reversed accrual records from the accrual tracking table <b>16</b> (all fields) with the reversed accounting document and its posting date. Like the accrual tracking table <b>16</b>, the accrual history table <b>18</b> may be implemented as any type of storage capable of holding data, e.g., a physical database, a data object, a data structure, RAM, etc. In the case of partial deliveries and shipped but unbilled events, the use of this table in the accrual system <b>12</b> will prevent an accrual for the quantity of the delivery item that has already been accrued based on the 30 days rule.

p-0025The accrual history table <b>18</b> can also be used for reporting purposes, technical research and auditing of accrual situations. The accrual history can also be purged on demand. The fields defined in the accrual history table <b>18</b> are the same of the accrual tracking table <b>16</b>, with the addition of Reversal Document number, Posting date and repost indicator. <ul><li id="ul0003-0001" num="0000"><ul><li id="ul0004-0001" num="0037">Client ID (K)</li><li id="ul0004-0002" num="0038">Sales organization (K)</li><li id="ul0004-0003" num="0039">Document number (K): used to store the delivery document number for SBU and partial deliveries accrual cases or the billing document number for billed not accounted accrual cases</li><li id="ul0004-0004" num="0040">Document item (K): used to store the delivery item number for SBU and partial deliveries accrual cases</li><li id="ul0004-0005" num="0041">Accounting document number (K): accrual accounting document number</li><li id="ul0004-0006" num="0042">Document category: used to identify the type of document, billing document or delivery document, which is stored in the “document number” field</li><li id="ul0004-0007" num="0043">Partially delivered indicator: used to distinguish partially deliveries accruals from SBU</li><li id="ul0004-0008" num="0044">Accrual accounting document number</li><li id="ul0004-0009" num="0045">Posting date: posting date of the accrual accounting document (shipping date for partial delivery and SBU, billing date for BNA)</li><li id="ul0004-0010" num="0046">Reference Quantity: picking quantity for partial delivery, shipped quantity for SBU, billed quantity for SBU at the time of accrual</li><li id="ul0004-0011" num="0047">Base Unit: Unit of measure of the quantity field</li><li id="ul0004-0012" num="0048">Cost amount: cost amount for partial delivery, SBU and BNA at the time of accrual</li><li id="ul0004-0013" num="0049">Cost currency: currency key of cost amount</li><li id="ul0004-0014" num="0050">Reversal accounting document</li><li id="ul0004-0015" num="0051">Reversal posting date</li><li id="ul0004-0016" num="0052">Repost indicator: used to indicate whether the delivery item is re-accrued for partial delivery and SBU</li><li id="ul0004-0017" num="0053">30 days rule reversal indicator: used to indicate whether the accrual for delivery item has been reversed based on 30 day rule. It is used by accrual posting program to prevent re-accrual of the quantity in the delivery item.</li></ul></li></ul>

p-0026Reversal system <b>14</b> utilizes reversal rules <b>15</b> to identify reversal scenarios from the inputted events <b>22</b>. Reversal scenarios include the following:

p-0027(1) 30 day rule—Reverse if the accrual has lapsed at least 30 days (accrual posting date+30 days) or the accrual still exists at end of the following posting period.

p-0028(2) Partial Delivery—Reverse if the delivery has been completely invoiced or deleted; or if the delivery item has been invoiced or deleted.

p-0029(3) Shipped but Unbilled (SBU)—Reverse if the delivery has been completely invoiced or deleted; or if the delivery item has been invoiced or deleted. Note that for SBUs, the Accrual Tracking Table is identified with a blank partially delivered indicator.

p-0030(4) Billed not Accounted (BNA)—Reverse if an accounting document has been generated or the billing document has been canceled.

p-0031In addition, when an accrual document has been reversed, the corresponding entry in the accrual tracking table <b>16</b> that was inserted from the accrual system <b>12</b> at the time of accrual, will be deleted. The entries deleted from the accrual tracking table <b>16</b> will be saved in the accrual history table <b>18</b>, together with the reversal accounting document number and the posting date.

p-0032The reversal system <b>14</b> can be run daily after a batch billing run (i.e., a process or program that bills all the transactions which are due to be billed at a given point in time) and before the daily accrual system <b>12</b>. This will enable the reversal of accrual accounting documents containing items that have been billed; items that have been accrued for a certain reason, and have been changed to the BNA status; or items that have been accrued together within the same accrual accounting document, and one of the items has been billed, and the other items needs to be re-accrued or reposted.

p-0033Referring now to <figref idrefs="DRAWINGS">FIG. 2</figref>, a table depicting a scenario of business events is shown that describes the operational differences between the on demand net accrual system <b>10</b> and the prior art methodology. The first column lists the inputted event <b>22</b>, the second column lists the action or results using traditional accrual approach, and the third column lists the action or results using the on demand net accrual system described above.

p-0034On May 15 a customer orders a quantity of 100 items, which does not result in any action taken under either approach. On May 22, a partial delivery of 20 items of the ordered items is made, which does not result in any action under traditional accrual, but under the present approach results in recognizing accrue revenue and cost for the 20 shipped items. Next, on May 28, an additional 30 of the ordered items are shipped with the same effect as the May 22 shipment.

p-0035On May 30, the last day of the month, accrue revenue and cost is recognized for the 50 shipped items under the traditional approach, but nothing is recognized under the current approach. Similarly, on June 1, accrue revenue and cost for the 50 shipped items are reversed under the traditional approach, but nothing is reversed under the current approach.

p-0036On June 2, a billing block is added to the order. No action is taken under either approach. On June 5, the final 50 items are shipped, which does not result in any action under traditional accrual, but under system <b>10</b> results in recognizing accrue revenue and cost for the 50 shipped items.

p-0037On June 15, the billing block is removed and the customer is billed. Under the traditional approach, only the real revenue and cost is recognized. However, under the new approach, the accrue revenue and cost for all 100 items is reversed, and the real cost and revenue is recognized through billing. On the last day of the month, June 30, neither approach takes any action.

p-0038Referring now to <figref idrefs="DRAWINGS">FIG. 3</figref>, a flow chart depicting operation of accrual system <b>12</b> is shown. In step S<b>1</b>, an accrual event is received. At step S<b>2</b>, the accrual tracking table <b>16</b> is checked to see if the event was previously posted. At step S<b>3</b>, accrual system <b>12</b> checks the accrual history table <b>18</b> to see if either a partial delivery or SBU event was previously accrued based on the 30 days rule. If the event was previously accrued, then the event is not posted, see step S<b>4</b>. Otherwise, the event is posted on the same day (e.g., via a batch operation) at step S<b>5</b> and the accrual tracking table <b>16</b> is updated with the event/accrual information.

p-0039Referring now to <figref idrefs="DRAWINGS">FIG. 4</figref>, a flow chart depicting operation of reversal system <b>14</b> is shown. Each day, reversal system <b>14</b> is run, e.g., via a batch operation, at step S<b>11</b>. Reversal system <b>14</b> checks to see if any of the reversal rules <b>15</b> (described above) have been triggered at step S<b>12</b>. If no rules <b>15</b> were triggered, the process ends. Otherwise, at step S<b>13</b>, all the events that triggered a reversal rule are reversed. Next, at steps S<b>14</b> and S<b>15</b>, the reversed events are deleted from the accrual tracking table <b>16</b>, and are added to the accrual history table <b>18</b>.

p-0040It is understood that the systems, functions, mechanisms, methods, engines and modules described herein can be implemented in hardware, software, or a combination of hardware and software. They may be implemented by any type of computer system or other apparatus adapted for carrying out the methods described herein. A typical combination of hardware and software could be a general-purpose computer system with a computer program that, when loaded and executed, controls the computer system such that it carries out the methods described herein. Alternatively, a specific use computer, containing specialized hardware for carrying out one or more of the functional tasks of the invention could be utilized. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods and functions described herein, and which—when loaded in a computer system—is able to carry out these methods and functions. Computer program, software program, program, program product, or software, in the present context mean any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or (b) reproduction in a different material form.

p-0041The foregoing description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art are intended to be included within the scope of this invention as defined by the accompanying claims.