WO1997024679A1 - Systeme de rendu de documents de facturation, et procede associe - Google Patents

Systeme de rendu de documents de facturation, et procede associe Download PDF

Info

Publication number
WO1997024679A1
WO1997024679A1 PCT/US1996/020102 US9620102W WO9724679A1 WO 1997024679 A1 WO1997024679 A1 WO 1997024679A1 US 9620102 W US9620102 W US 9620102W WO 9724679 A1 WO9724679 A1 WO 9724679A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer
billing
data
statement
billing statement
Prior art date
Application number
PCT/US1996/020102
Other languages
English (en)
Inventor
Alan W. Switzer
James R. Logan
Original Assignee
Tele-Communications, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tele-Communications, Inc. filed Critical Tele-Communications, Inc.
Priority to AU12933/97A priority Critical patent/AU1293397A/en
Publication of WO1997024679A1 publication Critical patent/WO1997024679A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing

Definitions

  • This invention relates in general to the field of data communication and more particularly to a system and method for the production of billing statements.
  • Service and product providers must bill their customers. To do so, these service and product providers, such as cable television operators, local telephone service providers, long distance telephone providers, and credit card companies, must produce periodic billing statements for each of their customers. In the case of a cable television operator, each customer receives a monthly billing statement.
  • a single cable television company may operate numerous cable television franchises in several geographic regions, covering millions of customers. Each of these customers receives a billing statement each month.
  • Billing statements are often printed and mailed by bill Tenderers, which a service provider, such as a cable television operator, will contract to produce its billing statements.
  • a service provider such as a cable television operator
  • the service provider often furnishes the bill renderer with the customer data to be printed on the billing statements.
  • a service provider may use more than one bill renderer to produce its billing statements.
  • Employing more than one bill renderer reduces the risks associated with using a single bill renderer for the entire production of btfling statements. If only a single bill renderer is used for the production of all of a service provider's billing statements, the timely delivery of the billing statements may be compromised if the selected bill renderer is unable to complete the production of the bills promptly because of mechanical failure, natural disaster, work stoppage, or some other reason.
  • Each bill renderer may require that the service provider format the customer data in a manner unique or proprietary to that bill renderer. Therefore, for each bill renderer, the service provider must be certain mat the data is provided to the bill renderer in the format required by the bill renderer. Separating customer data by bill renderer and then formatting the data according to each bill Tenderer's specifications is a time consuming and costly process for the service providers.
  • a billing statement rendering system and method in which the customer data to be printed or rendered onto a series of billing statements is provided to each of the bill Tenderers in a single format that can be interpreted by each of the service provider's bill Tenderers. It is an object of the present invention to provide a single, easily interpretable, bill renderer definition format that may be used by all of a service provider's bill Tenderers.
  • the customer data to be rendered onto a series of billing statements is formatted according to a bill renderer definition format.
  • the bill Tenderer definition format of the present invention defines the nested format of both global customer data and individual customer data for the billing statement production run.
  • the global customer data and individual customer data is formatted and provided to a bill renderer.
  • the bill renderer interprets the formatted data and prints a series of customer billing statements.
  • the formatted global customer data and individual customer data may be interpreted and then displayed on the computer terminal of a customer service representative of the service provider.
  • FIGURE 1 is a graphical representation of the architecture of a bill renderer and a service provider's customer management system indicating the data flow of the printing of a billing statement;
  • FIGURE 2 is a graphical representation of a customer billing statement printed according to the billing statement rendering system and method of the present invention.
  • FIGURE 3 is a flow chart of a method for providing customer billing data to a bill renderer according to the method of the present invention.
  • Service and product providers such as cable television providers, local telephone service providers, long distance telephone providers, and credit card companies, store customer data on one or more databases within a customer management system.
  • the customer management system manages the data comprising each customer account.
  • the customer management system updates the customer data so that an accurate current and historical record is maintained of each customer's account history.
  • FIGURE 1 is a graphical representation of a customer management system 10 of a service provider.
  • a customer management system may include one or more data servers 12 connected across one or more communications links 13 to one or more customer databases 14.
  • Databases 14 may be all located in one physical location or may be located in separate physical locations.
  • Each of data servers 12 is connected across one or more communications links 17 to a billing production processor 15, which processes and handles the customer data maintained in customer management system 10.
  • Billing production processor 15 of the present invention includes a billing data extraction processor 16 and a billing data format processor 18.
  • billing data extraction processor 16 extracts from customer databases 14 the customer data that is to be printed on the billing statements to be sent to the billed customers.
  • the output of billing data extraction processor 16 is provided to billing statement format processor 18.
  • the output of billing data extraction processor 18 is the unformatted customer data for each customer to be billed.
  • the unformatted customer data provided at the output of billing data extraction processor 16 includes account status information, customer address information, account balance information, legal notices, promotional notices, and other data for each of the customers to be billed.
  • Billing statement format processor 18 receives the unformatted customer data from billing data extraction processor 16 and converts this data according to a bill render definition format.
  • the output of billing statement format processor 18 is the formatted customer data for the set of customers to be billed.
  • the output of billing statement format processor 18 may be saved to one or more formatted customer billings file 20, which may on any suitable memorystorage medium, including tapes, disks, optical storage medium, or workstation or data server hard drives.
  • Formatted customer billing file 20 contains the formatted customer data for each of the customers to be billed.
  • Formatted customer billing file 20 is provided to one of any number of available bill Tenderers 22.
  • a bill renderer interpreter processor 24 (1) interprets the syntax of formatted customer billing file 20, which is formatted according to the bill renderer definition format, (2) extracts the customer data from formatted customer billing file 20, and (3) sends the interpreted and extracted data to a printer 26, which prints a series of customers billing statements 28.
  • the output of billing data format processor 18 is formatted according to the bill renderer definition format of the present invention.
  • the bill renderer definition format provides a simple format for the service provider's customer data.
  • the bill renderer definition format of the present invention is defined according to a set of well defined grammatical rules that can be easily interpreted by the bill renderer interpreter module 18 of each of the service provider's bill Tenderers 22.
  • the bill renderer definition format of the present invention includes a plurality of elements. Each element has a definition. An element is defined by a series of one or more nested elements, each of which may in turn have one or more elements nested within its definition, and so on. Formatted customer billing file 20 contains a plurality of elements, each arranged one after another on successive lines of customer billing file 20.
  • the elements comprising the bill renderer definition format of the present invention comprise terminal elements, nonterminal elements, and literal elements. Terminal elements, which serve as flags or markers, are indicated in the text below in bold face and are reproduced as shown in formatted customer billing file 20. Nonterminal elements are shown below in angle brackets. Terminal elements, other nonterminal elements, or literal elements may comprise the definition of a nonterminal element.
  • a literal element may be an integer or on alphanumeric string. As shown below, literal elements are preceded by a dash. A terminal element does not have a nested definition. In contrast, a nonterminal element has a nested definition.
  • nonterminal element within the definition of a element, the allowable repetition of zero, one, or multiple nonterminal elements is indicated by braces surrounding the nonterminal element.
  • bill renderer definition format of the present invention allows for the omission of a nontem ⁇ nal element that is bracketed by braces.
  • nonterminal element may include a list of nonterminal elements or terminal elements separated by a vertical bar, indicating that only one symbol from the list may be selected to complete the definition of the element.
  • the first element in formatted customer billing file 20 is "Render
  • nonterminal element "Render File” includes nonte ⁇ ninal element “Render File Header,” followed on the next line by nonterminal element “Statement,” followed on the next line by nonterminal element “Render File Trailer”.
  • the braces surrounding nonterminal element “Statement” indicate that zero, one, or multiple instances of nonterminal element “Statement” may appear on successive lines of customer billing file 20.
  • Nonterminal element "Render File Header,” which is nested as a nonterminal element in the definition of nonterminal element “Render File,” is defined as:
  • Render File Header serves as a flag to bill renderer interpreter processor 24 that a definition of the file header for each of customer billing statements 28 to be printed follows next in formatted customer billing file 20.
  • File Name is a literal element representing the file name of formatted customer billing file 20.
  • Statement Count is an integer value literal element representing the number of customer statements to be printed as part of the current billing statement production run from the data contained in formatted customer billing file 20.
  • the designation "1" indicates to bill renderer interpreter processor 24 that formatted customer billing file 20 is formatted according to release 1 of the bill renderer definition format.
  • the terminal element "GO” indicates to bill renderer interpreter processor 24 that the data from formatted customer billing file 20 is to be rendered onto a set of billing statements to be eventually sent to the service providers customers.
  • the terminal element "TEST” indicates that a test run of billing statements is to be printed but not sent to customers, and the terminal element “HOLD” indicates that bill renderer interpreter processor 24 is to interpret the data from customer billing file 20 but should not send the inte ⁇ reted data to printer 26.
  • the vertical bars separating terminal elements "GO”, “TEST”, and "HOLD” indicate that only one of the three available terminal elements may be selected to complete the definition of element "Render File Action.”
  • Terminal element "Stock Identifier” is an alphanumeric string representing the paper stock to be used for the billing statement.
  • Several paper stocks may be available, each having unique preprinted portions, such as company logos, watermarks, or preprinted boxes intended to surround account numbers or account balances.
  • the bill renderer definition format of the present invention is flexible such that it can define customer billing information to be printed on any predefined paper stock. The stock identifiers and the matching paper stocks are provided to the bill renderer in advance of the billing statement production run.
  • An insert is a separate legal, public service, or marketing notice placed in the same envelope as one or more billing statements.
  • the terminal element "Insert Definition” signals to bill renderer interpreter processor 24 that a definition of the inserts that may be used in the current billing statement production run follows.
  • the literal element “Number of Insert Bins” represents the number of available inserts for the current billing statement production run.
  • the next element in the definition of nonterminal element “Insert Definition” is a symbol comprising two nonterminal elements, "Insert Identifier” and "Insert Priority,” collectively bracketed by braces:
  • brackets indicate that the combination of the bracketed symbols may appear zero, one, or multiple times, with each new symbol appearing on a new line.
  • the nonterminal element "Insert Identifier" is further defined as:
  • Insert Number is a literal element representing an identifying number for an insert that has been previously been provided to the bill renderer.
  • Nonterminal element "Insert Priority” is further defined as:
  • the terminal elements "REQUIRED” or “OPTIONAL” indicate, respectively, whether the referenced insert must be included in the same envelope as the referenced billing statement or may be omitted depending on the mailing weight of the envelope or the availability of the insert.
  • a message is a text message printed on the billing statement and may contain legal or marketing information.
  • a message definition is useful if the same message is to be reproduced on a number of customer billing statements.
  • Nonterminal element "Message Definition” is bracketed by braces in the definition of element “Render File Header,” indicating that the element may appear in the definition of element "Message Definition” in formatted customer billing file 20 zero, one, or multiple times, with each new entry appearing on a new line.
  • Terminal element "Message Definition” signals to bill renderer interpreter processor 24 that the identification of a message follows.
  • Literal element "Message Identifier Number” is an alphanumeric identifier for the message.
  • Nonterminal element "Text” is defined as:
  • the literal element "Static Text” is an alphanumeric text string to be printed on the billing statement.
  • an example of a "Static Text” literal element may be a marketing or informational notice, such as:
  • Nonterminal element “Font Definition” is bracketed by braces in the definition of element "Render File Header,” indicating that the nonterminal element "Font Definition may appear in formatted customer billing file 20 zero, one, or multiple times, with each new entry appearing on a new line.
  • Nonterminal element "Font Definition is defined as:
  • Terminal element "Font Definition” signals to bill renderer inte ⁇ reter processor 24 that a font definition follows.
  • Nonterminal element "Font” is defined as:
  • Nonterminal element “External Picture Definition” is bracketed by braces in the definition of element “Render File Header,” indicating that the nonterminal element "External Picture Definition” may appear in formatted customer billing file 20 zero, one, or multiple times, with each new entry appearing on a new line.
  • An external picture is a logo or other picture that may be printed by bill renderer 22 on the referenced billing statements.
  • Nonterminal element "External Picture Definition” is defined as:
  • Terminal element "External Picture Definition” signals to bill renderer inte ⁇ reter processor 24 that the definition of an external picture follows.
  • Literal element "Picture Identifier” is an alphanumeric value representing an external picture.
  • nonterminal element "Render File Header” appears at the beginning of each customer billing file 20. Following nonterminal element "Render File Header” is one or more instances of nonterminal element "Statement.” Each nonterminal element "Statement” corresponds to a single customer billing statement that is to be rendered by bill renderer 22. In contrast, the information provided in nonterminal element "Render File Header" is global information pertaining to each of the customer billing statements to be rendered in the current billing production run.
  • nonterminal element "Render File Header” describes (1) the name of customer billing file 20; (2) the date of the production run; (3) the number of statements to be rendered; (4) the release of the bill renderer definition format; (5) the paper stock; (6) the available inserts for the current production run; (7) the available messages for the current production run; (8) the available fonts for the current production run; and (9) the available external pictures for the current production run.
  • Each nonterminal element "Statement” defines the printed matter that is to appear on a single customer's statement. Nonterminal element "Statement” is defined as:
  • Nonterminal element “Statement Header” is defined as:
  • Terminal element "Statement Header” signals to bill renderer processor 24 that a definition of a statement header follows.
  • Literal element "Statement Number” represents an integer representing the number of the billing statement in the current billing statement production run.
  • the first statement to be rendered has a literal element “Statement Number” of 1 ; the second statement to be rendered has a literal element “Statement Number” of 2, and so on.
  • the literal element "Account Number” represents the customer account number of the current statement.
  • the next symbol in nonterminal element "Statement Header” is nonterminal element "Insert Identifier," described above.
  • Nonterminal element "Insert Identifier” is bracketed by braces, indicating that the element may appear in the definition of nonterminal element "Statement Header” in formatted customer billing file 20 zero, one, or multiple times, with each new entry appearing on the same line, separated by spaces.
  • the bill renderer definition format of the present invention contains an exception to the usual formatting conventions with respect to nonterminal element "Insert Identifier.” If no inserts are scheduled to be placed in a customer's bill, nonterminal element "Insert Identifier" is represented by a blank line in customer billing file 20.
  • the terminal elements "SEND,” “CORPORATE,” AND “CABLESYSTEM” indicate, respectively, whether bill renderer should mail the completed bills to the send address on the bill, transport the completed bills to the cable service provider's co ⁇ orate facility, or transport the completed bills to the cable service provider's local franchise facility.
  • nonterminal elements comprising the definition of nonterminal element "Element” are separated by vertical bars, indicating that only one of the nonterminal elements may be selected. Recall, however, that nonte ⁇ riinal element “Element” is bracketed by braces in the definition of nonterminal element “Statement,” thereby allowing repetition of the nonterminal element "Element” in customer billing file 20.
  • the first symbol in the definition of nonterminal element “Element” is nonterminal element "Due Date,” which is defined as:
  • the terminal element "Due Date” signals to bill renderer inte ⁇ reter processor 24 that a definition follows for the due date of the current billing statement.
  • the nonterminal element "Static Text” is defined as:
  • Nonteirninal elements "Text” and “Font” are described above.
  • Nonterminal elements "ori x" and “ori y” are defined as:
  • the origin of the billing statement is defined to be the upper lefthand corner of the billing statement.
  • the coordinates of an alphanumeric string of static text are defined to be the lowermost lefthand portion of the alphanumeric string.
  • the literal elements "X Coordinate of Origin” and "Y Coordinate of Origin” represent point sizes, expressed as integers, that indicate the location of the static text string relative to the origin of the billing statement. There are 72.27 points per inch.
  • Terminal element "External Picture” signals to bill renderer inte ⁇ reter processor 24 that the location and identifier for an external picture follows.
  • the next element in the definition of nonterminal element “Element” is nonterminal element "Line,” defined as:
  • Terminal element "Line” signals to bill renderer inte ⁇ reter processor 24 that the location and definition of a line follows.
  • a line may extend in the vertical, horizontal, or diagonal direction on the billing statement.
  • Nonterminal elements "ptl x,” “ptl y,” “pt2 x,” and “pt2 y” are defined as:
  • Literal elements "X Coordinate of First Point” and “ Y Coordinate of First Point” define the x and y coordinates with respect to the origin of the billing statement of one termination point of the line.
  • Literal elements "X Coordinate of Second Point” and “Y Coordinate of Second Point” define the x and y coordinates with respect to the origin of the billing statement of the other termination point of the line.
  • Terminal element "LockBoxScanLine” signals to bill renderer inte ⁇ reter processor 24 that the location and definition of a Lock Box Scan Line follows.
  • a lock box scan line is the computer readable set of alphanumeric characters that is printed on the bill to aid financial clearinghouses in the processing of remitted bills.
  • the next element in the definition of nonterminal element "Element” is nonterminal element "Message,” defined as:
  • Terminal element "Message” signals to bill renderer inte ⁇ reter processor 24 that the definition and location of a message follows.
  • a message is a text message to be printed on the bill.
  • Literal element "Message Identifier Number” represents an alphanumeric identifier for a message that has previously been identified in the definition of nonterminal element "Render File Header.”
  • Nonterminal elements "ori x” and “ori y” define the location of the message with respect to the origin of the billing statement.
  • Nonterminal element "Font" specifies the font of the message.
  • nonterminal element “Element” is nonterminal element “Rectangle,” defined as:
  • Terminal element "Rectangle" signals to bill renderer inte ⁇ reter processor 24 that the definition and location of a Rectangle fol lows .
  • Nonterminal elements "ori x" and “ori y” specify the location of the upper lefthand corner of the rectangle relative to the origin of the billing statement.
  • Nonterminal element width and height are defined as:
  • Nonterminal elements width and height represent integer values that specify, respectively the width and height of the rectangle whose upper lefthand corner is located at the location specified by nonterminal elements "ori x" and “ori y.”
  • Nonterminal element “Rounded Rectangle” also appears in the definition of nonterminal element “Element”.
  • Nonterminal element "Rounded Rectangle” is defined as
  • nonterminal element Rounded Rectangle
  • Rectangle The definition of nonterminal element "Rounded Rectangle” is similar to the definition of “Rectangle” except for the provision of rounded corners on the rectangle produced by nonterminal element "Rounded Rectangle.”
  • nonterminal element Element
  • nonterminal elements Remit Address and "Send Address,” defined respectively as:
  • Nonterminal element "Number of Elements” specifies the number of address elements that follow in the definition of nonterminal element “Remit Address” or “Send Address.”
  • Nonterminal element “Address Element” is bracketed by braces, indicating that nonterminal element “Address Element” may appear zero, one, or multiple times in customer billing file 20 as part of the definition of nonterminal element “Remit Address” or “Send Address.”
  • Nonterminal element "Address Element” is defined as:
  • An address bar code is a computer readable format placed below a mailing address to aid the automated postal processing of the addressed billing statement.
  • Each of the nonterminal elements comprising the definition of nonterminal element "Address Element” comprises static text strings that can be printed at a defined location of the billing statement relative to the origin of the billing statement. This feature allows the address element to be positioned so that the remit address and the send address can be seen through a window in the envelope housing the billing statement.
  • nonterminal element “Element” The final element in the definition of nonterminal element “Element” is nonterminal element “Static Text,” which is defined above. Finally, formatted customer billing file 20 concludes with the nonterminal element "Render File Trailer,” which is defined as:
  • Bill inte ⁇ reter processor 24 recognizes literal element "RenderFileTrailer" as the final element of customer billing file 20.
  • FIGURE 2 is an example of a customer billing statement 30 rendered from customer data provided in the bill renderer definition format of the present invention.
  • Billing statement 30 was rendered from a customer billing file containing the following:
  • Customer billing statement 30 contains a number of preprinted portions, including service provider logos 32, preprinted boxes 34, and preprinted instructions 36.
  • the portion of the above example of customer billing file 20 beginning with “Render File Header” and concluding with “TCI001 " is the definition of nonterminal element "Render File Header.”
  • This portion of the above example of customer billing file 20 provides a set of global data that specifies (1) the file name of customer billing file 20; (2) the date; (3) the number of customer billing statements to follow; (4) the release version of the bill renderer definition format; (5) the paper stock identifier; (6) a flag indicating that actual customer statements are to be printed; (7) an insert definition; (8) several font definitions; and (9) an external picture definition.
  • a blank line is between the account number, "0001234560001,” and the statement action flag, "CORPORATE.”
  • a blank line is inserted in place of nonterminal statement "Insert Identifier" when no inserts are to be included in the same envelope as the customer billing statement. Note that this practice is an exception to the usual rule of the bill definition format of the present invention that requires that customer billing file 20 continue with the next element on the next line without the insertion of a blank line to denote the omission of a bracketed nonterminal element.
  • nonterminal element Render File Header
  • the available insert "TCI 100” is marked as "REQUIRED.” Therefore, had insert "TCI 100" been included in the defimtion of nonterminal element "Statement Header,” the inclusion of insert "TCI 100” would have been mandatory.
  • a plurality of the nonterminal elements "Element” comprise the remainder of the definition of nonte ⁇ ninal element "Statement.”
  • the portion of the above example of customer billing file 20 beginning with the elements "StaticText” and "3737 W 10TH ST” and concluding with the second instance thereafter of "fonts.BRbold" defines the placement of the service provider's business address 38.
  • the portion of the above example of customer billing file 20 beginning with the elements “StaticText” and “ 12/01/95” and concluding with the second instance thereafter of "fonts.BRbold” defines the placement of the due date 40 and amount due 42.
  • the portion of the above example of customer billing file 20 beginning with the elements "StaticText” and “THANK - YOU” and concluding with the fourth instance thereafter of "fonts.BRbold” defines the placement of a notice 44 thanking the customer for a pattern of prompt payment.
  • the portion of the above example of customer billing file 20 beginning with the element "RemitAddress” and concluding with the next instance thereafter of "fonts.Font4" defines the service provider's remit address 48. Included within the defmition of nonterminal element "Remit Address” is the service provider's zip code and an identification of the number of elements in the definition of nonterminal element "Remit Address.” These elements include an identification of external picture 50 and address bar code 52.
  • the portion of the above example of customer billing file 20 beginning with the elements "StaticText" and JOHN A SMITH” and concluding with the next instance thereafter of "fonts.BRbold" defines customer name 54.
  • the customer data provided to CSR terminal 64 is first inte ⁇ reted by a bill renderer inte ⁇ reter processor 62 before being outputted to CSR terminal 64.
  • the customer data provided to bill renderer inte ⁇ reter processor 62 may come directly from bill data formatting processor 18 or customer billing file 20.
  • bill renderer definition format of the present invention has been described in detail, the bill renderer definition format of the present invention is not limited to the syntax identified above, but is instead limited only by the claims to follow. Various changes, substitutions, and alterations can be made without departing from the spirit and scope of the invention as defined by the appended claims.

