Invoice management

Wrong amounts and missing details are best caught before the invoice goes out. If the customer finds the error first, or a supplier calls about a payment that never left, someone has to correct the invoice and work out what happened. That is a conversation to have, not a line to fix.

What a flow that works looks like

1. The source data is created where the work happens: in the timesheet, the order or the contract, not in a spreadsheet someone fills in afterwards.
2. The invoice is created from your own business logic, with the right customer, the right price and the right VAT rate.
3. It is sent in the format the recipient requires, including as an e-invoice via Peppol, which the public sector requires.
4. Incoming invoices are read and matched against orders or contracts. Your approval rules decide what goes through without sign-off and what gets stopped.
5. The flow is reconciled against the ERP, with an exception list that someone owns and can work through.

What does manual handling cost?

More than the hours. A customer invoice that goes out late gets paid late, and a supplier invoice left sitting in an inbox can go past its due date. Start with the hours anyway: the number of invoices a month times the time each one actually takes to handle. Then add what you paid in late-payment interest and reminder fees over the last year. That gives you a figure to set against building something.

We connect the flow to the ERP you already run, such as Fortnox or Visma, through ERP integration.