WBSO evidence control for Dutch R&D SMEs
Turn scattered WBSO evidence into an advisor-ready pack.
RDLedger gives Dutch R&D teams a live evidence cockpit for active S&O projects, linking technical progress to hours, surfacing gaps, and preparing advisor-ready WBSO packs. RDLedger works from the tools your team already uses, so engineers and scientists can keep doing R&D instead of reconstructing admin later.
Evidence-first
Human reviewed
No customer-data model training
Consultant compatible
S&O Evidence Cockpit
ACME Materials BVEvidence captured
1,248 This month across 3 S&O projectsEvidence timeline
Why it matters
From scattered records to a reviewable WBSO pack.
Watch our short walkthrough to see how RDLedger turns scattered WBSO evidence into a source-linked pack your advisor can review.
Evidence Audit Sprint
Start with a focused audit of active S&O project evidence.
In 10 business days, RDLedger maps the current evidence, flags weak links between hours and technical work, and prepares a practical handoff pack for advisor review.
Help protect the WBSO value behind your R&D work, without turning technical staff into administrators.
Evidence Audit Sprint
EUR 1,500-3,000
- Project evidence map and technical uncertainty summary
- Hours-to-evidence gap table
- Missing-evidence tracker with owners and deadlines
- Realisation readiness note
- Consultant/accountant handoff pack
Why teams use it
Keep a live pulse on WBSO evidence readiness.
See which projects are ready for review, where evidence is weak, and which actions need owner follow-up. RDLedger works with email, uploads, voice notes, hours exports, Drive/SharePoint links, and existing project tools before asking teams to change systems.
Capture evidence while work is fresh
Keep dated, source-linked records aligned to WBSO project progress.
Connect evidence to S&O hours
Show where logged hours are supported by technical progress, and where the advisor will likely need more proof.
Surface missing proof early
Turn missing sources, unclear technical results, and unsupported hours into clear owner-led follow-up actions.
Produce an advisor-ready pack
Package the evidence map, source index, hours gaps, assumptions for advisor review.
Audit walkthrough
See the four steps from evidence intake to advisor pack
Audit preview
1. Define the audit scope
Start with the S&O projects, current evidence locations, advisor deadlines, and the pack you need to produce.
What you see
The work is framed as pack production: what exists, what is
missing, who owns it, and what the advisor needs next.
ACME Materials BV
S&O Evidence Cockpit
Readiness Check
Quick WBSO Evidence Check
Answer six quick questions to see whether your WBSO evidence is organised enough for advisor review.
RDLedger organises, drafts, and reviews evidence. It does not assess
WBSO eligibility, guarantee outcomes, or submit filings to RVO.
FAQ
Practical questions before an Evidence Audit.
Does RDLedger use AI?
RDLedger uses AI behind the scenes to structure drafts and spot gaps. Outputs remain review-required, source-linked, and advisor-compatible. Final judgement and filing decisions stay with your team and advisor.
Is customer evidence used for model training?
No. Customer evidence, project files, hours records, and generated packs are not used to train AI models.
Does RDLedger replace our WBSO consultant?
No. RDLedger is designed to make consultant and accountant review easier by preparing cleaner, source-linked evidence packs. Final advice and filing decisions remain with your existing advisor or internal owner.
Does RDLedger decide whether work is WBSO-eligible?
No. RDLedger organises, drafts, reviews, and flags evidence gaps. It does not provide legal, tax, or subsidy advice, guarantee eligibility or audit outcomes, or submit filings to RVO.
What do we receive after an Evidence Audit?
You receive a project evidence map, technical context summary, source-linked evidence timeline, hours-to-evidence gap table, missing-evidence tracker, and consultant/accountant handoff pack.
Do engineers need to learn a new admin system?
No. The first workflow is deliberately light: email, file uploads, notes, screenshots, and existing tool links. The goal is to capture useful technical evidence without adding heavy weekly admin.