Redacting Financial Documents Before Sharing

Redact Financial Documents: Remove Account Numbers and Tax IDs

Bank statements expose account numbers, balances, and spending patterns. Sharing an unredacted bank statement for a rental application, mortgage pre-approval, or legal proceeding discloses far more financial information than the recipient requires. Most verification purposes need only specific data points such as average balance or income level, not the full transaction history and account credentials.

Financial documents also contain routing numbers, which together with account numbers are sufficient to initiate ACH transfers in many jurisdictions. Redacting routing numbers, full account numbers, and SSNs before sharing any financial document limits exposure to credential fraud, regardless of the recipient's trustworthiness. The OCR Redactor processes all redactions locally with no upload.

What to redact on bank statements and tax returns

Bank statements typically display the full account number on every page header. Redact all but the last four digits, the widely accepted convention for account verification. Routing numbers appear alongside account numbers on check images within statements in both fractional form and the nine-digit MICR form along the bottom of the check.¹ The routing number alone is semi-public information because it identifies the bank rather than the specific account, but combining it with even a partial account number increases the risk of unauthorized ACH initiation, so covering both is the safer practice.²

Tax return and income document redaction priorities

Transaction descriptions can reveal sensitive spending patterns, ongoing subscriptions, or relationships you prefer not to disclose.³ For income verification, cover all transactions and leave only the opening balance, closing balance, and summary figures. Tax returns contain SSNs or EINs, full name, address, and complete income breakdown.⁴ Consequently, redact SSN, EIN, address, and any income sources not required for the stated purpose before sharing any tax document. CapyToolkit processes each page locally, so sensitive financial data never leaves your device during this workflow. For tax returns used in a divorce or custody proceeding, the required disclosure scope is typically limited to income and deduction totals, not the full attachment schedules that reveal business relationships and investment holdings.

Pay stubs and financial records for employment verification

Pay stubs contain employer name, employee address, Social Security number, gross income, net income, year-to-date totals, and payroll deduction details.⁵ For a rental application that requires income verification, the employer name, gross income, and year-to-date figures are typically the only required fields. Redact the SSN, home address, and any deduction detail that reveals medical, retirement, or other benefit elections not relevant to the inquiry. Building on this, if the purpose is only to confirm employment, further redact the income amounts entirely and leave only the employer name and employment dates visible. Adjust the disclosure to exactly what the recipient has a legitimate need to see.

Workflow for financial document redaction

Scan or photograph the financial document and save as JPEG. Drop it onto the OCR Redactor drop zone. After OCR completes, identify every sensitive field: account numbers, routing numbers, SSNs, EINs, balances (if not required), and address fields. Draw rectangles over each. Confirm in the text panel that those strings no longer appear as readable text in the export. Export the PNG. For multi-page statements, process each page individually and combine the exported PNGs into a single PDF using a local PDF tool. Yet the most important verification step remains visual inspection of the final PNG before sending, not just the text panel review, because OCR may not detect every field accurately.

Redacting brokerage and investment account statements for legal proceedings

Brokerage statements expose more than a simple bank balance. A single monthly statement typically reveals account number, account type, total portfolio value, individual holding names and quantities, cost basis per position, realized gains and losses, dividend and interest income, and transaction history for the period. In a divorce proceeding, personal injury suit, or business dispute where asset disclosure is required, the minimum necessary scope for a specific proceeding may require only the total portfolio value and certain income figures, not the full holding breakdown that reveals investment strategy and unrealized positions.

Redact individual holding names and quantities for positions not relevant to the proceeding, leaving only the portfolio total and required income lines. For tax-related proceedings requiring capital gains verification, leave realized gains and losses visible but cover unrealized position details and cost basis for non-relevant holdings. Draw rectangles over each individual position row in the holding detail section and each transaction line outside the relevant period, leaving summary totals visible. The OCR Redactor supports narrow rectangles that cover specific rows without affecting adjacent summary rows above and below.

Financial document redaction for due diligence disclosures

Business due diligence processes require disclosing financial records to prospective buyers, investors, or lenders who have signed an NDA but who are not yet authorized to see all details. A prospective acquirer performing due diligence on a target company may need to verify revenue and EBITDA figures without receiving the full customer list embedded in the revenue breakdown. For these situations, redact individual customer names and transaction amounts in accounts receivable aging reports while leaving the aggregate total visible. Redact individual vendor names and payment amounts in accounts payable records while leaving total liabilities visible. This selective disclosure allows financial verification without premature disclosure of customer relationships and vendor agreements that remain commercially sensitive until the transaction closes.

Checking for financial identifier patterns in the OCR text panel after redaction

After placing all redaction rectangles, use the OCR text panel to verify that no financial identifier patterns remain visible in the export. Search the text panel for nine-digit numbers (SSN format: XXX-XX-XXXX), sequences of eight or more consecutive digits (account numbers), and the routing number format (nine digits at the start of a line, which is the standard position on bank letterhead). The OCR text extraction may not capture every number accurately, particularly on older bank statement designs with compressed fonts or light toner, so visual inspection of the image remains the primary verification step. The text panel search supplements visual review by catching identifiers in regions where your visual sweep may have moved quickly.

For brokerage statements with CUSIP numbers (nine-character alphanumeric identifiers for each security holding), search the text panel for nine-character strings beginning with a digit followed by two letters. CUSIP numbers identify specific securities and may require redaction when the holding itself is sensitive. For statements with ISIN codes (12-character international security identifiers beginning with a two-letter country code), search for 12-character uppercase strings beginning with two letters. Both identifier types appear in holding detail tables and are small enough that OCR sometimes merges them with adjacent text, making visual confirmation of their absence in the exported image the necessary final check.

Organizing multi-document financial redaction sessions

Financial disclosures for proceedings and due diligence typically involve multiple document types processed in a single session: bank statements, brokerage statements, tax returns, pay stubs, and loan documents. Before starting, list every document and the specific fields to redact in each, based on the disclosure scope defined by the proceeding rules or the NDA. Process one document type at a time, applying the same field checklist to each instance of that type before moving to the next type. This batch-by-type approach reduces the risk of applying the wrong redaction scope to a document, because all instances of a given document type share the same redaction rules and your attention stays calibrated to that type's specific field layout during the processing run.

For very large productions, group documents by type before you open the tool at all. CapyToolkit's OCR Redactor redacts each image you drop in, so a written field checklist per document type keeps the disclosure scope consistent across every instance and makes it easy to spot a page that drifted outside its rules. Reconfirm the NDA or proceeding scope once at the start of the session, then apply the same rectangles to each matching page without re-deciding field by field, beginning with mask account numbers past four digits on every statement.

When to use this

Use this tool when submitting financial documents for rental applications, mortgage approvals, legal proceedings, or business due diligence where you want to limit disclosure to exactly the information the recipient requires.

Examples