When the intercompany train stalls: Why “matched” doesn’t mean “resolved”

Finance and accounting teams believe intercompany is under control because their systems can match balances across entities. However, matching is only the signal. It’s not the movement. The real work begins after the discrepancy is flagged, and that’s exactly where the process breaks down. Intercompany transactions stall between detection and execution, which leaves journal entries unposted, ownership unclear and the close process waiting on decisions that never happen fast enough. If your intercompany process looks complete on the surface but still delays your close or forces last-minute manual adjustments, it’s worth asking a harder question: What actually happens after the match?

Flagging is not the finish line

Picture your intercompany accounting process as a rail network. Each intercompany transaction is a train moving between legal entities, like company A to company B or subsidiary A to subsidiary B. This train carries intercompany balances, cost allocations and expense allocation entries across your corporate group.

Matching is the signal light. It tells you something is aligned. It tells you something is misaligned. But it doesn’t actually move the train.

Most manual intercompany processes stop at that signal. Accounting software flags discrepancies between intercompany receivables and intercompany payables. Dashboards show that balances are “matched.” Accounting and finance teams see green lights and assume progress is being made when, in reality, nothing has moved.

The intercompany journal entry, which includes the debit and credit that updates general ledger accounts, adjusts liabilities and reflects the correct financial position, still hasn’t been created, approved or posted in SAP.

Take a manufacturing group operating across multiple legal entities. Subsidiary A records intercompany sales to subsidiary B. Company B records the payable, but timing differences and exchange rates create a mismatch. The system flags it. The match appears “resolved” on the dashboard. But over the next three days, finance teams debate ownership. Who posts the intercompany journal entry? Which chart of accounts should be used? Should the adjustment sit in the base currency of the parent company or the receiving subsidiaries?

The signal turned green, but the train never left the station.

Blame the manual hand-off

This is where intercompany management breaks down. Once a discrepancy is flagged, resolution depends on people. And people introduce friction.

When finance and accounting teams are stuck doing manual tasks, they get stuck in a loop of discrepancies instead of resolving them because they have to:

• Debate timing differences and ownership between company A and company B
• Hesitate on complex scenarios like intercompany loans, fixed assets transfers and internal transactions
• Route approvals through disconnected workflows instead of in-system execution
• Rely on email and spreadsheets to track decisions that never return to SAP
• Fragment the audit trail, which makes it harder to trace what actually happened

Meanwhile, the intercompany journal entry sits in limbo.

Accounts payable and accounts receivable teams wait on each other. Intercompany payable balances don’t align with intercompany receivable balances. Allocation decisions stall. No one owns the final step: posting the entry that resolves the issue.

In the manufacturing example, the delay compounds. The parent company can’t merge the data. Intercompany elimination is postponed. The close process stretches. What started as a minor mismatch in intercompany transactions became a missed group close deadline. The train is still sitting at the signal because no one is driving it forward.

Matching without posting is a false positive

A matched status without a posted intercompany journal entry is a false positive, not a resolution. Dashboards show aligned intercompany balances, but underneath:

• The accounting records haven’t changed
• The general ledger still reflects outdated positions
• Financial reporting pulls from incomplete data
• Accurate financial reporting becomes a matter of timing rather than truth

This is where risk builds quietly.

Without orchestration, visibility becomes misleading. Finance teams believe intercompany processes are complete, while intercompany journal entries remain unposted. During the audit, these gaps surface as discrepancies between reported numbers and actual ledger activity. Adjustments are made late. The audit trail shows delays. Questions follow.

Finance Automation by Redwood approaches this differently. It connects intercompany matching directly to execution. Once a match or mismatch is detected, the platform applies rules to generate the intercompany journal entry, route it through approvals within the system and post it natively in SAP.

This includes both sides of the transaction. The intercompany payable in company B and the intercompany receivable in company A are updated together. Debit and credit entries are aligned. General ledger accounts reflect the same reality across entities.

The manufacturing organization would’ve benefited from this automated process. Finance Automation would’ve generated, routed and posted both sides once rules, ownership and approvals were satisfied. The train wouldn’t have waited for manual coordination. It would have moved.

Put the train back on track

Intercompany accounting doesn’t fail at detection. It fails at execution. Orchestration is the reliable way to move from matching to resolution because it connects every step — detection, ownership, approval and posting — into one automated flow.

With Finance Automation, intercompany processes no longer rely on manual hand-offs. The system detects mismatches in real time across subledgers and general ledger accounts. It assigns ownership based on predefined rules tied to legal entities, transaction types or chart of accounts structures.

From there, workflows operate inside the platform, not outside it. Approvals happen in context. Audit trails are complete. Once approved, the intercompany journal entry is posted directly into SAP, which updates both sides of the transaction.

This applies across complex scenarios: intercompany loans, expense allocation, cost allocations, sales of goods and fixed assets transfers. Whether dealing with base currency adjustments, exchange rates or arm’s-length requirements under International Financial Reporting Standards (IFRS), the process remains consistent.

When your intercompany solution orchestrates the process, the train doesn’t stop at the signal. It continues through to its destination.

Finish what matching starts

Matching is only a signal, but the discrepancy continues without execution. Unresolved intercompany balances delay consolidation. They distort currency translation. They create double-counting risk in financial statements. They trigger internal disputes between business units and receiving subsidiaries. And they weaken decision-making because leadership is working with numbers that are still shifting.

Another example of intercompany journal entries makes this clear. If company A records a debit to intercompany receivable and company B fails to post the corresponding credit to intercompany payable, the imbalance carries forward. That single gap can cascade across reporting cycles and affect the balance sheet, financial position and consolidation outcomes.

Finance Automation ensures this doesn’t happen. Through rule-driven automation, it generates mirrored intercompany journal entry pairs, enforces approvals and posts across both entities’ books simultaneously. Cross-book posting orchestration keeps accounting records aligned and provides a complete audit trail from detection to resolution.

What begins as a small mismatch doesn’t grow into a bottleneck because it’s resolved at the source. Without this level of execution, intercompany accounting remains reactive. With it, the process becomes controlled, predictable and aligned with the demands of modern financial reporting.

Finance Automation is a platform designed to fully resolve this cycle end-to-end. The train won’t stall because underlying manual processes are still waiting for your team to complete them.

Learn more about what happens after the “match” to get your close train back on track.