The pair that did not match

Every internal deal is booked twice, and consolidation only works if the two bookings agree. Workday matches most pairs automatically; May’s four pairs left one difference of 1,250.00, and that remainder, not the matches, is what the close is for.

RuleReconcile intercompany as pairs: every receivable against its payable, matched by rule, with the unmatched remainder named and owned before consolidation.

Neverchase matched pairs. Workday matches most lines automatically; the close’s real work is the remainder, and effort spent re-proving matches is effort taken from it.

Both sides of every internal deal, and the one pair that disagrees. Consolidation eliminates matches; people resolve remainders.

◆ May, the pairsfour deals, one difference of 1,250.00.

Pair	Entity A books	Entity B books	Difference
IC-01 · shared services fee	220,000.00	220,000.00	0.00
IC-02 · license recharge	84,500.00	84,500.00	0.00
IC-03 · project labor	61,340.00	60,090.00	1,250.00
IC-04 · interest	12,900.00	12,900.00	0.00
Intercompany, May	378,740.00	377,490.00	1,250.00

Workday assigns match identifiers automatically for lines born from the same intercompany event, and its reconciliation report shows the differences. Three pairs above matched themselves; the 1,250.00 on the project labor pair is a rate applied on one side only, and it is the whole job. Sample values are illustrative, never client data.

◆ Why remainders happensame deal, two hands, two moments.

Matched-at-birth pairs stay matched. Remainders come from the deals booked by two hands at two moments: a recharge entered manually on one side, a rate or currency applied unevenly, a period cut off differently. The fix is upstream discipline; the control is this table, weekly, so December’s consolidation does not inherit June’s difference.

◆ The owned answerpairs as data, the remainder as a list.

Both sides land on the GL star with company and counterparty keys, so pairing is a join, the remainder is the rows that fail it, and each difference carries its age. The pattern is the SAP catalog’s uncleared-items discipline applied to internal deals.

Use case

Problem

Intercompany differences surface at consolidation, months after they were booked, and the close spends its time re-proving pairs that already match.

What we build

Both sides landed with counterparty keys: pairs by join, the unmatched remainder as a named, aged list, run weekly instead of at year end.

What you get

A consolidation that inherits no surprises: matches eliminated by rule, remainders resolved while the booking hands still remember, and one aging list instead of an email hunt.

How old is your oldest intercompany difference?

We build the pair join that names the remainder while it is young.

Talk to us

Terms on this page

GL: General ledger, the books this module lands and proves.
SAP: The sibling platform; the same pair discipline is documented there.
intercompany pair: One internal deal booked on both sides.
match identifier: The key that ties lines born from one event.
the remainder: Pairs that did not match; the close’s real work.
elimination: Removing matched internal activity at consolidation.
aged difference: A remainder with a birthday; older is worse.