Our money flows through several systems and accounts. Where does Nance start?

Usually at partner payout reconciliation, because that is where the most hours and the most risk sit. From there it expands to the intermediate accounts, the revenue splits and debtor management, at the pace you choose.

Does Nance replace our internal systems or our ERP?

No. Your platform keeps processing transactions and your accounting system stays the source of truth. Nance works between them, and where you allow it, reads directly from your production database and data warehouse.

Our money flows are unusual. Multi-sided, pass-through amounts, balances at several providers.

That is the normal case here, not the exception. Platforms move money between parties by design. Nance applies your rules per flow and per party, and asks when it hits something genuinely new.

How much control do we keep?

Full control. You decide which actions run automatically and which wait for approval, and every action is logged with its reasoning.

AI finance ops for platforms and marketplaces: payouts, splits and the close

Platform finance has a particular shape: every transaction touches at least three parties, but the money arrives in lumps that hide all of them. Partner payouts go out in batches, each one covering a high volume of underlying transactions that someone matches in Excel. Cash waits on PSP balances and suspense accounts where the accounting system's matching rules stop helping. Partner invoices arrive long after the bookings they cover, the take rate has to be split correctly on every transaction, and the debtor list is a long tail nobody has time to chase. The team ends up reconciling batch files at exactly the moment volume is climbing.

Nance is built for that shape. It connects to your payment providers, your inboxes, your accounting system, and where you allow it, your production database and warehouse. Then it runs the layer between them: every payout decomposed to the transaction, every intermediate account allocated continuously, every split booked per party, every bulk invoice checked at line level, every overdue counterparty chased on your rules. The flows can stay multi-sided. The finance ops stop depending on the spreadsheet.

The shape of Platforms & marketplaces finance.

Partner payout reconciliation

One batch payment per partner, an entire period of transactions behind it. Nance breaks every payout run down to the underlying transactions and matches them line by line, so the Excel sheet that used to do this can finally retire.

Intermediate accounts that stay clear

Money sits on Stripe, Mollie and Adyen balances and internal suspense accounts on its way to where it belongs. Nance allocates it continuously, including the flows where standard accounting-system matching rules give up.

The gap between booking and invoice

The transaction happens now, the partner invoice arrives much later. Nance keeps the two connected, so the AP cycle stops stretching and the close stops waiting on paperwork that covers last period.

Revenue shares booked per party

Every transaction splits into partner revenue, your platform fee and amounts you only pass through. Nance books each piece to the right party and the right account, instead of leaving the take rate to a spreadsheet formula.

Carrier and vendor invoices verified at line level

Bulk invoices from carriers and service partners look fine at the total. Nance matches them line by line against your own records and surfaces the small per-unit discrepancies that are invisible any other way.

Debtor management at volume

A long tail of small counterparties, none of them worth a manual chase, all of them worth chasing. Nance runs the reminders and escalations on your rules and only hands you the cases that need a human.

Frequently asked questions

Built for platform and marketplace finance ops