Expense Tracker Google Sheets: Templates and Setup

Import the supplied blank or worked XLSX into your own Google account, save it as Sheets and inspect the converted formulas. Set one reporting currency and clear date conventions. Give each entry a stable ID and private receipt reference. Review the month and company filters before using totals. The local pack provides an importable workbook, not a hosted sheet or bank connection.

Preview the Sheets expense tracker

The core register has one row for each paid cost or supplier refund. It holds the date, entry ID, company, project, payee, purpose, category, type, amount, currency, receipt reference, account and review status. Signed amount and Exception are calculated columns.

The summary does not require you to type the same cost twice. It selects rows by date and company, then adds signed amounts. A separate category view adds the category criterion. The result depends on those fields being entered consistently, not on the row's colour or where it happens to sit on screen.

Make your own private copy

Use File and Import in Sheets to select the local XLSX. Save the converted file as Google Sheets. Begin with the worked version if you want a known arithmetic check. The file does not ask for access to your account or create a hosted copy on your behalf.

Keep the file restricted while inspecting it. Check whether the folder shares access with a wider group. If you later invite someone to edit, agree which fields they own. A shared file is easier to review when people know where entries belong and who resolves exceptions.

Do not publish the sheet to the web as a shortcut for sharing it. The register can contain private business purposes and source references even without receipt images. Limit access to the actual recordkeeping task.

Set locale, dates and reporting currency

Choose the spreadsheet locale and a clear date display. Date and decimal conventions differ across locales. A date such as 04/05 can be read differently, so compare ambiguous imported dates to their source rather than merely changing how the cell displays.

True dates matter because SUMIFS compares date values. Text that looks like a date may not meet the period criteria. If January does not include an expected row, inspect the underlying date and selected company before changing the formula.

Set the reporting currency in Settings. The core file checks row currency against it. A currency format changes the display; it does not convert an amount. Preserve a supported exchange-rate record outside the core total before adding converted foreign costs.

Check formulas and protected ranges

Inspect the signed amount formula on a purchase and a refund. The sample Expense of 120 stays positive. Refund of 20 becomes negative. An unknown type needs an error state, not a silent zero. This keeps unsupported rows from looking like valid records with no cost.

Check January's inclusive start and exclusive February start. The first February cost belongs outside January. Then change the selected company in a check copy to confirm that B's 70 is distinct from A's 180. Restore the intended selection before entering live records.

The supplied range ends at row 1001. Extend all related ranges and validation before adding more rows. Copying one visible formula is not enough if the monthly summary or category check still ends at the old boundary. Use a known last-row amount to check the extension in a separate copy.

Protection can help prevent accidental formula edits. Recheck it after import because conversion may not preserve every platform detail the same way. A protected range does not hide the data from viewers and is not a substitute for sharing controls.

Enter receipts without exposing them

Give a source a short ID and store the actual receipt in private storage. Use Receipt Index to connect the source ID, private reference, transaction ID and status. A file reference is useful only if an intended reviewer can find the right document.

Test access from the review process rather than changing every receipt to public link sharing. A common folder can have inherited permissions that differ from the sheet. Keep sensitive supplier, employee or client information out of public samples and screenshots.

If a receipt is missing, record that state. Ask for the evidence or apply the business's documented exception process. Do not insert a fictitious source ID to clear the warning. A visible gap is easier to resolve than a misleading completed record.

Review and reconcile the month

Check the register against each payment account. A bank import or statement line can help locate a purchase, but the source and purpose still need review. A later card payment should not become the same operating cost again if the original card purchase was already recorded.

Keep transfers separate from business income and costs. Match their two sides in the account review. An incoming transfer from your own account is not automatically revenue just because it appears as money received.

Record unresolved differences in the checklist with an owner and next action. A summary can add correctly while omitting a whole account. Compare scope and row coverage as well as the final number before treating the month as closed.

Export and back up the sheet

Keep a reviewed period copy in controlled storage. Name it so the company and period are clear. If you export to XLSX, reopen the file and check the known sample or a reviewed total. A conversion can affect validation or display even when the arithmetic remains familiar.

