Reconcile a company-store invoice by matching each charge to an approved order, the supplier’s agreed billing milestone and any related credit—not by expecting the store’s sales total to equal the invoice. Keep merchandise, decoration, freight, service fees and refunds identifiable. Carry unresolved differences forward with an owner and supporting evidence rather than hiding them in an adjustment.
This is a month-end operating guide for the person who must explain a merchandise bill. It addresses a different decision from setting employee allowances: once orders exist, which charges are supported, which are timing differences and which need correction before approval?
Brand Sauce publishes this guide and provides company-store services. The reconciliation design below is our editorial recommendation, not a claim that every field or automation is available in a particular store. Confirm reporting, billing terms and exception handling during scoping. Platform examples use current Shopify documentation checked October 1, 2026; they do not establish how your Brand Sauce program is configured.
Start with the billing event, not the dashboard total
Ask the supplier to state when an item becomes billable: order acceptance, production release, shipment or another contracted milestone. Then confirm what counts as evidence of that event. A purchase order authorizes spending; a shipment record documents fulfillment activity; an invoice requests payment. They answer different questions.
For example, an order accepted on September 30 might ship in October. Under order-based billing it could appear on September’s invoice; under shipment-based billing it might not. Neither treatment is automatically an error. The exception is a charge that conflicts with the agreed basis or lacks the required evidence.
Write a one-page billing map before the first close. Include cutoff time and time zone, invoice frequency, treatment of partial shipments, decoration/setup charges, freight adjustments, taxes as invoiced, deposits, credits and payment terms. Have finance determine accounting treatment separately; this operational match should not silently become a policy for expense recognition or tax handling.
Use four connected records
A useful reconciliation needs more than an order spreadsheet. Build the following four views, even if they are simply separate tabs in a controlled workbook.
| Record | What it answers | Essential reference |
|---|---|---|
| Approved orders | What did we authorize, for which program? | Store/order ID, line ID, quantity, agreed price, cost center |
| Billing milestones | What became billable under the terms? | Order line, event type, date, quantity, evidence link |
| Invoices and credits | What did the supplier charge or reverse? | Supplier, document number, line reference, currency, amount |
| Payments and open items | What has been settled, and what remains unresolved? | Payment reference, applied invoice/credit, open balance |
Use a stable match key such as supplier plus store plus order ID plus line ID. An employee name is not a reliable key: names can repeat, and one employee can place several legitimate orders. Preserve the original identifier when a replacement is created, but give the replacement its own record and reason.
Keep invoice-level service charges in a separate section rather than assigning them to an arbitrary merchandise line. If you allocate those charges to departments, document the allocation rule and reconcile the allocated sum to the original charge. An allocation changes ownership of a cost; it does not create another supplier charge.
Check the export’s shape before summing it
Shopify’s order-export documentation explains that additional items in one order occupy additional rows, with many order-level fields left blank. It also lists separate financial and fulfillment fields, shipping, taxes and refunded amounts. This is a useful reminder to establish what one row represents before using spreadsheet totals.
Ask for a sample containing a two-item order, a partial refund and a split shipment. Mark each column as order-level, line-level or transaction-level. Sum each amount only at its proper level. If your reporting tool repeats a whole-order shipping charge on every line, multiplying or summing those rows can overstate freight. If blanks mean “same order,” preserve that relationship without copying the order total into every row and then adding it again.
Store the original export unchanged and work from a copy. Record its generation time, filters, currency and date basis. Before matching money, compare distinct order counts and line counts against the source view. A missing page of orders or an unintended status filter can produce a perfectly tidy but incomplete reconciliation.
Do not use one status as proof of everything
Shopify distinguishes payment, fulfillment and return statuses. Its documentation also notes that a canceled order may still require work if it has not been fully refunded. For your reconciliation, maintain separate columns for the commercial decision, fulfillment event and financial outcome.
“Canceled” is therefore a prompt to inspect the remaining charges, not an instruction to delete the order. Similarly, a requested credit is not an issued credit, and an issued credit is not necessarily cash returned. A replacement shipped without a charge should not be counted as another paid gift just because it has a new order number.
Define the evidence needed to clear each condition. A support message promising a refund belongs in the pending-credit queue. The issued credit document belongs in the invoice match. Payment evidence closes the cash question. Keeping those stages distinct makes follow-up specific: the team knows whether it needs a supplier decision, a document or settlement confirmation.
An illustrative invoice bridge
The following numbers are invented to demonstrate the method, not Brand Sauce prices or measured customer results. Assume one supplier, one currency and shipment-based merchandise billing. For simplicity, the example excludes tax, deposits and employee payments; a real reconciliation must include them where applicable.
| Reconciliation step | Illustrative amount | Reason |
|---|---|---|
| Approved merchandise across the selected orders | $4,000 | Starting order value |
| Less merchandise not shipped by cutoff | −$600 | Remains open, not yet billable in this example |
| Plus supported freight | +$240 | Shipment charges matched to references |
| Plus agreed service fee | +$100 | Invoice-level charge |
| Less issued merchandise credit | −$80 | Credit applied once to a billed line |
| Expected net invoice amount | $3,660 | $4,000 − $600 + $240 + $100 − $80 |
If the supplier’s net bill is $3,700, the unexplained difference is $40. Do not automatically label it shipping, tax or rounding. Identify the actual line responsible, obtain the supporting document and either accept it under the terms or request correction. The separate $600 of unshipped merchandise remains on the open-order schedule; it has not vanished from the program’s commitments.
This bridge is not a bank reconciliation. If the invoice is approved today and paid next month, the approval and settlement dates differ. Finance should retain that distinction rather than forcing the payment total into the same column as approved invoice value.
Resolve differences with an exception queue
Give every unmatched amount a reason, owner, next action and follow-up date. Start with the classifications below; avoid a permanent “miscellaneous” bucket.
- Timing: an order or credit falls outside the selected cutoff. Retain the reference and identify the period in which it should appear.
- Quantity: billed units differ from the billable quantity. Check partial shipments and canceled lines before requesting a correction.
- Price: the invoice differs from the approved quote. Confirm decoration versions, setup charges and any authorized revision.
- Freight: a delivery charge lacks an order or shipment reference. Ask whether it is original freight, a split shipment, a reshipment or an adjustment.
- Credit: a promised reversal has no issued document, or an issued document has not been applied.
- Duplicate: the same supplier document or charge appears twice. Compare document and line identifiers, not just equal dollar amounts.
Agree with accounts payable how supported and disputed portions are handled under the payment terms. A merch administrator should not improvise a payment hold policy. Escalate unresolved items before the due date, and retain the supplier’s response with the reconciliation rather than only in a personal inbox.
Use an activity window for refunds, not only an order-date filter
A current-month refund may relate to an older order. If the only export includes orders created this month, that adjustment can disappear from your working set. Keep a current-period credit/transaction view and link it back to the original order, including prior-period orders.
Shopify’s sales-discrepancy guidance explains that reports can differ because of timing and reporting logic; sales reports and payment finance reports also treat returns and refunds differently. Do not treat two differently defined totals as interchangeable evidence.
For employee-funded upgrades, retain the split between company and employee funding and identify where each refund belongs. Our employee-paid gift upgrade guide covers that program-design decision. The invoice reviewer needs the resulting funding references, not employees’ personal payment details.
Handle bulk stock and on-demand orders differently
Bulk purchasing can make sense for a known event quantity or a planned uniform rollout. Reconcile the supplier’s bulk purchase to its purchase order and agreed delivery evidence. Track later distribution from that stock separately: issuing an already-purchased shirt is not another supplier purchase.
On-demand programs create a different workload: more individual orders, potentially more shipment references and more cross-period open items. That can suit uncertain ongoing demand, but it does not eliminate reconciliation. A hybrid program needs both record types and an explicit production-model field so warehouse issues are not confused with newly purchased units.
For a stocked program, use the company swag inventory audit guide alongside the invoice process. To decide how spending belongs to departments before invoices arrive, use the department budget framework. These are connected controls, not interchangeable reports.
A repeatable close checklist
- Freeze the reporting period, time zone, currencies and billing basis.
- Save original orders, billable-event evidence, invoices, credits and payment records.
- Check row structure, distinct identifiers and completeness before totaling.
- Match quantities and prices; separate freight and invoice-level fees.
- Link credits and replacements to their original orders without double counting.
- Explain every remaining difference in the exception queue.
- Obtain the designated reviewer’s sign-off and carry open items forward.
For multiple currencies, reconcile each currency separately first. Have finance specify the reporting conversion method rather than mixing supplier invoice amounts with card-statement conversions. Preserve both original amounts and any conversion reference used in the reporting view.
Frequently asked questions
Should store sales equal the monthly supplier invoice?
Only if their scope, timing, funding and charge definitions genuinely match. Otherwise, build a documented bridge. A difference is a question to resolve, not proof that either system is wrong.
Can a spreadsheet handle this?
Yes, if it has stable identifiers, preserved source files, controlled formulas, clear ownership and a review step. Move to more automated matching when exception volume or manual effort exceeds what the team can reliably review—not simply because the program has a store.
What should we request before choosing a provider?
Ask for a sample invoice and matching export that include a split shipment, partial credit and invoice-level fee. Require a demonstration of how each difference is explained. For a proposed Brand Sauce company merch store, confirm which reports are native, which require manual work and who owns that work before launch.
A good close ends with supported charges and a short, owned list of open questions—not a total made to match by guesswork.
