Cross-Entity AP Settlement
Group treasury pays from one bank account; the bills belong to many companies. Cross-entity settlement lets one entity’s payment settle another entity’s invoice — with the intercompany bookkeeping that keeps both sets of books true generated automatically. This article covers when it’s allowed, what it records, and the one thing it deliberately refuses to do.
Access you'll need. Making the application requires the Accounts Payable v2 permission set (AP clerks & managers) or Accounting Admin v2 (system administrators). The Accounting Controller v2, Accounts Receivable v2, and Read Only v2 sets can review the settlements and IC balances but change nothing; the entity flags and IC account configuration are administrator setup.
The rule: both entities must consent
Cross-entity settlement is off by default and enabled per entity, per direction. For the AP side, the entity policy checkbox is Allow Cross-Entity Settlement (AP) — and it’s bilateral: the paying entity and the entity that owns the invoice must both have it enabled. One flag missing, and the application is refused. (The AR mirror — one entity’s receipt settling another’s sales invoice — has its own flag: Allow Cross-Entity Settlement (AR).)
What actually happens
Suppose Meridian’s US entity pays a $5,000 bill that belongs to its UK sister. The payment is a normal Cash Disbursement from the US entity; the application to the UK invoice is a normal application — you don’t do anything special. On top of the usual settlement bookkeeping, REDA Financials records the intercompany pair:
| Account (Entity) | Debit | Credit |
|---|---|---|
| Intercompany Receivable (US — the payer is owed) | $5,000 | |
| Intercompany Payable (UK — the beneficiary owes) | $5,000 |
- The UK invoice is settled; the vendor is paid; the UK company’s debt has simply moved — it now owes its US sister instead of the vendor.
- Each entity’s intercompany account comes from its own configuration (the entity’s default IC Receivable and IC Payable accounts) — set these up before enabling the flags.
- The entries are created with the application and removed with it: delete or unwind the application and the intercompany pair goes too.
Before it will work — the checklist
| Requirement | Where | If it's missing |
|---|---|---|
| Allow Cross-Entity Settlement (AP) ticked | On both entities — payer and invoice owner | The application is refused; the message names the cross-entity block |
| Default IC Receivable / IC Payable accounts configured | On each participating entity | There is nowhere to book the intercompany pair — set these up first |
| Same vendor on payment and invoice | Both documents | Applications only ever settle the paying vendor's own bills, cross-entity or not |
| A posted payment with unapplied money, a posted open invoice | The documents themselves | The ordinary application rules apply unchanged — cross-entity adds bookkeeping, it doesn't relax anything |
What it refuses to do: memos
Credit and vendor memos never cross entities. A memo adjusts revenue or expense, and that adjustment belongs to the entity that recorded the original document — moving it across companies would misstate both income statements. So memo applications are always same-entity; only cash settles across the group. If a memo’s credit genuinely needs to benefit another entity, the clean route is cash settlement or an expense allocation, each of which creates proper intercompany balances.
Setting it up (administrators)
- On each participating entity, configure the Default IC Receivable and Default IC Payable accounts.
- Tick Allow Cross-Entity Settlement (AP) (and/or AR) on every entity that should participate — remember, both sides of any given settlement need it.
- Agree the housekeeping: who reviews intercompany balances, how often they’re netted or settled, and in which currency. The system records the balances; the policy is yours.
Keeping intercompany balances honest
Every cross-entity settlement accumulates in the entities’ IC accounts — visible on each entity’s balance sheet and drillable like any account. Group accountants typically reconcile the mirror-image balances monthly (US’s receivable from UK should equal UK’s payable to US) and settle or net them periodically via intercompany journal entries or actual transfers.
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Enabling the flag on one entity only | Every settlement attempt fails — the consent is bilateral by design | Enable it on both sides of each relationship that should settle |
| Making cross-entity payment the default habit | Intercompany balances balloon, and month-end reconciliation grows with them | Pay from the owning entity where practical; reserve cross-entity for genuine treasury pooling |
| Trying to spend one entity's memo on another's bill | Refused, always — memos adjust the recording entity's own books | Settle in cash across entities, or share the cost via expense allocation |
| Skipping the monthly IC mirror check | A missed or unwound application leaves the two entities disagreeing about their mutual debt | Reconcile each pair: one side's IC receivable must equal the other's IC payable |
| Enabling flags before the IC accounts exist | Settlements have nowhere to book the intercompany pair | Configure Default IC Receivable and IC Payable first — then tick the flags |
Where to go next
- Understanding Expense Allocation — sharing costs rather than payments.
- Intercompany Journal Entries — manual cross-entity accounting.
- Cross-Entity AR Settlement — the receivables mirror.
Frequently asked questions
One (or both) of the entities doesn’t allow it. Check Allow Cross-Entity Settlement (AP) on the paying entity and the invoice’s entity — administrators can enable it on the entity records. If policy says it shouldn’t be enabled, pay the bill from the owning entity’s own account instead.
The paying entity’s — the cash truly left its account, which is why its books gain an intercompany receivable rather than an expense. Reconciliation stays clean on both sides.
Cross-currency settlement layers exchange-rate questions onto intercompany ones. Keep settlements within a currency where you can; where you can’t, involve your group accountant — the multi-currency rules in Understanding Multi-Currency apply on top.
They're deleted with it. The IC pair exists only to describe that settlement; undo the settlement and the mutual debt it created goes too. The invoice reopens, the payment's unapplied amount returns, and both entities' IC balances shrink by the amount.
The application itself is ordinary AP work — Accounts Payable or Accounting Admin. The entity flags and IC account configuration are administrator setup. Accounting Controller and Read Only can review the settlements and the IC balances they create, but change nothing.
Was this article helpful?