Skip to Content
  • Solutions

    Your challenge

    By challenge

    Start from the problem you have today.

    Solving document chaosFind every document by what it isRemoving manual workLet the system file and forwardEliminating audit stressEvery file audit-ready, every dayPreparing data for AIThe right version for AIAI across all your systemsOne governed knowledge layer

    Your sector

    By sector

    Blueprints for regulated sectors where documents carry liability.

    Read client cases →
    Accountancy & audit firmsPermanent files to e-signatureFinancial servicesKYC, contracts and client filesLegalMatters and deadlinesConstruction & engineeringDocument control and transmittalsManufacturingSpecs, quality and supplier filesPublic sectorRecords and compliance

    Your process

    By process

    One process, end to end.

    See the process library →
    Contract managementFrom first draft to renewalQuality management (QHSE)ISO, procedures and auditsPersonnel files (HR)Right access, right retention

    Free advice call

    Not sure where to start?

    Thirty minutes with a process architect. No obligation.

    Audit scoreHow audit-ready are you?Contract risk scoreHow big is your risk?

    Book a free advice call

  • Platforms
    M-Files

    One search bar for all your business information, with AI on your own documents.

    Why M-Files →
    M-Files AIAI on your own documentsCompare editionsWhich edition fits youM-Files HubshareSecure client portalM-Files MentNo-code document generationCompare M-FilesAgainst SharePoint, DocuWare, OpenText and more
    SharePoint +MacroView

    Mail and documents in SharePoint, managed as real case files.

    MacroView overview →
    SharePoint with SoftAdviceMicrosoft 365 as your document platformFiling from OutlookE-mail in the right file, in one moveAutomatic e-mail filingRules that file by themselvesAll MacroView featuresEvery feature on one pageMacroView or M-Files?An honest comparison
    Mindbreeze

    AI answers across all your systems, from trusted sources.

    Mindbreeze overview →
    Use casesSeven scenarios to start fromMindbreeze Insight WorkplaceAI agents and governed workflowsAgentic AIThe right context for every agentDeployment and securityCloud, hybrid or on premises
    dox42

    Automate every document, from any system.

    dox42 overview →
    dox42 with M-FilesGenerate straight into M-FilesPlan a dox42 demoSee it on your documentsAll integrationsERP, CRM, e-signing and more

    See it live.

    One hour, online, on your real use case.

    Plan an AI readiness talkFor AI across all your systemsMicrosoft 365M-Files and Microsoft, together

    Plan a demo

  • Approach

    How we work

    Process first. Technology second.

    Five steps from analysis to a working system, with one team end to end.

    See our approach →
    1. DiscoveryHalf-day session, advice within 10 days2. Discovery & designMap your processes and information3. Implementation & configurationBuild and configure your platform4. Integrations & customisationConnect and tailor to your systems5. Success servicesAdoption, support and growth

    AI governance

    AI you can defend

    Policies, controls and oversight for AI on your data.

    Governance framework →
    Shadow AI under controlWhat it is and how to contain itIs your data ready for Copilot?Check it before you switch it on

    Price request

    What does it cost?

    Transparent pricing per platform and per service.

    Price calculatorEstimate your licence costROI calculatorCalculate your savings

    Request a price

  • Knowledge

    Learn

    Knowledge Hub

    Learning, proof and what changes.

    Open the Knowledge Hub →
    BlogLong reads on information architectureWebinarsLearn it in an hourAnalyst reportsGartner and Forrester, no paywallUpdatesProduct news, translated into impact

    Regulation

    What the rules mean

    What each rule means for your documents.

    Regulation overview →
    PeppolMandatory in Belgium since 2026NIS2Cybersecurity duties for the mid-marketeIDAS 2The EU digital identity walletEU AI ActWhich obligations apply whenRetention periodsBelgium, the Netherlands and Luxembourg

    Free tools

    Answers in minutes

    Quick checks you can run today.

    SharePoint or M-Files?Take the 8-question quizRetention period lookupHow long to keep what

    AI Readiness Scan

    Is your data ready for AI?

    7 questions, your score out of 100 and concrete next steps.

    NewsletterOnce a month, in your language

    Start the scan

  • Cases
  • Who we are
  • Client zone
SoftAdvice - Proces & information architects
  • Plan a demo
  • Nederlands Nederlands (BE) English (US) Français (BE)
