TP-01 · FlowCount TP
Related-party transactions register & disclosure
Your related-party register, assembled from payments you already reviewed.
سجل معاملات الأطراف ذات العلاقة، جاهز للإفصاح
18.7M
of related-party flows across 4 counterparties, assembled from the sample population
Basis: illustrative sample engagement (fictional data)
The problem
Related-party flows are flagged in AP, then rebuilt by hand for the TP disclosure form.
What FlowCount does
Assemble every related-party flow (already flagged in the WHT review) into the TP disclosure form and a benchmark-ready register.
- AI and rules used
- Rules; entity resolution
- Builds on
- WHT Health Check related-party flag
How it works
Who does each step
- 01Rules
Collect
Every related-party flow from the reviewed population and the GL.
- 02Rules
Organise
By counterparty and nature, for the disclosure.
- 03Reviewer
Confirm
Against intercompany agreements.
What you send
- GL
- WHT population
- Intercompany agreements
What you receive
- RPT register
- Disclosure-form draft
Controls built in
- Group-structure model validated
- TP methodology signed off
Sample input → expected output
What the result looks like
Basis: illustrative sample engagement (fictional data)
| Counterparty | Country | Nature | Flows |
|---|---|---|---|
| Asia Holdco | SG | Dividends | 13.0M |
| Parent Holdco | AE | Management fees | 4.5M |
| Engineering Affiliate | DE | Technical services | 774k |
| Europe Opco | NL | Marketing + IT | 258k + 129k |
Portfolio scorecard
Where it sits on the roadmap
Value
3.80 / 5
Feasibility
3.30 / 5
Priority index
4.18 · rank 16 of 27
Quadrant
Strategic bet
Delivery
Wave 3 (6-12 m)
T-shirt size M: 4 to 8 weeks with 2 engineers + 1 tax SME + 0.25 QA, indicative build 120k to 275k. New data source or document type + rules + review-UI changes. How we score and sequence →
Your related-party register, assembled from payments you already reviewed.
Tell us about your situation and we will keep you posted as this solution moves forward.