Choose the location and period first

Decide which sales destinations and dates you are preparing before exporting data from your sales system. The file must use the period required by the program you are reviewing. Keep the original export unchanged and note its source and export date so a reviewer can compare it with the imported records.

Prepare one row per product and destination

For each row, include the product SKU, quantity of sellable units, destination country, destination region, and transaction date. Use the same SKU that identifies the product in your catalogue. Use country codes such as US or CA and the real state, province or territory code. Do not replace destination detail with your head-office location or a national total when the reporting task needs destination quantities.

If your file contains transaction types, distinguish SALE, RETURN and ADJUSTMENT. Keep the original signs and amounts. PackageReports treats returns as reductions and uses the sign entered for adjustments; check unusual adjustments with your team. Avoid including packaging weight, sales dollars or case counts in a field that expects sellable-unit quantity.

Upload, map and validate the file

  1. In the workspace, open Imports & sales and start a Sales ledger import. Choose your CSV or Excel workbook and upload it for preview.
  2. Under Map your columns, connect the source columns to SKU, quantity, country, region and date. Map transaction type when it is present.
  3. Review the sample rows and the row errors. Check the source row and field named in each error. Correct the spreadsheet or mapping and upload it again; the import screen maps columns and does not edit source rows.
  4. Choose Validate mapping. Confirm the import only after required rows pass validation. Keep the original file available for later review.

Use the step-by-step sales import instructions for the full column mapping and error list. Re-importing the same file is detected by its file fingerprint, but still check that a new export is not a revised copy with changed rows.

Match products and reconcile quantities

After import, inspect the Sales ledger for rows marked Needs product match. Link each source SKU to the correct catalogue product before calculating. Investigate renamed SKUs rather than creating duplicate product records just to make an import match.

Then look for duplicate rows, missing destinations, mixed units, unexpected case quantities and returns that may have been counted twice. Confirm the total belongs to the chosen year and location. For example, 1,000 sale units and 20 returned units leave 980 net units. At 10 g of a component per unit, that is 9,800 g (9.8 kg) as a physical subtotal; the program's requirements determine whether and how it is reported.

Record corrections before running the calculation

When you correct a source file, resolve an SKU or explain an adjustment, keep the reason and supporting source with the decision. Have a second reviewer compare the reconciled destination total with the original export. If you change imported sales or packaging data after calculating, run a new calculation so it captures the corrected inputs.

Check coverage and review the output

A successfully imported ledger does not prove that every product is in scope or that a government report is ready. Check published location coverage and official sources before relying on a calculation. Follow the calculation-review checklist to trace its totals to sales, components and the requirement version. PackageReports prepares reviewable data; your organization checks current program instructions and submits through the required external channel.