SoftAdvice - Proces & information architects
      • Solutions
      • Platforms
      • Approach
      • Knowledge
      • Cases
      • Who we are
      • Client zone
    • Nederlands Nederlands (BE) English (US) Français (BE)
    • Plan a demo

    Home/Process library/Debtor management at a technical services company

    Process library · Technical services

    From 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

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-12
    Sector
    Technical services
    Process
    Invoicing
    Starts with
    Invoice
    Result
    Paid
    Building blocks
    M-Files
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Capture and link
    Automatic
    →
    2
    Book and send
    Automatic
    →
    3
    Remind
    Colleague
    →
    4
    Collect or close
    Decision
    →
    ✓
    Paid
    In shortRhythmFlowExceptionsBuilding blocksFAQ

    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.

    The moment

    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
    The rhythm of finance

    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.

    The flow

    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.

    Automatic

    Book and send

    The invoice is booked and sent to the customer by mail or by post.

    AutomaticChoice of channel

    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.

    Colleague

    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.

    DecisionAutomatic close
    When something goes wrong

    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
    What changes for finance

    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
    Building blocks

    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.

    Read more

    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.

    Read more

    How we work

    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.

    Related

    All scenariosFrom site visit to approved reportM-Files with ERP and CRME-signaturesSuccess Services
    Related blueprints

    More from the process library

    All blueprints
    Technical services
    BP-13
    Site visit
    Approved report

    From site visit to approved report

    The site visit report is done. Technical check, proofreading and translation still to come. It has sat on a desk for a week.
    Every report through technical check, language check and translation before approval, recorded with the project.
    Audit trail · Version control
    M-Files
    Technical services
    BP-17
    Service question
    Verified solution

    Technical knowledge for service and engineering

    A technician stands at a broken machine. The fix exists, somewhere in the service history. They call a colleague.
    Specifications, service history and parts data found in one place, so the engineer reaches a verified fix sooner.
    Audit trail · Permissions
    Mindbreeze
    DMS
    ERP
    Finance departments
    BP-26
    Billing system
    Delivered invoice

    From one outbox to every customer, via Peppol or e-mail

    The invoice run is ready for several companies. Some customers are on Peppol, others still want a PDF by mail. Someone sorts them by hand.
    Invoices of several companies picked up at one point, filtered and checked, then sent via Peppol or by e-mail per customer.
    Audit trail
    M-Files
    Peppol
    PowerPack

    How many invoices are waiting for a reminder today?

    In Discovery we map your invoice flow and show where it can run by itself.

    Start with Discovery

    SoftAdvice
    Process library
    Blueprint BP-12
    Technical services
    Invoicing
    From invoice to paid
    The moment
    An invoice has been open for weeks. Nobody knows if a reminder went out.
    Every sales invoice linked to its project, reminded when late and closed when the accounting sees the payment.
    The flow
    1. 1
      Capture and link
      Automatic
    2. 2
      Book and send
      Automatic
    3. 3
      Remind
      Colleague
    4. 4
      Collect or close
      Decision
    Blueprint BP-12
    Sector
    Technical services
    Process
    Invoicing
    Starts with
    Invoice
    Result
    Paid
    Building blocks
    M-Files
    Recognise this moment?
    Tell us about your own process. We look at it with you, without obligation.
    Discuss this processsoftadvice.eu/plan-a-callRead the full blueprintsoftadvice.eu/in-practice/technical-services-debtor-management
    Blueprint from the SoftAdvice process library. Real process, described anonymously.
    Only M-Files Solution Partner in the BeNeLux · 100+ implementations since 2010
    See the flow

    SoftAdvice

    Process & information architects

    Partner of M-Files since 2010, and of MacroView and Mindbreeze, in Belgium, the Netherlands and Luxembourg.

    Otterstraat 199
    2300 Turnhout, Belgium
    info@softadvice.eu
    Belgium +32 2 895 06 00
    Netherlands +31 79 799 61 40
    Luxembourg +352 27 86 46 55

    LinkedIn

    Platforms

    • M-Files
    • SharePoint + MacroView
    • Mindbreeze

    Integrations

    • dox42
    • Penneo
    • Microsoft 365
    • All integrations

    Services

    • Discovery
    • Process consulting
    • Implementation
    • Integrations
    • Success services
    • AI governance

    Company

    • Who we are
    • Knowledge Hub
    • Newsletter
    • Contact

    Partners

    M-Files Solution PartnerSolution PartnerMacroViewMindbreezedox42

    Newsletter

    Once a month, in your language. Unsubscribe at any time.

    Subscribe

    Thank you. You will receive the next edition in your mailbox.

    © 2026 SoftAdvice BV. All rights reserved.

    PrivacyCookiesTerms

    We use cookies to provide you a better user experience on this website. Cookie Policy

    Only essentials I agree