Short answer
Invoice collection software for agencies should first establish which client invoices are genuinely unpaid, then help someone follow up calmly with the right evidence. DIGITAL EUR covers the first half today: a free in-browser demo that matches client bank transfers to invoices with visible reasons. Reminder drafting with human approval is planned, not available, and nothing is ever sent automatically.
Why is collecting money harder for agencies than for most businesses?
Agencies rarely send one simple invoice for one simple deliverable. A single client relationship can produce a monthly retainer, a project milestone, a re-billed media or software cost and an ad-hoc change request, often in the same month. Each of those invoices passes through the client's own approval chain, and each can be paid in a different way. The result is a receivables ledger that is easy to misread.
The patterns that cause most chasing errors are well known to anyone who runs an agency's finances:
- Retainers paid by standing order. The client's bank sends the same amount every month with the same text, such as "Retainer Harbour", and no invoice number. If last month's retainer is still open, there is no way to tell from the transfer which month it pays.
- Pass-through costs. Media spend, licences and production costs re-billed at cost or with a mark-up. They are large, they often need a separate approval, and a query on one line can hold up the whole invoice.
- Deductions. A client disputes part of an invoice and pays the rest. The transfer arrives short, sometimes with an explanation, often without.
- Purchase-order references. The client's accounts payable team quotes its own PO number instead of your invoice number.
- Group payers. A holding company or a shared-service centre pays on behalf of the brand you work with, under a different name and IBAN.
Vendor guides for agencies agree on the commercial consequence: the hardest part of collection is not writing the reminder, it is avoiding the wrong reminder. Chasing a client for an invoice that was actually paid by the parent company last week costs goodwill that a creative relationship depends on.
What does DIGITAL EUR do today, and what is planned?
DEMO (available now, free, no account): the Reconciliation Lab runs in your browser. You load an open-invoice CSV and a bank transaction CSV, review suggested matches with their reason codes, approve or reject each one under your name, see each invoice's allocated and outstanding amount, and export approved allocations as CSV. Files are not uploaded or stored; reloading discards everything.
PLANNED (not available, no date promised):
- reminder drafts generated from the matched, still-open balance, which a person reviews and approves before anything is sent; see our collections page;
- saved history so that the open balance carries over month to month;
- invoice status tracking with due dates and ageing, described on our invoice tracking page;
- several users with an approval step, and camt.053 bank statement import.
There is no AI copilot, no automatic sending and no payment collection. DIGITAL EUR never holds, moves or requests money on your behalf.
Worked example: an agency's month, with synthetic data
The data below is invented. Northlight Example Studio is a fictional agency. We ran these exact files through the matching code that powers the demo.
Open invoices:
| invoice_id | Client | What it is | amount_due | reference |
|---|---|---|---|---|
| N-0931 | Harbour Example AG | September retainer (still open) | 4500.00 | N-0931 |
| N-1002 | Harbour Example AG | October retainer | 4500.00 | N-1002 |
| N-1003 | Harbour Example AG | October media pass-through | 12380.00 | N-1003 |
| N-1004 | Pinecone Example SL | Website milestone 2 | 6000.00 | N-1004 |
| N-1005 | Quayside Example SRL | Social campaign | 2150.00 | N-1005 |
Harbour's IBAN is stored on all three of its invoices. Pinecone's IBAN is stored on N-1004. Quayside's is not known.
Incoming transfers:
| transaction_id | amount | remittance | payer |
|---|---|---|---|
| C01 | 4500.00 | Retainer Harbour | Harbour Example AG |
| C02 | 11880.00 | N-1003 less 500 disputed | Harbour Example AG |
| C03 | 6000.00 | PO 7781 milestone 2 | Pinecone Example Holding SL (different IBAN) |
| C04 | 2150.00 | INV N1005 | Quayside Example SRL |
What the engine returned:
| Transfer | Best candidate(s) | Score | Reasons | Flag |
|---|---|---|---|---|
| C01 | N-0931 and N-1002 | 35 each | exact amount, IBAN, name | Ambiguous |
| C02 | N-1003 | 65 | reference, IBAN, name, possible partial payment | — |
| C03 | — | — | no reference, IBAN or name evidence | Unresolved |
| C04 | N-1005 | 90 | reference, exact amount, name | — |
The engine also lists weaker alternatives for Harbour's transfers (for example C01 against the media invoice at score 0) because the payer's name and IBAN match. They sit below the main candidates and a reviewer simply rejects them.
What this means for collection:
- C04 is settled. "INV N1005" matches N-1005 because references are compared as whole tokens with flexible separators. Approve it; Quayside owes nothing.
- C01 needs a decision, not a reminder. One retainer payment arrived; two retainer invoices are open. The software refuses to guess. Most agencies would apply the payment to the older invoice, N-0931, but that is a policy choice you should record. Either way, Harbour still owes one retainer, not two.
- C02 is a part payment with a stated reason. Approving it allocates €11,880.00 and leaves €500.00 open on N-1003. That €500 is a dispute, not a late payment, and it should be handled as one: confirm what is contested before anyone sends a reminder.
- C03 is probably Pinecone's milestone, paid by its holding company. The name and IBAN differ, and the remittance quotes the client's PO number, not the invoice number. There is no evidence the engine can use, so it stays unresolved. A person who knows the account can approve it manually in their accounting system, and should add the holding company's IBAN to the client record.
Without matching, a naive "unpaid invoices" list on this day would show all five invoices, or, if someone ticked boxes by amount, could easily mark the wrong retainer as paid. After review, the genuinely open position is one Harbour retainer, a €500 disputed amount and nothing else. Only the retainer is a candidate for a reminder.
How should an agency collection workflow run?
A collection process that protects client relationships follows the money, not the calendar. We suggest this order:
- Import and match first. Load the period's bank lines and open invoices, and resolve every suggestion before anything else happens.
- Separate disputes from delays. Short payments with a reason and client emails querying a line go to the account lead, not to a reminder sequence.
- Confirm the payer map. Keep a list of every name and IBAN that pays for each client, including holding companies and shared-service centres.
- Send a statement before a reminder. For clients with several open invoices, a short statement listing what has been received and what remains open resolves many questions on its own.
- Escalate by stage, with approval. Friendly reminder, firmer reminder, call from the account lead, then formal notice. Each step should be approved by someone who knows the relationship.
- Log every decision. Who applied which payment, who approved which message, and why.
Steps 1 and 6 are what the DIGITAL EUR demo does today. Steps 4 and 5 describe the planned collections workflow. Reminder templates, dunning stages and tone guidance are covered in depth on our collections page.
What should a client statement show before you chase?
A statement of account is often the most effective first "reminder", because it shows the client that you have already done the checking. For the Harbour example above, a useful statement would contain:
| Line | Content |
|---|---|
| Invoices issued | N-0931, N-1002 and N-1003, with dates, amounts and references |
| Payments received | C01 €4,500.00 and C02 €11,880.00, with the dates they arrived and the remittance text the client used |
| How payments were applied | C01 to the September retainer (N-0931), C02 to the media invoice (N-1003) |
| Still open | October retainer €4,500.00; €500.00 on N-1003 noted as "under discussion", not as overdue |
| Request | Confirmation of the October retainer payment date, and the reason for the €500 deduction |
Two details make the statement land well. Quote the client's own remittance text, so their accounts payable team can find each payment in their system. And keep disputed amounts visibly separate from late ones: mixing them is the fastest way to turn a query into a conflict. In the demo, the approved allocations and the invoice summary give you the figures for such a statement; a generated statement document is not part of the product.
What does EU law already give an agency that is paid late?
Between businesses in the EU, the Late Payment Directive 2011/7/EU, as transposed into national law, sets the baseline. In summary: contractual payment periods should not exceed 60 calendar days unless expressly agreed and not grossly unfair; statutory interest is the reference rate plus at least eight percentage points; and the creditor is entitled to a fixed sum of at least €40 for recovery costs. Where payment is agreed in instalments, interest and compensation are calculated only on the overdue amounts, which matters for milestone and retainer billing.
This is a summary, not legal advice. National rules and your contract decide the detail, and a client who is a few days late is rarely worth charging. The collections page sets out the rules article by article.
Which invoicing habits make collection easier?
Most collection problems start at the invoice. These changes cost nothing and make matching, and therefore chasing, more reliable:
| Habit | Why it helps |
|---|---|
| One invoice per billing type (retainer, media, project) | A dispute on media costs does not block the retainer |
| A unique reference on every invoice, repeated in the payment instructions | Gives the strongest matching evidence (+65 in our rules) |
| A structured RF creditor reference where clients' banks support it | The SEPA rulebook recommends it for single-invoice payments |
| Retainer invoices that name the month in the reference | Standing orders can be updated to quote it |
| Asking clients to quote your invoice number as well as their PO | Turns an unresolved transfer into a matched one |
| Recording every payer IBAN per client | Adds evidence when the reference is missing |
The SEPA Credit Transfer rulebook gives payers 140 characters of remittance information and requires banks to deliver it to you in full and without alteration. What the client types is what you receive, so ask clearly. Our SEPA reconciliation guide explains structured references in detail.
How does this compare with other ways agencies chase invoices?
| Approach | Strengths | Weaknesses |
|---|---|---|
| Spreadsheet and manual emails | Free; full control over tone | Paid status is whatever someone last typed; no audit of who decided |
| Reminders inside invoicing or accounting software | Convenient; works well when clients pay by card or payment link | For bank transfers, reminder accuracy depends on how well payments were matched |
| Dedicated collection tools | Sequences, templates, client portals | Usually trust the paid status they are given; check how they treat part payments and disputes |
| DIGITAL EUR demo (today) | Shows why each payment was matched; ties and part payments surface explicitly | No reminders yet, nothing saved, no bank feeds, one file pair at a time |
Agency invoicing tools such as Zoho Invoice advertise payment reminders and advance payments that can act as retainers. Dedicated collection tools focus on reminder sequences. Both are useful. The question to ask any of them is the one this page is about: how does the tool decide that a bank transfer paid a particular invoice, and can you see that reasoning before a reminder goes out?
How to evaluate invoice collection software for your agency
- Feed it last quarter's awkward cases. A standing-order retainer, a part payment with a deduction, a holding-company payer and a combined payment. Note what the tool marks as paid.
- Check that a tie stays a tie. If two invoices fit a payment equally, the tool should ask, not choose.
- Check how disputes are held. Can a disputed balance be excluded from reminders without writing it off?
- Read the reminder before it leaves. Every message should require approval by someone who knows the client.
- Check the trail. Can you show a client exactly which transfers you received and how they were applied?
- Check where client data goes. Ask whether invoice or bank data is sent to third-party AI services, and whether that can be turned off.
- Price by client, not just by user. Agencies with many small clients and few finance staff should compare cost per client.
Points 1, 2 and 5 can be tested in our demo today. Points 3, 4 and 6 relate to the planned collections workflow. Indicative pricing for all plans is on our pricing page; prices are pre-launch test values and nothing can be bought.
Who is this a good fit for?
Likely fit: agencies invoicing clients in euro and paid mainly by SEPA transfer; agencies with retainers, re-billed costs and frequent part payments; finance leads who want to see the evidence before anyone sends a reminder.
Not a fit today: agencies that need automated reminder sequences now, card or payment-link collection, multi-currency invoicing, or a client portal. None of these is available. If your clients' books are kept by an external firm, our page for accountants shows how the same matching supports their review; consultancies with milestone billing will find their patterns on our consultancies page. For cross-border euro payment basics, see the euro payments guide.
Frequently asked questions
Does DIGITAL EUR send payment reminders?
Not today. Reminder drafting is planned, and when it exists every message will need a person's approval. Nothing is sent automatically.
How does it handle retainers paid by standing order?
If the transfer has no invoice number, the engine can only use the amount, IBAN and name. With one open retainer that gives a clear suggestion; with two open retainers of the same amount it flags a tie for you to resolve.
What if a client pays less than the invoice?
The suggestion carries a POSSIBLE_PARTIAL_PAYMENT reason and a 15-point penalty. If you approve it, the invoice stays open for the remainder, so you can decide whether that balance is late or disputed.
What if a client pays several invoices in one transfer?
Each invoice whose reference appears in the remittance becomes a candidate. You approve each one; allocations are capped so the transfer can never be used for more than its amount.
Can my team work on it together?
Not yet. The demo is single-user and keeps nothing. Multiple users with an approval step are planned.
Does it take card payments or offer payment links?
No. DIGITAL EUR does not process payments and never holds or moves money.
Sources
- Directive 2011/7/EU on combating late payment in commercial transactions, as adopted, via legislation.gov.uk and EUR-Lex — Articles 2, 3, 5 and 6 (accessed 5 November 2026)
- European Payments Council, SEPA Credit Transfer Scheme Rulebook 2025 version 1.0 (PDF), section on remittance information (accessed 5 November 2026)
- Zoho Invoice, Invoicing software for agencies — payment reminders and advance payments (accessed 5 November 2026)
- Chaser, Accounts receivable software for advertising, marketing and creative agencies — agency billing pain points described by a collection vendor (accessed 5 November 2026)