Skip to content

Commit d0eb64a

Browse files
drmowinckelsclaude
andcommitted
Document Relay, Wise, and PayPal in the finance section
Restructures `content/global-team/finance/` from a single page into a Hugo section and adds three sub-pages for the actual financial tools: - `relay/` — primary USD operating account: sign-in, transactions and bookkeeping export, virtual cards per subscription, ACH transfers, user management, recovery - `wise/` — international transfers: sending, receiving via local account details in multiple currencies, multi-currency reserves, sweep-to-Relay cadence - `paypal/` — donation channel: nonprofit fee tier, donor refunds, receipt template, weekly sweep to Relay, donor-fee absorption policy The `_index.en.md` preserves the existing donations policy with light edits and cross-links into the tool sub-pages, into the forthcoming nonprofit-administration section, and into 1Password for credentials. Stacks on #207. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent d6c9f3b commit d0eb64a

5 files changed

Lines changed: 323 additions & 23 deletions

File tree

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: "Managing RLadies+ Finance"
3+
linkTitle: "Finance"
4+
weight: 111
5+
chapter: false
6+
aliases:
7+
- /coordination/finance/
8+
---
9+
10+
RLadies+ runs as a US-registered 501(c)(3) nonprofit out of California, paid for by a mix of one-off donations, recurring sponsors, and grant income from partners like the R-Consortium and Posit.
11+
Money in covers conference travel, the small set of paid tools that keep the org running (Zoom, Calendly, Google Workspace, Meetup), reimbursements to chapter organisers for venue and refreshment costs, and the occasional honorarium for invited speakers.
12+
13+
Three external services handle the actual movement of money:
14+
15+
- [Relay]({{% relref "relay" %}}) is the primary USD operating account — the centre of gravity for incoming grant payments and outgoing operational spend.
16+
- [Wise]({{% relref "wise" %}}) handles anything cross-border — paying speakers or chapters abroad, receiving donations denominated in non-USD currencies.
17+
- [PayPal]({{% relref "paypal" %}}) is the donation channel for one-off contributors and small transactions.
18+
19+
State-level filings, tax returns, and the registered-agent service are handled separately through [VCorp]({{% relref "/global-team/nonprofit-administration/vcorp" %}}) in the [nonprofit administration]({{% relref "/global-team/nonprofit-administration" %}}) section.
20+
Credentials for every financial account live in the Shared vault — see [1Password]({{% relref "/global-team/infrastructure/1password" %}}).
21+
22+
## Donations
23+
24+
When someone sends an email inquiring about larger donations, offer to:
25+
26+
- provide them the routing and account number for a direct wire transfer (the account is in Relay; see the Relay page for where the details live in the dashboard), or
27+
- if they are in the US and prefer to send a check, give them the RLadies+ nonprofit HQ address in Oakland — the same address used for official mail (see [AnytimeMailbox]({{% relref "/global-team/nonprofit-administration/anytime-mailbox" %}})).
28+
29+
How to acknowledge the donation:
30+
31+
- Thank the donor in the email communication.
32+
- If the donor is comfortable with a public acknowledgement, add their name to the website's sponsors list.
33+
- If the donor is comfortable with a public acknowledgement, the social media team prepares a draft post for the donor to validate before publishing (see [social media management]({{% relref "/global-team/social-media-management" %}})).
34+
35+
For donations that arrive through PayPal directly, the PayPal page covers receipt issuing and the sweep-to-Relay cadence.
36+
37+
## Recordkeeping
38+
39+
The transaction exports from Relay, Wise, and PayPal are the source of truth for bookkeeping and for the annual Form 990 filing that VCorp prepares.
40+
A periodic export — monthly works well — uploaded into the Shared Drive's finance folder keeps the records reconcilable.
41+
42+
TODO: confirm whether RLadies+ uses an external bookkeeper or whether reconciliation is handled in-house by treasurer-role leadership.

content/global-team/finance/index.en.md

