Resolve payment reminders

Payment reminders get resolved before they escalate.

Recognize supplier payment reminders, match them against open items and payments, and reply.

Book a call

30 min · free · no prep needed

  • Comes in viaEmail
  • You decide onDisputed case
  • Lands inAccounting
Before → After · Resolve payment reminders

Today: lots of manual work.

  • Payment reminders land in the shared inbox and sit there.
  • For every reminder, you dig up the invoice and payment status.
  • Items that are already paid still get reminders – and nobody replies.
  1. Reminder arrives by letterMail opened, stamped and put in the routing folder by hand
  2. Which invoice was that?Invoice number searched in binders, the inbox and the ERP by hand
  3. Flipping through bank statementsPayment searched in the bank statement, line highlighted by hand
  4. Asking around the office“Who approved this?” – the answer comes after vacation by hand
  5. Type reply, file a copyReply to the supplier typed, printed, copy into the binder by hand

Example: Payment reminder MA-2026-0091 from Alpenstahl GmbH – waiting in the inbox

Custom

Describe it, don’t code it.

This is how the XFLOWLY Agent builds the “Resolve payment reminders” flow – in conversation, tested with a sample document. Your rules, your systems.

Resolve payment remindersDraftOverviewSpecial cases
Instructions
The flow takes shape as you describe it.

Example with synthetic data – on a call, we’ll show it with your own document.

Your systems

Works with what you already have.

From SAP to the Excel sheet: XFLOWLY connects to your systems and replaces none of them. Highlighted are the ones typically involved in supplier payment reminders.

S/4HANAECC / R/3Business OneBusiness CentralDynamics 365Navisionabas ERPproALPHAInforOracleOdooweclappXentralWawiSage
DATEVNTCSLexwareRZLDiamantSalesforceHubSpotPipedriveShopwareShopifyMagentoDocuWared.velopELOM-Files
SharePointOneDriveOutlookExchangeTeamsGmailExcelGoogle SheetsServiceNowJiraZendeskFreshdeskPersonioSuccessFactors

And everything without a big name:CAQ systemMESTime trackingPayroll softwareREST & ODataSQL databaseSFTP & network drivePortal without an APIIn-house software

Your system isn’t listed? XFLOWLY still connects – via API, database, file or directly through the user interface. Nothing gets replaced.

Check the connection on a call
Experience built in

Typical challenges – planned for from day one.

We know from experience what tends to go wrong with supplier payment reminders day to day. The flow catches it.

Content & discrepancies

The overdue invoice was paid long ago.

How the flow handles it

Payment date and reference are provided right away for the reply to the supplier.

What the flow covers

  • Recognize payment reminders and extract supplier, invoice, amount, dunning level and deadline
  • Find the invoice, open item and outgoing payment in the supplier account
  • Distinguish paid, scheduled, blocked, unknown and disputed cases
  • Route cases to accounting or purchasing
  • Prepare a reply with a payment advice or a request for an invoice copy
Practical example · Building materials trade

Supplier dunning letters are answered the next day – with proof of payment, before a delivery block looms.

  • Building materials trade
  • Building materials dealer
  • ≈ 320 employees
  • 8 locations
  • ≈ 220 dunning letters per month
  1. 1Starting point

    Dunning letters arrived at all eight locations and at headquarters. For each one, accounting pieced together invoice, payment and block reason; disputed cases sat untouched until a supplier threatened to stop deliveries.

  2. 2Implementation

    • Dunning letters are recognized – even when they come as account statements or payment reminders – and matched to the invoice in question.
    • Payment status, payment date and block reason come straight from Dynamics 365.
    • Paid invoices are answered with proof of payment; missing invoices are requested as copies.
    • Disputed cases go to the responsible location with all documents attached; the reply is already drafted.

    ConnectedDynamics 365Outlook

  3. 3Outcome

    • ≈ 65%run through without manual intervention
    • ≈ 35 hrsless manual work per month
    • 1 day instead of 9until the supplier gets a reply

    Time saved calculated with 15 min of manual work per transaction before.

Project timelineLive after 4 weeks

  1. Week 1WorkshopReply templates and responsibilities per location defined.
  2. Weeks 2–3Test with real documentsRan two months of past dunning letters through the flow.
  3. From week 4LiveLive for headquarters and all locations.
Good to know

Common questions about supplier payment reminders.

Rainer GruberAlexander TraxlerReinhard SchnetzingerCan’t find your question?

Ask the founding team directly – on a call or with a quick email.

Book a call

It reads payments and open items directly from your accounting system and matches them against the invoice in the reminder – including early-payment discounts and credit notes.

Only if you want it to. By default, the flow drafts the reply; disputed cases are always decided by Accounting.

The flow looks up the invoice in your open items list (open item matching) and checks invoice status, due date and payment block. Payment matching finds payments, including partial and bulk payments; credit note matching finds open credit notes. Then come dunning level matching and the check of dunning fees. If you do not have the invoice, the flow requests it from the supplier.

The flow prepares the reply with proof of payment or payment advice and the clearing document. It finds the usual reason as well: an unassigned payment at the supplier, a mismatched invoice reference, an early-payment discount deduction or a credit note that is still open. A disputed remaining balance or a blocked invoice goes to accounting with a clarification note.

Yes. If the supplier sends an account statement, the flow matches it against your accounts payable account (balance reconciliation) and shows every difference with the document. Clarifying remaining balances runs with follow-ups until the account reconciliation adds up.

No. This use case covers incoming reminders from your suppliers. Dunning runs and dunning blocks in your own accounts receivable are a separate process – if needed, we set up a separate flow for it.

That's exactly what the flow is built for. Every value it reads stays linked to the original document, and check rules match it against your ERP. Discrepancies, missing data or unclear matches create a task for the person responsible – with the document, the comparison and decision options. The case then continues right where it left off. Values that aren't in the document are never made up.

You decide: in the XFLOWLY Cloud on a dedicated virtual machine at Google Cloud in Frankfurt – or on your own server (on-premises) running Windows or Linux. Stored data is encrypted with AES-256, and credentials for your systems are additionally kept in a separate secret vault. You'll find all the details in the security factsheet on the platform page.

Easily: after a three-month minimum term, you can cancel XFLOWLY monthly with 14 days' notice. When your subscription ends, we provide a full export – documents, results and your flow definitions in machine-readable formats, available for 30 days at no extra cost. After that, your environment is deleted.

Can’t find your question?Ask us on a call
All questions

Processes that run themselves.

One call, your real process, no prep work. Afterwards, you’ll know what XFLOWLY can do for your business.

Book a call

30 minutes · free · no prep needed

0 cases handled since you got here · Click the logo to send another one through