Finance Guide

This guide is for people with the Finance role, who manage RAD's billing setup, run revenue and payout reports, and reconcile cloud costs. New to RAD? Start with Using RAD.

Finance is granted by an administrator on top of an ordinary account, so you keep everything a signed-up user has. When you sign in as Finance you land on the Billing page. Your navigation bar shows Billing, Labs and Audit Log first, then the everyday items your account also holds — Credits, Deployments and Solutions for an ordinary user account — and Pricing and Help last. (Labs appears only while lab sessions are switched on, and Setup Requests and Support Tickets are tabs inside the Help page.)

What you can do

• Create and edit subscription plans and their per-provider prices (Subscription Tiers).
• Configure the credit economy — credits-per-unit, fees, discounts and revenue shares (Credit Settings).
• Adjust any other user's credit balance (Credit Management).
• Issue Event Codes that give event attendees free credits.
• Approve or reject customers' requests for RAD to pay for their own Google Cloud projects (Linked Projects), set each customer's VAT rate, tax details and billing sub-account (Customer Billing), and report the VAT collected (VAT Report).
• Report on Module Revenue, and review and pay agent commission (Agent Revenue).
• Review every customer's RAD-managed project costs (Project Transactions) and org-wide GCP costs (Project Invoices).
• See per-payee payout totals (Payout Summary).
• Oversee every trainer's lab sessions, and end one to stop its spending (Labs).
• See every client project on the platform — who runs it, for which client, its status and wallet — read-only, under Solutions → Managed Environments → Client projects → All client projects (while client projects are switched on).
• View all users and the full lists of agents and partners; make limited user edits.
• Work the managed-setup and support-ticket queues (tabs on the Help page).
• Review the money-related entries of the Audit Log.

The Billing page

Open Billing from the navigation bar. It has twelve tabs, in this order: Subscription Tiers, Credit Settings, Credit Management, Event Codes, Linked Projects, Customer Billing, VAT Report, Module Revenue, Agent Revenue, Project Transactions, Project Invoices and Payout Summary. Each is described below.

Which tabs appear depends on two platform switches. Event Codes, Linked Projects, Customer Billing and VAT Report are always shown; every other tab needs Enable Subscription switched on, and Project Transactions and Project Invoices also need Enable Project Credits. The page always opens on the first tab you can use — with Subscriptions off, that is Event Codes. Linked Projects, Customer Billing and VAT Report are Finance's alone: administrators do not see them.

Subscription Tiers

Manage the recurring credit plans (tiers) that users can subscribe to. Each plan grants a set number of credits per billing cycle.

1. Go to Billing > Subscription Tiers.
2. Click to create a new tier, or select an existing one to edit.
3. Set the plan's name, its price, and the credits it grants. The form shows what that price would buy at the current credits-per-unit rate, so you can see whether the tier is better value than a straight top-up. Then, on each provider tab, paste the identifier of the matching price you have already created in that provider's own dashboard — Price ID for Stripe, Plan ID for Flutterwave. The price and credits are shared by both providers; only the identifier differs.
4. Save the tier. Update or remove tiers as your offerings change.

Above the tier table is a Payment Providers panel. Use it to switch Stripe and Flutterwave on or off — a provider's tab in the tier table stays disabled while that provider is off, and neither can be enabled until Credits and Subscriptions are both on. The same panel holds Reset Subscription Credits: leave it off and unused subscription credits carry over to the next billing cycle; switch it on and the allowance is replaced at each renewal instead of added to. Top-up credits are never affected either way.

Subscriptions only grant credits — they do not grant the Partner role.

Credit Settings

Configure the global parameters of the credit economy.

1. Go to Billing > Credit Settings.

2. Set the credits-per-unit value (how credits map to currency).

3. Set the revenue shares — the percentage of revenue allocated to referring agents (Agent Revenue Share) and to module partners (Partner Revenue Share).

