FR2730575A1 - Franking, accounting and invoicing of postal items and services - Google Patents

Abstract

The system follows a sequence of operations. Initially, a computer is authorised to communicate with the franking system, and a list of clients set up in the computer. The payment arrangements for each client are entered. The registers in the franking machine are validated against the computer entry, and corrected if in error, then the franking operation performed. Details of the franking are added to the totals, which are validated and recorded. Invoices are raised from this data at the payment intervals. For each item the tariff is determined, the item inserted in the machine and the franking printed on the item.

Description

 The evolution of franking machines has been constant since their appearance and their actual implementation in the 1920s.

Franking machines are essentially mass-produced devices intended to print a defined unit value for the delivery of packages and envelopes by government or private carriers. The term franking machine also includes other similar devices which produce an impression of a unit value, for example a machine for affixing fiscal stamps. Franking machines include internal accounting devices or registers, which account for a postage value stored inside the machine.

 In all systems that perform postage, such as a postage meter, special care must be taken to ensure that all postage applied is properly accounted for. This accounting is required by law and is typically accomplished through well known accounting registers maintained within the stamping application systems. The form of these registers can be that of increasing and decreasing registers. The ascending register is typically incremented by a value representative of the total value of the applied postage. At any time during operation of the system, the values, added together, of the ascending and descending registers must reflect the total amount of postage applied by the machine. The ascending register indicates the total amount of postage resulting from the use of the machine; and the descending register reflects the total amount that can still be used.

In order to provide the system with an initial amount of postage funds, the descending register is charged with the amount of a value which represents the amount of postage funds that can be applied, while the ascending register is placed on a condition of zero funds. If a component of the franking application system were decommissioned for any reason, it would typically be impossible to continue applying franking until the entire system was returned to service.

 The accounting device accounts for both the recharging of the franking machine with an additional postage value and the impression of franking by the printing mechanism of the machine. If independent external accounting systems are used, they are substituted for the metering systems or registers of the franking machine when accounting for postage printed by the machine. Therefore, postage meters must have high reliability to avoid loss of government or user funds.

 Very recently, we have observed an evolution, from a completely mechanical device of postage meter, towards machines which incorporate in an extensive way electronic components. And, although the number of modifications was appreciable, certain elements remained constant. For example, the need for security is absolute. Another factor common to past and present postage systems is the inclusion of a postage mark which is normally placed or printed in the upper right corner of an envelope or package surface.

Although the operation of postage meters has been satisfactory to date and continues to be satisfactory, postage systems which combine the convenience of a postage meter with the advantages of mail accounting systems using data processing devices to provide increased utility have become more common with the advancement of the electronic arts. These systems are less expensive and are more flexible while nevertheless offering the service capacity and the security necessary in the art of franking machines. Such a system, called "POSTAGE AND MAILING INFORMATION APPLYING
SYSTEM ", i.e. Mail franking and shipping information application system is described in U.S. Patent No. 4,725,718 to Ronald P.Sansone et al. Issued on 16 February 1988 and assigned to the assignee of the present invention.

 The evolution of mailing systems has resulted in a need for a mail management system that provides centralized control of one or more franking application devices in such a way that the activity of the devices can be controlled and recorded by a host system. In this way, it is possible to count the activity of all the franking application devices which are coupled to the host system. This centralized control leads to increased efficiency and reliability of accounting in the overall operation of a mail dispatch room. For example, in a large organization such as a corporation, the mail dispatch room typically performs mail forwarding services for various different customers, for example, different departments of the organization. Individual clients can be the sales department, the production department, the legal affairs department and other miscellaneous departments within the organization.

So that each department can be debited precisely for the services performed by the mailing room, it is desirable to generate a report which allocates, on a department by department basis, postage expenses and the value of the services delivered by the mailroom that are related to mail forwarding functions.

 In other organizations, the mailroom may be a primary service offered by the organization; the organization typically handling and shipping material for many different customers. In this type of organization, it is essential that the postage applied and the services related to the application of postage are allocated on a customer by customer basis so that each customer can be billed correctly for the postage spent and the services rendered. We can therefore realize that it is important, in any type of organization that includes a mail dispatch room, that mail dispatch can identify each customer in a special way so that each customer can be billed correctly.

 And, as described above, it is also essential that the postage value of each postal item processed is accurately recorded to avoid fraud or inadvertent errors in the application of postage. The underlying rule of thumb is therefore that the postage meter is always right. The shipping system must therefore meet both the requirements of the postal service and those of the customer.

 It is therefore an object of the present invention to provide a mail dispatch system which combines the convenience of a postage meter with the advantages of a postal accounting system.

To achieve this object, the present invention provides, according to a first aspect, a method of franking, accounting and invoicing of postal objects and services characterized in that it comprises the steps consisting in:
(a) authorize a data processing system to communicate with a postage meter;
(b) initialize an application program for said data processing system in which a customer account can be established or modified;
(c) entering customer data into said application and determining whether said customer pays for a transaction upon completion of said transaction or by being billed at the end of a predetermined time period;
(d) initiate a transaction by entering additional data and a first set of values in a data field of said application ;;
(e) verifying that registers of said postage meter agree with a record of said registers maintained within said data processing system and, if said registers do not match, make a correction;
(f) franking one or more postal items to a second value
(g) completing said transaction by totaling said first set of values, totaling said second values, and then determining whether said transaction data or said transaction value should be corrected;
(h) correcting said transaction value by a modification if it is incorrect and recording said transaction in the memory of said data processing system if said transaction value is correct; and
(i) request payment for said transaction or record said transaction value in said customer account for later billing, based on the determination in step (c).

Said transaction may include the steps of
(a) determine a tariff to be applied to a batch of postal objects, said batch of postal objects containing at least one postal object;
(b) inserting into said franking machine said batch of postal items and then franking each postal item from said batch and recording a postage value which is based on any contracts or discounts which are associated with said customer account; and
(c) determine whether a postal service or product should be included in said transaction, and then enter a value for said postal service or product.

 The postage meter can be operatively connected to said data processing system by a postage meter linkage device.

 Said transactions recorded in said customer account can be retained during said predetermined time and an invoice is generated in respect of said customer account.

Said additional data and said customer data are rectified, said rectification comprising the steps of:
(a) determining that ascending and descending registers of said franking machine are not correlated with increasing and decreasing registers recorded by said data processing system;
(b) determining a difference in values between said registers of said postage meter and said registered registers of said data processing system
(c) select a customer account to rectify
(d) calculate the amount of a value whose said account will be rectified, said amount of value being based on said difference in value and on any increase or discount corresponding to said account and
(e) writing said amount of value to said selected client account.

Said additional data and said customer data can be modified, a monetary value being moved either from a first account to a second account, or from said second account to said first account, said modification comprising the steps consisting in:
(a) determine an account to modify;
(b) determine an amount of value by which said account will be modified;
(c) determine whether said determined value should be added to or subtracted from said account; and
(d) moving said determined value from said first account to a second account if said determined value is to be subtracted from said first account, and moving said determined value from said second account to said first account if said determined value is to be added to said first account.

