An intercompany recharge for a corporate gifting program is easy to describe and surprisingly hard to close. One legal entity places the order, recipients sit across several entities, deliveries occur over time, credits arrive later, and settlement may use another currency. A reliable register does not decide the transfer price or tax treatment. It preserves the approved inputs and shows how each amount moved from operational evidence to an internal settlement record.
Download the localized register: Excel workbook and UTF-8 CSV example/input export. Version 2026-10-18-v1; verified October 20, 2026. The workbook contains six sheets, formula controls, and hypothetical sample data. Replace the samples with approved records before use.
Define the register before choosing an allocation formula
Start with the business event, not the spreadsheet. The register covers costs from a named gifting campaign or order after the program owner has decided which legal entities may participate. It begins with source lines and ends with a documented settlement position. It does not create an invoice, post a journal, decide deductibility, determine an arm’s-length price, or replace a local adviser. Those decisions remain with finance, tax, legal, and accounting owners.
The practical unit of control is an order line tied to an entity, campaign, cutoff, and currency. A campaign total is too broad because partial delivery and credits often apply to specific lines. A supplier invoice alone is also insufficient: it proves a charge from the supplier, not which group entity should bear the internal amount. Keep the source order line, delivery evidence, credit reference, approved allocation basis, and settlement reference connected by stable identifiers.
Use one record for each entity-and-line combination. If three entities share one order line, create three allocation rows linked to the same source line. Do not copy the source cost three times. Store the eligible source cost once, then calculate each entity’s share from the approved basis. A control should confirm that allocated shares plus an explicit rounding residual equal the eligible amount in that source currency.
The OECD Transfer Pricing Guidelines describe the arm’s-length principle for cross-border related-party transactions. That is a boundary for this operational register, not a rule that the workbook applies. The workbook never selects a method, markup, tested party, comparable, or local filing treatment. The controller supplies an approved basis and records who authorized it, when it applies, and what evidence supports it.
This boundary matters because the same delivery data can support different approved policies. A delivered-unit basis may reflect actual recipients. A fixed weight may reflect a preapproved funding commitment. A headcount or revenue key might be appropriate in another program, but it should not be improvised after costs are known. If the approved basis is missing, contradictory, or outside its effective period, the correct register output is blocked, not zero.
| Evidence layer | Minimum fields | Owner | What it does not prove |
|---|---|---|---|
| Program scope | Campaign, eligible entities, cutoff, approved basis | Program owner and controller | Tax or transfer-pricing treatment |
| Fulfillment | Order line, ordered units, delivered units, delivery reference | Gifting operations | Internal price or settlement date |
| Cost and credit | Eligible cost, source currency, credit amount and reference | Accounts payable or procurement | Which entity finally bears the cost |
| FX and settlement | Approved rate, rate date, settlement currency, payment reference | Treasury or controller | Local accounting entry or legal discharge |
Build the evidence chain from delivery to credit
Delivery is the point where a planned allocation meets operational reality. Capture ordered units and delivered units separately. A blank delivery quantity means the team does not yet know the outcome; zero means it knows that none were delivered by the cutoff. Those states must not be interchangeable. The register should preserve the cutoff used, because a line can be undelivered at month-end and delivered a week later.
Use delivery evidence that another reviewer can retrieve: a fulfillment export, carrier or vendor status tied to the order line, or an approved operations reconciliation. Avoid screenshots without identifiers. If a recipient-level file contains personal data, keep the minimum reference in the recharge register and store the sensitive evidence in the controlled source system. The register needs traceability, not a second uncontrolled recipient database.
Credits should point back to the original line. Record both the amount and the supplier credit reference. A late credit does not disappear because the original period closed. It becomes an open adjustment with a clear owner and treatment decision. Do not spread an unattributed credit across all entities simply to force a total to tie. If the credit applies to one line, allocate it using the approved treatment for that line; if scope is unclear, leave it open.
Three controls catch common failures. First, no credit can exceed the eligible original amount without an explanation and a separate approved adjustment. Second, the same source line cannot be imported twice. Third, negative quantities or costs are rejected unless the workbook explicitly models a credit line. These controls separate genuine reversals from accidental signs and duplicate extracts.
The downloadable register provides a dedicated delivery-credit sheet so the operations owner can complete evidence before finance selects a settlement result. That separation prevents finance formulas from turning missing operational facts into plausible-looking numbers. It also creates a clean handoff: operations attests to what was delivered and credited, while finance attests to the approved monetary treatment.
Connect this step to the broader global corporate gifting operations hub when the program still needs decisions about ordering, recipient support, fulfillment, and regional ownership. Use the separate budget allocation guide for pre-campaign funding. This register owns the later evidence-based entity settlement, so it should not repeat planning forecasts as if they were actual charges.
Worked case A: allocate a partially delivered order
Hypothetical case. A group orders 100 identical gift units for three entities. By the December 31 cutoff, 90 units have been delivered: 60 for Entity A, 20 for Entity B, and 10 for Entity C. The approved eligible source cost is USD 9,000. A supplier credit of USD 300 is expected for a damaged batch but has not yet been applied to the recharge. The program has two documented alternatives.
Under a delivered-unit basis, the 90 delivered units are the denominator. Entity A receives 60/90 of USD 9,000, or USD 6,000. Entity B receives 20/90, or USD 2,000. Entity C receives 10/90, or USD 1,000. The undelivered ten units are not silently charged. They remain in an exception record until delivery, cancellation, or credit evidence resolves them.
Under the preapproved fixed weights of 50%, 30%, and 20%, the same source cost would be USD 4,500, USD 2,700, and USD 1,800. That allocation may be valid if the funding commitment deliberately ignores timing, but delivery evidence alone does not authorize it. The controller must choose the basis that the applicable policy approved. The register shows both calculations and a selected-basis field so reviewers can see the alternative without mixing them.
The USD 300 expected credit stays open because the supplier has not issued a final reference and the controller has not approved its period treatment. If the supplier later credits the original line, the team records the reference and decides whether to reopen the original period or make a later adjustment. The register should preserve the original allocation, the credit event, the decision date, and the resulting settlement change. Replacing the original number would erase the audit trail.
Failure recovery is specific. If delivered units total zero, the delivered-unit calculation returns no amount. If weights total zero, the fixed-weight calculation returns no amount. If the three calculated shares sum to USD 8,999.99 because of rounding, the register places USD 0.01 in a residual field assigned under the approved rounding convention. It never hides the difference inside an entity row.
Acceptance for this case requires five facts: all three entity rows point to the same source line; delivered units reconcile to the evidence cutoff; the selected basis has an owner and effective date; allocations plus the visible residual equal USD 9,000 in USD; and the pending credit remains separately identified. A reviewer should be able to reproduce the result without relying on an email summary.
Worked case B: control FX, a late credit, and partial settlement
Hypothetical case. Entity A initially bears USD 5,000 of approved eligible cost. The receiving entity settles in EUR. Treasury approves a rate of 0.92 EUR per USD for this recharge and records the rate date and approval reference. The converted amount is EUR 4,600. A later supplier credit of USD 500 and a partial intercompany settlement of EUR 3,000 create two different events.
First, keep currencies explicit. The source amount remains USD 5,000. The approved conversion uses USD 5,000 × 0.92 = EUR 4,600. Do not subtract a USD credit directly from a EUR settlement. The controller decides whether to convert the credit using the original approved rate, a later approved rate, or another policy. Until that instruction exists, the credit remains in its source currency and the converted adjustment is blocked.
Second, distinguish reopening from later adjustment. Reopening the original period may keep the source cost and settlement aligned in one reporting period, but it can disrupt a closed ledger and previously approved intercompany confirmations. A later adjustment preserves the closed period but requires an explicit link to the original line and may create a timing difference. The register does not choose. It records the controller’s decision, effective period, approved rate, and resulting references.
Third, treat partial settlement as a remaining balance, not a failure. Before any converted credit adjustment, EUR 4,600 less EUR 3,000 settled leaves EUR 1,600 open. The record names both counterparties, the settlement reference, the date, and the person who matched the payment. A zero remaining balance is not accepted unless the source allocation, approved conversion, credits, and settlements all reconcile.
Missing FX is a hard stop. A blank rate is unknown, while a zero rate is invalid. The workbook intentionally returns no converted amount in both cases. A user cannot make the sheet appear complete by typing zero. Likewise, a credit greater than the converted amount or a negative settlement produces a blocked status that must be repaired at the source.
Acceptance requires the source and settlement currencies to be labeled, the rate and rate date to be approved, the late credit to remain traceable to the original line, and the partial payment to retain its own reference. Two people should sign off: the preparer who assembled the evidence and the controller or delegated reviewer who confirms the basis and reconciliation. The signoff confirms the register’s arithmetic and evidence; it does not substitute for legal, tax, or accounting approval.
Operate the six-sheet workbook without losing accountability
The first sheet explains scope, failure rules, and refresh timing. Read it before entering data. The entity-input sheet holds the campaign, order line, cutoff, delivered quantity, approved weight, eligible cost, currency, FX rate and owner. Amber cells are actual inputs. Do not paste formula results over them or use them as a scratch area.
The delivery-credit sheet belongs to operations and accounts payable. It holds ordered and delivered units, evidence references, credit amounts, credit references, and status. The allocation sheet then calculates the delivered-unit and approved-weight alternatives. Finance selects one approved basis per entity row. The selected source amount is a formula result, not a manual override.
The settlement sheet keeps the source amount, approved rate, converted amount, credit, settled amount, open amount, and settlement reference together. Open does not mean wrong; it means the record is not fully settled. Blocked means a prerequisite is missing or invalid. Complete means the formula prerequisites are present, but a human still needs to verify that the supporting evidence is authentic and applicable.
The source/change-log sheet records methodology sources, verification dates, limitations, and changes. When a formula, allocation rule, or field definition changes, create a dated entry with the owner, reason, and replacement evidence. Do not overwrite the version label and pretend earlier settlements used the new logic.
The CSV export is a portable example/input layout. It is UTF-8 with a byte-order mark so localized text opens reliably in common spreadsheet tools. Text values that could be interpreted as formulas are escaped. The CSV does not contain workbook formulas or all evidence controls, so use it for import or exchange, not as the sole reconciliation artifact.
Before each close, run a short control sequence:
-
Lock the campaign cutoff and retrieve the latest order-line delivery file.
-
Reconcile source costs and credits to supplier records by currency.
-
Confirm that each entity’s basis is approved and effective for the period.
-
Resolve duplicate lines, negative inputs, zero denominators, and missing FX.
-
Compare allocated totals plus rounding residual to the eligible source cost.
-
Match settlements to bank or intercompany references without combining currencies.
-
Obtain preparer and reviewer signoff, then preserve the version used.
If a control fails, repair the earliest incorrect layer. A settlement mismatch caused by duplicate delivery lines is not fixed by editing the open balance. Remove or correct the duplicate, recalculate allocation, reapply the approved FX convention, and then rematch settlement. This order keeps the evidence chain intelligible.
Assign one accountable owner to every exception and record a dated next action. “Finance reviewing” is not specific enough. The note should state which field or document is missing, who can supply it, which calculation is blocked, and what acceptance evidence will close the item. When the evidence arrives, preserve the earlier failed state and add the corrected result instead of erasing the history. This small discipline makes period-end review faster because open balances no longer depend on private messages or memory.
Review boundaries, sources, and refresh timing
Last verified: October 20, 2026. The workbook method uses hypothetical data and no market benchmark. The official OECD source was reviewed as a global transfer-pricing boundary. Japan’s National Tax Agency transfer-pricing documentation outline was checked as a jurisdiction-specific example of documentation expectations, including transaction and currency information, but it is not applied as a rule outside its facts or jurisdiction. No local tax rate, statutory invoice requirement, journal treatment, or filing threshold is asserted here.
Source quality is more important than volume. Use an official authority for the general boundary, the organization’s approved policy for the allocation decision, supplier and fulfillment records for actual events, and treasury evidence for FX and settlement. A blog post, search snippet, or template cannot establish the legal treatment of a related-party charge.
Review the register quarterly, whenever the allocation methodology changes, after a material workflow or supplier change, and before the annual version rolls forward. Keep prior versions because a later policy does not rewrite an earlier settlement. If a jurisdiction changes its rules, route the affected transactions to local specialists and update the method only after an authorized decision.
The 2027 label indicates the intended use year, not that the workbook predicts 2027 law or exchange rates. It includes no live rates, macros, external workbook links, or automated journal posting. Every rate is a dated, approved input. Every completion status is a control result, not a legal conclusion.
Accounting, tax, and transfer-pricing limitation
This register organizes operational evidence and arithmetic. It does not determine whether a charge is deductible, taxable, arm’s length, subject to withholding or indirect tax, supported by a statutory invoice, or correctly recorded under a particular accounting framework. Finance, tax, legal, treasury, and local advisers retain those decisions. If their approved treatment conflicts with the template, stop and document the authorized method rather than forcing the template result.
Close with a reproducible decision, not a forced zero
A strong intercompany recharge register does not make every row disappear at month-end. It makes each unresolved amount understandable. The reviewer can see what was delivered, which cost was eligible, which basis was approved, how the currency conversion was authorized, what credit arrived, what was settled, and who owns the next action. That is more useful than a zero balance created by manual plugs.
Adopt the register in one campaign first. Test a fully delivered order, a partial delivery, a zero-weight error, a late credit, a missing FX rate, and a partial settlement. Keep the evidence references retrievable. Once the owners can reproduce each result and recover from each failure, extend the method to additional campaigns without changing the control definitions midstream.
For teams that need a gifting execution layer after finance has set the policy, Giftpack can support corporate gifting and merchandise workflows. It does not replace the organization’s controller, tax, treasury, privacy, payroll, legal, or accounting decisions. Use the operational record to connect approved internal rules to actual gifting evidence, then hand the final settlement to the responsible finance process.