Close

PlaniFi Intercompany Matching and Reconciliation (ICMR)

PlaniFi Intercompany Matching and Reconciliation (ICMR) · Matching across every system in the group

Your problem is not inside a system. It is between them.

Intercompany reconciliation is one of the most stubborn headaches in the financial close. When trading entities sit on different systems, each has its own chart of accounts and its own way of identifying trading partners. ICMR matches across all of them.

What the solution delivers

What changes for the people who run the close, rather than a list of features.

Close days come back

Intercompany matching runs automatically, so the manual spreadsheet work that eats days of every close mostly goes away.

One view across every ERP

SAP and non-SAP entities sit in one model, even when their charts of accounts, master data and partner IDs do not line up.

Differences show up early

Variances appear in SAC as they happen, not at period-end, so they get fixed before they hold up the close calendar.

Less chasing

Finance teams drill into a difference and resolve it in one place instead of emailing counterparties back and forth.

A clear audit trail

A transparent, repeatable process replaces matching that lived in someone's head and spreadsheets, so controllers can see and explain every difference.

Why the close keeps slipping on this step

The reasons intercompany holds up a close, in the words finance uses for them.

  • Trading entities sit on different systems. Each one has its own chart of accounts and its own way of identifying trading partners, so the same transaction looks like two unrelated records.
  • The matching gets done by hand, in spreadsheets, against a period-end deadline.
  • Disagreements get settled by email between counterparties, which is slow and leaves no audit trail anyone can follow later.

How it works

Where the work happens, and what sits underneath it.

How intercompany matching and reconciliation works Transactions from several unrelated systems flow into SAP Business Data Cloud. SAP data installs as data products without replication, non-SAP data is brought in, and SAP Datasphere harmonizes accounts, master data and partner identifiers. Above it, the ICMR view and PlaniFi Consolidations both run on SAP Analytics Cloud and work against the same intercompany balances. Trading entities, different systems Entity ASAP ERP Entity BNon-SAP ERP Entity CAnother ledger SAP Business Data Cloud ICMR view Status at a glance Drill into the differences Resolve them PlaniFi Consolidations Intercompany eliminations and the group close Runs on SAP Analytics Cloud ↗ SAP Datasphere SAP data as data products, no replication. Non-SAP data brought in. Reconciles differences in accounts, master data and partner identifiers ↗ Own chart of accounts. Own partner identifiers. No waiting for period-end. No chasing counterparties by email.
All of it sits inside SAP Business Data Cloud. Your SAP data arrives as data products, installed into Datasphere without replication, and your non-SAP data is brought in alongside it. Above, the ICMR view and PlaniFi Consolidations work against the same intercompany balances on the same platform, so agreeing a balance and eliminating it are not two separate systems.

SAP Datasphere harmonizes the data

Transactions come in from SAP and non-SAP systems. Datasphere reconciles the differences in accounts, master data and partner identifiers, so records that describe the same transaction are recognized as the same transaction.

SAP Analytics Cloud is where your team works

Finance sees reconciliation status at a glance, drills straight into the differences, and resolves them. There is no waiting for period-end and no chasing counterparties by email.

What you get

What is in the box when the module is switched on.

Matching across systems that do not line up

Intercompany transactions matched across disparate SAP and non-SAP systems, even when the accounts, master data and partner identifiers disagree.

A process your team can act on

A manual, spreadsheet-bound reconciliation becomes a transparent, near real time process.

A realistic path to standing it up

A clear view of the architecture and what it takes to run this in your own landscape.

This is not standard content

Packaged content that ships with a platform is written once and then waits for the next release. This is not that. The content behind PlaniFi is based on more than a hundred implementations and a few hundred close cycles, and every one of them feeds back into it. It is actively maintained, improved, extended and optimized rather than frozen at the moment a template was first written.

That matters most where a template cannot anticipate the shape of the problem. Charts of accounts that were never designed to agree. Partner identifiers that differ by entity. An acquisition that lands mid-year with its own conventions. Those are cases the content has already met, because someone met them first and the answer went back into the product.

Who this is for

Controllers and consolidation leads who own the intercompany step of the close. Shared services and accounting managers whose teams do the matching by hand today. CFOs and finance directors of multi-entity, multi-ERP groups. If your close calendar has ever slipped because two entities could not agree on what they owe each other, this is aimed at you.

Why this rather than the matching already in your ERP

Native tools reconcile inside one system. Your problem lives between systems. A multi-ERP group gets something here that module level matching cannot give it: one reconciliation view across every system, no matter who runs what.

See it run

The demo

A recorded walkthrough of the solution, on the SimpleFi YouTube channel. Nothing to register for.

Watch the demo

The full webinar

30 minutes, virtual. Register to watch it, and the recording goes to everyone who does.

See webinar Talk to us about your close

Part of PlaniFi, not a bolt-on

ICMR is a module of the PlaniFi EPM solution. It is not a separate product stitched onto it, and it does not bring a platform of its own.

One SAP product, not an integration

It runs inside SAP Business Data Cloud, the same SAP product as PlaniFi Consolidations and the rest of the PlaniFi EPM solution. There is nothing in between to integrate, monitor or keep in version.

The same architecture

SAP Datasphere underneath, SAP Analytics Cloud above. That is how the consolidation application itself runs, which is why adding a module does not add an architecture.

The same interfaces

Your team works in SAP Analytics Cloud, where they already review and report. No second tool to learn and no second place to look for the status of the close.

The same licensing

It runs on the SAP platform licensing you already hold for PlaniFi. No third party license and no separate subscription to renew and defend at budget time.

SAP Datasphere plays a foundational role in SAP's broader strategic vision to unify data, analytics and planning across the intelligent enterprise. A module that runs there moves in the direction SAP is investing in, rather than having to keep pace with it from the outside.

Where this sits

ICMR is a module that adds to the core consolidation application. It is not a replacement for it, and it is not a standalone purchase.

PageWhat it is
PlaniFi Consolidations The core application. Consolidation process and rules, eliminations, roll forwards, cash flow, top-side journals.
PlaniFi Account ReconciliationCertifies that account balances are supported, in a uniform cycle every period, with the review recorded.
PlaniFi Month End Close Agent Runs the close process itself, in a fixed order, every month.
PlaniFi Data Consolidator Mapping and transformation, so the data arriving in the close is already under control.

Talk to us

See it against your own close

Thirty minutes, your close calendar, and an honest view of whether this fits. No deck.

  • Please use your work address. We do not send to personal mailboxes.
  • Do not polish it. We would rather see the real thing.
  • This field is for validation purposes and should be left unchanged.