Abstract

L'invention concerne un procédé de rendu de documents de facturation. Les données client sont formatées selon un format de définition de rendu de facturation, qui comprend les données client globales et les données client individuelles formatées selon un fichier de facturation client (20). Le fichier (20) est transmis à un système de rendu de facture (22), qui interprète et rend une série de documents de facturation (28).
PCT/US1996/020102 1995-12-27 1996-12-24 Systeme de rendu de documents de facturation, et procede associe WO1997024679A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU12933/97A AU1293397A (en) 1995-12-27 1996-12-24 Billing statement rendering system and method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US57937195A 1995-12-27 1995-12-27
US08/579,371 1995-12-27

Publications (1)

Publication Number Publication Date
WO1997024679A1 true WO1997024679A1 (fr) 1997-07-10

Family

ID=24316628

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1996/020102 WO1997024679A1 (fr) 1995-12-27 1996-12-24 Systeme de rendu de documents de facturation, et procede associe

Country Status (2)

Country Link
AU (1) AU1293397A (fr)
WO (1) WO1997024679A1 (fr)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4714996A (en) * 1985-11-26 1987-12-22 International Business Machines Corporation Impact calculation for version management in a distributed information service
US4853843A (en) * 1987-12-18 1989-08-01 Tektronix, Inc. System for merging virtual partitions of a distributed database
US4951196A (en) * 1988-05-04 1990-08-21 Supply Tech, Inc. Method and apparatus for electronic data interchange
US5263167A (en) * 1991-11-22 1993-11-16 International Business Machines Corporation User interface for a relational database using a task object for defining search queries in response to a profile object which describes user proficiency
US5317729A (en) * 1990-10-24 1994-05-31 International Business Machines Corporation Method for the storage of multi-versioned data with retrieval based on searched query
US5450537A (en) * 1989-12-08 1995-09-12 Hitachi, Ltd. Method and apparatus for completing a partially completed document in accordance with a blank form from data automatically retrieved from a database
US5450539A (en) * 1992-07-09 1995-09-12 Apple Computer, Inc. Apparatus and method of dynamically displaying a graphic button on a monitor
US5450538A (en) * 1991-11-08 1995-09-12 International Business Machines Corporation Graphical user interface control for expansion and re-sizing of data fields in forms

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4714996A (en) * 1985-11-26 1987-12-22 International Business Machines Corporation Impact calculation for version management in a distributed information service
US4853843A (en) * 1987-12-18 1989-08-01 Tektronix, Inc. System for merging virtual partitions of a distributed database
US4951196A (en) * 1988-05-04 1990-08-21 Supply Tech, Inc. Method and apparatus for electronic data interchange
US5450537A (en) * 1989-12-08 1995-09-12 Hitachi, Ltd. Method and apparatus for completing a partially completed document in accordance with a blank form from data automatically retrieved from a database
US5317729A (en) * 1990-10-24 1994-05-31 International Business Machines Corporation Method for the storage of multi-versioned data with retrieval based on searched query
US5450538A (en) * 1991-11-08 1995-09-12 International Business Machines Corporation Graphical user interface control for expansion and re-sizing of data fields in forms
US5263167A (en) * 1991-11-22 1993-11-16 International Business Machines Corporation User interface for a relational database using a task object for defining search queries in response to a profile object which describes user proficiency
US5450539A (en) * 1992-07-09 1995-09-12 Apple Computer, Inc. Apparatus and method of dynamically displaying a graphic button on a monitor

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
BELLSOUTH, CINCINNATI BELL: BILLING AGENTS FOR HIRE, Telco Business Report, 06 December 1993. *
GOLDMAN JOHN, "EXPEDYNE Strategic Billing Services Launched", PR NEWSWIRE, 16 June 1993. *
MISSISSIPPI BUSINESS JOURNAL, Vol. 15, No. 29, 19 July 1993, McCANN N.C., "BellSouth Subsidiary Offers Billing Services". *