The method can also include the steps of:
(a) determine whether or not said transaction was applied in error to said customer account and, if it is determined that said transaction was applied in error
(b) identify said transaction applied in error;
(c) transfer said transaction applied in error to a second account;
(d) calculate a value amount whose said data fields of said customer account will be modified, said value amount being based on any increase or any discount corresponding to said customer account;
(e) calculating a second value amount whose said data fields of said second account will be modified, said value amount being based on any increase or discount corresponding to said second account; and
(f) automatically transfer to their respective accounts said calculated amount of value and said second calculated amount of value.

 Said printed transaction can be summarized by said data processing system, a copy of said summarized transaction being given as received to said client.

 Said communication with said franking machine can occur in real time in such a way that an ascending index of each postal object being franked in said transaction and / or an ascending total of the value of each of said franking postal items of said transaction is displayed on a first display or on a second display.

Said data processing system can be in passive communication with a series of postage meters, said passive communication allowing a single postage meter at a time to actively communicate with said data processing system;
said data processing system maintaining a record of increasing and decreasing registers for each of the franking machines of said series of franking machines.

 Cash, coupons or any one of a series of vehicles representing a value may be placed in a means of containment in order to secure said cash, said coupons or said series of vehicles, said means of containment being able to be opened by an instruction of said application program.

According to a second aspect, the invention provides a method of franking, accounting and invoicing of objects and postal services characterized in that it comprises the steps consisting in
(a) authorize a data processing system to communicate with a postage meter;
(b) initialize an application program for said data processing system in which a customer account can be established and / or modified
(c) enter customer data into said application;
(d) initiate a transaction by entering additional data and values in a data field of said application ;;
(e) verifying that ascending and descending registers of said franking machine match a record of said registers maintained within said data processing system and, if said registers do not match, make a correction;
(f) completing said transaction by totaling said values, and then determining whether said transaction data or said transaction value should be corrected;
(g) correcting said transaction value by a modification if it is incorrect and recording said transaction in the memory of said data processing system if said transaction value is correct;
(h) record said transaction value in said customer account for later billing
(i) uploading said transaction data and said transaction value to a medium to be used for preparing said subsequent invoicing; and
(j) uploading to said data processing system a set of data and values.

The method can be implemented in a postage, accounting and billing apparatus for postal services which comprises:
(a) data processing means for recording customer accounts, account data, and calculating values for postage prepaid under the control of an application program, said programming evaluating discounts and / or surcharges on an automatic basis as required
(b) a weighing scale;
(c) at least one postage meter and at least one corresponding postage meter base;
(d) a display;
(e) a means of containment to retain and / or secure the species;
(f) a printer;
(g) a keyboard for entering data into said data processing means;
(h) memory means included in said data processing means for recording and maintaining said account for subsequent billing; and
(i) a modem.

 Said downloading can be accomplished using a modem which is operatively connected to said data processing system, said downloading from the system being carried out to a second data processing system.

 Said set of downloaded data or values may consist of a list of previously downloaded rates or rate updates, or may consist of an additional postage value to be added to the postage meter for postage.

These objects, features and advantages of the present invention as well as others will emerge more clearly from the following description of a preferred embodiment of the invention with reference to the accompanying drawings in which
FIG. 1 is a block diagram of a mail delivery system which can incorporate the present invention.

 FIG. 2 is a high level logic diagram of the method to be used using the system of FIG. 1.

 FIG. 3 is a logic diagram of how a new client file is created according to the method of FIG. 2.

 FIG. 4 is a logic diagram of how a client file is corrected according to the method of FIG. 2.

 FIG. 5 is a logic diagram of a customer search and of the corresponding section possible paths according to the method of FIG. 2.

 FIG. 6 is a logic diagram of the creation of a transaction according to the method of FIG. 2.

 FIG. 7 is a logic diagram of the execution of a transaction according to the method of FIG. 2.

 FIG. 8 is a logic diagram of how data derived from a postage transaction is written.

 FIG. 9 is a logic diagram of the franking management module which executes the transactions according to the capacity of the franking head.

 FIG. 10 is a logic diagram of the account transfer process according to the method of FIG. 2.

 FIGS. 11A and 11B are logic diagrams for managing the display for the transfer process.

 FIG. 12 is a logic diagram of the management of the display and printing of the transfer process report.

FIG. 13 is a logic diagram of the rectification process according to the method of FIG. 2
FIGS. 14A and 14B are logic diagrams for managing postage log interrogations which make it possible to examine and print the transactions executed for a given account.

 FIG. 15 is a logic diagram of the account reading function which is used to determine the existence or absence of an account and to read the account record if the account number is accessible.

 FIG. 16 is a logic diagram of how system reports can be reviewed and / or printed.

 FIGS. 17A, 17B and 17C are logical diagrams of the examination of reports which can be generated by the system.

 FIG. 18 is a logic diagram of the management of an examination screen and / or a printing process concerning the history of transactions.

 FIGS. 19A and 19B are logic diagrams for preparing the monthly system report for daily accumulated transactions.

 FIG. 20 is a logic diagram of the creation and accumulation of the different columns for sales control.

Referring now to FIG. 1, there is shown a mail sending system 10, which is representative of a system which would employ the method according to the invention and which includes:
a microprocessor 12 connected to the monitor 14 by a cable 22 (a);
a scanning device 16 connected to the microprocessor 12 by a cable 22 (b);
several connecting devices 18 (a to n) of franking machines connected to the microprocessor 12 by a cable 22 (c);
a digital input / output card 20 connected to the microprocessor 12 by an interface position 22 (d);
a modem 22 connected to the microprocessor 12 by a cable 22 (e);
a keyboard 24 connected to the microprocessor 12 by a cable 22 (f);
a weighing scale 26 connected to the microprocessor 12 by a cable 22 (g);
a printer 28 connected to the microprocessor 12 by a cable 22 (h) ;;
a memory 30 connected to the microprocessor 12 by a cable 22 (i);
franking machines 32 (a to n) connected to the connecting devices 18 (a to n) of franking machines by an interface cable
Echoplex 22 (j); and
a mail dispatch base 32 connected to the digital input / output card 20 by a cable 22 (k).

The mail dispatch base 32 is of the type which can be triggered remotely by the passage of a postal object; such bases are known and are developed and marketed by Pitney Bowes
Inc. of Stamford, Connecticut, which is the assignee of the present invention.

 A postage meter linkage device 18 enables a host data processing system to remotely control postage meters or known devices such as packet registers, scales or mailing machines. It should be noted that one or more franking machines 30 could be functionally connected to the microprocessor 12; a corresponding franking machine linkage device 18 would be used for each franking machine 32 which is functionally connected in this manner. An example of a postage meter linkage device is the MeterLink device which is developed and marketed by Pitney Bowes Inc. of Stamford, Connecticut, which is the assignee of the invention described herein. Typical applications that would employ a postage meter linker are to record postage or costs; update transaction records; define postage or other orders for postage machines; add funds to a postage meter; or distribute packing tape.

 The shipping system 10 has the capacity to perform weekly backup and restore of these data files so that data can be restored in the event of a system failure. Data from an individual day which could otherwise be lost, can be restored from any of several available media which include: a tape, a floppy disk, a download from a backup system, a download from a higher level system; or a download from any device of a series of memory devices that the shipping system 10 can download.

 Referring to FIG. 2, in step 50, the application program of the system 10, which will be called here the system, and the devices of the peripheral equipment are launched by an operator of the system using an appropriate code word. The use of a code word is controlled in that a system manager can issue code words based on the level of access that is allowed to the system. Customer data is entered in step 52. This data includes: customer name, address, customer type which may be occasional or regular, a system code for the customer general information which may be required by the postal authority or the mail service provider; and any special rates, discounts or surcharges that may apply to that customer. When customer data is entered, the system assigns any code required by the postal authority to identify this customer. The customer's mail items can then be weighed.

 The postal items are weighed individually in step 54 and the system determines in step 56, on the basis of incorporated rate tables, a postage amount for each postal item.

