If you need to record who fronted a roommate grocery bill, trip deposit, or club purchase, use a linked record field instead of typing names into a dropdown. Put each person in a separate People table, then connect the Receipts table's Payer field to it. Airtable's documentation on linking records covers this relationship between tables.

The field identifies the payer. It doesn't send money or decide who owes what.

Decide what the payer field must capture

A linked payer field stores a connection to a person, not a second copy of their name. That makes it easier to keep names consistent as the same roommates, travelers, or club members appear across many receipts.

Situation Payer setup What it solves
One person paid the merchant Link to one People record Records the person who fronted the expense
Two or more people paid, but exact contributions do not matter Allow multiple linked People records Shows everyone associated with the payment
Two or more people paid different amounts Use a Contributions table Records each person's amount separately
One person paid, but several people share the cost Keep one Payer link and add Participants or Shares Separates payment from responsibility

For a normal receipt, limit Payer to one record. Turn on multiple links only when several people actually paid. A receipt with three linked names still won't show whether they paid equal amounts.

Build the base around receipts, people, and proof

To be honest, a small household or trip tracker usually needs only two tables at first. Keep the field names plain so everyone knows what to update.

Table Field What to store
People Name One record for each roommate, traveler, family member, or participant
People Contact Optional email or phone detail for identification
Receipts Receipt file A photo or PDF of the receipt, when available
Receipts Expense date The date the cost occurred
Receipts Merchant and details Store, bill type, items, or a short description
Receipts Amount The full amount charged
Receipts Payer A link to one or more People records
Receipts Reimbursement status For example, Needs review, Waiting for reimbursement, Partly reimbursed, or Reimbursed
Receipts Reimbursed date The date the payer received money back
Receipts Notes Split rule, exception, or a non-sensitive payment reference

Create one People record per person. Don't create a new record for every spelling variation of the same name.

Because Payer points to a People record, you can correct a person's displayed name in one place. The receipts continue pointing to that record.

Set up the Airtable payer column

  1. Create a table named People. Add the participants before entering receipts. Use a consistent name, and add a contact detail if two people could be confused.

  2. Create a table named Receipts. Add fields for the date, amount, description, receipt file, reimbursement status, and notes.

  3. Add a field in Receipts and choose Link to another record. Select the People table, then name the field Payer. Airtable provides the linked-record setup described in its record-linking help documentation.

  4. Decide whether one receipt can have several payers. Leave multiple links off for single-payer expenses. Enable the option to allow linking to multiple records for shared payments.

  5. Add a test receipt. Enter the amount and date, then click the Payer cell and select an existing person. The selected person should appear as a linked record.

  6. Create a view for open reimbursements. Filter out records marked Reimbursed, then group or sort the remaining records by payer or expense date.

Test the setup before importing old receipts. Five sample records are enough to expose a confusing status name or a missing split field.

Do not expect names to link automatically

A linked field won't reliably turn matching text into a relationship by itself. If an imported row says Jordan in a plain-text field, you may still need to select Jordan's People record manually.

An automation can handle that workflow. Use a trigger such as a newly created receipt, identify the matching People record, and use an Update record action to write the link. Airtable's guidance on linking existing records with automations recommends testing the step to confirm that the intended records were found.

Use a matching value that is unique within your group. Duplicate names can create the wrong link, and an automation can repeat that mistake faster than a person can.

Know when one Payer field is not enough

Thing is, who paid and who owes are separate questions. A $96 dinner might have Maya as the only payer, while four people share the cost.

The Payer field answers the first question. It does not calculate the second.

Question Simple setup More precise setup
Who paid the merchant? Payer on Receipts Payer on Receipts
Who should share the cost? Participants linked to People A Shares table with one row per person
How much did each payer contribute? Not captured A Contributions table with an amount field
How much does each person owe? A note or manual calculation A Shares table with an amount owed
Who has been reimbursed? Reimbursement status on Receipts Status and date on each contribution or share

Add a Contributions table when the amount paid by each person matters. Give it links to Receipt and Person, plus Amount paid, Amount owed, Status, Reimbursed date, and Notes.

That extra table prevents a common error: counting the full receipt amount once for every linked payer. It takes longer to build, but the records stay useful when payments are uneven.

Record the split rule before requesting reimbursement

Write down how the group agreed to divide the cost. A payer column won't explain an exception six weeks later.

Split method What to record
Equal split Eligible people and the number of shares
Usage-based split The measurement used, such as nights, miles, or meals
Income-based split The agreed contribution rule and the people covered
Room-size split Which room or space each person occupies
Nights-stayed split Arrival, departure, and any cancellation adjustment

Pick the rule before sending requests. If the group changes the split after a dinner, record the decision in the allocation or contribution record instead of silently changing the original receipt total.

Income-based and other custom arrangements are group agreements. Make the terms visible to the people affected, and keep sensitive financial details out of general notes.

Turn the tracker into a reimbursement routine

Airtable can document the expense and the reimbursement status. The actual transfer happens somewhere else, such as a bank or payment app.

Use this short review routine:

  • Confirm the receipt image, date, merchant, and total.
  • Check that the linked payer and participants are correct.
  • Record the reimbursement status after the group agrees on the amount.
  • After payment, add the date and a non-sensitive reference, then mark the record complete.

Use a separate status for reimbursement rather than calling the receipt Unpaid. The merchant may already be paid even though the person who fronted the money is still waiting.

Keep the shared base easy to review

Give editing access to people who add or correct records. For everyone else, use commenting or read-only access where the workspace supports it.

Keep the People table clean. If someone stops participating, preserve their historical links and handle future selection through your process rather than reusing that record for a different person.

Review the tracker on a set schedule. A weekly check works for groceries and household bills; a trip group may prefer a review after each major booking and again after returning home.

Don't store full bank account numbers, card details, or payment passwords in receipt notes. Record only what the group needs to confirm the reimbursement.

FAQ

Can I use a single-select field instead of a linked payer field?

You can, especially for a very short, one-time list. A linked field is more useful when the same people appear across many receipts or when you want related records for each person.

What if I already typed payer names into a text field?

Create the People records, add the new linked Payer field, and connect each receipt manually. For a larger import, an automation can match a stable value and update the linked field, but test it before processing the whole table.

Can one receipt have multiple payers?

Yes. Enable multiple linked records in the Payer field and select each person. If their contributions differ, add a Contributions table with one row per payer.

Does the payer column calculate what each person owes?

No. It records who paid. Add participants, shares, or contribution amounts if the group needs a reimbursement calculation.

Can Airtable process the reimbursement?

No. Use Airtable for the record, status, receipt, and notes. Complete the transfer through a separate payment method and then update the tracker.

Start with People and Receipts, enter five test records, and reconcile one real reimbursement. If the test exposes different payer amounts or changing split rules, add Contributions before importing the rest of your receipts.