How to organize transaction records by counterparty for Bankruptcy Adversary Proceedings

Organize transaction records around stable counterparty identifiers, not vendor names alone. For each transaction, distinguish the contracting entity, invoice issuer, instructed payee, account holder, intermediary, and alleged beneficiary. Link those roles to bank records, accounting entries, agreements, and communications, then reconcile amounts and dates without converting accounting descriptions into legal conclusions. The deliverable is a counterparty transaction matrix supported by an identity register, source index, reproducible reconciliation, and assigned evidence gaps. Counsel can use it to test disputed relationships, focus discovery, and prepare transaction-specific witness questions.

When to use this workflow

Use this workflow when debtor records, counterparty productions, or bank exports identify transactions under inconsistent names—or group distinct entities under one vendor account. It helps debtor, trustee, and defense counsel separate records concerning a named adversary defendant from records concerning affiliates, collection agents, processors, or other recipients.

The scope is US federal bankruptcy adversary proceedings. Bankruptcy Rules 7026 and 7033–7037 incorporate corresponding Civil Rules governing discovery. Rule 9014 treats contested matters differently, including exceptions for specified Rule 26 disclosure and conference provisions unless ordered otherwise. Consult Bankruptcy Rules 7026–7037 and 9014, local rules, and case-specific orders. (uscourts.gov)

This is an evidence-organization workflow, not a determination of avoidance elements, transfer dates, or liability. Keep claim-specific legal analysis separate. Contractual relationships require examination of the actual language, governing law, facts, and transaction context.

What you need

Collect material that tests identity and transaction relationships rather than relying solely on the debtor’s vendor master:

• Matter boundaries: operative pleadings, named parties, disputed transactions, relevant orders, petition date, and counsel-approved review periods.
• Entity records: vendor masters, contracts, amendments, remittance instructions, account-holder records, and available name-change, assignment, or merger documents.
• Transaction records: native ledger exports, invoices, credits, payment batches, bank statements, remittance advices, refunds, reversals, and allocation schedules.
• Source context: document IDs or Bates numbers, custodians, systems, export versions, date coverage, filters, and field definitions.
• Known gaps: unmatched payments, disputed identities, missing attachments, contradictory account details, and incomplete production periods.

Retain originals and use controlled working copies. Preserve spreadsheet names, sheet names, row identifiers, and export settings. Record whether a source contains full account details or only masked identifiers; do not infer ownership from an incomplete account reference.

Use the template

Use the Bankruptcy Adversary Proceedings — Counterparty transaction matrix below. You can copy this table into your working document or spreadsheet.

Use one row per transaction-role relationship when multiple entities participate. Repeat the transaction ID, but designate only one row as amount-bearing for each actual movement of funds. An invoice row may show face value without entering the cash total. Link refunds and reversals as separate movements rather than silently netting them.

The entity ID points to an identity register containing full names, aliases, and supporting records. The role describes an evidenced function, not assumed liability. Label dates individually: invoice, payment initiation, bank debit, receipt, or posting.

Cite document pages or workbook, sheet, and cell ranges. Use evidence statuses such as “supported,” “provisional,” or “disputed,” with an explanation. Record currency, reconciliation reference, and review status within the relevant fields. Detailed calculations and mapping histories belong in linked workpapers, not crowded table cells.

Step by step

1. Define the transaction population and review question

Start with the pleaded dispute: were specified payments received by the defendant, an affiliate, or an intermediary? Identify the accounts, transaction types, and periods requiring review. Use the petition date as a reference point, not a substitute for counsel’s claim-specific timing analysis.

Explain why each transaction enters the population. Include potentially relevant returns, credits, and reversals. Keep an exclusion list identifying omitted records and reasons, so another reviewer can reconstruct the population. Distinguish transactions actually pleaded from additional records collected to explain them.

Record in the matrix: transaction ID, population basis in the issue field, initial amount, and supporting source.

2. Build an identity register before merging names