The system advances to step 58 where the system interrogates the ascending (ascending) and descending (descending) registers of the franking machine and the ascending and descending registers recorded by the system to determine if they match. If the registers of the machine differ from the registers of the system, the system calls up a correction screen in step 59 and performs a correction in step 60; otherwise, the system advances to step 62. Registers of a franking machine may differ from the registers of the system in the case where the franking machine has been taken out of the line and used independently of the system, and where the postage meter was then reintroduced into the system.

A correction consists of several stages; these consist of
determining that increasing and decreasing registers of said postage meter are not correlated with increasing and decreasing registers recorded by said data processing system;
determining a difference in values between said registers of said franking machine and said recorded registers of said data processing system
select a client account to rectify
calculate the amount of a value whose said account will be rectified, said amount of value being based on said difference in value and on any increase or discount corresponding to said account and
write this amount of value in said selected customer account.

 When the rectification is completed in step 60, the system returns to step 52. A logic diagram of the rectification process is shown in FIG. 13.

 When the system has advanced to step 62, the individual postal items are franked by the postage meter according to the value determined in step 56. In step 64, the system then determines any applicable service charges to be added to the client's account; the postage amount plus all charges are entered into the customer's account and displayed in a data field in step 66. In step 68, the system queries to determine if there is an error in the fields displayed. If the answer is yes, the system performs a transfer in step 70; if the answer to the query in step 68 is no, the system closes the transaction in step 72.

A transfer consists of several stages, namely
determine whether or not said transaction was applied in error to said client account and, if it is determined that said transaction was applied in error:
identify said transaction applied in error;
transfer said transaction applied in error to a second account;
calculate a value amount whose said data fields of said customer account will be modified, said value amount being based on any increase or any discount corresponding to said customer account;
calculating a second value amount whose said data fields of said second account will be modified, said value amount being based on any increase or discount corresponding to said second account; and
automatically transfer to their respective accounts said calculated amount of value and said second calculated amount of value.

When the transfer is complete in step 70, the system returns to step 72 where the system closes the transaction before advancing to the interrogation of step 74. In step 74, the system interrogates to determine if there are additional transactions. If the answer is
YES, the system returns to step 52. On the other hand, if the answer is
NO, the system advances to step 76. A logic diagram of the transfer process is shown in FIG. 10 where the system queries to determine if there are additional transactions.

 When the system has determined in step 74 that there is no additional transaction, the system again queries, in step 74, to determine if an error has been written. The errors that are the subject of steps 68 and 76 relate to the writing of transaction data, in whole or in part in an erroneous account; and they can therefore occur both before and after the closing of a transaction in step 72. If the answer in step 76 is YES, the system queries in step 78 whether or not a transfer has been performed. If the answer to the query in step 78 is YES, the system advances to step 80 and performs a transfer. On the other hand, if the answer at step 78 is NO, the system advances to step 82.

 After steps 78 and 80, or if the response to the query in step 74 is NO, the system advances to step 82. In step 82, the system queries to determine if the customer should be billed. If the answer to the query in step 82 is YES, the transaction is written to the customer's account in step 84 for future billing. The system then closes the application program in step 90. If the response to the query in step 82 and NO, the transaction is written to the customer's account in step 86, which causes the cash drawer to open so that the customer can pay the value of the transaction in step 88. When the cash drawer closes by the system operator, the system advances to step 90 and closes the application program.

 Going to FIG. 3, there is shown a logic diagram of the creation of a new customer account. The system operator enters the application program in step 100 and in step 102 enters a system code for the new client. In step 104, the system queries its database to determine if the code entered in step 102 already exists. If the answer to step 104 is YES, the system advances to step 106 where the legend "ALREADY EXISTS", that is to say already exists, is displayed to the system operator. The system then advances to step 108 where the customer's name is displayed. From step 108, the application is exited in step 126. If the answer to step 104 is NO, the system sets a default code to match the system code in step 110. A system code is assigned by the system operator when a customer initiates its first transaction. A code can also be assigned to a customer by the postal system or by the postal service provider. If the customer's account is established or is being established and the postal system or the postal service provider has not yet established a code for the customer, the system assigns a default code to the corresponding data field. At different points in the application, a customer code assigned by the postal service or by the shipping service provider can be entered in the defect field in order to identify this customer.

 As soon as the default code is placed in step 110, a default initialization of the data fields is carried out in step 112; this allows data to be entered in these fields in step 114. The system advances to step 116 where it queries to determine if the data entries have been made appropriately. If the answer is YES, the system interrogates in step 120 to determine whether there is a validation of the entries. If the answer is YES, the system saves the new data in step 122, thereby creating in step 124 a new client file. The exit from the application is carried out in step 126.

 If the answer to interrogation 116 is NO, the system indicates in step 118 to the system operator that an error has occurred. The system then advances to step 126 and exits the application.

 If the answer to the interrogation of step 120 is NO, the system advances to step 126 and exits from the application.

Referring now to FIG. 4, there is shown a logic diagram of the modification process. A modification consists of several stages
first determine an account to modify
determine an amount of value whose said account will be modified;
determining whether said determined value should be added to or subtracted from said account; and
move said determined value from said first account to a house account if said determined value must be subtracted from said first account, and
move said determined value from said home account to said first account if said determined value is to be added to said first account.

 To make a modification, the system operator enters the application program in step 130 and begins, in step 132, a client search by system code, default code, or client name. Client research is described in detail in FIG. 5. In step 134, the system queries to determine if the client's search has been successful. If the answer to the query is NO, the system advances to step 156 where the client file is closed and the program returns to the application menu. However, if the answer to the query in step 134 is YES, the system displays in step 136 the selected client and allows the system operator to make changes to the desired data fields.

 The system operator makes changes in step 138 and the system then advances to a series of queries that begin in step 140. In step 140, the system queries to determine if the postal code field has varied. The postal code is assigned by the postal service or by the shipping service provider.

