IBM document processors
check processing peripheral for IBM mainframes
IBM manufactured and sold document processing equipment such as proof machines, inscribers and document reader/sorters for financial institutions from 1934 to 2005.
IBM and document processing
Prior to the introduction of computers, cheque processing was performed manually by each institution. IBM recognised the opportunity to automate this processing and began building machines for this purpose, starting with the IBM 801 Bank Proof machine in 1934. By eliminating hand written ledgers, the IBM 801 automated teller operations.
By the mid 1950s many banks began investigating the use of new technology to handle the ever growing volume of cheques that needed to be processed each day. As an example, Bank of America's checking accounts were growing at a rate of 23,000 per month and branches were forced to close their doors by 2 p.m. to finish the daily postings. In the United Kingdom, wages began to be paid by cheque. The number of cheques cleared by the central clearing house had grown from around 250 million in 1938 to around 320 million in 1951 and reached over 500 million by 1964.
A number of technologies were developed by companies like EMI in the UK (Figure Reading Electronic Device or FRED), and Compagnie des Machines Bull in France (CMC-7) to make cheques machine-readable by means of pre-printed characters or characters that were inscribed on the cheque when it was being proofed at the branch.
Begin with the source’s own compact description: “IBM document processors” is check processing peripheral for IBM mainframes. The dossier treats that line as a proposition to test through document, processors and check, not as a finished interpretation.
Why this record matters
The phrase “check processing peripheral for IBM mainframes” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jul 3, 2026. The linked authority identifier is Q5968666. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1934, 2005, 1938 and 1951.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “IBM document processors”, its source revision and the description used here.
- Expand the search: follow IBM document processors primary sources, IBM document processors archive and document research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “IBM document processors”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “IBM document processors” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.