# Google Forms Data Entry Into Sheets for Transactions

- Author: CheapBankConvert (https://cheapbankconvert.com)
- Published: 2026-10-17
- Category: The cost of manual data entry
- Canonical: https://cheapbankconvert.com/blog/google-forms-data-entry-into-sheets

> Use Google Forms for data entry into Sheets: a free form for each transaction, dropdowns that prevent typos, and rows that land ready to sort.
Google Forms data entry into Sheets works by building a free form with one question per field (date, payee, category, amount), then linking the form to a spreadsheet. Each submission becomes one row. Dropdowns fix the spelling of categories, and validation rules refuse amounts that are not numbers, so the sheet stays sortable without cleanup.

## Why use Google Forms data entry into Sheets for transactions?

A form puts one transaction on the screen at a time, with labelled boxes, and refuses bad answers before they reach the sheet. A bare spreadsheet accepts anything in any cell. For a household or a small club where several people record spending, the form keeps everyone's rows in the same shape.

Typing straight into a sheet has three weak spots. People type the same category three ways ("Groceries", "grocery", "Food shop"), so totals by category split. Amounts arrive with currency signs or words, and Sheets stores them as text that a SUM skips. And on a phone, a wide sheet is fiddly to scroll, so people stop entering things on the go.

A form fixes each of these:

- **Fixed choices.** A dropdown question offers only the categories you list, spelled your way.
- **Checked numbers.** A rule on the amount question rejects anything that is not a number.
- **Phone friendly.** The form opens as a simple page in any browser, so a receipt can be logged at the till.
- **Shared without edit rights.** Others can submit rows without being able to change or delete past rows in the sheet.

The cost is speed for bulk work. A form handles one row per submission, which suits the transaction you just made, not a month of statement lines. The last section of this post covers where that line falls.

## Building a transaction entry form: questions and dropdowns

A transaction entry form needs four to six questions, each matched to the right question type. Use a Date question for the date, a Short answer for the payee and the amount, and a Dropdown for the category and the account. Mark the date, amount and category as required so no row lands half empty.

Start at forms.google.com with a blank form. Give it a plain title, such as "Household spending", and add the questions below. The categories in the table are examples; replace them with your own.

| Question | Question type | Required | Rule or choices (example) |
| --- | --- | --- | --- |
| Date | Date | Yes | None needed, the date picker sets the format |
| Payee | Short answer | No | Length, maximum 60 characters |
| Category | Dropdown | Yes | Groceries, Rent, Utilities, Transport, Eating out, Other |
| Account | Dropdown | Yes | Joint checking, Credit card, Cash |
| Amount | Short answer | Yes | Number, greater than 0 |
| Money in or out | Multiple choice | Yes | Out, In |

### Why a separate "in or out" question

Asking people to type a minus sign for spending is the commonest source of sign errors. A separate in-or-out choice lets everyone type the amount as printed, a positive number, and a formula in the sheet turns spending negative later. One click replaces one easily forgotten keystroke.

### Keep the category list short

A dropdown with thirty categories is slow to scroll on a phone, and people pick "Other" to escape it. Six to ten categories is easier to choose from. You can always split a category later in the sheet by filtering on the payee.

### Add a short description to the amount question

Forms lets you add a line of help text under a question. Use it for the amount: "Numbers only, no dollar sign, for example 42.50". That one line prevents most rejected submissions before the rule has to.

## Response validation rules that block transaction amount typos

Response validation is a rule on a question that rejects an answer that breaks it and shows your error message. For transaction amounts, a Number rule rejects letters, currency signs and blanks. You can also set a range, so an extra zero that turns 45.00 into 450.00 can be caught if you cap ordinary amounts.

Google's help page on [setting rules for a Google Forms question](https://support.google.com/docs/answer/3378864) lists the rule types: number, text, length and regular expression. Its examples include a number greater than or equal to a value and a number between two values. To add one, open the question's More menu, choose Response validation, then pick the rule type.

Rules that suit a spending form:

1. **Amount: Number, greater than 0.** With the in-or-out question doing the sign, every amount should be positive. A zero or a minus sign is rejected.
2. **Amount: Number, between 0.01 and a cap you choose.** If almost nothing you buy tops 2,000, a cap of 2,000 stops a slipped digit. Larger one-off payments then need the cap raised or a separate entry, which is a fair price for catching typos.
3. **Payee: Length, maximum 60 characters.** This blocks a pasted paragraph without getting in the way of a normal name.
4. **Reference number, if you track one: Regular expression, matches digits only.** Useful for check numbers.

Validation cannot tell that 45.00 should have been 54.00. Both are valid numbers in range. Swapped digits need a check against a total, such as the bank's monthly figures, after the rows are in.

If you would rather type straight into a sheet, the same idea exists in spreadsheets. [Excel data validation for data entry](/blog/excel-data-validation-for-data-entry) sets these rules on the cells themselves, so a desktop user gets the same protection without a form.

## Linking the transaction form to a Google Sheets response sheet

A form stores answers on its own until you link it to a spreadsheet. Once linked, each new submission is added as a row in that sheet. You can create a fresh sheet or send responses to one you already have, and the link can be removed later without losing the rows.

Google's page on [choosing where to save Google Forms responses](https://support.google.com/docs/answer/2917686) gives the steps:

1. Open the form and click the Responses tab, then Summary.
2. At the top right, click More, then Select destination for responses.
3. Choose Create a new spreadsheet, or Select existing spreadsheet.
4. Click Create or Select.

The same page notes that Sheets puts the response data in a table, and that the sheet shows up in Google Drive like any other file. It also warns that sharing settings do not stay in sync. If you add a person to the form later, add them to the sheet separately if they need to see the rows.

### Do your work on a second tab

Treat the response tab as an inbox. Do not sort it, insert columns into it or type over its cells, since new rows keep arriving there. Add a second tab for your formulas and summaries that reads from the first. A formula such as `=QUERY(Responses!A:G,"select * where F is not null")` on a second tab gives you a copy you can arrange freely. Adjust the tab name and column letters to your form.

## What do Google Forms transaction rows look like in Sheets?

Each submission lands as one row, with one column per question in the order you built them, plus a column recording when the form was sent. Dates arrive as real dates and validated amounts as numbers, so sorting and summing work at once. The only extra step is applying the sign from the in-or-out answer.

Here is an example of three rows as they might land. The values are made up.

| Submitted | Date | Payee | Category | Account | Amount | Money in or out |
| --- | --- | --- | --- | --- | --- | --- |
| 3/4/2026 18:02:11 | 3/4/2026 | Corner Grocer | Groceries | Joint checking | 64.18 | Out |
| 3/5/2026 08:15:40 | 3/5/2026 | City Transit | Transport | Credit card | 2.75 | Out |
| 3/6/2026 12:01:03 | 3/6/2026 | Payroll | Other | Joint checking | 1850.00 | In |

### Turning amounts into signed values

On your working tab, add a signed amount column. If Amount is in column F and the in-or-out answer is in column G, the formula in a new column is:

`=IF(G2="Out",-F2,F2)`

Copy it down. Spending is now negative and income positive, and `=SUM()` over that column gives the net for the period. A pivot table on Category and the signed column gives totals per category.

### Fixing a wrong row

Rows submitted by mistake can be fixed in two places. Responses can be set to allow editing after submission, or you correct the cell in the sheet. Correcting the sheet is quicker, but keep a short note column for edits so the change is visible later.

### Checking the rows against a statement

At month end, compare the total of the rows for one account with the bank's figures for the same dates. If they differ by exactly one amount, a transaction was never entered. If they differ by a number divisible by 9, look for two swapped digits.

## Google Forms entry limits: when a form slows statement work

A form is the wrong tool for entering a whole bank statement after the fact. Each row means opening the form, filling five questions and pressing Submit, then reloading. That is fine for one purchase on the day, and slow for sixty rows from last month's PDF.

A rough comparison makes the point. Suppose, as an example, that a form submission takes 30 seconds and a typed row in a sheet takes 20. Sixty statement rows then take 30 minutes through the form and 20 minutes typed directly. What that half hour is worth depends on your rate, and [working out what your time is worth per hour](/blog/what-is-my-time-worth-per-hour) gives three ways to set it.

Use the form for live entry and something else for backlogs:

- **Daily spending as it happens:** the form, on your phone.
- **A month of rows already in a text-based PDF:** copy the text out, using the steps in [how to copy a PDF into Excel and fix the paste](/blog/how-to-copy-a-pdf-into-excel), or convert the file.
- **A scanned or paper statement:** typing, because nothing can be copied.

There is one more limit. A form cannot read an attachment and fill itself in. If you were hoping to upload a statement and get rows back, that is a converter's job, and many "free forever" converters have conditions worth reading first; [what a free forever PDF converter really gives you](/blog/free-forever-pdf-converter) goes through them. CheapBankConvert, which is not open yet, plans to charge once per statement with a free two-page preview, and the [homepage](/) lists the early prices. A converted CSV can be imported into the same spreadsheet your form feeds, so both routes end up in one place.