If a code is issued, the code is placed in the appropriate field above the default code. However, if no code is being edited, the default code remains in the field. If the answer to the query in step 140 is yes, the system advances to step 142 and queries to determine if the selected postal code already exists. If the answer to the interrogation of step 142 is YES, the system advances to step 144 where the legend ALREADY EXISTS, that is to say already exists, is displayed for the system operator; the system displays in step 146 the client file for the preexisting client and then advances to step 156 where the client file is closed and the program returns to the application menu.

 If the response to the query in step 140 is NO, the system advances to step 148 where the system queries to determine whether or not entries have been made appropriately. If the answer is NO, the system indicates an error in step 150 and advances to step 156 where the client file is closed and the program returns to the application menu. If the answer to the query is YES, the system validates the modification in step 152, modifies the customer data in the database in step 154, and then advances to step 156 where the client file is closed and the program returns to the application menu.

 Turning now to FIG. 5, there is shown the steps necessary to carry out a customer search. The operator of the system begins in step 160 the search for the client and is offered a choice of three routes, depending on whether or not the system operator has entered a system code number, a postal code number, or the proper name of the client sought. If the system operator has entered the system code, the operator enters the search in step 162. The system performs the search in ascending numerical order in step 164 and then displays the list of clients at the step 166. The customer list represents customer names, postal codes, and indicates whether they are regular or occasional customers.

 If the operator of the system has entered the postal code, the operator enters the search in step 168. The system continues the search in ascending numerical order in step 170 and then displays the list of customers at the step 172. The client list represents client names, postal codes, and indicates whether they are regular or occasional clients.

 If the system operator has entered the letters of the client's proper name, the operator enters the search in step 174. The system performs the search in alphabetical order in step 176 and then displays the list of clients in step 178. The customer list shows customer names, postal codes and whether they are regular or occasional customers.

 The customer lists presented in steps 166, 172 and 178 each advance to step 180 where the system queries to determine whether or not items should be selected from the displayed lists. If the system operator makes a selection, the system advances to step 182 where the selected client is displayed; the system then advances to step 184 where the customer search is completed. If the system operator does not make any selection in step 180, the system advances to step 184 where the customer search is completed.

 Referring now to FIG. 6, the creation of a transaction is shown as beginning with a date check in step 190. The purpose of the date check is to ensure that the system has not been restored or configured again.

 After checking the date in step 190, the client is selected in step 192. The system queries in step 194 to determine if the selection in step 192 is correct. If the answer to query 194 is NO, the system advances to step 210 where an operator selection error or end is recorded. On the other hand, if the response to the interrogation of step 194 is YES, the system interrogates in step 196 to determine if the account is locked. If the answer is YES, the system advances to step 210 where an error or end of operator selection is recorded. On the other hand, if the answer to the interrogation of step 196 is NO, the system interrogates, in step 197, to determine whether or not a tariff adjustment is necessary. If the answer is YES, the system advances to step 198 where the rates are adjusted. If the answer to the query in step 197 is NO, the system advances to step 199 where the system can accept a weight from the 24 weighing scale, or the system can accept manual entry.

 When a weight is accepted in step 198, the system advances to step 200 and selects a type of postal shipment, by a class or tariff process. Based on the type of postal shipment, the system determines in step 202 the postage cost and queries in step 204 to determine if the calculated cost is acceptable. It is possible to adjust transaction invoices in ascending or descending directions to reflect discounts, surcharges or other debits.

If the answer to the interrogation of step 204 is NO, the system advances to step 210 where an end of operator selection is recorded. On the other hand, if the response to the interrogation of step 204 is YES, the system interrogates in step 206 to determine whether or not the system is prepared to execute the transaction. If the answer to the interrogation of step 206 is NO, the system advances to step 210 where an end of operator selection is recorded. On the other hand, if the answer to the interrogation of step 206 is YES, the system advances to step 208 where a transaction execution is recorded as a true event and the transaction is created in step 214. The creation of the transaction prepares the system for execution of the transaction. A transaction is executed according to the steps described later in FIG. 7.

 If the answer to one of the interrogations of steps 194, 196, 204 and 206 has led to step 210, the system records as execution false transaction transaction in step 212, and the absence of transaction is completed in step 214.

 Referring now to FIG. 7, the execution of the transaction created by the steps of FIG. 6 is represented there. The transaction is created in step 220 and the system performs a hardware check in step 222. The hardware check is performed to ensure that all of the hardware needed to complete a given transaction is connected and available. At step 224, the system queries to determine if the hardware check is correct. If the answer is NO, the system records an error as a true event in step 248 and advances to step 250 where the transaction is executed as an error. On the other hand, if the response to the interrogation in step 124 is YES, the system resets all partial settings of the franking machine in step 226, return to zero or abbreviated RESET, according to the English term, and initializes in step 228 the amount of postage .

 From step 228, the system advances to step 230 and queries to determine if the initialization of the postage amount is correct. If the answer to the interrogation of step 230 is NO, the system advances to step 248 and records an error as a true event; the system then advances to step 250 where the transaction is executed as an error. On the other hand, if the answer to the query in step 230 is YES, the system checks the consistency of the franking machine in step 232. The consistency of the franking machine refers to the interface between the machine franking machine 32 and system 10 immediately after initialization, and immediately before actual franking. When the consistency of the franking machine is established, in step 234, the system sets the value on the franking machine 32 and locks the keyboard of the franking machine 32; the system then franks the postal item and monitors the process as it occurs. The postage transaction is concluded in step 236 and the system reads the postage meter to obtain an indication that the register of the postage meter has recorded the transaction. The system queries in step 238 to determine if the postage meter reading has been correct. If the answer to the query is NO, the system goes to step 248 where an error is recorded as a true event; on the other hand, if the answer is YES, the system checks the franking machine in step 240 and queries in step 242 to determine if the check was successful.

If the response to the query is NO, the system proceeds to step 248 where an error is recorded as a true event. On the other hand, if the answer is YES, the system numbers in step 244 the franking operation for the system log; and it indicates that an error is logged as a false event in step 246.

 From step 246, or step 248, the system advances to step 250 where the transaction is completed and recorded as executed. Saving entries to the database, or closing transactions, are shown in FIG. 8.

 Referring now to FIG. 8, the system writes the postage transaction file in step 260 and stores the file in the franking transaction table in step 288. From step 260, the system reads the code number from the client, with respect to the system, and the date of the transaction at step 262 in the account table of the client at step 290; if necessary, the codes and the date can be updated at this stage. The system advances to step 264 where the transaction is recorded in the recording transaction table, in step 292. From step 264, the system interrogates the recording transaction to determine whether the recording is correct. If the answer to the query is NO, the system advances to step 280 where the tables are retrieved and restored; on the other hand, if the answer to step 266 is YES, the system writes the client account file and stores it in the database in step 294.

When the customer account file has been registered, it is possible to enter the customer account, in step 270, to update or create the customer account. Entries are updated in the customer account table in step 296. When the appropriate entries have been made, the system queries in step 272 to determine if the account and its corresponding entries are correct. If the answer is
NO, the system advances to step 280 where the tables are retrieved and restored. On the other hand, if the answer to the interrogation of step 272 is YES, the system registers in step 274 the file of the franking machine, abbreviated as PFM according to the English term postal franking machine, and opens the table corresponding to step 298. The system advances to step 276 where the internal registers of the system update the postage meter number and the postage amount. The updated amounts are stored in the franking machine table in step 300, based on the machine number. As soon as the update is stored, the system interrogates, in step 278, to determine whether the update is exact. If the answer is NO, the system advances to step 280 where the tables are retrieved and restored; on the other hand, if the answer in step 278 is
YES, the system goes to step 284 where the registration files are updated; an error is recorded as a false event in step 286; and the database is closed or updated in step 302. From step 280, the error is recorded as a true event in step 282 and the database is then closed in step 302.

 Referring now to FIG. 9, the stages of the postage process are shown. Starting from the application program in step 310, a transaction is then created in step 312.

