ASMART's recommended billing method is billing by the number of kilobytes (units of 1024 bytes or characters) in an ASCII/ANSI* text file. However, the following must be true:
The reasons for the steps above are to avoid a situation where transcription is done in a word processing file, complete with word processing only formatting (such as indents, bolds, underlines, etc.), and then saved as an ASCII text file for billing purposes only. If one where to do this, if would defeat the one to one correlation between the number of characters typed in an ASCII text file and the number of bytes the computer says are in the file.
Billing by this method offers the following advantages:
There is a one to one correlation between the number of visual characters plus spaces that appear on the screen or a printout of an ASCII text file and the number of bytes that the computer reports.
There is one exception, however, pressing the enter key (which generates a carriage return) creates two characters or bytes on a PC: a carriage return character followed by a line feed character. Therefore, every carriage return in a text file contains 2 characters or bytes. Since there are not very many carriage returns in a text file compared to the rest of the text, this is not a big issue for billing.
One of the best things about billing by the number of kilobytes in an ASCII text file is the fact that anyone, anywhere, can verify that the counts you came up with match theirs. Both your clients and your transcriptionists can now independently verify that are being billed or paid correctly and honestly.
Everything you ever wanted to know about
ASCII text files
Formatting and printing issues with ASCII
text files
*Note that wherever ASCII text is used, it also refers to ANSI (windows) text files also.