What was said
What this says
Current to 10 Oct 26Onboarding call on 26 Jan 2026. HubSpot and Zendesk connectors are live and refreshing before 07:00. Exact Online is pending and its March date depends on Sanne sending merchant code lists within two days.
What happened: Joost was at a meeting with the regulator side, so Sanne spoke for Veldmaat. She asked for the access model first and a date for Exact Online second.
Customer view: Sanne confirmed HubSpot and Zendesk load and that she keeps her own refresh log. She reported one miss the previous week, already ticketed.
Commercial: access can be restricted by group at space and source level, not by single field. Bank detail columns would be excluded at load time, which needs Joost's agreement.
Watch: the March connector commitment depends on the merchant code lists, which do not fully match between Exact Online and HubSpot. Hannah said she is comfortable with March only once she has them.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Sanne to ask Joost about excluding bank detail columns and confirm to Elena by email.
- Sanne to send the two merchant code lists within two days so Hannah can confirm or move the March date.
- Elena to close the open refresh ticket with a written explanation and propose a training date.
Risks
Current to 9 Oct 26- The Exact Online connector date in March depends on merchant code lists that do not fully match between Exact Online and HubSpot.
- Bank detail columns cannot be hidden by field, so exclusion at load time needs Joost's agreement, which is not yet given.
- One refresh miss was reported the previous week and the ticket is still open.
Opportunities
Current to 9 Oct 26- A training session built on real merchant questions, including chargeback review, can show value early on Veldmaat's own data.
- Widening from the first user group once HubSpot and Zendesk have settled.
Transcript
- Elena Novak NoneHello Sanne, hello Hannah. Joost is not joining today, I believe. Sanne, is that right?
- Sanne Bakker NoneRight. He is at a meeting with the regulator side. Back later. I will report.
- Elena Novak NoneThank you. As in my email, the agenda has three points. One, status of the connectors. Two, the access model that Sanne asked about. Three, the plan for Exact Online and the first users.
- Hannah Lowe NoneBefore that, Sanne, what do you most need from me today? I'd like to answer that first.
- Sanne Bakker NoneAccess model. And a date for Exact. In that order.
- Elena Novak NoneThen we will take them in that order after the status. Status, to confirm: the HubSpot connector is live and the Zendesk connector is live, since the role was corrected. Exact Online is pending. Sanne, does that match what you see?
- Sanne Bakker NoneYes. HubSpot loads. Zendesk loads. Last three mornings refresh complete before 07:00. I keep a log. One miss last week, already ticketed.
- Elena Novak NoneI have the ticket, and I will make sure it is closed with a written explanation. Hannah?
- Hannah Lowe NoneOn the access model. The short answer is: yes, you can restrict by group. The longer answer is that it works at the level of the spaces and the sources. So you can say merchant risk sees the finance source, and account managers see HubSpot and Zendesk only. What I can't do is hide single fields inside a source.
- Sanne Bakker NoneFields. Like bank details?
- Hannah Lowe NoneIf bank details sit in the Exact Online source, then everyone with that source can see them. To be precise, we would exclude those columns at load time instead. That is a mapping choice, and I'd want Joost's agreement before we do it.
- Sanne Bakker NoneExclude them. I think he will agree. I will ask.
- Elena Novak NonePlease ask, and tell me his answer by email so that it is on record. I will add it to the actions.
- Hannah Lowe NoneGood. For the Exact Online side, then. I have the two administrations that merchant risk uses. I've looked at the structure. The merchant identifier in Exact is a customer code, and in HubSpot it is a company property. Do the two match?
- Sanne Bakker NoneMostly. Some have a prefix in Exact. Some do not. Some merchants have two codes.
- Hannah Lowe NoneThat is the thing I was worried about. Could you export both lists into a sheet, with the codes side by side, and flag the ones you know do not match? Then I do not have to guess.
- Sanne Bakker NoneCan do. Two days.
- Elena Novak NoneThank you. May I record that as: Sanne sends the code lists within two days? I want to be careful with the date for the connector. The commitment is the Friday in the first week of March, and the lists are what it depends on.
- Sanne Bakker NoneFine. Two days.
- Hannah Lowe NoneWith the lists in hand I'm comfortable with March. Without them I'm not, and I'd tell you.
- Elena Novak NoneNow the first users. Joost wanted a proposal. I suggest the data team, two account managers, and one person from merchant risk, then widen. Sanne, what do you think?
- Sanne Bakker NoneFine. Add the person who does chargeback review. She will ask the most. She asks hard questions.
- Elena Novak NoneThat is useful. I will make sure the training session is built around real merchant questions, not a demo script.
- Hannah Lowe NoneI can do that session on your own data once HubSpot and Zendesk have settled. The merchants will recognise themselves.
- Elena Novak NoneTo confirm the actions. One: Sanne asks Joost about excluding bank detail columns and tells me by email. Two: Sanne sends the two code lists within two days. Three: Hannah reviews the lists and confirms the March date or tells us. Four: I send the first user group and propose a training date. Five: I close the open ticket with a written explanation.
- Sanne Bakker NoneOkay. That matches.
- Elena Novak NoneThank you both. Kind regards, and speak soon.
- Hannah Lowe NoneThanks, both.