Originally published at soluqube.com.
Allocating a transaction price by relative standalone selling price usually gives each performance obligation a share with fractions of a cent. Rounding every line on its own can make the allocations sum to a cent more or less than the contract. A residual-cent policy names which obligation absorbs that difference, so the allocation ties to the transaction price exactly.
Why does relative SSP allocation leave a residual cent?
Relative SSP allocation multiplies the transaction price by each obligation's share of total standalone selling price. Those shares are rarely whole cents. Round each line half-up on its own and the rounded lines can add up to one cent more, or one cent less, than the contract. That leftover cent is the residual, and it has to land somewhere.
The formula is the one in every Step 4 memo: allocation for obligation i = transaction price × SSP of i ÷ sum of all SSPs. With two obligations and round numbers, such as $120,000 split by SSPs of $100,000 and $25,000, the shares come out clean at $96,000 and $24,000. With three or more obligations, or with SSPs that do not divide evenly, they usually do not.
A one-cent residual is not material on its own. The reason to settle it is mechanical: if the allocated amounts do not sum to the transaction price, the contract liability never fully unwinds, someone books a plug, and the next reviewer has to work out where the plug came from.
What does ASC 606 say about rounding the allocation?
ASC 606-10-32-28 through 32-41 set the allocation objective, require a relative standalone selling price basis, and govern how discounts and variable consideration are allocated. They do not specify how to round an allocation to the cent. That choice is left to the entity, which is why it belongs in a written, consistently applied policy.
The relevant paragraphs, for reference:
- ASC 606-10-32-28 and 32-29: the allocation objective, and the relative standalone selling price basis as the default.
- ASC 606-10-32-31 to 32-35: determining standalone selling price at contract inception and estimating it when it is not directly observable.
- ASC 606-10-32-36 to 32-38: a discount is allocated proportionately to all obligations unless the stated criteria for allocating it to only some are met.
- IFRS 15 paragraphs 73–86 and the corresponding paragraphs of Ind AS 115 carry the same allocation model.
None of these paragraphs mentions cents. Read the primary text rather than a summary when you write the policy; the point here is only that the rounding convention is an entity-level choice.
Worked example: $100,000 across three performance obligations
A $100,000 contract bundles implementation (SSP $30,000), premium support (SSP $30,000) and a platform subscription (SSP $120,000). Total SSP is $180,000, so the $80,000 discount is spread proportionately. Each raw allocation ends in a repeating 6. Rounding every line half-up gives $100,000.01. Soluqube's engine allocates $16,666.67, $16,666.67 and $66,666.66, which sums to exactly $100,000.00.
Step one, round every line independently:
\
FAQ
Is the residual cent the same as the residual approach in ASC 606?
No. The residual approach in ASC 606-10-32-34(c) is a method for estimating a standalone selling price when that price is highly variable or uncertain. The residual cent is a rounding artefact: the one-cent difference left when relative-SSP allocations are rounded to the cent and no longer sum to the transaction price.
Does ASC 606 prescribe a rounding method for SSP allocation?
The allocation guidance in ASC 606-10-32-28 through 32-41 sets the objective and the relative standalone selling price basis, but it does not specify a cent-level rounding convention. An entity chooses one, documents it, and applies it consistently so the allocation can be re-performed.
Which obligation absorbs the residual cent in Soluqube?
Soluqube rounds every obligation half-up to the cent except the one listed last, which receives the transaction price minus the sum of the others. Ratable schedules give each month the floored amount and the final month absorbs the remaining cents. If allocations or the schedule fail to tie to the transaction price, the engine rejects the result.
Want this on your own contracts? Request a free 3-Contract Audit-Defense Workpaper: https://soluqube.com/book-demo
Top comments (0)