4. Set the rest of the economy from the same tab. Each setting is its own small form with its own Save button, so you can change one without touching the others: the free-credit grants (Signup, Monthly, Referral and the referral limit), the Minimum Top-up (the smallest one-off purchase in US dollars: $10 by default, between $1 and $1,000), the low-credit trigger, credits-per-hour, the four module fees (CR and GKE, fee and setup fee), the RAD-Managed Module Discount, the deploy credit buffer, the Sandbox/Development/Production/Lab admission floors and monthly project budgets, the project credit margin, the three linked-project settings (Linked Project Margin, 10% by default and between 0% and 100%, added to Google's list price for a customer's own linked project; Linked Project Floor, 2,500 credits by default; and Linked Project Floor (days of spend), 7 by default — a linked customer must hold the larger of the fixed floor and that many days of their recent spend), the deployment refresh interval, Billing Reconciliation Alert (in US dollars, 1 by default, up to 10,000: RAD alerts its administrators when more than this much Google Cloud cost in one billing window could not be attributed to anyone), and the starting values for the ROI calculator. The referral limit (Referral Rewards) takes three kinds of value: -1 means unlimited, 0 switches the referral program off (no referral credits, and the Refer and earn section disappears from Profile, along with its shortcut on Credits), and a positive number is the monthly number of referrals each referrer earns credits for. Agents are exempt from that monthly cap. Solution bundle discounts have no control on this tab: a solution's module fees are discounted 15% for three or four members, 20% for five or six and 25% for seven or more, and changing those tiers is an administrator's settings change (solutionBundleDiscountTiers), not a form here.

5. Decide what a failed deployment is charged, on the Failed Deployments card. It has two independent switches, and each label states its own outcome ("Build cost charged" / "Build cost not charged", "Module fee charged" / "Module fee not charged"):

   • Build cost — whether the metered Cloud Build time of a new deployment that fails or is cancelled is charged.
   • Module fee — whether the module fee is charged for that deployment even though it never succeeded.

   In the current release both are off: no failed deployment is charged anything. Turning either on applies to deployments that fail from then on; it never re-bills past failures. The switches cover the failure of a deployment's creation only — failed updates and teardowns are not charged, and lab deployments are billed through the trainer's session instead. Whatever you choose, charges for failures are capped per user (by default at three charged failures in any 24 hours), so a module that keeps failing cannot drain a customer's balance. A successful deployment is always charged in full, whichever way these are set.

This tab also holds Adjust All Credits, which applies the amount you enter to every user's balance at once — positive to grant, negative to deduct. Tick Free to move awarded credits, or leave it clear to move purchased credits. Large adjustments will not submit until you have given a reason and typed the confirmation phrase shown. Use Credit Management below to change one person instead.

Note: the platform switches — Enable Credits, Enable Subscription and Enable Project Credits — live on the administrator's Setup page, which Finance cannot open. Enable Subscription is the switch for every purchase: with it off there are no new subscriptions and no one-off top-ups on either provider, the buy and subscribe options disappear, and existing subscribers can still cancel their plan from the Credits page. As Finance you see and configure the billing UI, but you do not switch these on or off from it.

Credit Management

Adjust an individual user's credit balances.

1. Go to Billing > Credit Management.
2. Search for the user by email.
3. Click Edit and set the balances. There are three, and they behave differently: Awards are free credits reset each month, Subscription credits come from a plan and are replaced at renewal where reset is enabled, and Top-up credits were bought outright and never expire. Spending draws on awards first, then event credits (claimed with an event code, below, and not editable here), then subscription, then top-up. Monthly Partner is not a spendable balance — it is the recurring allotment added to a partner's Awards each month.
4. Save the change.

Two things to expect. You cannot adjust your own balance: the save is rejected and you are told to ask another finance or admin user, which keeps two identities on every grant. And if someone else changed that user's balance while your edit form was open, your save is rejected, the form closes and the table refreshes — re-open it and make the change from the current figure.

Only the balances you actually change are saved; the others are left exactly as they are, including a negative or part-credit balance. The edit form has no Is Partner? control for you: partner status is a role, and only administrators change roles.

Event Codes

Give the attendees of a partner event (a DevFest, a workshop) free credits they claim themselves by entering a code.

1. Go to Billing > Event Codes and click New event code.
2. Type a code or click Generate, and name the Event.
3. Set Credits per claim and Maximum claims. The form shows the most the code can give away (credits × claims) before you create it.
4. Set Claim until (and optionally Claim from), and when the credits expire — either a number of days after claiming or a fixed expiry date.
5. Optionally restrict it to email domains or a list of attendees (one email per line), then click Create code.

Each account can claim a code once, and only with a verified email address. The credits land in the user's Event credits balance: they are free (never counted as purchased), are spent after the monthly awards, do not pay for Google Cloud usage in a RAD-managed project, and expire on their own date rather than with the monthly reset. Once a code exists its credits and validity are fixed; you can still Disable or Enable it, move its closing date, or change its cap. Details lists who claimed it, and Export claims (CSV) downloads that list.

