Client billing
Keep the invoice and payment update together
Create the billing record, issue a payment link when the workflow is ready, and keep provider updates, adjustments, and follow-up context close to the invoice.
Explore client billingConnect the approved amount, payment update, exception context, and finance result—so the next person can see what happened and what comes next.
| Transaction | Amount | Date | Status |
|---|---|---|---|
| Invoice #1038: Mason Lee | $1,800.00 | Mar 20 | ✓ Completed |
| Client payment: Nora Studio | $8,500.00 | Mar 19 | ✓ Completed |
| Subscription: Beta Inc | $149.00/mo | Mar 18 | ✓ Active |
Company news
Read Gruv press releases and research.
Paying contractors in their own currencies out of your own bank accounts means one account per currency, and every one of them has to hold money before a run starts. The buffer gets sized once, against the biggest run anyone can remember, and then nobody looks at it again. What that costs is cash you cannot spend, parked in a currency you may not need again this quarter. Topping an account up is itself a cross-border payment with its own value date, and euro settlement in T2, the system the euro area central banks operate, does not run on Good Friday, Easter Monday, 1 May or 26 December. None of those four is a Federal Reserve holiday, so a US payment calendar does not show them.
Volume is rarely what forces this decision. A team can push a great many payments through one bank and one accounting system without any of it being hard, because every question has an answer in one of two places. What changes the arithmetic is how many parties hold part of the answer: a second bank, a provider whose statuses stop inside its own portal, a marketplace that decides what a seller is owed, a tax authority that takes its cut before the money reaches you. Each of those adds a place to look. The cost of joining them up is that somebody has to make the identifiers agree first, and agreeing what a customer reference means across four systems is a conversation between teams that happens before anything is built.
Some countries require a customer to deduct tax from what they pay a foreign supplier, and the reduced rate a treaty allows depends on proving where the supplier is resident. For a US company that proof is Form 6166, a letter the IRS issues confirming US residence for a tax year. It is requested on Form 8802, costs $185 for a non-individual applicant, and the IRS asks you to allow at least 45 days. Nobody starts that clock at contract signature. The first invoice goes out while the request is still queued, the customer deducts at the domestic rate because their law tells them to, and the invoice sits open against a payment that is correct. Recovering the difference means a refund claim in the customer's country, which asks for the same certificate.
Start with the job in front of you
You do not need to replace every system at once. Start where an approved amount becomes a payment instruction, then make the status and finance handoff easier to follow.
Client billing
Create the billing record, issue a payment link when the workflow is ready, and keep provider updates, adjustments, and follow-up context close to the invoice.
Explore client billingVendor payments
Import a payout batch, inspect item status and reason details, process the enabled workflow, and export the result for finance.
Explore payout batchesPayment operations
Connect the invoice, beneficiary, external reference, provider update, and current status so support can start from the right record.
Explore payment operationsFinance close
Keep amounts, currencies, item outcomes, and operational references structured for the accounting process your team already follows.
Explore reportingA practical operating path
Name the system that approves the invoice, contractor work, seller share, creator earnings, or affiliate commission. Gruv should receive the approved payable—not invent it.
Use stable client, beneficiary, invoice, batch, and external references so each payment update can be traced back to the business event that created it.
Item status, reason codes, explanations, and provider references give operations and support enough context to find the next owner.
Export the final amounts, currencies, statuses, and references into the finance process instead of rebuilding the payment trail at month end.
Bring one real workflow
A useful working session starts with one invoice, payable file, or payout batch—not a generic feature checklist.
Show us the records and handoffs your team uses today. We’ll map the first useful lane, the open coverage questions, and the result finance needs back.
Start with one invoice, payable file, or payout batch.