Assign stable entity IDs and map each source-system name to a proposed entity. Preserve trade names, former names, spelling variants, vendor numbers, and account references. Treat a shared address or similar name as a lead requiring verification.

Keep affiliates distinct. Where documents suggest a merger or assignment, record the document and applicable period without resolving succession or liability through the identity mapping. Maintain a change history identifying the previous mapping, new evidence, reviewer, and affected transaction rows.

Record in the matrix: entity ID, encountered alias, identity evidence, and unresolved matching question.

3. Separate transaction roles and account ownership

Identify the contracting party, invoice issuer, instructed payee, account holder, intermediary, and alleged beneficiary where sources permit. If roles coincide, show the evidence connecting them. If several entities appear, add linked rows rather than replacing one name with another.

Compare agreements and amendments with invoices and payment instructions. An agreement may identify the seller but does not itself establish receipt of a particular payment. Likewise, remittance instructions identify where payment was requested, not necessarily who owned the destination account or ultimately retained funds.

Keep provisional identities when ownership is unknown. Record an alleged beneficiary as alleged, not as an established recipient.

Record in the matrix: supported role, source citation, competing account, and evidence needed to connect roles.

4. Reconcile the payment chain without choosing legal dates

Trace bank movements to payment batches, ledger entries, invoice applications, and returns. Preserve initiation, debit, receipt, and posting dates separately where available. Do not relabel a bank debit as receipt by the defendant without supporting evidence.

Maintain a workpaper showing gross outflows, inflows, and unresolved differences. Document duplicate removal, fees, currency treatment, and any conversion method. A single payment may cover several invoices; several payments may satisfy one invoice. Preserve those allocation links rather than forcing a one-to-one match.

Assign only actual cash movements to cash totals. Accounting descriptions remain source labels, not conclusions about ownership, receipt, or avoidance.

Record in the matrix: amount, currency, totaling treatment, date types, reconciliation reference, and unresolved difference.

5. Test sources and preserve evidentiary gaps

Identify whether each proposition rests on a contemporaneous record, system export, witness account, or counsel’s inference. Check source coverage and extraction filters. Identify a custodian or witness who could explain account ownership, allocations, or export methodology.

Authentication and hearsay are separate questions. Evidence Rule 901(a) requires sufficient support that an item is what its proponent claims; indexing it does not supply that foundation. (uscourts.gov) Rule 803(6) separately sets conditions for qualifying regularly conducted activity records, including foundation and trustworthiness requirements. (uscourts.gov)

Preserve adverse evidence and contradictions. A ledger assignment inconsistent with payment instructions belongs in the matrix, not outside the review population.

Record in the matrix: exact source, evidentiary concern, potential foundation witness, and contradiction requiring review.

6. Turn unresolved relationships into targeted discovery

Group gaps by proposition: entity identity, account ownership, payment allocation, onward transfer, or refund linkage. Identify the record or testimony that would answer each question before drafting requests. A missing allocation schedule may justify focused follow-up rather than broad affiliate discovery.

Through Bankruptcy Rule 7026, Civil Rule 26(b)(1) limits discovery to nonprivileged information relevant to claims or defenses and proportional to case needs; discoverability does not require admissibility. Apply governing discovery orders. (uscourts.gov)

Keep privileged analysis separate from production-facing versions. Describe absent evidence as “not located in the reviewed production,” unless other evidence supports a stronger conclusion. Distinguish a proposed request from one actually served.

Record in the matrix: unresolved proposition, proposed source, request reference or proposed status, and responsible lawyer.

7. Validate and freeze the review version

Have a second reviewer test mappings, trace entries to originals, and reproduce totals. Review every high-consequence exception, including unidentified account holders, unsupported refund allocations, and transactions attributed to multiple defendants. Explain differences rather than forcing reconciliation.

Freeze a dated version with its identity register, source index, and calculation file. Preserve subsequent corrections in a new version. Before proposing an evidentiary summary, separately assess Evidence Rule 1006: it concerns voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates at a reasonable time and place. An internal matrix is not automatically such an exhibit. (uscourts.gov)

