Veldmaat Payments / BB-Demo – Onboarding
Callcompleted
Veldmaat Payments: documents · 2026-02-06 09:45
Joost Verbeek raised two missed 07:00 refreshes this week, one caused by BB-Demo's own test load. Yusuf Demir set out fixes and said he would confirm them in writing. Joost insists Exact Online must not slip.
What was said
What this says
Current to 10 Oct 26Joost Verbeek raised two missed 07:00 refreshes this week, one caused by BB-Demo's own test load. Yusuf Demir set out fixes and said he would confirm them in writing. Joost insists Exact Online must not slip.
What happened: Sanne Bakker reported two misses, Wednesday and Thursday, with refresh finishing at twenty past seven and then almost eight. Yusuf Demir traced one to a slow HubSpot deals endpoint and the other to his own Exact Online test load overlapping the nightly refresh.
Customer view: Joost said the agreement was complete by 07:00, not almost. Two account managers have already asked Sanne whether numbers are current, so trust is being lost before use begins.
Commercial: This is a data freshness service-level issue and Joost said he would go to Elena if the fixes are not delivered. He also said the refresh must not take attention from Exact Online.
Watch: Yusuf committed to an incremental HubSpot pull that night, an alert by the next day and a finish time the next morning. Joost asked for the misses to be recorded.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Yusuf switches the HubSpot deals pull to incremental and stops overnight tests.
- Yusuf adds the half past five alert and reports the finish time in writing to Sanne and Elena.
- Yusuf sends the unmatched open items list and Sanne checks it the same day.
Risks
Current to 9 Oct 26- Repeated missed 07:00 refreshes are eroding the account managers' trust in the data before they have started using it.
- Joost will escalate to Elena if the fixes are not delivered as promised.
- The March Exact Online date is under pressure while refresh problems compete for engineering attention.
Opportunities
Current to 9 Oct 26- Visible, written delivery of the fixes can restore confidence and protect the first renewal.
Transcript
Yusuf Demir NoneMorning. Yusuf. Hello Sanne, hello Joost.
Joost Verbeek NoneGood morning. I will start with the question I always ask. Were the last actions done?- Yusuf Demir NoneSome. Zendesk now starts earlier, that is done. Bank columns are excluded, done. Second administration test load ran. Not everything is where I want it, and I'll go through it.
Sanne Bakker NoneTwo misses this week. Wednesday and Thursday. Refresh not complete at 07:00. Both ticketed. Again.- Joost Verbeek NoneAgain. That is the word I do not like. Last week was five minutes. What was this week?
- Sanne Bakker NoneWednesday, finished at twenty past seven. Thursday, later. Almost eight.
- Yusuf Demir NoneThose are the numbers I have too. Let me explain what I found, then you tell me if it's acceptable. Wednesday: the HubSpot source returned the deals endpoint slowly. Thursday: the Exact Online test load for the second administration overlapped with the nightly refresh and they competed for the same warehouse.
- Joost Verbeek NoneSo the second one was our test, not a normal night.
- Yusuf Demir NonePartly, yes. I scheduled the test in the same window. That was my decision and it was wrong. I should have run it in the daytime. I'm moving it.
- Joost Verbeek NoneTo be honest, I appreciate that you say it. But you understand the effect. Sanne has to explain to the account managers why the data is old. They stop trusting it before they have started using it.
- Sanne Bakker NoneTwo people already asked me. Whether numbers are current. I do not like answering.
- Yusuf Demir NoneThat's fair, and it's exactly the situation I want to avoid. The nightly refresh should be complete by 07:00 on business days. That is the target on the order form side and I don't want you to feel you have to chase it.
- Joost Verbeek NoneWhat was agreed was complete by 07:00. Not almost. So what is the plan?
- Yusuf Demir NoneThree things. One, no tests in the overnight window from now on. Two, I'm looking at the HubSpot deals pull: it fetches everything every night when it only needs changes since the last run. I'll switch it to incremental. Three, I'll add an alert that fires at half past five if the pull is not near the end, so I can intervene before 07:00 and not after.
- Sanne Bakker NoneIncremental. Why was it not before?
- Yusuf Demir NoneBecause the initial setup used a full pull to be safe. I should have switched it after the first weeks. That is on me.
- Joost Verbeek NoneWhen is it done?
- Yusuf Demir NoneI'd like to avoid giving you a date I can't keep. I can do the incremental change tonight, and the alert by tomorrow. I'll confirm both in writing to Sanne and to Elena. Tomorrow morning I'll tell you the finish time.
- Joost Verbeek NoneTonight and tomorrow. I write it down. If it is not so, I will say it to Elena.
- Yusuf Demir NoneUnderstood. That's your right.
- Sanne Bakker NoneExact Online. Where is it? Friday in March is not far.
- Yusuf Demir NoneSecond administration test: loaded, and the row count is in the sheet. Matching to merchants is where it is. The merged codes work. There's a handful of open items with no merchant at all, and I need Sanne to look at them, because I can't say from the source whether they're old or real.
- Sanne Bakker NoneSend the list. I check today.
- Joost Verbeek NoneI want to be clear. The delay of the refresh must not take attention from Exact Online. Both are in the agreement. I will not trade one for the other.
- Yusuf Demir NoneUnderstood. They are separate pieces of work and I'll treat them that way.
- Yusuf Demir NoneSummary. One, no overnight tests. Two, HubSpot deals incremental tonight. Three, alert by tomorrow. Four, I send the list of unmatched open items today and Sanne checks. Five, finish time reported tomorrow morning. Elena gets all of it in writing.
- Joost Verbeek NoneCorrect. And I want it recorded that two mornings were missed this week.
- Yusuf Demir NoneRecorded. Thanks, Yusuf.