The system queries in step 314 to determine if the transaction created in step 312 should be executed. If the response to the query is NO, the system advances to step 336 where the postage transaction is completed. On the other hand, if the response to the query is YES, the system advances to step 316.

 The postal franking machine includes a franking head which has an upper print field limit of 999.99 when recording a transaction value. If the franking transaction exceeds the limit of 999.99 the system determines in step 2316 the "n" transactions which will be carried out at the maximum limit of 999.99 and then calculates the transactions which will be recorded at a certain lower value to 999.99 where "n" represents the number of transactions. Values less than 999.99 are represented in the calculations as xxx, xx. It is possible to use a print head for which the upper limit of the print field is 99.999.

 The number of transactions is determined by setting l equal to zero (1 = 0) in step 318, then advancing to step 320 where an increment of transactions is calculated by setting l = 1 + 1 and 1 <n. From step 320 there are two routes. The first path goes through step 326 where transaction 1 is executed at 999.99; the second path concerns the transaction xxx, xx which is implemented when the system advances to step 322 where the interrogation "l = n + 1?" is asked. If the answer to the question is YES, the system advances to step 336 where the franking transaction is completed. If the answer to the interrogation of step 322 is NO, the system performs in step 324 the transaction where l = n + 1 at xxx, xx. The two steps 326 and 324 lead to step 328 where the system queries to determine if an error has occurred. If the answer to the query is YES, the system advances to step 334 and displays an error to the system operator before completing the franking transaction in step 336. On the other hand, if the response to the query is NO, the database is updated in step 330. After updating the database, the system queries in step 332 to determine whether or not an error is indicated during updating the database.

If the answer to the query is YES, an error is displayed to the system operator before the franking transaction is completed in step 336. If the answer is NO, the system enters the path before l step 320, and the cycle is run again until the answer to step 322 is YES.

 Referring to FIG. 10, the steps necessary to complete an account data transfer are shown. The transfer begins in step 350 and a transaction is then selected in step 352 in the postage transaction history table in step 372. A search is performed in step 354 to determine a source account and a destination account for the transfer. The search is performed in step 374 using the table of customer accounts.

 From step 354, the system advances to step 356 where all applicable tariffs are selected for the source and destination accounts. Advancing to step 356, the entries are recorded in the registration history file, in step 378 and in the customer account registration file in step 376. When the entries are made in step 358 , the system advances to step 360 where the source and destination accounts are corrected and adjusted as to the rates applicable to the specific parameters of the accounts. As soon as the corrections are entered in the customer account table in step 380, the system interrogates to determine whether an update error has occurred. If the response to the interrogation is YES, the system advances to step 370 where the registration files and accounts are brought back to the situation prior to the transfer attempt; the account transfer is then considered to be completed in step 384. If the response to the query in step 362 is NO, the system updates in step 364 the history table in step 382. The the system then queries in step 366 to determine if an error occurred during the update. If the response to the query is YES, the system advances to step 370 where the registration files and the accounts are brought back to their situation prior to the transfer attempt. If the answer to the query in step 366 is NO, the registration files are adjusted in step 368 and the account transfer is completed in step 384.

 Turning now to FIG. 11A and 11B, there is shown the management of the screens of the system operator for the transfer process. The management of the screens of the system operator begins at step 390 and advances to step 392 where the system history file is loaded. The system queries in step 394 whether the loading of the history table has been successful. If the answer to the query in step 394 is NO, the system follows path D to step 426 where the program screen is closed and the system operator is returned to the system menu. If the answer to the query is YES, the system advances to step 396 where the system operator is offered the opportunity to read the available keys to make an account selection. The system then advances to step 398 where a query is asked to determine whether to select from an available list of transactions. If the answer is YES, the system initializes the data field of the source account using the account history field in step 400; the selected transaction is then displayed to the system operator in step 402 before taking the route In step 424. If the response to the interrogation is NO, the system advances to the interrogation of step 404 .

Step 404 queries to determine if the destination account field should be selected. If the response to the query is YES, the system queries to determine if the destination account has been read correctly. If the answer is YES, the destination account is initialized by means of the destination data field in step 408, before progressing along the path A towards step 424. If the response to the interrogation of the step 408 is NO, the system displays the legend to the system operator in step 414
UNKNOWN ACCOUNT NO, that is to say n of unknown account, before advancing along the path A towards step 424. If the answer to the interrogation of step 404 is NO, the system interrogates at step 412 to determine if the confirmation key has been selected.

 If the confirmation key is selected in step 412, the system asks in step 414 to determine whether the source and destination accounts are known. If the accounts are known, the transfer of accounts is carried out in step 416 before advancing along the path A towards step 424. If the source and destination accounts are not known, the system displays at l step 418 the known count before advancing along the path A towards step 424. If the answer to the interrogation of step 412 is NO, the system interrogates in step 420 to determine whether the HELP key or help, is required. If the answer is YES, the online help function is activated in step 422 for the system operator before the system advances along path A to step 424. interrogation of step 420 is NO, the system advances directly along path B towards step 424.

Step 424 is an interrogation intended to determine whether a CLOSE key, that is to say closing, must be selected. If the answer to the query is NO, the system advances along the route
C to return to step 396. If the answer to the query is YES, the close button is selected and the program screen is closed in step 426 and the system operator is returned to the system menu . The option is offered to the system operator to print a transfer report; the mechanism for managing the printing of the report is shown in FIG. 12.

 Referring to FIG. 12, there is shown the management of the system operator screen for printing the report which details the movements of the account data during a transfer. The management of transfer reports begins at step 430 and advances to step 432 where the transfer process is displayed. In step 434, the system operator can read the key legends for the keys that are available during the transfer process.

The system operator is queried at step 436 to determine if the confirmation key should be selected. If the answer is NO, the system enters the program immediately before step 434. On the other hand, if the answer is YES, a copy of the transfer report is printed in step 438; the screen is closed at step 440; and the system then completes the transfer management process in step 442.

 Another process that makes changes to the system is rectification. A correction becomes necessary when it is determined that the increasing and decreasing registers of the system of the postage meter of the system are not correlated with the increasing and decreasing registers recorded by the data processing system. This can happen when the postage meter is taken out of the system and used offline for a period of time before being put back into the system. Steps in the rectification process are shown in FIG. 13.

A correction consists of several stages which are
determining that increasing and decreasing registers of said postage meter are not correlated with increasing and decreasing registers recorded by said data processing system;
determining a difference in values between said registers of said postage meter and said registered registers of said data processing system;
select a client account to rectify
calculate the amount of a value whose said account will be rectified, said amount of value being based on said difference in value and on any increase or discount corresponding to said account and
write this amount of value in said selected customer account.

 Referring now to FIG. 13, the need for a correction is decided at a step 450. The system then determines, at a step 452, the difference in amount between the increasing and decreasing registers of the postage meter and the increasing and decreasing registers recorded by the system data processor. In step 450, the system operator selects a destination account and advances to step 456 where the system data processor increments the registered machine registers until they match the machine registers postage. The system advances to step 458 where a record of the transaction is generated within the destination account; the destination account can be a "dummy" account or a "house" account used to detail registry differences, or a client account can be selected.

