Logistics and distribution
How long must distributors keep sales, inventory and purchasing records?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Distributor record retention has no single legal number: each sales, inventory and purchasing record must be kept for the longest period set by tax rules, contracts, product liability exposure, lenders and any legal hold. Map every record family to its drivers, confirm the periods with your tax adviser and counsel, and destroy records only once no driver still requires them.
Key takeaways
- The longest applicable driver sets the retention period, so one record can outlive the rule that first required it.
- Sales tax exemption certificates, inventory valuation workpapers and lot traceability records are the ones most often discarded too early.
- Legal holds, open audits and open claims suspend deletion regardless of the schedule.
- Retiring an ERP is a retention decision; keep a readable archive, not just a database backup nobody can open.
The short answer#
Distributors must keep sales, inventory and purchasing records for as long as the longest rule or obligation that applies to each record. Federal and state tax rules set a floor tied to how long a return can be examined, contracts and statutes of limitations add their own periods, and product liability exposure can run longer still for traceability records.
The federal income tax floor is the clearest starting point. The IRS says to keep records that support income, deductions or credits until the period of limitations for that return runs out: generally 3 years, 6 years if unreported income exceeds 25% of the gross income shown, and 7 years for a bad debt deduction. Records relating to property, such as warehouse equipment and racking, are kept until the limitations period expires for the year the property is disposed of, so asset files can outlast almost everything else.
Because the other drivers differ by state, product line and contract, a single company-wide number usually fails somewhere. The practical answer is a schedule by record family, with each period confirmed by the people who carry the risk.
This is general information, not tax or legal advice. Retention periods depend on your states, products, contracts and filings, so confirm each period with your tax adviser and counsel.
The three drivers: tax, contracts and product liability#
Tax, contracts and product liability are the three drivers that set most distributor retention periods. Lenders, insurers and privacy laws add further conditions, but these three decide the baseline.
Use the table as a checklist for the conversation with advisers, not as a source of periods.
| Driver | What generally sets the period | Records most affected | Who confirms |
|---|---|---|---|
| Income tax | The IRS period of limitations: generally 3 years, longer in the cases the IRS lists, and until the disposal year closes for property records | Invoices, vendor bills, inventory valuation, fixed asset files | Tax adviser |
| Sales and use tax | Each state's audit lookback and its rules on exemption and resale certificates | Exemption certificates, taxable sales detail, use tax accruals | Tax adviser |
| Contracts | State statutes of limitations and audit clauses in customer and supplier agreements | Customer contracts, pricing agreements, POs, rebate claims | Counsel |
| Product liability and recalls | Exposure for the products you sell and any industry rules on traceability | Lot and serial records, supplier certifications, returns and warranty files | Counsel and insurer |
| Unclaimed property | State lookbacks on uncashed checks and unapplied credits | Customer credit balances, vendor credits, AP and AR ledgers | Tax or unclaimed property adviser |
Retention by record family#
Retention by record family is how most distributors turn drivers into a usable schedule. Group records by what they are, not by which system holds them, because the same invoice may sit in the ERP, the EDI archive and a scanned document store.
The rows below show the drivers that typically apply. Fill in the period column only after advisers have confirmed it.
Three families are lost most often. Exemption certificates get overwritten when a customer sends a renewed one, valuation workpapers live in a controller's personal spreadsheets, and lot records sit in a WMS whose purge setting nobody has checked. Give each of them a named home and an owner.
| Record family | Examples | Drivers that usually apply |
|---|---|---|
| Sales | Quotes, sales orders, invoices, credit memos, proof of delivery | Income tax, sales tax, customer contracts |
| Tax documents | Exemption and resale certificates, tax rate overrides | Sales and use tax, often the longest of the sales records |
| Purchasing | Purchase orders, receipts, vendor invoices, three-way match records | Income tax, supplier contracts, use tax |
| Supplier programs | Rebate claims, special pricing claims, co-op fund records | Supplier agreement audit clauses, income tax |
| Inventory | Cycle counts, physical counts, adjustments, valuation workpapers | Income tax and inventory method support, lender audits |
| Traceability | Lot and serial records, certificates of conformance, recall notices | Product liability, customer requirements, industry rules |
| Returns and warranty | RMAs, inspection notes, warranty claims, supplier returns | Product liability, supplier agreements, income tax |
Events that override the schedule#
Some events stop deletion no matter what the schedule says. A records schedule should name them and say who can lift a suspension, because automated purges in an ERP or document system will otherwise run on time.
Check for these before any purge or system retirement.
- Litigation holds, including threatened claims from customers, suppliers or former employees.
- Tax audits or notices that are open, and tax years still open to examination.
- Open freight claims, warranty disputes and supplier chargebacks.
- Lender field exams and borrowing base reviews in progress.
- Unclaimed property reviews or voluntary disclosure work.
- Acquisition or financing diligence where records have been requested.
How to build a schedule a CFO can defend#
A defensible schedule is short, specific and actually followed. Most problems come from schedules that list periods nobody enforces, or from systems that purge on their own settings regardless of policy.
Work through these steps with the controller, IT and outside advisers.
- Inventory record families and the systems that hold each one, including email and scanned documents.
- List the drivers for each family and get the period confirmed in writing by the right adviser.
- Check each system's own purge and archive settings against the schedule.
- Name an owner for legal holds and for approving any deletion.
- Plan for system retirements: export to a readable archive with indexes, and test that records can be found.
- Review the schedule when you enter new states, product lines or customer programs.
Illustrative: an electrical distributor retires its legacy ERP#
Illustrative: a fictional electrical distributor is moving from a legacy ERP to a cloud ERP. The legacy system holds many years of sales orders, purchase orders, special pricing claims, lot records for wire and cable, and RMA history. The vendor offers a database backup, but nobody on staff could read it without the old software.
The CFO maps record families to drivers with the tax adviser and counsel, finds that exemption certificates and traceability records need the longest retention, and has IT export the legacy data into readable tables and documents with an index by customer, supplier and date. Records under an open warranty dispute are flagged with a hold.
Because the history is preserved in usable form, the company can later decide whether parts of it are worth assessing for licensing, instead of losing the option at cutover.
Retention, deletion and data licensing#
Retention and data licensing interact in two directions. Records a company is required to keep may also be records it can license, if rights allow, and records kept only for value still have to respect privacy commitments and any obligation to delete personal information that is no longer needed.
A licensed copy does not extend how long a company may keep personal information, and records under a legal hold are usually left out of scope until the hold lifts. SourceX reviews those limits in the Rights step of the SourceX five-step transaction, and the SourceX Evidence Packet records the retention and privacy basis for what was delivered.
Frequently asked questions
Can we keep records only in electronic form?
Usually electronic records are acceptable if they are complete, accurate, readable and retrievable for as long as they must be kept. Scanned paper and system exports both qualify in many cases. Confirm the requirements that apply to your filings with your tax adviser before destroying paper originals.
Do emails with customers and suppliers need to be kept?
Emails that form part of a contract, a price agreement, a claim or a dispute generally follow the retention of that record. Routine email can follow a shorter policy. The risk is that the important messages sit in personal mailboxes, so the policy should say where record emails are filed.
Do retention rules differ by state?
Yes. Sales and use tax lookbacks, statutes of limitations for contract claims and unclaimed property rules vary by state. A distributor selling into many states usually adopts the longest period that applies to a record family rather than tracking each state separately.
Must records be destroyed when the period ends?
Not always, but holding records forever has costs: storage, discovery exposure and privacy risk for personal information. Many companies delete on schedule, de-identify what they keep for analysis, and document both decisions. Whatever the choice, apply it consistently.
Does an old ERP have to stay running to meet retention?
Not necessarily. Many companies export legacy data into readable files or a low-cost archive with search, then retire the system. The test is whether a specific invoice, PO or lot record can be found and produced when an auditor or court asks. For tax purposes, the IRS's Rev. Proc. 98-25 covers machine-sensible records: it lets a taxpayer request a Record Retention Limitation Agreement to limit which such records must be kept, and it requires prompt notice and a replacement plan if they are lost or destroyed. Ask your tax adviser whether it applies before decommissioning.
Sources
- Keep records supporting income, deductions or credits until the period of limitations runs out: generally 3 years, 6 years if unreported income exceeds 25% of gross income shown, 7 years for a bad debt deduction; property records until the limitations period expires for the year of disposal. Source
- Rev. Proc. 98-25 lets a taxpayer request a Record Retention Limitation Agreement for machine-sensible records and requires prompt notice and a replacement plan if such records are lost or destroyed. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.