Invoicing and payments
From signed contract to paid invoice.
The invoice starts where the contract ended: same line items, same client record. EUR invoices with btw handled, retainers that bill themselves, payment through Stripe Checkout, and one collections queue for everything overdue.
30 minutes, no slides. We map your current stack live. Dutch or English.
A real Metiva invoice list with demo data, not a render.
One record, start to finish
The invoice starts where the contract ended.
In a ten-tool stack, the deal closes in one tool, the contract is signed in a second, and the invoice is typed into a third. Metiva writes the invoice from the signed contract, on the same record, so nothing is copied and nothing drifts.
- A signed contract converts one-to-one into an invoice: same line items, same client.
- No retyping into a separate billing tool, so the invoice can never disagree with the deal.
- The invoice lives on the same client record as the conversation, the deal, and the contract.
- Paid media management, maandelijksEUR 2.500,00
- Landing page optimalisatieEUR 1.200,00
- Rapportage en attributieEUR 450,00
A contract converted into an invoice, with sample data, illustrative.
Dutch billing, handled
Invoices your boekhouder will not send back.
Metiva is built for Dutch agencies first, so the billing rules Dutch agencies live under are the defaults, not a customization request.
btw on its own line
EUR invoices with 21% btw as a separate line, the way Dutch bookkeeping expects it. Amounts are quoted ex-btw, so nothing is hidden in the number.
Reverse-charge when it applies
For EU B2B clients outside the Netherlands, invoices carry the btw-verlegd (reverse-charge) treatment, configured once during implementation.
30-day terms by default
Statutory Dutch payment terms are the default: betaling binnen 30 dagen, adjustable per client where you have agreed something else.
Getting paid
Paid through Stripe, chased by the system.
Sending the invoice is half the job. Metiva also carries the part most stacks leave to memory: taking the payment, running the retainer, and keeping one honest list of what is still open.
- Clients pay through Stripe Checkout, the checkout they already trust, including deposits and partial payments.
- Retainers bill themselves on their schedule, so recurring revenue does not depend on someone remembering.
- Everything overdue surfaces in one collections queue, so nothing slips because it lived in a spreadsheet.
- 12 days overdueBrouwer Retail2026-0131
- 4 days overdueNoord Media2026-0127
- Due in 6 daysAtelier Duin2026-0140
Sample data, illustrative
Your boekhouding stays yours
We connect to your accounting. We never replace it.
Your administration lives with your boekhouder, in Moneybird or Exact Online, and that is where it should stay. Metiva writes the invoice, takes the payment, and keeps the client record straight; your accounting stays the system of record for the books.
- Today: invoicing and payments run inside Metiva, with Stripe Checkout for the payment itself.
- On the roadmap: sync to Moneybird and Exact Online, so invoices land in your administration without export files. We say roadmap because it is not shipped yet.
Configured per company
Set up to how your agency runs billing, not sold as-is.
Metiva is not one dashboard sold a hundred times. During implementation we configure this module to how your agency actually works, on a core that stays maintained and upgraded for everyone. A one-time implementation, then a monthly service retainer (a supportabonnement, not software rental), priced by the client brands you manage with unlimited seats.
Configured per client
- btw profile and reverse-charge rules21% / verlegd
- Payment terms30 dagen
- Invoice numbering and branding2026-0142
- Retainer schedulesMonthly
Isolated per client
Each client company's data is isolated by design, and every request binds to a tenant from a verified claim in the signed token. If it cannot resolve, it fails closed.
EU data residency
Your data is stored and processed in the EU, with right-to-erasure built in, because Dutch agencies answer to the AVG and so does Metiva.
Consent, deny-by-default
Tracking stays off until a visitor opts in, IP addresses are truncated and encrypted at rest, and EU identification stays company-level without consent.
The full picture lives in the Trust and Security Center.
Built on one system
- 1:1
- Contract lines to invoice lines
- 1
- Collections queue for everything overdue
- 30
- Day payment terms by default
- 0
- Per-seat fees
Converted, never retyped
No spreadsheet on the side
Betaling binnen 30 dagen, per client adjustable
The whole team works the invoices
Capability counts, not performance promises. We show you the rest live on the call.
Questions
Straight answers about invoicing.
Metiva is one system, priced per company, not per seat: a one-time implementation, then a monthly service retainer priced by the client brands you manage, with unlimited seats. The monthly is a service retainer, not software rental: hosting, maintained integrations, support, and accurate attribution. 12-month commitment, then cancel monthly, with two months free on annual prepay. Tell us how you run and we quote you directly, on WhatsApp or by email.
No, and it never will. Metiva connects to your accounting, it does not replace it. Today invoicing and payments run inside Metiva with Stripe Checkout; sync to Moneybird and Exact Online is on the roadmap, and we call it roadmap because it is not shipped yet. Your boekhouding stays the system of record for the books.
Through Stripe Checkout, from the invoice or from their client portal, including deposits and partial payments. No bank-transfer chasing unless you prefer it: 30-day terms are the default and payment links sit on every invoice.
EUR invoices carry 21% btw as a separate line, quoted ex-btw. For EU B2B clients outside the Netherlands the invoice applies the btw-verlegd (reverse-charge) treatment. Your btw profile and terms are configured once, during implementation.
Retainers bill themselves on their schedule. You set the amount and the cadence once, the system generates and sends the invoice each period, and anything unpaid surfaces in the collections queue.
From the same record as everything else. A signed contract converts one-to-one into an invoice: same line items, same client. There is no separate billing database to keep in sync, which is why the invoice can never disagree with the deal.
One connected system
Send the invoice the system already wrote.
Invoicing is one angle on the same system that runs your inbox, pipeline, contracts, and attribution. We will show you the whole thing, with your real stack on the screen.
30 minutes. No slides. We map your current stack live. Dutch or English.