Short answer
Invoice payment reconciliation for consultants means matching each client's bank transfer to the specific phase, instalment or expense invoice it pays, so you always know what each engagement still owes. DIGITAL EUR does this today in a free in-browser demo with visible reasons and human approval. Saved history and an engagement-level receivables view are planned, not available.
What makes consulting receivables different?
A consultancy's invoices follow the shape of its engagements, not a neat monthly cycle. A single client can owe money on several lines at once, and each line behaves differently when the payment arrives:
| Billing pattern | What the invoice looks like | What tends to arrive at the bank |
|---|---|---|
| Fixed-fee phase or milestone | One invoice per phase, issued when the phase is accepted | The full amount, or an instalment if payment was split |
| Time and materials | Monthly invoice based on approved hours | The full amount, sometimes weeks later after a timesheet query |
| Retainer or advisory fee | Same amount each month | A standing order with a generic text and no invoice number |
| Re-billed expenses | Travel, licences, subcontractor costs | A separate transfer, often described only as "travel costs" |
| Advance or deposit | Sometimes requested before any invoice exists | Money with nothing yet to match against |
Two further complications are typical of consulting clients. Larger clients pay through procurement systems that quote their own purchase-order number rather than your invoice number. And engagements are often contracted by one entity but paid by another, such as a group parent or a shared-service centre, under a different name and IBAN.
Billing guides written for consulting firms concentrate on getting the invoice right: milestone weights, approvals and timesheet checks. That is important, but it stops at the moment the invoice is sent. The reconciliation question comes afterwards: which payment closed which invoice, and what is genuinely still open on each engagement?
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 your open invoices and your bank transactions as CSV files, review each suggested match and its reason codes, approve or reject it under your name, and see every invoice's allocated and outstanding amount. You can export the approved allocations as CSV. Files are not uploaded or stored; reloading the page discards everything, so export what you need.
PLANNED (not available, no date promised):
- saved history, so an instalment approved in March is still recorded when the balance arrives in May;
- a receivables view grouped by client, with due dates and ageing, as described on our invoice tracking page;
- camt.053 bank statement import and saved matching rules;
- reminder drafts that a person approves before sending, described on our collections page.
Engagement or project tags are not part of the current data model. Today, the closest substitute is to put the engagement code in the invoice reference, as in the example below.
How the matching decides
The rules are fixed and visible. Each suggestion adds points for evidence and subtracts points for warning signs:
| Reason code | Points | Typical consulting case |
|---|---|---|
| INVOICE_REFERENCE | +65 | The client quoted your invoice number |
| EXACT_AMOUNT | +20 | Full payment of a phase or expense invoice |
| COUNTERPARTY_IBAN | +10 | The usual paying account of that client |
| COUNTERPARTY_NAME | +5 | The payer's name equals the client name on the invoice |
| POSSIBLE_PARTIAL_PAYMENT | −15 | An instalment of a phase invoice |
| AMOUNT_EXCEEDS_OUTSTANDING | −25 | Two invoices paid together, or a duplicate |
There is no suggestion without a reference, IBAN or name match: a payment that merely equals an invoice amount is never proposed. When two invoices tie for the top score, both are flagged as ambiguous and you decide. Every suggestion, including a perfect score of 100, waits for approval, and each allocation is capped at what the invoice still owes and what the payment still has available. The complete method is on the reconciliation product page.
Worked example: a consultancy's month, with synthetic data
The data below is invented. Fictional consultancy, fictional clients. We ran these exact files through the matching code behind the demo.
Open invoices:
| invoice_id | Client | What it is | amount_due |
|---|---|---|---|
| C-2026-31 | Tidewater Example NV | Phase 1, fixed fee, payable in two instalments | 9600.00 |
| C-2026-32 | Tidewater Example NV | Re-billed travel, September | 1184.40 |
| C-2026-33 | Granite Example Oy | Advisory fee, September | 7200.00 |
| C-2026-34 | Granite Example Oy | Advisory fee, October | 7200.00 |
Each invoice's reference equals its invoice number, and both clients' IBANs are on file.
Bank credits:
| transaction_id | amount | remittance | payer |
|---|---|---|---|
| D01 | 4800.00 | C-2026-31 phase 1 50pct | Tidewater Example NV |
| D02 | 1184.40 | Travel costs Sept | Tidewater Example NV |
| D03 | 7200.00 | PO 45001234 | Granite Example Oy |
| D04 | 7200.00 | C-2026-34 | Granite Example Oy |
| D05 | 3000.00 | Advance new engagement | Fjord Example AS |
What the engine returned (main candidates):
| Transfer | Candidate | Score | Reasons | Flag |
|---|---|---|---|---|
| D01 | C-2026-31 | 65 | reference, IBAN, name, possible partial payment | — |
| D02 | C-2026-32 | 35 | exact amount, IBAN, name | — |
| D03 | C-2026-33 | 35 | exact amount, IBAN, name | Ambiguous |
| D03 | C-2026-34 | 35 | exact amount, IBAN, name | Ambiguous |
| D04 | C-2026-34 | 100 | reference, exact amount, IBAN, name | — |
| D04 | C-2026-33 | 35 | exact amount, IBAN, name | — |
| D05 | — | — | no evidence for any open invoice | Unresolved |
Lower-scored alternatives (for example D01 against the travel invoice at score 0) are also listed because the payer's name and IBAN match; a reviewer rejects them.
Reviewing it in the right order:
- Start with the strongest evidence. D04 quotes C-2026-34 and matches on every signal. Approve it first. The October advisory invoice is now fully allocated.
- The tie on D03 resolves itself. D03 quoted only the client's PO number, so on evidence alone it fits both advisory invoices equally. With October already settled, the only open candidate is September's C-2026-33. Approve it. If you had approved D03 against October first, the later attempt to apply D04 to October would be refused, because the invoice would already be fully allocated. The cap protects you, but reviewing high-evidence matches first avoids the detour.
- D01 is an agreed instalment. The partial-payment penalty is a prompt, not an error. Approve it: €4,800.00 is allocated and €4,800.00 stays open on C-2026-31 until the second instalment arrives.
- D02 is the expense re-bill. No invoice number, but exact amount, IBAN and name all agree and it is the only candidate at that score. Approve it.
- D05 is an advance for an engagement with no invoice yet. There is nothing to match it to, so it stays unresolved. Record it as a payment on account in your accounting system, and match it when the invoice is issued.
Result: four approved allocations and one documented open item. On the receivables side, the only balance outstanding is the second Phase 1 instalment of €4,800.00 from Tidewater. Everything else is either paid or explained.
What routine keeps consulting receivables clean?
A short, regular routine prevents the quarter-end scramble that consulting firms often describe:
- Weekly or fortnightly, not quarterly. Matching twenty transfers is quick; matching two hundred at quarter end, after people have forgotten the context, is slow.
- Export open invoices and bank lines for the same period. Include the remittance text, payer name and IBAN, and a credit/debit column. The demo reads comma-separated files with dot decimals, up to 2 MB and 20,000 rows.
- Run the match and review strongest evidence first. References before amounts, as in the example.
- Classify what remains. Instalments in progress, disputes, unknown payers and advances each need a different action.
- Update client records. Add every new paying IBAN and any group entity that pays on a client's behalf.
- Export the approved allocations and record them in your accounting system, or pass them to your accountant. Our accountant export page describes the planned formats.
What should each open item on your list say?
After review, every item that is not fully allocated needs a short, specific status. Vague notes such as "check later" are how consulting receivables drift for months. A simple classification, applied to the example above, looks like this:
| Item | Status | Next action | Owner |
|---|---|---|---|
| C-2026-31, €4,800.00 open | Instalment in progress | None until the agreed date for instalment 2 | Finance |
| D05, €3,000.00 received | Advance, no invoice yet | Record on account; issue the invoice when the engagement starts | Engagement lead |
| (none in this month) | Disputed amount | Confirm the contested scope with the client before any reminder | Engagement lead |
| (none in this month) | Unknown payer | Ask the client which entity paid and add its IBAN | Finance |
Keeping instalments and disputes apart matters for consultants in particular: a client that holds back part of a phase fee usually has a scope or acceptance question, and that conversation belongs to the person running the engagement, not to a reminder template. In the demo, the invoice summary shows each invoice as open, partially allocated or fully allocated; the status column and owner above are your own notes.
How can a consultant make payments easier to match?
| Change | Effect on matching |
|---|---|
| Put a unique reference on every invoice and in the payment instructions | The strongest evidence (+65) becomes available |
| Include the client's PO number and your invoice number on the invoice | Procurement teams can quote both |
| Split instalments into separate invoices if the contract allows | Each payment becomes an exact match instead of a partial |
| Invoice re-billed expenses separately from fees | Expense queries do not delay fee payments |
| Use a structured RF creditor reference where clients' banks support it | Recommended by the SEPA rulebook for single-invoice payments |
| Ask group payers to name the client entity in the remittance | Turns an unknown payer into an explained one |
The SEPA Credit Transfer rulebook gives the payer 140 characters of remittance information, requires banks to forward it in full and without alteration, and recommends the ISO 11649 structured creditor reference for payments that refer to a single invoice. Our SEPA reconciliation guide covers how to adopt it, and the euro payments guide covers cross-border basics.
If payment is agreed in instalments, EU late-payment rules calculate interest and compensation only on the instalment that is overdue (Article 5 of Directive 2011/7/EU), which is another reason to know precisely which instalments have arrived. Follow-up on genuinely late invoices is covered on our collections page.
How does this compare with the alternatives?
| Approach | Good at | Weak at |
|---|---|---|
| Spreadsheet log of invoices and payments | Free; adapts to any billing model | Status is whatever was typed last; instalments and ties are easy to misapply |
| Matching in your accounting software | Bank feeds and posting in one place; most suites support part payments and advances | How a suggestion was chosen is often not visible; behaviour varies by product |
| Professional-services automation (PSA) tools | Milestones, timesheets and invoice generation | Many focus on creating invoices; payment matching is often left to the accounting system |
| DIGITAL EUR demo (today) | Visible reasons, ties flagged, allocations capped, approval log | No saved history, no bank feeds, no posting, no engagement tags, euro only |
Accounting tools commonly let you record a partial payment and keep the invoice open for the balance, and record an advance and link it to an invoice later. If your accounting system already does this well for bank transfers, you may not need a separate tool. DIGITAL EUR is meant for consultants who want to see the evidence behind each match before it reaches the books.
Evaluation checklist for consultants
- Use last quarter's real awkward cases, anonymised: an instalment, a PO-only payment, an expense re-bill and a group payer.
- Check partial payments. Does the invoice stay open with the correct remainder?
- Check ties. Two identical fees and one payment without a reference: does the tool ask you, or guess?
- Check over-allocation. Can a payment be applied to more than its amount, or an invoice paid twice?
- Check advances. How does the tool hold money that arrives before the invoice?
- Check the evidence. Can you show a client, or an auditor, which transfer settled which invoice and who decided?
- Check the cost per month at your volume. Our illustrative plans are on the pricing page; they are pre-launch test prices and nothing can be purchased.
The demo answers points 2, 3, 4 and 6 today. Point 5 is handled outside DIGITAL EUR for now.
Who is this for?
Likely fit: independent consultants and small consultancies invoicing in euro, paid mainly by SEPA transfer, with phase, instalment, advisory and expense invoices running in parallel.
Not a fit today: firms that need project accounting, timesheets, multi-currency invoices, bank feeds or automatic posting. If an external firm keeps your books, our page for accountants shows how they can review the same matches; agencies with retainers and media costs will recognise their patterns on our agencies page.
Frequently asked questions
Can I track an instalment plan?
Within one session, yes: approving an instalment leaves the invoice partially allocated with the remainder shown. Because the demo saves nothing, the history does not carry over to the next month. Saved history is planned.
What if a client only quotes their purchase-order number?
The engine does not read PO numbers. It falls back on amount, IBAN and name, which may produce a tie. Put your invoice number next to the PO number on the invoice to help the client quote both.
How do I handle an advance received before I invoice?
The demo can only match against invoices, so an advance stays unresolved. Record it as a payment on account in your accounting system and match it once the invoice exists.
What if a client's parent company pays?
If the parent's name and IBAN are not on the invoice record, there is no evidence to match and the payment is left unresolved for you. Recording the parent's IBAN against the client makes future payments matchable.
Does it work with currencies other than euro?
The engine only pairs an invoice and a payment in the same currency. DIGITAL EUR is designed around euro receivables and does not convert currencies.
Will it post the results to my accounting software?
No. It exports a CSV of approved allocations, labelled as a demo export and not an accounting entry. You record the results yourself.
Sources
- European Payments Council, SEPA Credit Transfer Scheme Rulebook 2025 version 1.0 (PDF), section on remittance information (accessed 5 November 2026)
- Directive 2011/7/EU on combating late payment in commercial transactions, Article 5, as adopted, via legislation.gov.uk and EUR-Lex (accessed 5 November 2026)
- Holded Help, Invoice reconciliation: full, partial and advance payment — example of how accounting software handles part payments and advances (accessed 5 November 2026)
- BigTime, How to automate milestone invoicing in a consulting firm — example of PSA-focused milestone billing guidance (accessed 5 November 2026)