What does Multi-Entity Clearing and Audit-Ready Ledgers conclude, in numbers, about “Shared Costs Between Related Entities: the Arm's Length Principle, Allocation Keys and Contemporaneous Documentation”?

Answer: Chapter 4 shows that one entity's share of a cost pool moves from 0.2100 by usage to 0.7001 by revenue, so keys must be written in advance and follow benefit. In Chapter 5 four-way reconciliation matches 0.9500 of orders automatically, a tolerance of 0.03 clears exactly the benign residues, and cross-entity duplicates are found only by original document number.

Scope of the numbers: The book is a handbook of accounting and compliance routines and is not personal tax advice. Parameters are illustrative, data synthetic, and all calculations come from the book's programs.

中文版

Data table

The numbers below are printed verbatim by the chapter's Python program and can be reproduced by running it. standard-library Python onlyprinted values that match the answer: 0.2100, 0.7001

A. 48,000.00 u shared pool, three allocation keys (u)
  entity     usage    revenue  usage+5%   spread
  SITE   24,960.00  13,148.60 26,208.00 13,059.40
  LIB     6,240.00     779.16  6,552.00  5,772.84
  AIX    10,080.00  33,606.73 10,584.00 23,526.73
  HX      6,720.00     465.51  7,056.00  6,590.49
B. column totals 48,000.00 / 48,000.00 / 50,400.00
C. AIX carries 0.7001 of the pool by revenue, 0.2100 by usage
D. the key decides who bears the cost; it must follow the
   benefit received and be written down before the month
Show the full program
# Chapter 4. p41: one shared-service cost pool split among four entities
# by three keys: measured usage, revenue share, and usage with a cost-
# plus charge by the service entity. Pool, usage and revenues are
# illustrative units (u). The 5 % mark-up is an
# illustrative point inside a range that must be supported by the
# group's own contemporaneous documentation; it is not a recommended
# rate. Exact fractions, cents assigned by largest remainder.
from decimal import Decimal
from fractions import Fraction

POOL = Fraction(4800000, 100)                      # 48,000.00 u
ENT = ["SITE", "LIB", "AIX", "HX"]
USAGE = {"SITE": 520, "LIB": 130, "AIX": 210, "HX": 140}   # hours
REVENUE = {"SITE": 3409967, "LIB": 202067, "AIX": 8715592,
           "HX": 120725}                                  # cents
MARKUP = Fraction(5, 100)


def split(total, weights):
    cents = int(total * 100)
    wsum = 0
    for e in ENT:
        wsum += weights[e]
    exact = {e: Fraction(cents * weights[e], wsum) for e in ENT}
    floor = {e: int(exact[e]) for e in ENT}
    left = cents
    for e in ENT:
        left -= floor[e]
    order = sorted(ENT, key=lambda e: (-(exact[e] - floor[e]), e))
    for e in order[:left]:
        floor[e] += 1
    return {e: Decimal(floor[e]).scaleb(-2) for e in ENT}


if __name__ == "__main__":
    by_use = split(POOL, USAGE)
    by_rev = split(POOL, REVENUE)
    by_cp = split(POOL * (1 + MARKUP), USAGE)
    print("A. 48,000.00 u shared pool, three allocation keys (u)")
    print("  entity     usage    revenue  usage+5%   spread")
    for e in ENT:
        trio = [by_use[e], by_rev[e], by_cp[e]]
        print("  {:<5} {:>10,} {:>10,} {:>9,} {:>9,}".format(
            e, by_use[e], by_rev[e], by_cp[e], max(trio) - min(trio)))
    tot = [Decimal(0)] * 3
    for e in ENT:
        tot[0] += by_use[e]
        tot[1] += by_rev[e]
        tot[2] += by_cp[e]
    print("B. column totals {:,} / {:,} / {:,}".format(*tot))
    print("C. AIX carries {:.4f} of the pool by revenue, {:.4f} by usage"
          .format(by_rev["AIX"] / Decimal(48000), by_use["AIX"] /
                  Decimal(48000)))
    print("D. the key decides who bears the cost; it must follow the")
    print("   benefit received and be written down before the month")

Single source and citation

Fan, Y. (2026). Multi-Jurisdiction Digital Revenue Clearing, Cross-Border Tax-Base Compliance Boundaries and Audit-Ready Automated Ledgers (Version 1.0.0), Chapter 4: Shared Costs Between Related Entities: the Arm's Length Principle, Allocation Keys and Contemporaneous Documentation. 5D Library. DOI pending

DOI pending · monograph page goes live after publication · 5DL-B-402 · v1.0.0 · CC-BY-NC-ND-4.0

BibTeX
@book{fan2026402,
  author    = {Fan, Yafu},
  title     = {Multi-Jurisdiction Digital Revenue Clearing, Cross-Border Tax-Base Compliance Boundaries and Audit-Ready Automated Ledgers},
  year      = {2026},
  publisher = {5D Library},
  edition   = {1.0.0},
  note      = {DOI pending}
}

Other chapter answers in this book