Also Published As

Publication number Publication date
AU1293397A (en) 1997-07-28

Similar Documents

Publication Publication Date Title
KR100368587B1 (ko) 전표처리 시스템 및 전표파일링 시스템
US8156045B2 (en) Methods and systems for associating customized advertising materials with billing statements
US8374971B2 (en) System and method for management and delivery of content and rules
US20050065893A1 (en) System and Method for Commingled Remittance Payment Processing
WO2002001391A3 (fr) Systeme et procede de creation d'annonces publicitaires par ordinateur
CN108108448B (zh) 一种生成全国道路画像的方法及系统
US20020161710A1 (en) Document, document processing system and document generating system
US20050050442A1 (en) System and method of publication
US20040015455A1 (en) Postal or electronic mail addressing and processing method
US7003179B2 (en) Sheet-recognizing machine
CN111652699A (zh) 用于税票系统的数据传输方法
KR100439516B1 (ko) 2차원 바코드를 이용한 고지서 처리 시스템 및 방법
CN102982624A (zh) 一种pos机交易中心基于tlv格式数据的打印方法
WO1997024679A1 (fr) Systeme de rendu de documents de facturation, et procede associe
US6061694A (en) Message structure
US20070061224A1 (en) Method and system for ordering and performing printing services and postal services
EP1298571A1 (fr) Systeme de facturation pour l'utilisation d'un code bidimensionnel
Bancel-Charensol Impacts on information and communication technologies on service production systems
CN111210329A (zh) 会计凭证的生成方法、装置、存储介质和电子设备
WO2007042136A1 (fr) Systeme d'expedition de marchandises, procede d'expedition de marchandises, composantes d'expedition et emplacement de distribution des marchandises
US7509281B1 (en) System and method for statement presentation
JP6694991B2 (ja) 納付書処理システム及び納付書処理方法
WO2021229822A1 (fr) Système de détermination de données électroniques, dispositif de détermination de données électroniques, procédé de détermination de données électroniques et programme de détermination de données électroniques
JPH1139519A (ja) 後払料金情報収集装置および後払料金情報収集システムおよび後払料金情報収集をコンピュータに実行させるプログラムを記録した記録媒体
JPH078918A (ja) 委託輸送・配達事業の受付業務の自動化の方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE HU IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG UZ VN AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 97524376

Format of ref document f/p: F

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase