Track shipping insurance claims from lost parcel to final recovery

The claim schedule should connect the customer order, outbound shipment, customer remedy, inventory consequence, claim filing, carrier decision, and cash recovery. It should not assume that one amount proves another.

Build the population from shipments with loss, damage, shortage, or delivery-dispute statuses. Include the order number, tracking number, carrier, ship date, expected delivery date, last scan, destination, declared value, coverage type, and date the issue was reported. Keep claims that were never filed in the population so management can see missed filing opportunities.

Reconcile the list to customer-service cases and refund or replacement records. A claim export alone omits parcels that operations identified but did not submit. A refund export alone includes service remedies unrelated to covered shipping loss. The tracking number and order number provide the bridge between them.

Preserve carrier scan history or proof of delivery as it existed when the case was opened. A later status update may resolve the shipment, but it should not erase why support issued a refund or why the business filed a claim.

Record whether the customer received a refund, replacement, partial credit, or another approved remedy. Capture the approval date, amount, payment or credit reference, replacement order, and related shipping cost. This customer action may occur before the carrier accepts liability.

A replacement shipment has its own inventory and freight records. Link it to the original order but do not fold the second shipment into the claim receivable. If the original parcel is later delivered, record how operations handled the recovered item or duplicate delivery rather than deleting the original loss case.

Consider an insured parcel containing several items where only one item arrived damaged. The customer may receive a partial refund while the claim includes merchandise value and a portion of freight. The schedule needs line-level support for the affected item and should leave unaffected order value outside the claim calculation.

The claim record should show required documents and their status. Typical evidence includes the sales invoice, proof of value, tracking history, photographs, packaging evidence, customer statement, repair estimate, and proof of the refund or replacement. Record the filing deadline from the applicable carrier or policy terms and assign an owner.

Do not mark a claim filed because documents were collected. Store the submission date, claim number, amount requested, submission confirmation, and the exact evidence sent. If the carrier requests more information, add the request date, response due date, response date, and document link.

Use a status sequence that reflects the external process: evidence gathering, ready to file, submitted, information requested, accepted, partially accepted, denied, appealed, paid, or closed. This makes overdue actions visible without treating every open case as the same problem.

Build the claim request from documented components. Show merchandise cost or other approved value basis, covered freight, deductible, coverage limit, exclusions, and any noncovered amount. Link the calculation to policy terms and source documents.

The customer selling price, inventory cost, declared value, and insurer recovery can all differ. Keep them in separate fields. The offshore preparer can assemble and recalculate the amounts under an approved method, while management decides the accounting policy and any interpretation of coverage.

When the filing amount differs from the customer's remedy, include a short explanation. A replacement may cost less than the original sale price. A partial refund may address customer service concerns beyond physical damage. The claim may be capped. Those differences should remain visible rather than forced to reconcile.

When the carrier accepts, reduces, or denies a claim, retain the decision notice and compare each approved component with the request. Record denial reason codes in plain language and assign the next action. Missing packaging evidence calls for a different response from a filing-deadline denial or a coverage exclusion.

An appeal should create a dated event on the same claim, with the amount contested and the additional evidence supplied. Do not replace the first decision with the appeal status. The history lets a reviewer see how the final result developed.

If management records a receivable, link it to the approved evidence and posting reference. A submitted claim or optimistic support message is not the same as accepted recovery. The controller retains the decision about recognition, measurement, allowance, and write-off.

Match payment using claim number, carrier remittance, amount, and deposit date. If several claims are paid together, allocate from the remittance detail. Do not distribute a batch payment in proportion to requested amounts unless management approves that method and no better evidence exists.

Show gross approved recovery, deductible, fees, offsets, and net cash separately. A net deposit may settle the claim while concealing why cash differs from the accepted amount. Tie the posting to the correct entity, bank account, and ledger account.

Age unpaid accepted claims from the promised or expected payment date and unresolved filed claims from the next action due date. Use separate queues for missing evidence, carrier response, appeal, payment, and accounting approval. Updating a note should not reset age.

Before closing a case, confirm the customer remedy, inventory impact, claim decision, cash recovery, and ledger posting. State why any difference remains between the business loss and carrier recovery. Archive the source pack, correspondence, approvals, remittance, and posting support together.

The monthly review packet should show cases opened, claims filed, amounts requested, accepted recoveries, denials, cash received, missed deadlines, and open actions. These are process measures, not predictions about future recovery. Management reporting support can carry the approved results into the close packet.

An offshore bookkeeper can maintain the case register, index evidence, prepare claim calculations under approved rules, match decisions and payments, and verify postings. Client management retains coverage interpretation, customer remedy policy, recognition, estimates, appeals, write-offs, and final approval. Bookkeeping services can support the recurring preparation under that division of responsibility.

• U.S. Small Business Administration, Manage your finances
• IRS, Recordkeeping