Intercompany Netting demo
Pairs each intercompany payable with its receivable, explains each difference and nets the cycle to one payment per entity 1:34
What the demo shows
Matches, disputes and nets intercompany invoices before settlement for group treasury
The netting matrix shows what each entity owes each other this cycle, and beside it the result: one payment in or out per entity, with the drop in payments and currency trades as numbers. An intake agent reads the invoices from each ledger, the portal and email; a matching agent pairs each payable with the other side's receivable; a dispute agent explains every difference from the documents (an unbooked credit note, a short receipt, an old markup) and drafts the fix for the right entity, which a person sends. A netting agent calculates the positions and the FX, and shows what each option would do; a check agent recalculates the whole run on its own and must agree to the cent. Entities confirm their positions, the group treasurer approves with a reason code and e-signature, and a settlement agent drafts the payments, journals and regulatory reports.
Transcript
- Intercompany Netting matches, disputes, and nets intercompany invoices for group treasury.
- One published case auto-matched only 14% of intercompany receipts.
- Overnight, agents read 414 invoices and matched 96%.
- The matrix shows who owes whom, $86 million.
- Netted, 18 payments of $9.4 million, and 12 fx.
- trades. Mexico and the UK are $230,000 apart.
- The dispute agent finds why, a UK credit note Mexico never booked.
- Isabel sends its request, Carmen books it, and the pair matches.
- A second agent recalculates the run alone and agrees to the scent.
- The group treasurer approves with a reason code, and her signature.
- Every value cited, every decision signed, every step logged.
- Result, 88% fewer payments, about $750,000 a year.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.