The system interrogates in step 460 to determine an error has occurred in generating the transaction record. If the response to the query is YES, the system restores the registration files in step 462 and then advances to step 466 where the account correction is completed. If the answer at step 460 is
NO, the system deletes the restoration of registration files in step 464 and then advances to step 466 where the account correction is completed.

Referring now to FIGS. 14A and 14B, there is represented the management of postage journal queries which make it possible to examine and print the transactions executed for a given account. The interrogation screen management begins at step 470 and advances to step 472 where an initialization of the default parameters takes place. The system displays the data fields in step 474; and the system operator can then read, in step 476, which keys are available for operating the active window. At step 478, the system queries to determine if the keys pressed were correct. If the answer to the query is
YES, the system queries to determine if the account data can be read. If the answer to the query in step 480 is
NO, the system displays the legend ACCOUNT NO. UNKNOWN, that is to say N of unknown account, and advances along path A to enter the program at step 510. If the answer to the interrogation at step 480 is YES, the system allows the system operator to examine the transaction log. On the other hand, if the answer to the interrogation of step 478 is NO, the system proceeds to step 486.

 At step 486, the system queries to determine if the help key should be selected. If the answer to the query is YES, the system displays the help screen in step 488 before advancing along path A to enter the system in step 510. If the answer to the interrogation is NO, the system asks, in step 490, whether the account field to be displayed. If the answer to the query in step 490 is YES, the account number and the field are initialized and the system advances along the path A to enter the program in step 510. If the answer to the interrogation of step 490 is NO, the system advances along path B until an interrogation of step 494.

The system queries in step 494 to determine if the data field should be selected and what input is required for the field. If the answer is YES, the system queries in step 496 to determine if the date is valid. If the answer to the query is
NO, the system displays ERROR - INVALID DATE, that is to say invalid date error, and then advances along path A to enter the program in step 510. On the other hand, if the response to the interrogation from step 496 is YES, the system initializes the date at step 500 and advances along path A. If the answer at step 494 is NO, the system advances to an interrogation at step 502.

In step 502, the system queries to determine if there is a tariff to be evaluated based on time parameters. The effect of this interrogation is to evaluate day or morning rates where these distinctions may be available. If the answer is YES, the tariff key is set to the appropriate setting in step 504 and the SYSTEM advances to path A. If the answer to the query in step 502 is
NO, the system proceeds to the interrogation of step 506 and interrogates to determine if there are other optional tariffs. If the answer is YES, the system sets the tariff key based on the option criteria of step 508, then advances to path A.

 All the advances along the path A, and a response NO to the interrogation of step 506, cause the program to enter the step 510. Step 510 asks whether or not the cancel key is chosen.

If the answer is NO, the system advances along the path C, and enters the program in step 476. If the answer to the interrogation of step 510 is YES, the management of interrogation screen is completed in step 512.

 Referring now to FIG. 15, there is shown the account reading function which is used to determine the existence or absence of an account and to read the account record if the account number is accessible. The system begins reading the account record at step 520, and then advances to an interrogation at step 522.

 In step 522, the system queries to determine if initialization of the access keys has occurred. If the answer is NO, the system indicates a file access error in step 524 before advancing to step 532 where the reading of the account record is completed. If the answer to the query in step 522 is YES, the system advances to step 526 and queries to determine if a search for the account number has been successful. If the response to the query is NO, an invalid operation is displayed to the system operator in step 528 before advancing to step 532 where the reading of the account record is completed. If the answer to the interrogation of step 526 is YES, the system confirms the operation in step 530 before concluding the reading of the account in step 532.

 Referring now to FIG. 16, there is shown the screen management process for examining reports and for the printing process. The management of the examination screen begins at step 540 and advances to the interrogation of step 542 which interrogates to determine whether the loading of tables of reports has been successful. If the answer is NO, the system advances to step 544 which indicates to the system operator an error in reading the file before advancing to step 560 where the examination screen for this process is closed and the system operator is returned to the system menu. On the other hand, if the answer to the query in step 542 is YES, the system draws up a list of the data fields to be examined in step 546. The system then displays the screens listed and the log in step 548 In step 550, an opportunity is offered to the system operator to examine the keys which are active; and the system then queries in step 552 to determine whether the print key should be selected. If the answer is YES, the system prints the log in step 554 and enters the program flow in step 556.

If the answer to the query in step 552 is NO, the system advances to step 556.

In step 556, the system queries to determine if the close button should be selected. If the answer to the query is
NO, the system enters the program in step 550. On the other hand, if the response to the query in step 556 is YES, the system advances to step 558 where the screen is prepared for closing, and then at step 560 where the screen is closed and where the system operator is returned to the system menu.

 Referring to FIG. 17A, 17B and 17C, there is shown the process by which reports produced by the system can be examined. Screen management of the interrogation begins at step 570 and then advances to step 572 where an initialization of the field parameters occurs. In step 574, an opportunity is offered to the system operator to read active keys available for actuation of the system. The keys are selected to enter an account number and in step 576 the system queries to determine if the selection is correct.

If the answer to the interrogation of step 576 is YES, the system interrogates, in step 578, to determine whether the account chosen is a single account; this is accomplished by querying to determine if a single account indication is a true event. If the response to the query in step 578 is YES, the system queries to determine if the account number field is correct. If the answer to the query is NO, the system displays the legend ENTER
ACCOUNT NO., That is, between account N, then advances along path A to enter the system in step 642.

 If the answer to the query in step 578 is NO, the system queries in step 580 to determine if the selection of all accounts is established as a true event. If the answer to the query is YES, the report can be examined by the system operator in step 588 before the system advances along path A to enter the system in step 642. If the answer to the interrogation of step 580 is NO, the system advances directly to path A.

 If the response to the query in step 582 is YES, the system queries in step 584 to determine if the selected account can be read. If the answer to the query is YES, the report can be examined by the system operator in step 588 before the system advances along path A to enter the system in step 642.

If the answer to the query in step 584 is NO, the system displays UNKNOWN ACCOUNT NO., That is to say N of unknown account, before advancing along path A.

 If the response to the query in step 576 is NO, the system queries in step 592 to determine if the help key has been selected. If the help key has been selected, the system advances to step 594 where the online help is used. The system then advances along path A. On the other hand, if the answer to the interrogation of step 592 is NO, the system advances along path B towards the interrogation posed in step 596.