You cannot claim event codes yourself. Finance and admin accounts — the accounts that create codes — are refused, and nobody can claim a code they created, even after losing the role. This is the same rule that stops you adjusting your own balance. The event-code box on the Credits page (the Claim credits row) is not shown to you for that reason; while the referral program is on, you see a Get your referral link link there instead.

Module Revenue

See the revenue deployments generate, and the share allocated to each partner or agent.

1. Go to Billing > Module Revenue. It opens on the last 7 days and loads straight away.
2. To change the period, choose a start and an end date — the range cannot exceed 366 days — and click Refresh.
3. With no partner or agent selected you are looking at full platform revenue for that period. Select one or more partners (or agents) to narrow it to their revenue share, calculated from the percentage set in Credit Settings. You can also filter by module.
4. Each row shows the date, module name, user email, credit cost and revenue. Export to CSV takes the full filtered set, not just the page on screen.

Agent Revenue

Agent commission and the payouts that settle it. An agent earns a share (the Agent Revenue Share in Credit Settings) of the module fees their referred users pay with purchased credits. It is worked out in US dollars and paid in cash, outside RAD. Build charges, project usage, awarded or promotional credits, the self-serve project surcharge and anything spent in a lab never earn. The Agent guide has the full rules.

The tab has two parts.

The commission statement.

1. Go to Billing > Agent Revenue and pick an agent — current or former, since a demoted agent can still be owed commission. You see their statement exactly as they do: totals (Earned, Reversed, On hold, Payable, In payout, Paid) and one row per commission. Above it, Rewarded referrals this month and All-time rewarded referrals show how many people the agent has referred who earned them referral credits — counts only.
2. Each commission is on hold for 30 days before it becomes payable, so a refunded or disputed fee can be dealt with first.
3. To take a commission back, for example because its fee was refunded, use Reverse on its row and give a reason. The reversal is recorded as a new negative entry, never an edit. If the commission hasn't been paid yet, the pair nets to zero — and if it sits in a payout batch that isn't marked paid yet, that batch's total drops by the same amount. If it has been paid, the amount is deducted from that agent's next payout. The reason is shown to the agent and written to the audit log.

Agent payouts.

1. Choose a Cut-off date and click Create payout batch. The batch takes every commission payable by the cut-off and nets any reversals.
2. Agents owed less than the $50 minimum carry forward to a later batch; nothing is lost.
3. A deactivated agent is left out. Their commission stays recorded and on hold, and is paid in a later batch only if the account is reactivated. A deactivated account also earns no new commission.
4. Pay each agent outside RAD, then enter the Payment reference and mark the batch paid. The agent's statement then shows those commissions as Paid.

Creating a batch, marking it paid and reversing a commission each write an audit-log entry.

Linked Projects, Customer Billing and VAT

A customer can ask RAD to pay Google for a Google Cloud project they already own (Credits → Linked Projects on their side — see the User Guide). RAD then debits their purchased credits hourly for its usage, at Google's list price less any Google credits you pass through to them, plus the Linked Project Margin, plus their VAT. These three tabs are where you run that, and where every customer's VAT is set.

Customer Billing. Look a customer up by email (customers already configured are listed for you to pick) and set:

• VAT rate (%) — 0 to 50. 0 means no VAT and counts as set; leaving it empty clears it, and a customer with no rate cannot be linked. The rate applies to everything that customer pays — module fees, build costs and RAD-managed project usage as well as a linked project's usage — and for a lab session or client project it is the rate of whoever funds it (the trainer or the subscriber). It applies from the next charge and is never retroactive: a deployment keeps the rate it was confirmed at.
• Country (two-letter code) and Tax ID.
• Billing sub-account ID — optional. It must be open, sit under RAD's reseller billing account and be usable by RAD's service accounts; RAD checks this when you save and names anything missing, and Re-check runs the check again. Leave it empty to use RAD's main billing account. A change applies to projects linked or created afterwards, including the RAD-managed projects RAD creates for that customer; existing projects are never moved.
• Google credits passed to this customer — Free tier, Sustained and committed use discounts and Promotions, each off by default (usage is charged at list price). RAD's reseller margin and its negotiated discounts with Google are never passed on.
• Linked project floor override (credits) — optional. Replaces the platform's fixed linked-project floor for this customer; the days-of-spend floor still applies on top, whichever is larger. Leave empty to use the platform default.

You can't change the billing settings of your own account, or approve, reject or unlink your own linked projects — another Finance user or an administrator must.

