Why not just use Stripe Billing? +
Because it answers a different question. A billing stack – Stripe, since the Metronome acquisition, also for complex usage models – works out what a customer owes and collects it. If you charge by card or direct debit, you are done there and don't need billcu. If you wait for bank transfers on 30 to 90-day terms, that is where it starts: escalation levels aimed at people instead of card retries, matching partial payments, a 13-week cash forecast, contract ARR. billcu covers the stretch that comes after – working with your billing stack, not against it.
Is billcu a payment processor? +
No. billcu doesn't process payments – it runs receivables management: dunning, cash forecast and ARR. It complements Stripe/your bank, it doesn't replace them.
Who is billcu for? +
For SaaS and recurring-revenue mid-market companies with B2B invoices and payment terms that want to steer receivables, cash and ARR in one lean cockpit.
How does the AI capture work? +
You upload a PDF (PO, contract, document); the AI reads customer, amounts, due date and contract ID and pre-fills a draft. You review and confirm – done.
Do I need reviews and approvals? +
No – billcu runs fully automatically. Reviews and approvals (e.g. four-eyes sign-off before invoices or reminders go out) can be switched on optionally and are mostly used during onboarding.
How fast are we live? +
Usually within a few days: a one-time data import, setup of your tenant, add users – no long ERP project.
Where is our data? +
On a server isolated for you in Germany (EU), your own database, your own subdomain, encrypted backups. DPA included.
Can we offer billcu to our own clients? +
Yes – as an implementation partner: you roll billcu out to your clients and earn a commission. Each end client gets their own isolated billcu instance; the client relationship stays with you.
