Netting

Netting shows up most often where a company is your customer and your supplier at the same time; the receivable builds on one account, the payable on another, and only the difference moves at period end. It is also standard inside a group, where subsidiaries run a central netting cycle instead of paying each other one by one. Advances, credit notes and mutual charges are pulled into the same calculation, and what reaches the bank statement is a single line. The ledger still carries every invoice and note that line was meant to settle. Netting itself is not the problem. The problem is that the decision rarely records which items it covered. In practice the agreement is sometimes formal and sometimes just a phone call between two accounting departments, and in the second case no document records which invoices were offset.

In reconciliation, netting breaks every rule that depends on matching amounts. A net transfer equals no single invoice, so something has to decide which invoices it clears and in what order. This is exactly why first-in-first-out application, invoice-specific application and partial payment splitting exist. When the two parties apply the same net amount differently, the balances keep agreeing while the open item lists drift apart: you have closed the March invoice, they have closed the April one. At the next confirmation the totals show no difference while the lines refuse to agree. How the net amount was allocated matters as much as the net amount itself. Foreign currency items make it harder still: if the two sides were booked at different rates, the net amount will not tie to the last kurus and the small residue has to be separated as an exchange difference.

The most common confusion is mistaking netting for reconciliation. Netting is a decision to offset two balances; reconciliation is the evidence that the items really do offset each other. Netting without that verification does not remove an error, it buries one: a duplicated invoice or an unrecorded return simply dissolves into the net figure. A second confusion is treating the single bank line as proof. It proves that money moved, not which obligation it settled. iFinances allocates a net movement across the items behind it, records the reason for that allocation and lists whatever remains as an exception. It does not keep your books and never closes a line on its own. Both routes into the platform are ready. You can upload statements, invoice lists and bank files as Excel or CSV, or connect directly to the system that holds them, and the route is chosen with you during setup.