Save changes saves only the fields you changed. The Change history beneath lists every change, its old and new value, who made it and when.

Linked Projects. Every customer request, awaiting ones first, with the customer, status, billing account and dates.

• Approve links the project's billing to RAD straight away, on the customer's billing sub-account or RAD's main account. The dialog shows the customer's VAT rate, purchased credits against the floor, and sub-account, and you must tick Customer has capped Gemini API and GPU quotas — check the project's quotas before you do. Approval is refused (the reason is shown in the dialog) until the customer has a VAT rate set and holds at least the floor in purchased credits — the larger of the fixed floor and the days-of-spend floor over their linked projects' recent spend. It is also refused if the customer is no longer the project's verified owner, if the project is one RAD created or runs (a RAD-managed, lab or client project), or if the customer has removed RAD's billing role from any of their linked projects (the dialog names it).
• Reject needs a reason, which the customer sees.
• Unlink detaches RAD's billing account from a linked or paused project. If the customer hasn't linked their own, its services stop (their data is kept). Usage up to then is still charged once metering catches up.
• A stop — yours or the customer's — finishes only once RAD has confirmed its billing account is off the project. If the detach fails, the project stays Unlinking, its usage is still charged to the customer, and RAD retries every 15 minutes; Retry detach on the row tries again straight away. If the customer has removed RAD's billing role, RAD alerts its administrators and can't finish the stop until the role is restored.

You don't pause projects yourself: RAD pauses a linked project when the customer's purchased balance falls below the floor, after emailing them, and restores it when they top up — except while the customer has removed RAD's billing role from any of their linked projects, when nothing of theirs is restored until it is back.

VAT Report. VAT collected per customer, per country and per month — VAT charged less VAT returned on refunds, including the VAT on Google Cloud usage a customer paid late (once those arrears are collected) — in credits, each charge at the rate snapshotted when it was made, with a US-dollar figure beside it. Choose a date range (This month and Last month are shortcuts) and a country, switch between By customer, By country and By month, and use Export CSV. Movements into and out of a lab escrow or client wallet are left out — VAT is counted when those credits are spent.

Project Transactions

Every customer's RAD-managed Google Cloud project costs, as they were charged.

1. Go to Billing > Project Transactions. It opens on the last 7 days.
2. Search by project ID or owner email, adjust the dates, and click Search.
3. Each row shows the project, its owner and the credits charged. Every page of results is loaded, so totals and exports cover the whole period.
4. Usage Google reported after the lab session or client project that funded a project was settled shows as a separate billed after settlement figure on that project's row. It is billed to the funder as an amount owed and is not part of the charged total.

Project Invoices

Reconcile actual Google Cloud spending.

1. Go to Billing > Project Invoices. It opens on the current month and loads it.
2. Pick another month to change it; Fetch Project Invoice reloads.
3. Each row shows the project's name and ID, its owner, the list cost in credits (the cost at the credits-per-unit rate, before any project margin — so it is not the amount debited) and the total cost in your display currency. Totals beneath the table cover the page on screen and say so. Export to CSV exports every project for that month.

Per-deployment Module Costs are not a Billing tab — they live on the Credits page.

Payout Summary

See per-payee payout totals across partners and agents. This tab is available to finance and admin only.

1. Go to Billing > Payout Summary. It opens on the last 7 days and loads straight away.
2. To report on another period, choose a start and an end date — both required, maximum 366 days — then click Calculate Payouts.
3. Each row shows the payee's email, whether they're paid as an Agent, a Partner or both, the number of transactions, the purchased credits behind them, the Setup Revenue a partner earned as the engineer on completed setup requests, and the Amount Due in your billing currency. Agent figures come from the commission ledger, and the commission-basis total counts each spend once, even when it paid both an agent and a partner. Period totals appear beneath the table, and Export to CSV gives you the same list to work from.

Recording a partner payout

RAD does not send money — you pay partners outside the platform — but once you have, record it so both you and the partner have a lasting record.

1. Select the period the payment covers. The period must have ended: Mark paid stays disabled while the period includes today, because anything earned after you recorded it could never be paid.
2. On the partner's row, optionally enter your payment reference, then click Mark paid.
3. RAD recalculates the partner's amount for that period and stores it with the rates in force at that moment. That stored figure is the permanent record: if the revenue-share rate changes later, the live figure on this page moves but the recorded payment does not, and the row shows both when they differ.

A period can be recorded once per partner; marking the same period again changes nothing, and a period that overlaps one already recorded for that partner is refused. Each recorded payout writes an audit entry, and the partner sees it in the Payouts section of their Module Revenue tab. Agent commission has its own payout flow on Agent Revenue.

