Compare both sides of related-entity balances, trace why they do not match, and receive a structured reconciliation pack for your close. Rudrriv can support intercompany receivables and payables, loans, recharges, settlements and other agreed intercompany accounts.
Standard delivery: 5–7 working days after scope and required files are confirmed.
Illustrative interface and sample values — not client data.
Start with a focused pairwise check or request a custom quote for broader period-end and recurring close requirements. Pricing is confirmed against entity count, transaction volume, currencies, data quality and required outputs.
For a small, defined intercompany mismatch between two related entities.
For finance teams reconciling multiple intercompany accounts, counterparties or currencies before close.
For groups that need a repeatable monthly or quarterly reconciliation workflow.
The $30 entry point reflects a current publicly listed market price for a focused intercompany/control-account reconciliation project. Broader service tiers are quoted rather than assigned unsupported fixed prices.
Get in touch with our expert. Tell us what you need, and we'll help identify the most suitable service, scope and pricing for your intercompany reconciliation requirement.
The workflow is built around proving both sides of each related-entity position, isolating exceptions and creating a traceable close-ready reconciliation output.
Receive the agreed entity ledgers, subledgers, schedules and period details.
Identify corresponding intercompany accounts, entity pairs, currencies and references.
Structure dates, references, amounts and descriptions so both sides can be compared consistently.
Match clear items and classify timing, FX, cut-off, coding and one-sided differences.
Document open items, reconciliation movements and proposed follow-up or adjustment requirements.
Complete a quality review and provide the agreed reconciliation pack for finance-team action.
The exact scope depends on your entity structure, but the service can be designed around the intercompany balances that create close and consolidation friction.
Mirror receivable and payable positions between related entities.
Compare principal, interest and settlement movements where included.
Trace management fees, allocations and internal service charges.
Review the accounting sides of intercompany cash movements and clearing.
Separate true balance differences from exchange-rate and translation effects.
Identify transactions recorded in one entity but missing from the counterparty books.
Explain differences caused by the same transaction being recorded in different periods.
Prepare reconciled schedules that support your consolidation and elimination workflow.
A difference is not a single problem category. The reconciliation becomes useful when each variance is traced to a reason and assigned a clear next action.
Rather than forcing two totals to agree, Rudrriv can work through the underlying transactions, counterparties and periods so matched items are separated from genuine exceptions.
The same transaction is recorded in different accounting periods.
One entity recorded the transaction while the counterparty did not.
Both sides exist, but conversion or revaluation creates a variance.
Related entries are posted to different intercompany or clearing accounts.
Descriptions, dates or document references do not align cleanly for matching.
Payments or offsets are grouped differently across the two entity records.
Deliverables are tailored to the agreed scope, with emphasis on traceability, reviewer clarity and practical follow-up rather than a single unexplained balancing number.
Matched and unmatched items remain visible so reviewers can follow the reconciliation logic.
Important assumptions, cut-offs and treatment questions are called out instead of silently absorbed.
Open differences can be grouped into practical follow-up categories for the responsible finance team.
The final file structure is designed to support internal review, close documentation and downstream consolidation work.
This comparison describes the working-state change the reconciliation service can directly create. It does not promise downstream financial or audit outcomes.
The reconciliation sits between ledger extraction and downstream consolidation or reporting. Each stage should produce evidence that the next reviewer can understand.
Two related entities report different closing balances and the finance team needs a traceable explanation before close review.
Intercompany accounts have grown across entities and a consistent counterparty reconciliation structure is needed.
Both sides contain the underlying transaction, but exchange-rate and revaluation effects make the reported balances difficult to compare.
Prior-period balances contain open items that need to be traced, categorized and either supported or escalated for accounting review.
Clear boundaries protect the quality of the reconciliation. Broader accounting, consolidation, tax or system work can be separately scoped, but should not be implied by a reconciliation-only engagement.
The service organizes and reconciles supplied records; it does not issue an audit opinion or assurance conclusion.
Tax, legal and transfer-pricing policy or documentation require appropriately scoped specialist advice.
Proposed adjustments can be documented, but entries are not posted without explicit authorization and scope.
Reconciled balances can support elimination and consolidation, but full consolidation is a separate service unless agreed.
These are educational examples only, not Rudrriv client case studies or claimed customer results.
Entity A records the recharge in May while Entity B records the payable in June.
One entity records the drawdown while the counterparty ledger does not contain the matching entry.
Both entities recorded the invoice, but different rates or revaluation timing create a closing variance.
Matched and open items remain visible for review.
Entity, period and deliverable boundaries are confirmed before work.
Differences are categorized instead of hidden inside one total.
Outputs are organized for finance-team review and follow-up.
Engagements can be scoped for customers worldwide.
Initial enquiries avoid unnecessary sensitive data and work follows agreed channels.
Answers to common questions about scope, inputs, pricing, delivery, adjustments and recurring support.
Intercompany reconciliation compares transactions and balances recorded between related entities so the corresponding receivable, payable, loan, recharge or other intercompany positions can be matched, explained and prepared for period-end close or consolidation.
The agreed scope can include counterparty mapping, ledger comparison, transaction matching, exception classification, timing and foreign-exchange difference review, open-item schedules, a closing balance bridge and proposed adjustment support for your finance team's review.
We normally need the relevant general-ledger or subledger extracts for each entity, intercompany account mappings, period dates, currency information, supporting invoices or schedules where available, and details of known differences or prior unresolved items.
A focused pairwise balance check starts at $30 USD. Broader multi-entity, multi-account or recurring close support is quoted after the transaction volume, entity count, currencies, data quality and required deliverables are reviewed.
The standard delivery window is 5–7 working days after the required files and scope are confirmed. Large multi-entity reconciliations or periods with extensive exceptions may require a custom timeline.
Yes. Multi-entity and multi-currency requirements can be scoped. The work can identify timing, exchange-rate, cut-off, one-sided posting and mapping differences, with the final treatment remaining subject to your accounting policies and approval process.
Not by default. The service can prepare proposed adjusting entries or clearly documented correction requirements, but posting into your accounting system is only performed when explicitly included in the agreed scope and authorized by you.
No. Intercompany reconciliation helps establish and explain matching balances. Consolidation, statutory reporting, tax, transfer-pricing documentation and legal or regulatory advice are separate activities unless specifically included in a broader approved engagement.
Yes. Recurring support can be scoped for monthly or quarterly close cycles, including standardized counterparty schedules, exception tracking, review packs and follow-up on unresolved differences.
Depending on the plan, you can receive a reconciliation workbook or schedule, matched and unmatched item listing, exception summary, closing balance bridge, supporting notes and proposed adjustment or follow-up actions for your finance team's review.
Yes. A reconciliation can often be completed from suitable ledger, subledger and supporting-report exports. The exact files required depend on how your intercompany accounts are structured and how much transaction detail is available.
Choose the focused starting plan or submit the enquiry form with your entity count, period, currencies, approximate transaction volume and the accounts that need to be reconciled. Rudrriv will review the requirement and confirm the appropriate scope.
Share the essentials below. Required fields are validated on the server and the page does not redirect after submission.