Record in the matrix: review status, correction-history reference, and owner of every remaining exception.

Worked example

Fictional scenario: Counsel for debtor Northbank Components LLC reviews payments alleged against defendant Alder Supply LLC. The debtor’s vendor master uses “Alder” for both Alder Supply LLC and Alder Receivables LLC. The records do not establish their legal relationship.

A supply agreement identifies Alder Supply as seller, and its invoice INV-208 directs payment to Alder Receivables. A payment batch references INV-208; the corresponding bank statement records a $96,000 debit. No account-holder confirmation or collection agreement has been produced.

The ledger also records a $24,000 credit under “Alder.” A later bank statement records an incoming $24,000 payment with an “Alder” reference, but no remittance advice identifies the sender’s legal entity or connects it to INV-208. All parties, documents, amounts, dates, and reviewers below are fictional; dates are in 2026.

The provisional P01 identifier prevents an unsupported assignment of the incoming payment to Alder Receivables. The matrix supports a $96,000 outflow and a separate $24,000 inflow, not a concluded $72,000 liability amount. Counsel should investigate ownership, agency, and allocation before attributing receipt to Alder Supply or treating the inflow as a refund of TX-01.

Common mistakes

• Grouping by vendor label: Replace name-only grouping with stable entity IDs and source-supported mappings.
• Equating payee instructions with receipt: Separate instructed payee, account holder, and actual recipient; identify missing settlement evidence.
• Counting every role row: Mark amount-bearing rows and reconcile cash totals against bank movements.
• Collapsing dates: Preserve distinct date types and assign legally operative date questions to counsel.
• Netting unexplained credits: Keep unallocated inflows separate until evidence supports the connection.

Final quality check

• Every transaction has a stable ID and documented population basis.
• Entity consolidations have supporting evidence; uncertain aliases remain provisional.
• Contracting, invoicing, payment, and intermediary roles are distinguishable.
• Source citations resolve to the exact supporting page, row, or cell.
• Totals reproduce without duplicated role rows or unexplained offsets.
• Adverse records, missing periods, and contradictory mappings remain visible.
• Evidentiary concerns and source coverage have been reviewed.
• Open issues are resolved or assigned to a reviewer with a defined next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, chronology, and deposition preparation capabilities can support counterparty-record review. Use chronology review to examine transaction sequences and trial preparation to develop document-backed witness questions. The matrix remains counsel’s work product; identity mappings, reconciliation, and legal conclusions require human verification. Book a demo to discuss this evidence-analysis workflow.

Frequently asked questions

Should each counterparty have a separate spreadsheet?

Prefer one controlled master matrix with counterparty-specific views. Separate files can hide shared transactions and inconsistent mappings. If separate workbooks are necessary, retain common entity and transaction IDs and a single reconciliation source.

How should payments through a processor be recorded?

Give the processor its own entity ID and role. Link the debtor’s debit to available settlement and allocation records. Leave receipt and retention unresolved where those records do not establish them; do not equate the processor with the merchant.

What if the ledger conflicts with the bank statement?

Preserve both and specify the conflict: amount, date, account, allocation, or status. Check batches, fees, reversals, and export coverage. Explain which proposition each record supports rather than silently selecting one as universally authoritative.

Can the matrix be shared with opposing counsel?

Prepare a separately reviewed version if sharing serves the matter. Check privileged analysis, confidentiality restrictions, source accuracy, and unresolved inferences. Identify whether the version is a discussion aid, discovery support, or proposed evidentiary summary; those purposes require different review.

Sources

• Federal Rules of Bankruptcy Procedure: Rules 7026–7037 and 9014, addressing adversary discovery and contested-matter distinctions.
• Federal Rules of Civil Procedure: Rule 26(b)(1), addressing discovery scope.
• Federal Rules of Evidence: Rules 901(a), 803(6), and 1006, addressing authentication, qualifying business records, and evidentiary summaries.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.