At step 596, the system queries to determine whether or not the daily report option is being selected. If the answer is
YES, the system initializes the daily parameters in step 598 and then advances to step 604 where the available window fields are displayed again to the system operator. If the answer to the query in step 596 is no, the system queries in step 600 to determine if a monthly option has been selected for the report. If the answer is YES, the system initializes the monthly parameters in step 602 and then advances to step 604 where the available window fields are displayed again to the system operator. If the answer to the interrogation of step 600 is NO, the system advances to step 606.

 In step 606, the system queries to determine if a single account option has been selected. If the answer is YES, the accounts field is indicated in step 608 as a false event and the unique accounts field is indicated as a true event. If the answer to the query in step 606 is NO, the system queries in step 610 if the option for all accounts has been selected.

If the answer is YES, the field of all accounts is indicated as a true event in step 612, and the field of single accounts is indicated as a false event. The system advances from steps 608 and 612, along path A, to step 642.

 If the answer to the query in step 610 is NO, the system queries in step 614 to determine if the reports should be based on selected date fields. If the answer is YES, the system queries in step 616 if the selected dates are correct.

If the answer is YES, the system initializes the date using the date field in step 618. However, if the answer in step 616 is
NO, the legend INVALID DATE, that is to say invalid date, is displayed to the system user at step 620 before advancing along path A. If the response to the interrogation of the step 614 is NO, the system advances along path B towards the interrogation of step 622.

At step 622, the system queries to determine if a particular month should be selected for the report field. If the response to the query is YES, the system queries at step 624 to determine if the selected month is the correct month; and, if the response to the query is YES, the system performs an initialization of the month using the month field in step 626 before advancing along the route
A to step 642. If the answer to the query in step 624 is
NO, the system displays: INVALID MONTH, that is to say invalid month, and advances to path A.

 If the response to the query in step 622 is NO, the system queries in step 630 to determine if an operator field should be selected. If the answer is YES, the system queries at step 632 to determine if the operator is authorized to use this field. If the answer to the query is NO, the system indicates ERROR - OPERATOR NOT RECOGNIZED to the system operator, at step 634, that is to say that there is an unrecognized operator error. On the other hand, if the answer to the interrogation of step 632 is YES, the operator equals the operator field and this is displayed in step 636. Steps 634 and 636 then advance then towards path A .

 If the answer to the query in step 630 is NO, the system queries in step 638 to determine if an account number field should be selected. If the answer is YES, the account number field is initialized at step 640 and the system advances along path A towards step 642. If the answer to the interrogation at step 638 is no, the system advances to step 642.

 All entries in path A and a NO response to the interrogation of step 638 advances to the interrogation of step 642. In step 642, the system interrogates to determine if the CANCEL key, c ' i.e. cancel, must be selected. If the answer is no, the system advances along the path C to enter the program at step 574 where the opportunity is given to the system operator to select from the available keys of the active screen. If the answer to the query in step 642 is YES, the system closes the screen in step 644 and then finishes examining the report in step 646.

 Referring to FIG. 18, the procedure for managing the examination screens when displaying a transaction is shown there. The management of the examination screen begins at step 650 and then advances to the interrogation of step 652. In step 652, the system interrogates to determine whether the loading of the history file is correct. If the answer is NO, the system advances to step 654 which indicates to the system operator a file read error before advancing to step 670 where the examination screen for this process is closed and the system operator is returned to the system menu. On the other hand, if the answer to the interrogation of step 652 is YES, the system displays in step 656 the available data fields and the system establishes a list of the data fields to be examined. The system then displays in step 658 the fields listed. At step 660, the operator is offered the opportunity to examine the keys that are active, and the system then queries at step 662 to determine whether the print key should be selected. If the answer is YES, the system prints the log in step 664 and enters the program flow in step 666. If the answer to the query in step 662 is NO, the system advances directly to the 'step 666.

In step 666, the system queries to determine if the close button should be selected. If the answer to the query is
NO, the system enters the program at step 660. On the other hand, if the answer to the interrogation of step 666 is YES, the system advances to step 668 where the screen is prepared for closing, then to step 670 where the management of the examination screen is completed and where the system operator is brought back to the system menu.

Then passing to FIG. 19A and 19B, examining customer services and managing the fields that produce monthly sales reports are shown. Sales accounting begins at step 680 and proceeds to step 682 where the report fields are displayed to the system operator. When the display screen is active, the system advances to step 684 where the operational keys available to the system operator can be examined and activated before advancing to the interrogation of step 686. In step 686, the system queries to determine if a month number should be selected. If the answer is YES, the system interrogates in step 688 to determine if the month is in the field 1 <month 5 12. If the answer is NO, the system displays in step 690 ERROR - INVALID
MONTH NO., That is to say error - Invalid month. After the display of step 690, the system advances on path A towards step 718.

However, if the answer to the query in step 688 is
YES, the month is made equal to the month number in step 692 and the system advances to path A. If the answer to the query in step 686 is NO, the system advances to step 694 where the system queries to determine if the number of elements to be placed in the accounting field will be used as a parameter. If the answer to the interrogation is YES, the number of elements is made equal to the number of elements in step 696 before advancing towards path A. If the answer to the interrogation of step 694 is NO, the system advances to the interrogation of step 698.

 Step 698 is an interrogation intended to determine whether the system operator requests assistance from the help key. If the answer is YES, the online help is made active in step 700. After using the online help, the system advances to path A. If the answer to the query in step 698 is NO, the system advances along path B towards step 702. Step 702 is an interrogation intended to determine whether a confirmation must be selected for a number of accounting fields. If the answer is YES, the system asks if the month = 0 in step 704; if the number of items = 0 in step 708, and if sales = 0 in step 712.

 If the answer to the query in step 704 is YES, the month zone is not entered in the report fields in step 706 and the system advances to path A. If the response to the query in step 708 is YES, the element number area is not entered in the report fields in step 710 and the system advances to path A. And, if the response to the interrogation of the step 712 is YES, the sales area is not entered in the report fields in step 714 and the system advances to path A.

 If the answer to the query in step 704 is NO, the month zone is reserved for entry in the sales report and the system advances to the query in step 708. If the response to the query in step 708 is NO, the item number area is reserved for entry in the sales report and the system advances to the query in step 712. And, if the response to the query in the step 712 is NO, the sales area is reserved for entry in the sales report and the system advances to step 716 where the sales report is drawn up. When the sales report has been established, the system advances to path A.

 All entries in path A, and a NO response to the interrogation of step 702 advances the system to the interrogation of step 718. In step 718, the system interrogates to determine whether the closing must be selected. If the answer is NO, the system advances along path C to enter the program at step 684 where the opportunity is offered to the system operator to select from the available keys on the active screen. If the answer to the query in step 718 is YES, the system closes the screen in step 720, and then finishes examining the report in step 722.

Turning now to FIG. 20, the stages of creation and accumulation of different columns of sales control are shown. Sales control starts at step 730 and then proceeds to display the fields available in step 732. From step 732, the system creates the sales report in step 734, displays the report to the system operator in step 736, and then activates operational keys in step 738 for selecting the system operator. The system advances from step 738 to step 740 where the system queries to determine if the print button should be selected. If the answer to the query is YES, the system prints the sales report. If the answer to the query in step 740 is
NO, the system advances to the interrogation of step 744.

