Home/Process library/Debtor management at a technical services company
Process library · Technical servicesFrom invoice to paid: debtor management at a technical services company
Every sales invoice is linked to its project, sent out, followed up with reminders when payment is late, and closed automatically when the accounting system sees the payment. Finance only steps in where a decision is needed.
See the flow Map your own flow
In short
In this scenario a technical services company follows every sales invoice in M-Files from creation to payment. The invoice comes from the accounting system, the invoice and project number are read automatically and the invoice is linked to its project. It is booked and sent by mail or post. When payment is late, reminder levels and collection follow as workflow steps. M-Files sees the payment through the matching in the accounting system and closes the invoice. SoftAdvice designed and documented the process.
Many projects, many invoices, one finance team
An invoice has been open for weeks. Nobody knows if a reminder went out.
A technical services company works with technicians in the field on many projects at once. Every project leads to invoices, and every invoice has to be sent, followed up and, when payment is late, reminded.
Without a process, that follow-up lives in a spreadsheet and in the heads of a few people. Reminders go out late or not at all, and nobody sees which project an unpaid invoice belongs to.
- Invoices created in the accounting system
- Each invoice tied to a project
- Sent by mail or by post
- Payments seen in the accounting
What runs by itself, at every beat
Debtor management follows the life of every invoice. The process knows at each moment what comes next.
Every invoice
Read and linked
Invoice and project number are read, and the invoice is linked to its project.
Every day
Booked and sent
New invoices are booked and go out by mail or post.
After the due date
First reminder
Unpaid invoices move to reminder level 1, by mail or by post.
Still unpaid
Second reminder and collection
Level 2 follows, then the invoice is prepared for collection when needed.
On payment
Closed by itself
The accounting matching marks the invoice as paid or credited, and the workflow closes it.
From invoice to paid, step by step
Most steps run on data from the accounting system. People choose how to send and decide on collection.
Capture and link
The invoice comes from the accounting system as a PDF. Capture software reads the invoice and project number, and M-Files links the invoice to the project.
Book and send
The invoice is booked and sent to the customer by mail or by post.
Remind
When payment is late, the invoice moves to reminder level 1 and later level 2. A colleague chooses mail or post for each reminder.
Collect or close
If it stays unpaid, the invoice is prepared for external collection. As soon as the accounting shows it paid or credited, the workflow closes it.
Every exception has a state
An invoice without a project number, or with a wrong one, does not disappear into a pile. It gets its own state, so finance sees it and corrects it before it goes out.
- No project number on the invoice: its own state
- Wrong project number: flagged for correction
- Any invoice can be put on hold
- Key steps confirmed with an electronic signature
From chasing invoices to managing exceptions
The team no longer keeps a list of who still has to pay. The process keeps it, and shows only what needs a decision.
Before
- Open invoices tracked in a spreadsheet
- Reminders sent when someone remembers
- No link between invoice and project
- Checking payments by hand
Now
- Every invoice has a clear state
- Reminder levels follow by themselves
- Invoices visible per project
- Paid invoices closed from the accounting
M-Files, connected to the accounting system
The process runs in M-Files, but the data comes from the systems the company already uses.
Accounting data in M-Files
Customers, suppliers, ledger accounts, VAT codes, departments and bookings are read from the accounting system, so documents carry real accounting data.
Capture of invoices
Capture software reads invoice and project numbers from the PDF and hands them to M-Files.
Workflow with signatures
Reminder levels, collection and closing are workflow states; key steps are confirmed with an electronic signature.
Process architecture first, software second
We drew every state and transition of this process before we built it. Writing the process down is part of our Success Services.
Map
We map how invoices really flow today and who follows them up.
Design
We design the states, reminder levels and exceptions in a process diagram.
Connect
We connect M-Files to the accounting and project systems.
Document
We write the process down, so finance knows what happens and what to check.
Questions about this scenario
Does M-Files replace our accounting software?
No. The accounting system stays the place where invoices are created and payments are matched. M-Files follows the invoice as a document and reads the accounting data it needs.
Can we set our own reminder rules?
Yes. The number of reminder levels, the timing and the choice between mail and post are set to match your payment terms and way of working.
What if a customer disputes an invoice?
The invoice can be put on hold at any step. When a credit note follows, the accounting marks the invoice as credited and the workflow closes it.
Is this only for technical services companies?
No. Every company that sends many invoices tied to projects or orders can work this way.
How many invoices are waiting for a reminder today?
In Discovery we map your invoice flow and show where it can run by itself.
