Missing counterpart entries
A posting on one entity with nothing on the other stays on that side.
Intercompany reconciliation
Upload both entities' intercompany extracts. When Company A receivable is 100,000 and Company B payable is 97,000, the 3,000 difference is a list of missing, mismatched, or unmatched postings — not a single unexplained plug.
Intercompany balances disagree because one side booked a charge the other has not, dates differ, or references do not line up. Spreadsheet nets hide those rows. A two-sided run keeps each mismatch inspectable.
How it works
Step 1
Receivable side and payable side, or both ledgers.
Step 2
Entity, document number, amount, date, and counterparty.
Step 3
Pair counterpart postings and leave unpaired rows on the side that has them.
Step 4
Missing counterpart, amount mismatch, date mismatch, reference mismatch.
Step 5
Share the same structured difference list with each entity.
What this workflow is designed to do with uploaded files.
A posting on one entity with nothing on the other stays on that side.
Same reference, different amount — both values remain visible.
Period differences can be listed even when the amount agrees.
Amounts that agree but references do not can be reviewed instead of auto-cleared.
Rows that cannot be paired remain in the exception list for both entities.
Company A receivable 100,000. Company B payable 97,000. Difference 3,000. The run shows a 2,400 charge booked only on A and a 600 amount mismatch on IC-441. The 3,000 is fully listed.
Sample preview
Sample pair. Figures are fictional.
| Field | Company A receivable | Company B payable | Difference |
|---|---|---|---|
| Closing balance | 100,000 | 97,000 | Difference 3,000 |
| IC-440 management fee | 12,000 | 12,000 | Matched |
| IC-441 inventory | 8,400 | 7,800 | Amount mismatch 600 |
| IC-442 allocation | 2,400 | — | Missing counterpart on B |
Intercompany work needs clarity and auditability. The result should say which documents created the difference, not only that a difference exists.
Continue with the workflows that usually sit next to this one.
No. It compares uploaded entity files and lists differences. It does not write to either ledger.
Each run compares the files you upload. Repeat the same recipe for other entity pairs.
Each file keeps its uploaded amounts. Matching uses the keys and rules you configure for that run.
Upload both entity extracts and review the documents that create the difference.