Data Panda brings your WeFact data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
WeFact is a Dutch invoicing and light-CRM platform out of Eersel, running for ondernemers since 2005. The product wraps quotes, sales invoices, purchase invoices, subscriptions, products, payments and a contact-moment log around an account that an owner-operator can run without a bookkeeper sitting next to them. It hands off cleanly to the actual ledger via direct connections to Exact Online, Yuki, SnelStart, Twinfield and a handful of others, and it pairs natively with Mollie for payment links and PSD2 banks for reconciliation.
That makes WeFact the place where the money story of a Dutch SME starts: the quote that became an order, the recurring subscription that bills tomorrow, the customer whose last invoice is two weeks overdue. Pulling it into a warehouse turns those rows into something the rest of the business can use. Recurring revenue, churn on subscriptions, average days to payment per customer and quote-to-invoice conversion all live across WeFact and whatever sales or operational system feeds it. WeFact is great at sending the invoice. It is not built to answer the questions a board asks the morning after.
Recurring revenue, debtor aging and quote conversion tied to WeFact rows, without a weekly export.
Let the invoicing tool react to what sales and operations already know.
Use WeFact history to score payment risk, predict churn and forecast cash.
Internal tools on WeFact data for people who should not have a WeFact login.
A list of concrete reports, automations and AI features we have built on WeFact data. Pick the one that matches your situation.
Which subscriptions are about to churn?
Subscriptions ranked by failed Mollie or bank payments over the last three cycles, combined with downgrades on the same account. Surfaces the customer whose recurring invoice keeps bouncing weeks before the cancellation email lands.
What is our real DSO per customer, including credit notes and partial payments?
Days sales outstanding per account computed on invoice date against payment date, with credit notes and partial payments handled, rolled up per segment and per salesperson. Replaces the average that hides the two accounts dragging the whole portfolio.
How much of next month's revenue is already on the WeFact subscription book?
Sum of recurring invoices scheduled to bill in the next thirty days from active WeFact subscriptions, split by product and by customer segment. Tells the owner what is committed before the new-business pipeline is even consulted.
Recurring revenue, debtor aging and cash forecast tied to WeFact invoice and subscription rows. Month-end reporting closes on numbers that already exist in the billing tool, not on a spreadsheet rebuilt from a CSV.
Open receivables and payment history visible on the customer record before you offer new terms or a renewal price. A renewal won at a discount on an account that pays sixty days late is not won.
Subscription health, failed-payment trend and quote-to-invoice conversion in one place. Operations sees which products carry the recurring revenue and which ones cause the support ticket spike that follows a price change.
WeFact invoices and credit notes land in Exact Online as journal entries with VAT, GL coding and customer set, and payment status flows back. The Dutch SME closes the month on numbers already booked, instead of reconciling the billing tool against the ledger by hand.
Sent invoices, credit notes and bank-matched payments from WeFact land in Yuki as sales journal entries with VAT codes and customer references intact. The accountant works in Yuki, the owner works in WeFact, and neither has to ask the other for a CSV at month end.
A won HubSpot deal raises a WeFact quote or invoice with the right product, price and contact pre-filled. Invoice and payment status flow back onto the HubSpot company record so the next sales conversation starts with the customer's actual payment behaviour, not yesterday's pipeline number.
Customers in WeFact with active, lapsed or failing subscriptions land in their own Mailchimp segments, kept in sync. Renewal nudges, win-back campaigns and product-news mails go to the right list, and customers in arrears stop being asked to upgrade.
A failed Mollie or bank payment on a WeFact subscription posts to a Slack channel with the customer, the product and the payment history attached. Customer success picks up the call before the third failure tips the customer into cancelling.
WooCommerce orders post into WeFact as invoices with line items, VAT and shipping split out, and refunds raise credit notes. The webshop owner stops keeping a separate spreadsheet to map shop orders against the invoicing tool.
These are the 9 tables we currently pull from WeFact into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your WeFact data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
WeFact subscriptions land as their own table with billing frequency, next-invoice date, product and customer keys, joined to the actual invoice rows they generate. That lets you compute monthly recurring revenue, churn and renewal pipeline directly, instead of inferring them from a stream of invoices.
Yes. Payment events from WeFact's Mollie and bank reconciliation arrive as their own rows joined to invoices, so paid, partially paid, failed and open are first-class states. That makes failed-payment trend, true DSO and cash-flow timing reportable without exporting from each tool separately.
We review your WeFact setup and the systems around it. Together we pick the first thing worth building.