At step 744, the system queries to determine if the close button should be selected. If the answer to the query is
NO, the system enters the program in step 738. On the other hand, if the response to the query in step 744 is YES, the system advances to step 746 where the screen is prepared for closing, and the sales report is printed. From step 746, the system advances to step 748 where the report has been printed, the screen is closed and the system operator is returned to the system menu.

 As those skilled in the art understand, many variations of the present invention are possible. These variants include, but are not limited to: the nature and scope of each of the hardware components of the data processing system; the capacity of the system to process more than one support and the respective speeds of the supports; the ability to scan data in the system; the decision concerning the acceptance or rejection of immediate billing operations, unlike periodic billing operations, the extent of the upper limit of the print field of the print head when recording a transaction value; and the extent to which data can be downloaded from the system, either to a transfer medium or to another data processing system.

Claims (15)

 1. Method for franking, accounting and invoicing of objects and postal services, characterized in that it comprises the steps consisting in:  (a) authorize a data processing system to communicate with a postage meter;  (b) initializing (50) an application program of said data processing system in which a customer account can be established or modified;  (c) entering (52) customer data into said application and determining (82) whether said customer will pay for a transaction upon completion of said transaction, or by being billed at the end of a predetermined time period;  (d) initiating a transaction (54, 56) by entering (64) additional data and a first set of values in a data field of said application ;;  (e) verifying (58) that registers of said postage meter match a record of said registers maintained within said data processing system and, if said registers do not match, make a correction (59, 60);  (f) franking (62) one or more postal items to a second value  (g) completing (66) said transaction by totaling said first set of values, totaling said second values, and then determining (68) whether said transaction data or said transaction value should be corrected;  (h) correcting (70) by modifying said transaction value if it is incorrect and recording (72) said transaction in the memory of said data processing system if said transaction value is correct; and  (i) request (86, 88) a payment for said transaction or record (84) said transaction value in said customer account for subsequent billing, depending (82) on the determination of step (c ).  2. Method according to claim 1, characterized in that said transaction comprises the steps consisting in:  (a) determining (56) a tariff to be applied to a batch of postal items, said batch of postal items containing at least one postal item;  (b) inserting (54) into said franking machine said batch of postal items and franking (62) each postal item of said batch and recording a postage value which is based on any contracts or discounts which are associated with said account of the customer; and  (c) determining (64) whether a postal service or product should be included in said transaction, and then entering a value of said postal service or product.  3. Method according to claim 1, characterized in that  the postage meter (32 a to n) is operatively connected to said data processing system (12) by a postage meter linkage device (18 a to n).  4. Method according to claim 1, characterized in that  said transactions recorded in said customer account are retained for said predetermined time and an invoice is generated with respect to said customer account.  5. Method according to claim 1, characterized in that  said additional data and said customer data are rectified, said rectification comprising the steps of:  (a) determining (58, 59) that ascending and descending registers of said postage meter are not correlated with ascending and descending registers recorded by said data processing system;  (b) determining (452) a difference in values between said registers of said franking machine and said registered registers of said data processing system;  (c) select (454) a customer account to be corrected ;;  (d) calculating (456) the amount of a value whose said account will be rectified, said amount of value being based on said difference in value and on any increase or discount corresponding to said account and  (e) writing (458) said amount of value to said selected client account.  6. Method according to claim 1, characterized in that  said additional data and said customer data are modified, a monetary value being moved either from a first account to a second account, or from said second account to said first account, said modification comprising the steps consisting in:  (a) determine (132 to 136) an account to be modified;  (b) determining (138) an amount of value by which said account will be modified;  (c) determining (138) whether said determined value should be added to or subtracted from said account; and  (d) moving (154) said determined value from said first account to a second account if said determined value is to be subtracted from said first account, and moving said determined value from said second account to said first account if said determined value is to be added to said first account .  7. Method according to claim 1, characterized in that it further comprises the steps (68-70; 76-78) consisting in:  (a) determine whether or not said transaction was applied in error to said customer account and, if it is determined that said transaction was applied in error  (b) identify said transaction applied in error;  (c) transfer said transaction applied in error to a second account;  (d) calculate a value amount whose said data fields of said customer account will be modified, said value amount being based on any increase or any discount corresponding to said customer account;  (e) calculating a second value amount whose said data fields of said second account will be modified, said value amount being based on any increase or discount corresponding to said second account; and  (f) automatically transfer to their respective accounts said calculated amount of value and said second calculated amount of value.  8. Method according to claim 1, characterized in that  said printed transaction (438) is summarized by said data processing system and  a copy of said summarized transaction is given as received to said client.  9. Method according to claim 1, characterized in that  said communication with said franking machine occurs in real time in such a way that an ascending index of each postal item being franked in said transaction and / or an ascending total of the value of each of said postage postage of said transaction is displayed on a first display or on a second display.  10. Method according to claim 1, characterized in that  said data processing system is in passive communication with a series of postage meters, said passive communication allowing a single postage meter at a time to actively communicate with said data processing system; and in that  said data processing system maintains a record (58) of increasing and decreasing registers for each of the franking machines of said series of franking machines.  11. Method according to claim 1, characterized in that  cash, coupons or any one of a series of vehicles representing a value are placed in a confinement means in order to secure said cash, said coupons or said series of vehicles, said confinement means being able to be opened by an instruction of said application program.  12. Method for franking, accounting and billing of postal objects and services, characterized in that it comprises the steps consisting in:  (a) authorize a data processing system to communicate with a postage meter  (b) initializing (50) an application program of said data processing system in which a customer account can be established and / or modified;  (c) enter (52) customer data in said application  (d) initiating a transaction (54, 56) by entering (64) data and additional values in a data field of said application;  (e) checking (58) that said ascending and descending registers of said franking machine agree with a record of said registers maintained within said data processing system and, if said registers do not match, make a correction (59, 60);  (f) completing (66) said transaction by totaling said values, and then determining (68) whether said transaction data or said transaction value should be corrected  (g) correcting (70) by modifying said transaction value if it is incorrect and recording (72) said transaction in said memory of said data processing system if said transaction value is correct;  (h) record (84) said transaction value in said customer account for subsequent billing  (i) uploading said transaction data and said transaction value to a medium to be used for preparing said subsequent invoicing; and  (j) uploading to said data processing system a set of data and values.  13. Method according to claim 12, characterized in that it is to be implemented in an apparatus (Fig. 1) for postage, accounting and billing of postal services which comprises:  (a) data processing means (12) for recording customer accounts, account data, and calculating values for postage prepaid under the control of an application program, said programming evaluating discounts and / or increases on an automatic basis as required  (b) a weigh scale (26);  (c) at least one postage meter (32 a to n) and at least one corresponding postage meter base (34)  (d) a display (14);  (e) a means of containment to retain and / or secure the species;  (f) a printer (28) ;;  (g) a keyboard (24) for entering data into said data processing means (12);  (h) memory means (30) included in said data processing means for recording and maintaining said account for subsequent billing; and  (i) a modem (22).  14. Method according to claim 12 characterized in that  said downloading is accomplished using a modem (22) which is operatively connected to said data processing system and  said downloading of the system is carried out to a second data processing system.  15. Method according to claim 12, characterized in that  said set of data or downloaded values consists of a list of rates or rate updates previously downloaded, or consists of an additional postage value to be added to the postage meter for postage.