Close a corporate gifting campaign by reconciling approved gifts, recipient claims, physical stock and supplier credits at one documented cutoff. Keep unexplained records and unresolved obligations visible. A shipment is not recipient acceptance, and a supplier credit does not make damaged stock usable. The downloadable workbook helps expose these differences before anyone signs the campaign closed.
What the closeout workbook does
Download the English campaign closeout workbook. This is an editable English-language XLSX, methodology version October 13, 2026, last verified October 19, 2026. Its figures are hypothetical, not customer results, market benchmarks or accounting entries. The example intentionally stops sign-off because some records remain unresolved. A valid workbook can correctly report an unfinished campaign.
The workbook contains Reconciliation, Inputs, Orders, Claims, Inventory, Credits, Exceptions and Instructions. The first seven operational roles promised by the template are present, with a separate exception sheet so failures have a visible review destination. Start with Instructions, then change the amber inputs. The sample has 500 approval rows, 430 current claim rows, 25 supplier-credit rows and one inventory item. It is a bounded template, not an unlimited data integration.
Use it when operations, finance and procurement already have authorized exports but disagree about what “complete” means. It is not a forecasting model, invoice generator or replacement for the supplier’s records. Operations owns the approved population and shipment controls. Support owns delivery evidence and unresolved recipient cases. Procurement owns damaged-goods evidence and supplier discussions. Finance decides document treatment and accounting recognition separately.
For a small campaign, a single controlled workbook may be easier to inspect than a new integration. For recurring, high-volume programs with many partial shipments, currencies or approval units, use a properly governed data model and treat this file as a requirements and testing reference. Do not stretch a one-item example into a universal fulfillment system.
Freeze the population, period and evidence
Choose one campaign identifier, a period start, a closeout cutoff and a time zone. The example uses campaign C-A and local dates October 1–13, 2026. The verification date is later and does not extend the campaign period. Normalize timestamped exports to the chosen local date before import; the workbook does not perform time-zone conversion. Document both the original timestamp and conversion rule outside the public template.
Keep four exports distinguishable: approvals and orders, current recipient claims, inventory movements, and supplier credits. Record export time, source owner, row grain and immutable source reference. Preserve the raw export separately. If the source contains event history, first create one documented current canonical record per claim. Never count every status event as another recipient claiming a gift.
The Internal Revenue Service recordkeeping guidance, checked October 19, 2026, distinguishes business records and their supporting documents. This workbook provides an operational index to such evidence; it does not establish deductibility, retention periods or a particular accounting treatment. Ask the company’s finance and records owners to decide those matters for the actual transaction and jurisdiction.
Use identifiers rather than recipient names or addresses in the shared workbook. Store necessary personal information in the authorized source system, with access restricted to the relevant team. A finance reviewer may need the evidence reference and amount without needing the recipient’s home address. A warehouse operator may need a stock identifier without permission to edit supplier-credit documents.
Before calculations, compare source controls with the imported population. “The export opened” is not proof of coverage. Confirm campaign scope, the number of approved units and the explicit unclaimed population. Missing controls must remain missing, while a genuine zero must remain zero. An unexplained difference is a finding to investigate, not a balancing number to type into a spare cell.
Use keys and states that do not erase exceptions
The sample assumes one approved gift unit per approval identifier and one current claim per approval. Real programs can differ. If one approval can create several gifts or several shipment lines, redesign the grain and test the joins before importing. Do not solve a one-to-many relationship by copying an approval total onto every shipment row.
Field dictionary for the downloadable model
| Field or record | Meaning in this template | Owner and failure rule |
|---|---|---|
| Approval identifier | One approved gift unit, within one campaign | Operations; blank or duplicate keys stop sign-off |
| Claim identifier | One current canonical recipient claim | Data owner; duplicate claims or unmatched approvals require repair |
| Delivery proof reference | Carrier evidence associated with a delivered claim | Support; missing proof is not silently accepted |
| Item and damage batch | Physical item and separately identified damaged stock | Warehouse and procurement; credits do not restore stock |
| Credit identifier and document date | Supplier credit with units, price and a supporting document | Finance; invalid keys, dates or documents remain exceptions |
Apply precedence before summarizing. An invalid or duplicate key is unresolved. Otherwise, use the linked canonical claim state. An approval with no matching claim can be marked unclaimed only when its source explicitly says so. No match alone means unknown. The sample’s explicit unclaimed marker is a source classification, not a shortcut based on the row’s position.
Delivery and acceptance need different evidence. A carrier proof reference can support the narrow delivered state; it cannot prove that the recipient inspected the item, liked it or accepted a business obligation. If inspection is required, retain that as a separate owner-controlled record. Do not rename a delivered count “satisfied recipients.”
The recipient-experience guide covers invitation, choice and support. Use those stages to locate a problem, while retaining this workbook’s narrower job: reconciling the campaign’s records at a fixed cutoff.
Hypothetical case A: 500 approvals do not reconcile themselves
Assume 500 gifts were approved. There are 430 claim records, including 12 failed deliveries, plus 58 explicitly unclaimed approvals. Assume the other 418 claims have carrier delivery evidence. These are illustrative inputs, not an observed campaign. The word “including” matters: adding the 12 failures to 430 claims would count those claims twice.
The status partition is 418 delivered, 12 failed, 58 unclaimed and 12 unexplained, totaling 500. The missing 12 are calculated as 500 minus 430 minus 58. The workbook retains them as unknown rather than inventing cancellations, invitations or deliveries. Both the 12 failed deliveries and the 12 unexplained approvals prevent an ordinary complete closeout.
Hypothetical status reconciliation at the same cutoff
| Population | Units | Decision and evidence |
|---|---|---|
| Claims with delivery proof | 418 | Retain proof references; do not infer recipient acceptance |
| Claims with failed delivery | 12 | Support assigns a remedy or documented no-send resolution |
| Explicitly unclaimed approvals | 58 | Operations verifies the cutoff and expiry classification |
| Unexplained approvals | 12 | Data owner locates the missing outcome; no balancing plug |
| Approved population | 500 | Reconcile the complete partition to the frozen approval control |
Operations can keep the campaign open while support investigates, or seek an authorized partial administrative close with a separately owned open-obligation register. The supplied workbook does not automatically grant that exception: its default sign-off stays halted. Closing a purchasing period and closing every recipient obligation are different decisions, with different signatures and evidence.
Compare the alternatives explicitly. Keeping the campaign open preserves reversibility and recipient choice, but requires more support labor and can delay releasing unused budget. A controlled partial close may simplify period reporting, but adds policy review and a durable owner for each unresolved item. Neither option improves regional reach: local carrier access and recipient contactability still govern recovery. Both must support an accessible, non-pressuring contact route.
Do not automatically resend all 12 failed gifts. Support first checks the original shipment, recipient preference, address authority and possible duplication. A recipient-approved no-send may be the appropriate outcome. The delivery-failure recovery guide helps separate address changes, returns and replacements. Acceptance evidence is the recorded remedy, its owner and the new reconciled state, not another outbound label.
Hypothetical case B: 40 damaged units and 25 credited units
Assume 40 units in warehouse stock are damaged and quarantined. Each has a hypothetical unit cost of USD10. The supplier has issued 25 separate one-unit credit records, each supported by a distinct document reference. Thus “25 credits” means 25 credited units in this example, not 25 documents of unspecified value. The workbook can only reconcile amounts once this meaning is explicit.
The damaged value under these assumptions is USD400. The 25 documented units total USD250, leaving USD150 associated with 15 units unresolved. This is an operational comparison, not an entitlement to a refund or an accounting entry. Procurement must reconcile the accepted damage batch and remedy with the supplier. Finance decides when and how a valid document affects the actual books.
The stock example starts with 600 units, no receipts, 430 shipped units and no returns. Expected physical stock is 170. Quarantining 40 of those units leaves 130 usable units. The physical count remains 170 because damaged stock still exists in custody. A credit changes the commercial reconciliation, not the physical count. Crediting 25 units does not turn them into usable gifts or add 25 units back into stock.
Consider a replacement, a supplier credit or a documented no-replacement outcome. Replacement may preserve recipient choice but requires budget for handling, labor for inspection, receiving access and time for another shipment. A credit may reduce an agreed commercial balance but leaves sourcing and regional availability unresolved. No replacement avoids another delivery, but requires an authorized policy decision and a clear recipient obligation outcome where a recipient was affected.
Reversibility differs too. A pending remedy can be changed before commitment, while disposal or a consumed replacement may be difficult to reverse. Keep disposal authority, physical disposition and credit issuance separate. Do not destroy damaged goods solely because a spreadsheet shows a credit. For a regional warehouse, identify who can physically inspect the stock rather than requiring a remote finance reviewer to certify an unseen item.
If one credit arrives after October 13, exclude it from the frozen cutoff’s recognized operational credit total and track it in the next documented version or obligation record. Do not backdate its document cell to clear the exception. The model has date checks, but it cannot determine whether a supplier document is legally valid or belongs in a particular reporting period.
Read and extend the formulas safely
The model uses ordinary keyed counts, exact-match retrieval, conditional sums and a visible inventory roll-forward. Microsoft Excel’s SUMIFS documentation, checked October 19, 2026, explains matching criteria and equally sized ranges. Function syntax is not a substitute for deciding the record grain or validating source completeness.
In the English workbook, the following formula belongs in Reconciliation B16. It sums valid, supported credit amounts, not every pasted number. The adjacent amount still to resolve compares the damaged-unit assumption with that supported total. An exception remains visible if a document is missing, a key is duplicated or the document falls outside the cutoff.
=SUMIFS('Credits'!F6:F30,'Credits'!I6:I30,"No issue")
Check the ranges together when adding rows. Extending the amount range alone can break the formula or silently omit related criteria. This edition’s sample capacity is fixed: copy the appropriate formula and validation patterns, expand tables and every bounded join and check, then test the first added record. Do not claim automatic unlimited expansion from the presence of a filter button.
Use a disposable copy for tests. Duplicate a claim identifier and confirm two affected records surface. Remove one delivery-proof reference and confirm it is flagged. Move a date one day beyond the cutoff and confirm exclusion. Change a credit quantity from one to two and confirm the unresolved amount changes from USD150 to USD140, then restore the sample.
Also test zero, blank and negative stock. A zero receipt is valid; a blank required receipt input is incomplete. Shipping more units than available must expose negative usable stock, not clamp it to zero. The exception sheet reads the sources and results; business calculations do not depend on that terminal review sheet. This keeps an error display from becoming a hidden business input.
Give each discrepancy an owner and a next action
Operations prepares the approval and shipment controls, records the campaign’s purpose and confirms the permitted no-send path. The data owner documents joins, source normalization and the rule selecting one current claim state. Support retains delivery proof and unresolved recipient cases. Warehouse staff confirm custody and damage. Procurement validates supplier remedies. Finance owns credit documents, amounts and the final financial decision.
Each finding needs a stable affected identifier, an observation date, an owner, a concrete next action and a next review date. “Waiting on supplier” is incomplete without the supplier’s specific pending document or decision. “Finance reviewing” is incomplete without identifying the amount and reason. Use an existing authorized case system for detailed work rather than copying sensitive conversations into the workbook.
Do not make a status change stand in for source repair. If two claim identifiers collide, find the authoritative record and preserve the correction trail. If a delivery proof is missing, retrieve the evidence or change the state with an explained decision. If a physical count differs, recount the relevant location and investigate the movement history before adjusting inventory.
Separate access to input fields from authority to approve. A preparer may correct an export mapping without permission to waive a supplier balance. A finance reviewer may approve a document treatment without permission to recontact recipients. Named signers in the template are required inputs for owner review, not a captured electronic signature or proof that the underlying transaction has been authorized.
Run a closeout rehearsal before signing
Use the following checklist on the actual frozen data, not only the example. Keep a reproducible version with its original exports and record the spreadsheet application used for the final calculation. A download that opens with cached values still needs a changed-input check in the intended working application before operational use.
-
Confirm one campaign, approval grain, source controls, local period and cutoff.
-
Verify source export owners, timestamps and complete record coverage.
-
Reconcile duplicate and unmatched keys before interpreting totals.
-
Keep carrier delivery evidence separate from recipient inspection or acceptance.
-
Recount stock and preserve damaged inventory’s custody and disposition evidence.
-
Match supplier credit units, amounts, documents and dates without assuming refunds.
-
Test a duplicate key, missing proof, out-of-period date, blank input and negative stock.
-
Confirm every open obligation has an owner, next action and dated review.
-
Obtain the required operations, procurement and finance decisions outside the template.
-
Archive the signed version, source references and unresolved-obligation handoff together.
If a formula changes, preserve the prior version and rerun affected checks. If a late credit or carrier correction arrives, create a dated successor and explain the changed population or amount. Do not silently replace a signed historical file. For the first real campaign, rehearse with a small authorized sample that includes a failure and an unresolved record, not only successful deliveries.
Quarterly refresh is a practical starting cadence for the template, with earlier review after a source-field, provider, policy or spreadsheet-engine change. This is an editorial maintenance recommendation, not a statutory retention rule. Keep the methodology date, actual verification date and campaign cutoff distinct so a reader knows what was refreshed.
Make the handoff usable across teams
Before the closeout meeting, have each owner retrieve one source record using only the identifier and evidence reference supplied in the workbook. If finance cannot find the supplier document, or support cannot connect a claim to its approval, the handoff is not usable even when the formulas calculate. Fix the reference or access route in the authorized system. Do not email a larger personal-data export simply to make the test easier.
Agree how late evidence will enter the next version. A carrier correction can change an operational state without changing the original approval. A supplier document can reduce an unresolved amount without changing physical inventory. Record each change on its own basis, including observation time, effective date where established, responsible owner and affected identifiers. Never apply one department's closeout date indiscriminately to every ledger.
For multiple warehouses, reconcile custody location by location before presenting the campaign total. Transfers need a sending and receiving reference; otherwise both locations may report the same units or neither may report them. This one-item template does not model transfers or multiple locations automatically. Expand the design and independent tests before use, or retain separately reconciled location schedules with an explicit consolidation owner. Avoid copying aggregate inventory into each regional file.
Finish by confirming who will still own unresolved obligations after the project team disbands. A named person, an existing case reference and a dated next review are more useful than a shared folder marked final. These are handoff controls, not permission to waive an obligation.
Close the records without closing your eyes to obligations
A useful campaign closeout gives the next owner a defensible explanation of every approved unit, every physical item and every supplier-credit amount. Zero unexplained differences is meaningful only when the population, dates, units and evidence are correct. Where an obligation remains, an explicit controlled hold is a better result than a fabricated completed state.
Keep the workbook’s scope narrow. It connects operational records and makes missing decisions visible. It does not prove that a recipient was satisfied, that a damaged item can be reused, that a supplier must refund money or that a tax treatment is correct. The organization’s authorized owners retain those decisions and the evidence supporting them.
Giftpack can support agreed merchandise, inventory and fulfillment workflows. If fragmented execution is causing recurring reconciliation work, discuss a scoped merchandise program and verify the required records and exception handoffs before committing. Giftpack does not replace finance, tax, privacy, procurement or employer decisions.