One payout covers hundreds of orders
The bank line is a single sum, net of fees and refunds. The work is finding every invoice inside it.
The problems every online shop on Business Central has with payment providers, and how Kvitta handles each one. Then the rules, the safeguards, and who it is for.
Matching the two is a daily job in every online shop on Business Central. Here is what eats the time, and what Kvitta does with each.
The bank line is a single sum, net of fees and refunds. The work is finding every invoice inside it.
A short payment, a refund with no credit memo, a reference nobody recognises. The spreadsheet waits until someone decides.
Add-ons and partners change matching for you, on a quote and a release date.
Logic built inside Business Central is limited to what an extension can do, and every change waits for a release.
Log in to each portal, download, paste, check, post. Then again tomorrow.
The method lives in one head and one spreadsheet. Holidays and sick days stop the close.
Each rule is one sentence. It runs the same way every day, until you change it. No ticket, no release window.
Kvitta reads every open customer entry in Business Central, not just today's payouts, and sorts them into lists with the action each one needs. Close a set in one posting, write off rounding together, or chase what is overdue.
The expensive mistakes in this work are the quiet ones. Kvitta is built to stop them.
One price per company, never per seat.
Why each payment provider should have its own bank account, with a worked example.