What is EDI 867 Product Transfer and Resale Report?

Definition

EDI 867 Product Transfer and Resale Report is an electronic business document used by trading partners to communicate product movement, transfers, sales, and resale activity. It commonly supports supplier, distributor, retailer, and manufacturer relationships where a seller needs visibility into how products move through a downstream channel. The report can include quantities sold, transferred, returned, or otherwise reported during a defined period.

Unlike a purchase order or invoice, the EDI 867 focuses on reporting product activity after or during distribution. This information helps suppliers understand channel demand, reconcile reported quantities, support replenishment decisions, and align financial records with commercial activity.

How EDI 867 Works

The process begins when a distributor, retailer, or other trading partner collects product transaction data from its sales or inventory systems. The information is structured according to the agreed EDI 867 transaction format and transmitted electronically to the recipient.

The receiving system validates the document and maps relevant information into its ERP, order management, inventory, or financial systems. Product identifiers, quantities, dates, locations, transaction types, and trading-party information can then be used for reporting and reconciliation.

  • Product identification: Identifies the items being transferred, sold, or reported.
  • Transaction quantities: Communicates units associated with resale, transfers, returns, or other activity.
  • Dates and locations: Establishes when and where the product activity occurred.
  • Trading-party information: Connects reported activity with the relevant supplier, distributor, retailer, or customer.

Key Data Elements in an EDI 867

An EDI 867 can contain detailed information needed to interpret product activity accurately. The exact segments and values depend on the trading-partner implementation guide, but reports commonly identify products, quantities, transaction dates, units of measure, locations, and reference numbers.

For finance teams, these details provide a useful connection between operational activity and downstream financial records. Reported resale quantities can help support revenue analysis, inventory reconciliation, customer reporting, and settlement processes when the commercial agreement requires such information.

EDI 867 and Procurement Controls

EDI 867 data can complement procurement controls by showing what happened to products after they entered a trading network. Purchase orders establish expected purchases, while resale reporting provides additional evidence about subsequent product activity. Strong controls should connect requisitions, purchase orders, receiving information, and downstream transaction reports where appropriate.

Organizations can also incorporate Fraud Prevention in Purchase Orders | Secure Automation into broader procure-to-pay controls. Comparing authorized purchasing activity with product movement and resale information can improve spend visibility and help finance teams investigate unusual transaction patterns.

EDI 867 and Financial Workflows

EDI 867 reporting can feed financial processes that depend on accurate product activity. When resale or transfer information affects settlement, commissions, rebates, billing, or other commercial arrangements, timely reporting helps teams align operational records with accounting workflows.

Downstream processes may eventually involve invoice approval, particularly when reported activity supports an invoice, adjustment, or settlement calculation. Separating operational reporting from invoice authorization helps maintain a clear audit trail between the underlying transaction data and the resulting financial decision.

Payment controls also benefit from accurate transaction context. A Payment Approval process can use validated financial and commercial information before funds are released, while an Accounts Payable Payment represents the resulting settlement of an approved obligation.

Reconciliation, Payments, and Cash Flow

EDI 867 information can support reconciliation when reported product activity must be compared with invoices, settlements, inventory records, or cash transactions. Bank Reconciliation focuses on matching accounting records with bank activity, while EDI 867 provides operational evidence that can help explain the commercial activity behind financial transactions.

Payment operations can incorporate the same transaction evidence. Organizations managing payments can use validated transaction information to support payment scheduling and cash controls. Payment Approvals can apply contextual information to authorization workflows, while Fraud Prevention can complement transaction controls by checking payment-related anomalies, duplicate activity, and supplier or banking information.

Accurate timing also matters for cash flow. When reported product activity is available promptly, finance teams can improve visibility into expected settlements, working-capital movements, and treasury requirements.

EDI 867 and Electronic Payment Processing

Once commercial activity has been validated and the resulting obligation has been approved, organizations can connect payment workflows with their preferred payment method. Reconciliation Of Bank Statements can help match invoices and payment transactions against bank records, while Payment Processing By ACH can support electronic payment execution with appropriate file, access, and audit controls.

For supplier settlements, reviewing the reported transaction data alongside agreed payment terms can also help identify differences between expected and actual vendor payment timing. This supports better payment governance without changing the operational purpose of the EDI 867 report.

Business Uses and Best Practices

Organizations commonly use EDI 867 reporting to improve channel visibility, support inventory analysis, reconcile reported activity, and strengthen communication between trading partners. Its value increases when reported transactions are consistently mapped to product masters, locations, contracts, and relevant financial records.

  • Maintain consistent product identifiers across trading partners and internal systems.
  • Validate quantities, dates, units of measure, and transaction types before downstream processing.
  • Reconcile reported activity with inventory, sales, settlement, and accounting records.
  • Define clear ownership for exceptions, adjustments, and trading-partner inquiries.
  • Retain transaction records and supporting references for audit and commercial reconciliation.

Summary

EDI 867 Product Transfer and Resale Report provides structured electronic visibility into product transfers, resale activity, and related downstream transactions. By connecting operational reporting with inventory, procurement, reconciliation, approval, and payment workflows, organizations can improve transaction accuracy and strengthen financial reporting. Effective implementation depends on consistent data standards, validated product information, reliable system integration, and clear reconciliation procedures.