| | 35 | <para> |
| | 36 | With the help of the <literal>unknown_billingcode</literal> directive in |
| | 37 | <filename>pykota.conf</filename>, you can decide what happens when a billing |
| | 38 | code is encountered when printing, and this billing code is not yet in |
| | 39 | <application>PyKota</application>'s database. Automatically adding it to |
| | 40 | the database is a common choice, which saves time for the <application>PyKota</application> |
| | 41 | administrator. |
| | 42 | </para> |
| | 43 | |
| | 44 | <para> |
| | 45 | Finally, the <literal>overwrite_jobticket</literal> directive in |
| | 46 | <filename>pykota.conf</filename> allows you to overwrite the job billing |
| | 47 | information at the latest stage of printing, for example if the application used to print |
| | 48 | doesn't allow end users to give a value to the billing code when submitting the print job. |
| | 49 | </para> |
| | 50 | |
