QuickBooks
Send an expense to QuickBooks as the right transaction type
Pass expense preflight and create the intended Bill, Purchase, or Vendor Credit with correct coding. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.
Before you begin
- Audience: Expense Admin, company admin, accounting manager.
- Connected QuickBooks
- eligible approved or not-required expense
- complete accounting coding and mappings
- company/expense access.
Sales → Expenses (#/expenses) → QuickBooks preflight/send; integration mappings
Send an expense to QuickBooks as the right transaction type
-
Open the workspace
In JobBuddy, go to Sales → Expenses (#/expenses) → QuickBooks preflight/send; integration mappings.
-
Confirm access and starting state
Connected QuickBooks; eligible approved or not-required expense; complete accounting coding and mappings; company/expense access.
-
Complete the main setup
Review Bill versus Purchase selection and Vendor Credit for supported negative/correction cases, approval gate, vendor/account/payment-method mappings, line product/tax/customer/project/cost-code mapping, receipt attachment, preflight errors, retry, and coding correction after sync.
-
Verify the result
Pass expense preflight and create the intended Bill, Purchase, or Vendor Credit with correct coding.
Expected result: Pass expense preflight and create the intended Bill, Purchase, or Vendor Credit with correct coding.
Troubleshooting
The page, control, or action is unavailable.
Confirm the required access and starting state: Connected QuickBooks; eligible approved or not-required expense; complete accounting coding and mappings; company/expense access.
The result is incomplete or unexpected.
Approval/review state, supplier/vendor, accounts, payment method, customer/project, products, taxes, cost codes, receipt, positive/negative amount, and sync history select or block the transaction.
The issue remains after checking the record.
Capture the exact visible error, record status, approximate time, and intended result. Give support only the minimum customer-safe evidence needed to trace the problem.
What happens next
- Pass expense preflight and create the intended Bill, Purchase, or Vendor Credit with correct coding.
- Review the resulting record, status, notifications, and related history before continuing downstream work.
- Use the related guide when the next action belongs to another JobBuddy workflow.