Run incoming and outgoing cheques through one controlled system. Read handwritten amounts, route exceptions to a named reviewer, hold post-dated items until their date, record returned cheques with their reasons, and keep an audit trail from capture to reconciliation. See the full requirements checklist.
99%+ extraction accuracy · Bank-grade encrypted storage · Hosted or on-premise · Trusted by hundreds of businesses
Cheque management turns every piece of paper into a record you can actually find. Snap or scan a cheque — incoming payment, outgoing supplier cheque, or anything in between — and the platform reads it automatically. Payee, amount, date, account, memo: all extracted, all searchable.
No more spreadsheets. No more flipping through binders. Just search for what you need — "Northwind, over $5,000, this quarter" — and find it in seconds.
The image is captured and the platform automatically picks out the key fields — no manual data entry.
Type what you're looking for. Filter by payee, amount, date, or status. Find it in seconds — even across thousands of cheques.
A cheque image proves what arrived. A controlled record proves who decided what, on which evidence, and when. Chequedb joins capture, extraction, review, approval, reconciliation and archive around that record.
The person who prepares or corrects an item is not the person who approves it. Both identities and the decision are recorded on the item.
Source image, extracted fields, reason code, correction, reviewer and timestamp stay on the same record, not in an email thread.
Received, in review, approved, returned and reconciled states each carry a named owner and an audit event.
Filter by cheque, account, amount, status, reviewer or event, then export the set for internal audit.
Register, route, store, report and reconcile every cheque, incoming and outgoing, without a spreadsheet or a paper ledger.
One central register for every incoming and outgoing cheque. Search, filter and open the full history of any item in seconds.
Route cheques for approval by amount, department or custom rule, with notifications and reminders that keep items moving.
Bank-grade encrypted storage with unlimited capacity for cheque images and data. Every view, edit and approval is logged.
Role-based permissions, from viewer to administrator, so each user sees and does only what their role allows.
Dashboards show cheque volumes, pending approvals, clearance status and trends as they happen.
Connect to banking partners for real-time status updates, automatic reconciliation and faster clearance information.
Paper ledgers and spreadsheets record that a cheque exists. A cheque management system controls what happens to it.
| Task | Manual register or spreadsheet | Chequedb cheque management system |
|---|---|---|
| Capture cheque details | Typed by hand from the paper item | AI-powered extraction with 99%+ accuracy, including handwriting |
| Store cheque images | Filing cabinets or shared drives | Bank-grade encrypted storage with unlimited capacity |
| Approve an item | Signature on paper or an email reply | Rule-based digital approval with maker-checker |
| Spot an error or fraud | Found at month-end, if at all | Amount mismatch, duplicate and forgery checks before approval |
| Track status | Phone calls to the bank | Real-time tracking, notifications and bank status updates |
| Hold post-dated cheques | A diary or a reminder in a calendar | Automatic hold until the cheque date, with a maturity list |
| Prove who did what | Initials in a ledger | Complete automated audit trail for every view, change and approval |
Clean reads move on. Anything uncertain stops in one queue with an owner, a reason code and the original image attached.
A captured cheque has different numeric and written amounts. The reviewer compares both fields with the original image, resolves the exception, and records the reason for any correction. The item then follows the configured approval workflow. The source image, correction, reviewer decision and later status changes stay attached to the same record for reconciliation and audit review.
Start with cheque image capture, then inspect extracted fields and validation signals. The management system handles the ownership, decisions and follow-up around those inputs.
The written and numeric amounts disagree, or the OCR cheque number disagrees with the MICR read. The reviewer sees both values beside the image.
Value bands, payee type or repeat exceptions send an item to a named approver, who sees the evidence and not just the total.
Missing endorsement, duplicate candidate, stale date, post-dated item and corrected field each carry their own reason code.
Cleared, returned, pending and exported states link back to the deposit or ledger reference in your own records.
Find items by extracted content, account, amount, status, reviewer or audit event.
Every view, change, approval, rejection, export and reconciliation is recorded with user, timestamp and before-and-after values.
The item pipeline itself, from image capture to posting, is covered on the cheque processing software page. Status across the register is covered on the cheque tracking page.
Status lists are easy. The control question is who moves an item from one state to the next, and what the record keeps when it moves.
| State | Owner | Evidence recorded |
|---|---|---|
| Captured | Capture channel or teller | Front and back images, capture source, user or device, timestamp |
| Extracted | System | Extracted fields, amount_match and post_dated flags, raw MICR read where supplied |
| In review | Operations reviewer | Reason code, conflicting values, reviewer identity |
| Corrected | Reviewer (not the approver) | Field-level before-and-after values and the correction reason |
| Approved | Approver named by rule | Approver identity, rule matched, decision and comment |
| Rejected or held | Reviewer or approver | Reason code and release conditions |
| Submitted to bank | Your banking integration | Submission reference and timestamp |
| Cleared | Bank status feed or advice | Bank reference, value date, matched deposit or ledger entry |
| Returned | Operations reviewer | Return reason from the bank, return date, next-action decision |
| Reconciled | Finance owner | Matched ledger reference, any difference and who closed it |
| Archived | Records owner | Retention period applied, export references, access log |
Bank integration feeds status and clearance updates into these states. Holds, clearing and funds availability stay with the bank.
Post-dated cheques are a working credit instrument in Gulf, South Asian and trade finance flows. The record has to show when an item becomes presentable, who holds it and what happens if it fails.
Keep the date printed on the cheque and the intended presentation date as separate fields, so neither overwrites the other.
List items by presentation date, grouped by counterparty, so the next items due are always visible.
The validation.post_dated flag lets a rule stop an item from moving on before its date, without waiting for a reviewer.
An item in dispute stays on hold with a reason code. Both the hold and the release decision stay in the audit trail.
When a counterparty replaces a cheque, link the new item to the original so the history reads as one case.
Post-dating has different legal effect in each country. Confirm the rule set with the bank for each account.
Check a single item with the post-dated cheque calculator. This is general information, not legal advice.
A returned cheque is a decision point, not just a status. Record the reason the bank gave against the original capture, keep the image beside it, and route the item to a reviewer with a defined next action.
| Return reason | Evidence to keep | Next action to record |
|---|---|---|
| Insufficient funds | Return reason and date, source image, extracted amount, account and payee | Representation date or escalation for collection, and who decided |
| Refer to drawer | Return advice, image, earlier returns from the same drawer | Contact the drawer, hold the item or start recovery |
| Signature differs | Image of the signature panel and the reviewer note | Escalate to signatory review rather than redepositing |
| Payment stopped | Return reason, stop instruction reference and date | Confirm the stop is still valid, then release, replace or recover |
| Post-dated, presented early | Printed date, intended presentation date, submission time | Re-queue for the correct date and record how the early presentation happened |
| Stale or out of date | Printed date, presentation date and the staleness rule applied | Return to the counterparty for a new cheque |
| Words and figures differ | Both amounts, image, any correction and its reason code | Resolve before any further presentation; never correct silently |
| Account closed | Return reason and date, image, earlier history | Escalate and flag the counterparty record |
| Duplicate presentment | Both item references, both submission times and capture sources | Suppress the second item and record why |
A returned cheque does not prove fraud. The record shows the reason received, the evidence held and the decision taken. Collection and legal action sit outside the portal.
Incoming capture gets the attention, but issued cheques carry their own loss exposure. They need a register that accounts for every leaf.
Cheque number, account, payee, amount, date and approving signatory, recorded when the cheque is issued.
Every leaf accounted for, with the reason and the reviewer. A missing leaf is an exception, not a footnote.
Record the stop instruction with reason, requester and date. In the United States a written stop-payment order lasts six months unless renewed (UCC 4-403).
Banks that offer positive pay match presented cheques against the list of issued items the account holder sends. India introduced a Positive Pay System for high-value cheques in January 2021. Confirm the file format with your bank.
Review outstanding items at a set age. In the United States a bank is not obliged to pay a cheque presented more than six months after its date (UCC 4-404).
Long-outstanding cheques eventually meet unclaimed property rules, which differ by jurisdiction. Keep the follow-up history on the item.
Payment release and account debits stay with the bank and your ERP. The portal holds the register, the evidence and the decisions.
A printed MICR line survives almost any system. A handwritten amount in words often does not. Chequedb reads handwritten amounts, payee names and dates with 99%+ accuracy, including cursive and colloquial forms like "twenty-five hundred".
Your scanner handles capture. Chequedb handles everything after: MICR normalisation, OCR and ICR field extraction, cross-checks, exception routing and the review queue. It works with desktop units, two-pocket production scanners, ATMs and kiosk devices.
USB scanners for branch or back-office use, returning an image and MICR string per item through TWAIN or ISIS drivers. Includes the Rototype DAB-8000 and Epson check scanners.
Multi-pocket units with accept and reject sorting for high-volume back offices, such as the Digital Check SmartSource Professional. Other multi-pocket units connect through the Chequedb SDK.
Departmental batch scanners and self-service ATM and kiosk capture devices, connected over Ethernet or USB to the platform API.
The scanner captures front and back images and reads the MICR line, where the device has a read head.
The Chequedb SDK or REST API receives the images, MICR string and job identifier.
MICR and OCR reads are cross-checked to flag altered MICR lines or mismatched amounts. Confident items post; mismatches go to review with a reason code.
Native support covers the Digital Check CheXpress CX30, TellerScan TS250 and SmartSource Micro Elite, and the Panini Vision X. See the Rototype DAB-8000, Epson check scanners and Digital Check SmartSource Professional for other compatible devices.
Chequedb syncs extracted cheque data, approval status and audit events into the finance systems your team already runs, including SAP, Odoo, QuickBooks, Xero and custom ERP workflows through the REST API. Integration supports idempotent posting, control totals and audit trail sync for multi-entity groups.
Agree which fields, review states and reason codes the finance system receives, and which reference joins the two records.
Retries and lost replies are checked against the item reference before resubmission, so a cheque is not posted twice.
Batch count and value totals travel with each export, so a partial transfer is visible rather than silent.
The workflow changes with where the cheque enters and who is allowed to decide.
High volume, branch and back-office capture, maker-checker at scale and reconciliation against clearing output.
Several entities through one queue, with approval rules per entity and consolidated reporting for group finance.
Customer cheques in, supplier cheques out, month-end matching to receivables and payables, and evidence for the auditor.
If the record cannot answer these, the cheque workflow is not under control.
Approver identity, role, timestamp and the evidence in front of them at the time.
Field-level before-and-after values, who changed them and the reason code.
Items past their date or past expected clearance, with owner and last action.
The reason received from the bank, the reviewer decision and any replacement that followed.
Views, searches and exports are part of the trail, not just edits.
Image, fields, decisions and events exported together for internal audit.
Paper registers usually fail these tests on completeness, not intent.
The preparer cannot approve. Retest the rule after every role change, not only at go-live.
Corrections add a new event with before-and-after values. In the United States, 18 U.S.C. 1519 (Sarbanes-Oxley section 802) makes falsifying or destroying records in a federal matter an offence.
Group returns and mismatches by reason, payee and branch, so a repeating cause is fixed rather than reviewed again and again.
Agree the retention period with the bank, auditor and local rules, then apply it to images, fields and the audit trail together.
Screen a single cheque before it reaches the review queue, then apply the same rule to captured items in the portal.
Calculate the configured expiry date and days remaining from the cheque date.
Compare the cheque date with the presentation date and flag a stale item.
See whether a cheque is post-dated and how many days remain until its date.
Each page covers one part of the cheque workflow.
Join hundreds of businesses that have transformed their cheque operations with Chequedb. Bring your scanner, review queues and audit requirements to one walkthrough. Sample cheque images and a review policy are enough to start.