Material returns and supplier credits: close the loop after pickup

Define the endpoint before marking a return complete

A returned box can disappear from the site while its financial follow-up remains unresolved. The field may know a driver collected it, purchasing may be waiting for supplier acceptance and accounts payable may not have a credit reference. If each team uses “returned” to mean something different, the shared register can look finished before anyone has reconciled the outcome.

Define the endpoint for your control process. It may require an agreed disposition, a supplier credit memo and confirmation in the appropriate account record, with any difference resolved by the responsible reviewer. Keep physical movement and financial reconciliation as separate states. This gives each team a clear task without asking a pickup photo to prove an accounting event.

Download the blank return-to-credit CSV near the top of this page. It is free and requires no signup. The worksheet provides a starting column set, while the fictional example below shows the intermediate decisions and open items. Adapt the fields and review responsibilities to your actual purchasing, supplier and finance process.

Confirm what is being returned and who controls it

Identify the project, purchase order and line, supplier item reference, quantity, unit and physical location. Check whether the material belongs to the company, another contractor, the owner or another party before arranging its disposition. A surplus item at your jobsite is not automatically yours to return for a credit.

Connect the item to its original receiving and purchasing records. An invoice description may use a different unit or shorthand from the field label. Resolve the match before asking the supplier to collect it. If some units were installed, transferred, damaged or already returned, show the remaining quantity rather than assuming the original purchased amount is still available.

Include the material's reported condition and supporting photos where appropriate. A field description can start the request without establishing that the supplier will accept it. Record uncertain identity, packaging or condition as an open question. The next responsible person should see what needs confirmation rather than inherit a completed-looking return line built on assumptions.

Record the actual return authorization and terms

Ask the supplier to confirm the specific item, authorized quantity, destination, reference and agreed disposition. Preserve any stated charge or condition in the source communication. Keep a proposed return separate from an accepted request. Do not use a standard spreadsheet percentage as proof that a restocking charge or credit amount applies to this transaction.

For the worked example, fictional return RT-08 covers material with an agreed gross return value of $1,500 and an agreed $150 restocking charge. Assume the appropriate reviewer confirmed those teaching inputs from the example's supplier response. The expected net credit is therefore $1,350. These values are invented; they do not describe a standard supplier policy or a customer result.

If the reply authorizes only part of the requested quantity, update the authorized portion while keeping the remainder open. Name the person responsible for the difference. An authorization reference alone is not enough if the receiving team cannot identify which material it covers or which conditions the supplier expects before issuing a credit.

Separate a planned pickup from the supplier commitment

Use different fields for your requested pickup date, the supplier's confirmed date and the actual collection. In RT-08, the team initially plans for Friday, but the supplier later confirms Monday. The Friday plan should not continue to appear as a verified commitment. Keep the response and confirmation date beside the current expectation.

Give the pickup coordinator the current location, receiving contact, unit or package identity and authorized quantity. If material moves to another staging area, update the collection instructions and preserve the change. A repeated reminder containing an obsolete location can add work without making collection more likely.

After pickup, retain the available collection reference and the quantity reported as removed. Record who supplied the account and any limitation. A signed carrier slip or photograph can support the physical event, but it does not by itself establish the supplier's accepted quantity, credit memo or account posting. Those remain separate follow-up tasks.

Obtain supplier receipt and resolve quantity differences

Ask for the supplier's receiving or acceptance reference under the agreed process. Compare it with the authorized material and the collection account. A driver taking the carton establishes a different event from a supplier confirming its contents and condition. Keep the references linked so the office can follow the same return through both handoffs.

Test a partial acceptance. If the supplier reports fewer acceptable units than the field says were collected, preserve both accounts and assign a clarification. The register should identify the disputed quantity and its sources. Do not silently replace the field quantity or assume the supplier is wrong merely because the expected credit was larger.

Existing procurement tools already serve parts of this workflow. Kojo's official field page advertises managing returns and recording delivery evidence. That is an established option to evaluate, not evidence that every return automatically produces a reconciled credit. Ask any proposed system to demonstrate the exact collection, acceptance and financial handoffs your team needs.

Sources: Kojo official field workflows: returns and delivery evidence

Reconcile the expected value, memo and posted amount

Continue RT-08 with a credit memo for $1,300, while the expected net credit remains $1,350 and no posting has yet been verified. There are two distinct issues: a $50 difference between the expectation and memo, and a $1,300 memo still awaiting confirmation in the account record. Calling the return recovered would hide both questions.

The table shows a control example rather than a required accounting treatment. Have the responsible finance reviewer identify the appropriate records and the point at which an amount is counted as posted in your process. Preserve the actual reference and review decision. Do not classify a supplier promise or an unverified note as an applied credit simply because it includes a number.

Once a $1,300 posting is verified in this example, the expected-versus-posted difference becomes $50. Keep that difference open until the reviewer confirms its explanation or agreed adjustment. A charge dispute, accepted quantity change or data correction requires its own source. Do not automatically write off the difference just to make the register balance.

Use the blank worksheet as a shared handoff record

The CSV starts with return identity, project, purchase-order line, item and unit. It then separates requested and authorized quantities, the authorization reference, planned and confirmed pickup, the return receipt, expected net credit, memo and posted credit. The final fields identify the difference and next responsible action. All response cells start blank.

Use a stable return identifier across communications and records. Keep source references concise but usable by the people who need them. Avoid putting private documents in unrestricted links simply to make the sheet convenient. The authorized reviewer should be able to locate the evidence without exposing unrelated project or supplier information.

Do not combine several uncertain events into one free-text status. A short status can summarize the row, but the underlying source fields should still explain what occurred. If your team needs a history, retain dated changes or a separate event log. This lets another coordinator distinguish a revised supplier commitment from a new physical collection or a later accounting correction.

Follow up on the missing event rather than the whole return

Assign a question that the recipient can answer. Purchasing may need the supplier's accepted quantity. A warehouse coordinator may need a pickup reference. Finance may need the credit memo or posting evidence. “Any update on the return?” is less actionable than a request that identifies the missing event and the source you need.

For RT-08, ask the supplier to explain the $50 memo difference and ask the finance owner to confirm the $1,300 account posting separately. Keep each answer linked to the return identifier. One response may resolve a quantity question while leaving the financial application open. The shared register should preserve that distinction.

Agree how reminders change when the state changes. Stop requesting a missing memo once the correct memo has arrived, and route the remaining reconciliation question to the appropriate owner. A general reminder that ignores the latest response can frustrate the supplier and leave the office rebuilding the thread by hand.

Review the outstanding list with purchasing and finance

At a regular review, distinguish material awaiting authorization, pickups without confirmed commitments, collected returns without acceptance, memos without posting evidence and unresolved value differences. Summarize counts and amounts according to those meanings. Avoid labeling every expected credit as an already recoverable balance when its authorization or accepted quantity remains uncertain.

Reconcile the active list to resolved items and new requests. Explain why an item closed, which source supports the disposition and who reviewed it. If an expectation changes, retain the reason rather than overwriting the original amount without context. This makes the report useful when another person later asks why the supplier's statement differs from the initial estimate.

Measure the work your team wants to improve: missing confirmations, unresolved differences and time spent reconstructing return history. Use your own baseline when evaluating a system. A cleaner worksheet can help coordinate the process, but it does not establish a guaranteed recovery amount or show that every financial difference was caused by a supplier error.

Automate confirmation collection with review at the financial handoff

Start with a narrowly defined follow-up: collect the supplier authorization, confirm a pickup commitment or request a missing memo reference. Preserve the original response beside any summary and route ambiguous answers to a person. Keep the actual posting or adjustment decision within the financial review process your team authorizes.

Test the proposed workflow with a changed pickup date, partial acceptance and the RT-08 memo discrepancy. Ask whether it maintains the correct current state without losing history or creating duplicate requests. Record which steps remain manual and who receives a failed message or inaccessible attachment. The exception path matters as much as the clean demonstration.

Bring one redacted return packet to a Buildalytic demo: the request, supplier reply and unresolved credit question. Its custom-workflows offering provides a starting point for coordinating follow-up around existing purchasing and finance tools. Ask to map the missing event, responsible person and source-preservation path, then confirm the implementation scope before rollout.

Sources: Buildalytic custom workflows