Viewing users, agents, and partners

As Finance you can see all users and the full lists of agents and partners.

• See and search every account on Billing > Credit Management — the table lists all users and has a "Search by email" box. There is no separate Users page for Finance; that one is admin-only.
• See the partners and agents on the platform through the pickers on Module Revenue, Agent Revenue, and the Assigned Engineer field on Setup Requests.

Limited user edits

The only change you can make to a user account is to their credit balances (Awards, Subscription, Top-up and the Monthly Partner allotment), and never on your own account.

All roles — including granting or revoking the Partner role — and a user's active status are admin-only, so the Credit Management screen shows you no role controls. You can still set the Monthly Partner allotment for someone who already holds the Partner role.

Labs

Finance oversees lab sessions; it does not run them.

1. Click Labs in the navigation bar (the same view is Solutions → Managed Environments). You see every trainer's sessions, with a date range, a status filter and a Trainer column.
2. Open Participants on a session to see its settlement — committed, consumed, refundable, and anything absorbed by RAD — and its participants. Export CSV downloads the list.
3. Each participant's environment opens a read-only deployment page: build status and logs, with secrets masked. The Outputs tab and generated passwords or keys are not shown to you; they belong to the participant and the trainer.

The one change you can make is End now, which stops a session's spending straight away. It moves no money: the escrow settles later, once the session's Google Cloud usage has been metered. Everything else — creating or duplicating sessions, starting clocks, extending, adding or removing participants, resending invitations, provisioning and topping up — belongs to the session's trainer or an administrator, and those controls are not shown to you.

Setup Requests

Managed-setup requests from users who want RAD to handle a deployment for them appear here.

1. Click Help in the navigation bar, then open the Setup Requests tab.
2. The tab opens on the last 7 days and loads straight away. To change it, choose a status filter and a start and end date, then click Load Requests.
3. Expand a request to work it: set its status (new, in-progress, completed or cancelled), choose an Assigned Engineer (only registered partners are accepted), record Revenue Achieved, and add internal notes. Click Save to apply.
4. Saving a request as completed is what calculates the split between platform and engineer revenue, so set the revenue figure before you mark it completed. The engineer keeps 75% and the platform 25% by default; an administrator can set a different platform share (Platform revenue share (setup requests) in settings), and a share of 0 is honoured. The module Partner Revenue Share does not affect setup requests. Changing the revenue on a request that is already completed recalculates the split without changing its completion date. Export to CSV gives you the loaded set for reporting.

Audit Log

Open Audit Log from the navigation bar to see who changed what, and when, on the platform's money. Your view shows the money-related actions only: credit balance changes and bulk adjustments, referral awards, agent commission reversals and payouts, setup-request revenue splits, event codes, lab session charges, refunds and settlements — including a place a trainer paid for on a participant's behalf (with the trainer's note about the offline payment, if they left one) — and customer-billing changes and linked-project requests, approvals, rejections, pauses and unlinks. Administrators see every action.

• The page opens on the last 7 days. Change the dates, pick an Action, or type part of an email in Performed by, then select Load. The range can be up to a year.
• Select Show all on a row to see everything recorded with it, such as the balance before and after a change.
• Results are paged beneath the table; choose 25, 50, 100 or 200 rows per page.
• If a range holds more actions than one load can read, only the most recent are shown and a notice asks you to narrow the dates.

The log is read-only.

Getting help

Click Help in the navigation bar:

• Send Message tab — a contact form that raises a support ticket and emails the support team. The My Tickets tab beside it lists the tickets you have raised and their status. Finance is a staff role, so you can raise a ticket without purchased credits on your account (ordinary users need them while purchases are switched on). Each account can raise up to 5 tickets in any 24 hours.
• Setup Requests tab — described above.
• Support Tickets tab — the shared ticket queue. Because billing is one of its categories, you can triage it: Finance and admins may assign, reassign or clear a ticket's assignee to anyone, where support agents may only claim an unassigned ticket or release one they hold.

The ROI calculator is not on Help — it's the last tab on the Credits page, Calculate ROI. Credits appears in your navigation only if your account also holds the ordinary user role; otherwise go to /credits directly. Without the user role you have no credit ledger of your own, so the page does not offer Credit Transactions and opens on Module Revenue instead; Module Costs and Project Invoices are there as usual.

A Contact Us link in the footer also takes you to the Help page.