CSV holds one tab's data rather than the whole workbook. It loses formulas, protection and the cross-tab structure. Check dates and IDs after export. Preserve the original sheet and source references so a receiving system's import can be reconciled to the reviewed records.

If a later edit breaks a total, compare the formula and range to the retained worked copy. Do not erase the error with a typed zero. Find whether the fault lies in the input, criteria or formula coverage, then record the correction in the appropriate version.

Check a new shared editing process

Agree which person enters records and which person reviews them. If both edit the same rows, keep the responsibilities clear. One person changing a category while another changes the source can make a row look reviewed without either seeing the final combination.

Use stable entry IDs in questions and corrections. A row number can change after sorting. A short ID lets a reviewer point to the same event in the source index and export. Keep those IDs as text if leading zeroes or a fixed format matter.

Check an imported batch near its boundary

Inspect the first and last imported rows. Compare dates and amount types with the source. A batch can bring in text dates or a different decimal convention even when the displayed cells look familiar. Resolve that before relying on a monthly total.

Use a copy to check a range extension. Put a known amount in the last new row and confirm its effect on the selected total. Then inspect a row outside the month. Both checks matter: the new row should be included when appropriate and excluded when it fails the date criterion.

Keep a source index usable after a file move

If a private receipt folder moves, check the references. A valid spreadsheet formula cannot repair a broken file path. Open several sources from the index, including one used in a correction. Update the storage reference deliberately and retain the source ID.

Do not fix access by making every receipt public. Check who needs the evidence and grant the appropriate access through your storage process. The register can keep a readable ID while sensitive source bytes remain separate.

Use a print copy for a defined purpose

Print the selected record or checklist rather than the whole file by default. State the company and period on the copy. Check that source IDs and totals remain legible. A page that fits the width but reduces text beyond practical reading is not a useful handoff.

Keep the live file and reviewed export separately identifiable. A printout is a snapshot of what was selected at that time. It does not update when the sheet changes, so note any later correction through the same entry IDs.

FAQ: the Sheets tracker

Is the workbook already hosted in Google Sheets?

No. The local pack supplies an XLSX for private import. You create and control the Sheets copy in your own account. After conversion, check sharing and the worked totals before entering real records. No account access, hosted-file creation or bank connection is required by the supplied workbook's stated calculations.

Can I add receipt images directly?

The pack uses a private reference rather than embedding receipt bytes. Keep the actual documents in controlled storage and connect them through source IDs. This makes access easier to review separately from the register. If your process adds attachments elsewhere, check who can view them and preserve a reliable reference in the sheet.

Why is my date not included in a total?

Check whether the cell is a real date, whether it meets the inclusive start and exclusive end, and whether its company ID matches the selection. A visible date label does not prove its stored type. Compare to the source and worked example before changing the formula or broadening the reporting period.

Does sheet protection make the file confidential?

No. It can limit edits to selected cells. It does not hide visible information from someone who can open the sheet. Use sharing settings and private storage to control access. Filtering or hiding rows is also not a confidentiality boundary for employee, company or receipt records in the same workbook.

Can I keep only the CSV backup?

A CSV can preserve selected input rows, but it does not retain the workbook, formulas or review structure. Keep a Sheets or XLSX copy as well. Inspect the CSV before importing it elsewhere, especially dates and IDs. Reconcile the receiving system's totals to the reviewed source rather than assuming export proves a correct transfer.

Sources and checks

Checked 15 October 2026. The examples are fictional and the arithmetic is original.

• IRS records: Business recordkeeping and supporting documents.
• Excel SUMIFS: Official multiple-criteria sum syntax.
• Sheets SUMIFS: Official Sheets multiple-criteria sum syntax.
• IRS books: Publication 583, December 2024 edition, Recordkeeping System section.

Related records and guides

• business expense spreadsheet
• project expense tracker excel
• business expense tracker

Verdict on the expense tracker Google Sheets file

Use the expense tracker Google Sheets file after a checked private import. Keep date types, formula coverage and receipt access under review. The result should be a set of records you can trace, not just a total that looks plausible.