Writing a one-page card policy for a small team
Who may order cards, for what, and how receipts come back. One page answers it all before money moves.
In this guide
In a small team, card spending usually starts informally: the founder orders a card for ads, a designer asks for a font licence, a developer needs a server for a test. It works until it does not. Someone pays for a tool nobody approved, a receipt goes missing, a card is still attached to a former contractor's account, or two people buy the same software. A one-page card policy prevents most of this. It does not need legal language or a committee. It needs to answer six questions in plain words before money moves.
Question 1: who may order cards?
Name the person or people who can order cards from the team's account. In most small teams this is one or two people, often the founder and an operations lead. Everyone else asks them. Keeping ordering in few hands means one person always knows how many cards exist and what each is for.
Because ordering and revealing card details both require the account's authenticator, this also decides who holds the authenticator. Do not share one authenticator between several people; it makes it impossible to know who did what.
Question 2: what can cards be used for?
List approved categories, for example:
- advertising on agreed platforms;
- software and subscriptions on the approved tools list;
- hosting and domains;
- one-off purchases for a named project, with approval.
And list what cards are not for: personal purchases, gifts, anything for a client unless agreed in that client's contract. Clear lines prevent awkward conversations.
Question 3: what are the limits?
| Limit | Example |
|---|---|
| Purchases anyone can make without asking | Under $50, from an approved category |
| Purchases that need approval | $50 and above, or any new subscription |
| Who approves | The person who orders cards |
| How approval is recorded | A message in the team's finance channel |
The card balance is a hard limit in itself. The policy adds the soft limits that keep everyone aligned before the hard one is reached.
Question 4: one card per what?
Decide how cards are split: per purpose (ads, tools, hosting), per project, per client or per person. Per purpose suits most small teams. Per client suits agencies. Per person suits teams where several people buy different things independently. Write the choice down so new cards follow the same pattern. One big card or several explains the cost of each extra card, which is one issue fee of $5.00.
Question 5: how do receipts come back?
State where receipts go and by when. For example: "Save every receipt in the shared receipts folder, named date-merchant-amount, within three days." Name the person who checks receipts at month end. The month-end close describes a twenty-minute routine that fits most teams.
Because My Cards shows balances, status and expiry dates but not a merchant transaction list, receipts are the only record of what each card paid. The policy should make that clear.
Question 6: what happens when someone leaves?
When a team member leaves, on their last day:
- remove them from every tool they had access to, especially those with billing rights;
- move subscriptions they managed to the right owner;
- remove team cards from any personal accounts they used for work;
- collect outstanding receipts;
- remove their seats from per-seat tools; see seat-based pricing surprises.
Add a line to the policy that card details are never shared in chats or documents, and never stored in screenshots. Why card details should never live in screenshots is a good link to include.
A sample policy
Here is a short version a five-person team might use:
- Only Sam and Priya order cards and hold the account authenticator.
- Cards are split by purpose: ads, tools, hosting. Client work gets its own card.
- Anyone may buy approved tools under $50. Anything else needs Sam or Priya's approval in the finance channel first.
- Receipts go in the shared folder within three days. Priya closes the books on the first working day of each month.
- Card details are copied from the account when needed and never stored elsewhere.
- When someone leaves, Priya removes their access and moves their subscriptions that day.
Keeping the policy alive
Pin the policy where the team will see it. Review it every six months, or whenever the team changes size. If people keep asking the same question, add the answer. If a rule is never followed, either enforce it or remove it. A short policy that everyone follows beats a long one nobody reads.
Quick answers
Can several team members have their own BuyVCC accounts?
Yes. Each account has its own sign-in and authenticator. Some teams prefer one shared business account managed by one person; others give each buyer an account.
Does the policy need legal review?
For a small team, a clear one-page note is usually enough. Larger organizations may need formal policies.
See how it works and pricing. Paid orders are usually checked and issued within a few hours.
BuyVCC Team
The people who review BuyVCC orders write these guides from the questions customers send us. Notice something outdated? Let us know.