Lines changed: 0 additions & 23 deletions
This file was deleted.
Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
title: "PayPal (donations)"
3+
linkTitle: "PayPal"
4+
weight: 30
5+
---
6+
7+
Most one-off donations to RLadies+ land in PayPal — community members clicking the donate link, conference attendees sending small amounts, anyone for whom PayPal is the convenient option.
8+
The balance never accumulates there for long; it gets swept to [Relay]({{% relref "../relay" %}}) on a regular cadence so the operating account remains the source of truth.
9+
10+
## Account type
11+
12+
RLadies+ holds a PayPal nonprofit account, which qualifies for the reduced transaction-fee rate that PayPal offers verified 501(c)(3) organisations.
13+
TODO: confirm whether the account is also enrolled in PayPal Giving Fund (PPGF), which lets donors give without the standard 2.99% fee in exchange for a slightly delayed disbursement cadence.
14+
15+
The 501(c)(3) verification on file is what unlocks the lower rate; if the IRS determination letter ever needs to be re-uploaded, the most recent copy lives in the Shared Drive's compliance folder (alongside what VCorp keeps).
16+
17+
## Who has access
18+
19+
Admin tied to the role mailbox, credentials in the [1Password]({{% relref "/global-team/infrastructure/1password" %}}) Shared vault.
20+
Additional team members are added via PayPal's user-permissions system rather than sharing the admin login.
21+
22+
TODO: list the current PayPal team members and their assigned permissions.
23+
24+
## Operational tasks
25+
26+
### Signing in
27+
28+
1. Open [paypal.com](https://paypal.com).
29+
2. Sign in with your individual PayPal user credentials, or the admin login from 1Password for admin operations.
30+
3. Complete the 2FA challenge.
31+
32+
### Viewing donations
33+
34+
1. Click **Activity** in the top nav.
35+
2. Filter by date range, or filter by type **Payments received**.
36+
3. Each row shows the donor, amount, fee, and net.
37+
38+
For automated reporting, **Reports****Activity download** exports a CSV.
39+
40+
### Issuing a refund
41+
42+
Donors sometimes mis-click or change their mind. Refund within PayPal directly:
43+
44+
1. Find the transaction in **Activity** → click it.
45+
2. Click **Issue a refund**.
46+
3. Choose full or partial; PayPal usually returns the original transaction fee to the org as well.
47+
4. Confirm.
48+
49+
The donor sees the refund in their PayPal account within minutes (or back to their card within a few business days).
50+
51+
### Issuing a tax-deductible receipt
52+
53+
PayPal can auto-send receipts that include the org's 501(c)(3) status and EIN — useful for US donors claiming deduction.
54+
55+
1. Sign in as admin → **Account Settings****Notifications**.
56+
2. Enable the **Donation receipt** notification (TODO: confirm exact menu name).
57+
3. The receipt template can be customised under **Account Settings****Customer notifications****Donation receipt template**.
58+
59+
The template should include the legal RLadies+ name, the EIN, the donation date and amount, and the standard "no goods or services were provided" language required by the IRS for full deductibility.
60+
61+
TODO: confirm RLadies+ has this template configured and reviewed by VCorp.
62+
63+
### Sweeping the balance to Relay
64+
65+
PayPal balances should not accumulate — they're not insured the way a bank balance is, and the source of truth for bookkeeping is the Relay account.
66+
67+
1. **Wallet** in the top nav.
68+
2. **Transfer money****Transfer to your bank**.
69+
3. Select the linked Relay account.
70+
4. Enter the full available balance (or leave a small buffer if you expect refunds).
71+
5. Confirm.
72+
73+
Standard transfers take 1-3 business days; instant transfers cost a fee and aren't worth it for routine sweeps.
74+
A weekly or bi-weekly cadence works well.
75+
76+
### Adding a team member
77+
78+
1. **Account Settings****Account Access****Manage Users**.
79+
2. **Add a user** → enter their name and email.
80+
3. Choose the permissions: typical donor-management roles need **View transactions**, **Issue refunds**, and **Download reports**. Admin operations stay with the admin login.
81+
4. They accept the invitation and complete their own login setup.
82+
83+
### Removing a departed team member
84+
85+
1. **Account Settings****Account Access****Manage Users** → click the departing user.
86+
2. **Remove user**.
87+
3. If they had admin login access, rotate the admin password in 1Password.
88+
89+
## Recovery
90+
91+
Recovery codes for 2FA in 1Password.
92+
PayPal's account recovery falls back to email verification at the role mailbox; Workspace access remains the prerequisite.
93+
94+
If a donor reports a chargeback or PayPal flags a transaction as suspicious, respond through the **Resolution Center** rather than letting it auto-resolve against the org's interest.
95+
96+
## Things to watch for
97+
98+
- **PayPal periodically requests re-verification of 501(c)(3) status.** These notifications land at the role mailbox; acting on them quickly keeps the reduced-fee rate.
99+
- **Funds held on a newly-large transaction.** PayPal's risk system sometimes holds disbursement on an unusually large donation. If you know a large donation is coming (a sponsor commitment, a memorial fund), email PayPal Business Support beforehand to pre-empt the hold.
100+
- **Donor-fee absorption policy.** PayPal lets donors optionally cover the transaction fee. Decide and document whether the donate-page widget asks the donor to do this (recommended for transparency) or whether RLadies+ absorbs the fee silently.
101+
- **Failed sweeps to Relay.** A broken bank link can leave the PayPal balance growing without notice — confirm sweeps actually arrive at Relay in the days after initiating.
102+
- **Currency conversion on non-USD donations.** PayPal auto-converts at its own rate, which is worse than Wise. For donations large enough to matter and where the donor can choose, direct them to the Wise account details instead.
Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
title: "Relay (business banking)"
3+
linkTitle: "Relay"
4+
weight: 10
5+
---
6+
7+
Every USD-denominated transaction RLadies+ makes — paying for Zoom, reimbursing a chapter for venue costs, receiving a grant disbursement, sweeping a PayPal balance — flows through a single Relay account.
8+
Relay is the operating bank: the place statements come from, the place cards are issued from, the place the routing and account number on every wire-transfer instruction point at.
9+
10+
## Why Relay
11+
12+
Relay ([relayfi.com](https://relayfi.com)) is a US business banking platform aimed at small businesses and nonprofits.
13+
The fit for RLadies+ is straightforward: no monthly account fees on the standard tier, unlimited virtual debit cards (useful for scoping subscription payments), clean transaction exports for bookkeeping, and a UI that treats multiple human users as a first-class concept rather than an awkward add-on.
14+
The alternative — opening a traditional US business bank account from outside the US, with leadership scattered globally — would be a lot more friction for the same end state.
15+
16+
TODO: confirm whether RLadies+ is on Relay's free tier or Relay Pro (Pro adds wire transfers and automated rules).
17+
18+
## Who has access
19+
20+
The Relay admin account is tied to the role mailbox and credentials live in the Shared vault in [1Password]({{% relref "/global-team/infrastructure/1password" %}}).
21+
Leadership members are added as individual Relay users with their own logins rather than sharing the admin credentials — Relay supports per-user roles (Admin, Bookkeeper, Approver, View Only) and per-user roles make audit trails meaningful.
22+
23+
TODO: list the current Relay user roster and their assigned roles.
24+
25+
## Operational tasks
26+
27+
### Signing in
28+
29+
1. Open [app.relayfi.com/login](https://app.relayfi.com/login) in your browser.
30+
2. Sign in with your individual Relay user credentials (not the shared admin login unless you specifically need admin operations).
31+
3. Complete the 2FA challenge using the authenticator app you set up at first login; recovery codes are in 1Password under your Relay item if you've stored them there.
32+
33+
### Viewing transactions and exporting for bookkeeping
34+
35+
1. Click **Transactions** in the left sidebar.
36+
2. Set the date range using the filter at the top right.
37+
3. Click **Export** → CSV.
38+
4. Upload the CSV to the finance folder in the Workspace Shared Drive (see [Shared Drive]({{% relref "/global-team/infrastructure/google-workspace/shared-drive" %}})).
39+
40+
Doing this monthly keeps reconciliation manageable and gives [VCorp]({{% relref "/global-team/nonprofit-administration/vcorp" %}}) clean source data for the annual Form 990.
41+
42+
### Creating a virtual card for a subscription
43+
44+
Virtual cards let you cap a subscription's monthly limit and revoke it without touching the physical card. Use one per service so a leak or runaway charge is contained.
45+
46+
1. Click **Cards** in the left sidebar.
47+
2. Click **+ New card** → choose **Virtual****Subscription**.
48+
3. Name the card after the service it pays (e.g., `Zoom subscription`, `Canva Pro`).
49+
4. Set the monthly limit just above the expected charge.
50+
5. Copy the card number into the 1Password entry for the service that will use it.
51+
6. Use the card details to set up payment in the service's billing settings.
52+
53+
### Issuing an ACH transfer
54+
55+
1. Click **Payments****Send payment**.
56+
2. Choose **ACH** as the method.
57+
3. Enter recipient details (routing, account number, name on account).
58+
4. Set the amount and the description (descriptions show up on the bank statement — make them meaningful for bookkeeping).
59+
5. Schedule for the next business day or a specific date.
60+
61+
For international payments, use Wise instead — see [Wise]({{% relref "../wise" %}}).
62+
63+
### Adding a new Relay user
64+
65+
1. Sign in as an Admin.
66+
2. Click **Settings****Team****Invite member**.
67+
3. Enter the new user's email (their personal email is fine; their Relay login is separate from any other login).
68+
4. Choose a role (Admin, Bookkeeper, Approver, View Only) appropriate to the work they will do.
69+
5. They accept the invitation via email and complete their own 2FA setup.
70+
6. Confirm they can see the expected accounts and transactions.
71+
72+
### Removing a departed user
73+
74+
1. **Settings****Team** → click the departing user → **Remove**.
75+
2. Revoke any virtual cards they personally created (Cards → filter by creator → freeze or close).
76+
3. If they had access to physical cards or the admin login, rotate the relevant credentials and update 1Password.
77+
78+
## Recovery
79+
80+
If 2FA breaks on a user's login, recovery codes saved in 1Password at first sign-in are the first option.
81+
If the admin login is the blocker, Relay support can recover via the role mailbox — which means Google Workspace access is the real prerequisite to financial recovery.
82+
Cross-link: [Google Workspace admin recovery]({{% relref "/global-team/infrastructure/google-workspace/admin-console" %}}#troubleshooting).
83+
84+
## Things to watch for
85+
86+
- **Subscription auto-renewals on virtual cards.** A virtual card with a $50/month limit won't catch a service that quietly raises to $100/month — review transactions monthly.
87+
- **Stale user access.** Departing leadership rarely flag their own offboarding; the six-monthly admin review (see [1Password]({{% relref "/global-team/infrastructure/1password" %}})) should include a Relay user-list walk.
88+
- **Monthly statement to the role mailbox.** Make sure someone in finance actually reads it; treat it as evidence rather than noise.
89+
- **Tax-relevant transactions.** Large incoming grants and outgoing honoraria both have 1099 / W-9 implications; flag them to VCorp at the time of the transaction, not at year-end.

0 commit comments

Comments
 (0)