Log expense claims as QuickBooks expenses
Each expense claim submitted by staff is recorded in QuickBooks against the right category, payee and date.
New submission on your employee expense or reimbursement form
Create an Expense (Purchase) in QuickBooks with the category, amount and payee
One-directional. A submission triggers the action — nothing is written back into your form.
Expense claims tend to arrive as messages, spreadsheets and half-remembered card transactions, then sit until someone has a free afternoon to key them in. The delay is what makes month-end slow, not the volume of claims.
Routing the claim form into QuickBooks records each expense against the right category on the date the money was actually spent, rather than the day it was processed. Office managers and small finance teams running reimbursements for a handful of staff get the most out of it, because the coding decision happens once, on the form.
Setting it up
- 1
Rewrite the Expense Category options on your copy of the form so they match account names in your chart of accounts one for one. The Zap matches on the name, and a mismatch is what sends everything to Uncategorised Expense.
- 2
Publish the form, then point the formformform "New Submission" trigger at it and add QuickBooks Online with the Create Expense action.
- 3
Set Payment Account in the Zap to a fixed value — usually a payroll clearing or employee reimbursements liability account — so the claim sits as owed until you actually pay it out.
- 4
Map Vendor or Merchant Name to Payee, with a Find Vendor step in front so repeat merchants like a single taxi firm do not multiply across your vendor list.
- 5
Map Expense Category to the account on the expense line, and run Amount ($) through a Zapier Formatter number step first so entries typed as "£42.50" or "42,50" do not fail.
- 6
Map Date of Expense to the transaction date. Left unmapped, QuickBooks stamps the date the Zap ran, and claims submitted late land in the wrong month.
- 7
Join Business Purpose, Employee Full Name and Approving Manager Name into the memo, so the audit trail travels with the transaction rather than living in a separate form response.
- 8
Add a filter requiring Approving Manager Name, submit one real claim, check it under Expenses, then turn the Zap on.
What maps where
Using the Employee Reimbursement Request as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | QuickBooks |
|---|---|
| Vendor or Merchant Name | Payee on the QuickBooks expense |
| Expense Category | Account on the expense line |
| Amount ($) | Amount on the expense line |
| Date of Expense | Transaction date on the expense |
| Business Purpose | Description on the expense line |
| Employee Full Name | Memo on the expense, recording whose claim it was |
Variations worth knowing
If you settle claims in a batch through payroll, map Employee Full Name to Payee instead and keep Vendor or Merchant Name in the line description. Each employee then has a running balance in QuickBooks that clears when you pay them.
Map Department to Class or Location on the expense, which needs class tracking switched on in QuickBooks settings. Month-end reports then break spend down by team without anyone tagging transactions afterwards.
If something isn't arriving
Staff type currency symbols, commas and trailing text into free-text answers. Make Amount ($) a number question in the form editor and add a Formatter Numbers step in the Zap, which strips anything QuickBooks would reject.
The category names on the form and the account names in QuickBooks are not identical. Either align the wording exactly, or add a Zapier Lookup Table that translates each form option into its account, which lets you keep plain-English options for staff.
Frequently asked questions
Does this actually pay the employee back?
No. It records the expense and, if you use a clearing account, the amount you owe. The payment itself still goes out through payroll or your bank in the usual way, and you clear the balance in QuickBooks when it does.
Can a manager approve the claim before it reaches QuickBooks?
Not inside the form — there is no approval workflow. Most teams add a Zapier step that emails the named approver and waits, or let everything post to a clearing account and review the list in QuickBooks before paying out.
Someone submitted the same claim twice. Will QuickBooks catch it?
No. Every submission triggers a new expense, and nothing is read back from QuickBooks to compare against. Delete the duplicate in QuickBooks, and consider a Zapier filter on merchant, amount and date to catch obvious repeats.
Related automations
- Add new clients to your QuickBooks customer list
Every new client who fills in your intake form arrives in QuickBooks as a customer record, ready to invoice.
- Onboard contractors and suppliers as QuickBooks vendors
New suppliers and contractors fill in their own details once, and the vendor record is created in QuickBooks.
- Raise a QuickBooks invoice from an order request
An order placed through your form becomes a draft invoice in QuickBooks, with terms and PO number already filled in.
- Record a paid order as a QuickBooks sales receipt
An order that has already been paid for is logged in QuickBooks as a sales receipt against the right income account.
- Turn a quote request into a QuickBooks estimate
Quote requests land in QuickBooks as estimates against a named customer, ready for you to price and send.
- Add counter signups to your Customer Directory
A signup at the till or on your site becomes a Square customer profile straight away, spelled the way the customer typed it.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free