Returned and Incorrect Parts Log

This log is used to record returned parts, incorrect parts, and core returns tied to a repair order. It captures the vendor, invoice, return authorization, shipping details, credit status, and ledger posting in one place. That makes it easier to match the physical return to the expected credit and close the loop on accounting.

It is usually maintained by the parts coordinator, parts manager, or an operations admin who handles vendor returns. In smaller shops, the estimator or office manager may also update it when parts are returned or credits arrive. The key is to assign one owner so entries are consistent and follow-up does not get missed.

Update it as soon as a return is initiated, shipped, credited, or denied. Waiting until the end of the week often leads to missing tracking numbers, lost RA references, and credits that never get posted. For busy collision repair operations, same-day entry is the safest cadence.

Use it for incorrect parts, returned parts, and core parts that require a credit or reconciliation step. It is especially useful when the part must be shipped back to the vendor, when a core charge is involved, or when the shop needs proof that the return was accepted. If a part never leaves the shop and no credit is expected, it usually does not need a full return record.

Record the denial reason, the date you received the denial, and any supporting documents or photos that may help with the dispute. Then assign a follow-up action, such as re-submitting the RA, contacting the vendor rep, or attaching proof of condition at return. The log should make the dispute trail easy to audit later.

The template includes fields for expected credit, actual credit received, credit memo number, and whether the ledger was posted. That lets accounting compare what should have been credited against what actually posted. It reduces the chance that a return is completed physically but never reflected in the parts ledger.

Yes. You can add vendor-specific fields, change the return types, or include extra status values that match your workflow. If your shop uses conditional logic, you can show follow-up fields only when a credit is denied or a return requires additional action. Keep the form lean so it follows the minimum-necessary principle and does not collect fields you will not use.

Common attachments include part photos, shipping labels, RA confirmations, credit memos, and invoices. If your workflow supports it, link the log to your DMS, accounting system, or shared drive so the supporting documents stay attached to the same record. That creates a cleaner audit trail and makes retrieval faster during disputes or month-end review.

The biggest mistakes are skipping the original invoice number, forgetting the RA number, and not recording the actual credit received. Another common issue is using free-text fields for dates or quantities, which makes reconciliation harder later. It also helps to mark required versus optional fields clearly so the log stays usable in a busy shop.