Source
Choose one amount everyone trusts
Decide which approved earnings, usage, or settlement record supplies each invoice line and total.
Self-billing setup
Build self-billing around the data you trust
Start with one supplier group and one approved earnings source. Map the invoice fields, review step, document, and payout handoff before you scale.
Approved source dataInvoice reviewPayout handoff
Self-billing setup
Planning viewFirst supplier group
Map the workflow before rollout
Define
Approved source
- Earnings or usage
- Billing period
Review
Invoice draft
- Line items and currency
- Dates and notes
Confirm
Program handoff
- Supplier document
- Payout reference
Pilot before you scale
Confirm the source, document, and handoff
Design the flow before you automate the invoice
A strong self-billing program starts with a shared source of truth and a clear handoff—not with a PDF template.
Fields
Map the invoice before automation
Define the period, descriptions, quantities, prices, currency, dates, notes, and attachments the draft needs.
Review
Keep the approval step clear
Choose who reviews a draft, resolves a mismatch, and decides when the document can move forward.
Handoff
Plan how the record moves on
Decide when to generate the PDF, how the supplier receives it, and which payout reference finance needs.
How it works
Start with one supplier group, then expand
More in Mass Payouts
Explore more in Mass Payouts
Payout risk review
See which payout instructions need attention, understand the reason, record the decision, and execute only approved item
Overview
Upload payout rows by CSV or API, catch field and beneficiary issues, review and process the batch, see each payout stat
Batch review
Review payment-run status, inspect individual payouts and reason codes, take the actions available to you, and download
Frequently Asked Questions
What can Gruv support today?+
Gruv can create an invoice draft from supplied line items and source details, record review information, and generate a PDF. The self-billing trigger, supplier delivery, and payout handoff are configured for the program.
Can approved earnings or usage feed the invoice?+
Your integration must define how approved earnings or usage becomes invoice line items. Gruv does not assume that mapping or a batch-close trigger for every program.
How do we keep the invoice and payout amounts aligned?+
Use the same approved source and mapping for both records, then review any fees, tax, reserves, or adjustments before release.
What should we confirm for each market?+
Confirm the self-billing agreement, responsible invoice issuer, required tax fields, document language, delivery method, and record-retention needs before launch.
Next step
See where Gruv fits
Tell us what you are trying to do, where it needs to work, and how your team handles it today.
Contact the team