a. Go to Accounting > Batch/Export Transactions.
b. Review the list of unbatched invoices. Confirm that all completed jobs for the closing period have been invoiced and that invoice details (items, pricing, Business Unit, tax zone) are accurate.
c. Batch and post all invoices for the period. Posting locks the invoice and generates journal entries (Debit: Accounts Receivable; Credit: Revenue per line item GL account).
⚠︎ Invoices that have not been posted will not appear on financial reports. Payroll and accounting reporting only include posted invoices. Always verify all period invoices are posted before running any closing reports.
⚠︎ If auto-batching is enabled, invoices can be re-batched within seconds of being created. Temporarily disable auto-batching if you need to manage batches manually during the close process.
a. Go to Accounting > Customer Payments. Review payments collected during the closing period.
b. Verify that all payments are applied to the correct invoices. Check for unapplied payments — bulk commercial checks may need to be manually distributed via Accounting > Customer Payments > Bulk Apply.
c. Batch and post all payments for the period. Posting generates journal entries (Debit: Bank/Cash; Credit: Accounts Receivable).
a. Go to Accounting > Bank Deposits.
b. Group individual payments into deposits that match your actual bank statement. For example, if your bank shows a single $5,000 deposit but ServiceTitan shows 20 individual $250 payments, group those 20 payments into one deposit.
c. When this syncs to your accounting software, it appears as a single entry, making bank reconciliation significantly faster.
⚠︎ Review open jobs before closing the period. Jobs with costs but no invoices inflate expenses and understate revenue on your financial statements.
a. Go to Reports > All Reports and search for a Jobs report template (or a custom WIP report if your team has built one). Filter for jobs completed during the closing period that have not been invoiced.
b. Review open jobs with costs but no invoices. Follow up with dispatchers or technicians to complete and invoice outstanding work before closing.
c. For companies using Project Management, review project-level Budget vs. Actual data from the project record to identify underbilled or overbilled projects.
⚠︎ Use the Accounting Detail Legacy Report for transaction-level data, and cross-reference with your accounting system's WIP or job costing reports for the full picture.
a. Once all invoices and payments for the period are posted, export the batch to your accounting system (QuickBooks Desktop, QuickBooks Online, Sage Intacct, or Xero).
b. After export, verify export status. Go to Accounting > Batch/Export Transactions and confirm all items show as Exported. Check for GL Errors at Accounting > GL Errors.
⚠︎ "Exported" does not mean successfully synced. If your accounting system rejected a record, the individual record's sync status may show "Error" even though the batch shows "Exported." Always check per-record sync status.
⚠︎ Once exported, invoices are permanently locked in ServiceTitan. The only way to correct an exported invoice is to create an adjustment invoice (credit memo). Correction must happen in the accounting system for anything already synced.
a. In your accounting software, run the Income Statement (Profit & Loss) report for the closing period. Select the relevant Class/Department (which maps to your ServiceTitan Business Units).
b. Review total revenue, cost of goods sold, and net income for accuracy.
c. To cross-reference against ServiceTitan data, go to Reports > Legacy Reports and search for Accounting Detail. This report provides a summary of transaction balances by GL account for the period.
a. In your accounting software, run the Balance Sheet as of the last day of the closing period.
b. Confirm that total assets equal total liabilities plus equity.
c. If the report is out of balance, review recent journal entries and unposted transactions in your accounting software before exporting additional data from ServiceTitan.
a. In your accounting software, run the Trial Balance for the closing period.
b. Verify that total debits equal total credits. Any difference indicates unbalanced journal entries that need correction before closing.
a. In your accounting software, run a Tax Liability report for the closing period.
b. Review the tax collected and tax owed amounts by jurisdiction to confirm accuracy before filing.
⚠︎ ServiceTitan Tax Zone names must match your accounting software's Tax Item names exactly. Mismatches cause export errors and incorrect tax reporting. If you're using Avalara, rates are looked up automatically by address — but manual tax zone overrides can cause double-taxation on commercial recurring service visits.
a. In your accounting software, review revenue by GL account or Chart of Accounts for the closing period.
b. Cross-reference revenue totals against the ServiceTitan Accounting Detail Legacy Report (Reports > Legacy Reports > search "Accounting Detail") and/or the BU Dashboard Revenue report (Reports > All Reports > search "BU Dashboard Revenue") to verify that all revenue is posted to the correct GL accounts.
⚠︎ GL mapping in ServiceTitan does not affect job-level margin calculations inside ServiceTitan — ST calculates margin independently. However, items with no GL assignment export to a catch-all or default account in your accounting software. This is a silent data quality issue. Fix GL mappings in the Pricebook, but note that fixes only apply to future exports — historical data already exported is not retroactively corrected.
a. Go to Accounting > Accounting Periods (or Settings > Accounting > Accounting Periods).
b. Set the status of the closing month to Closed. This blocks any user (without admin override) from editing, voiding, or adding transactions in that month.
⚠︎ Closing an accounting period is irreversible in practice. Once closed, unposting is blocked — only adjustment invoices (credit memos) are allowed for corrections. Lock months promptly after reconciliation to prevent backdated edits that change your printed financial statements.
a. Go to Reports > All Reports, find the report you want to schedule, and click the Calendar icon (or open the report, click More, and select Schedule).
b. Choose between a Simple Report (individualized per recipient) or Flexible Report (same report for all recipients).
c. Set the delivery cadence (e.g., every 1 month), date range (e.g., Previous Month), recipients, and export format (PDF or XLSX). Click Schedule.
d. To view or edit existing schedules, go to Reports > Scheduled Reports.
a. Verify the date range on the report covers the full closing period. Transactions posted on the last day of the month are commonly missed if the end date is set one day early.
b. Check for unposted invoices. Go to Accounting > Batch/Export Transactions. Invoices that have not been posted will not generate journal entries and will not appear in your accounting software.
c. Confirm that completed jobs have been invoiced. Use a Jobs report (Reports > All Reports > search "Jobs") filtered for completed jobs without invoices to find gaps.
d. Check for export errors at Accounting > GL Errors. Records that failed to sync will show "Error" status even if the batch shows "Exported."
a. Run the Trial Balance in your accounting software for the same period. Verify that total debits equal total credits — a mismatch here confirms the imbalance source.
b. Review recent journal entries in your accounting software. Look for one-sided entries or entries with mismatched debit and credit amounts.
c. In ServiceTitan, go to Accounting > Journal Entries to review journal entries created during the period. Check for GL errors at Accounting > GL Errors.
d. Check for pending adjustments or voided transactions that may not have been fully reversed. Correct any errors, then re-run the balance sheet to confirm it balances.
a. If the invoice has been exported, it is permanently locked in ServiceTitan. You cannot unpost or edit it.
b. Create an adjustment invoice (credit memo) in ServiceTitan to reverse the financial impact. This creates a new invoice record with reversing GL entries while preserving the original audit trail.
c. If the accounting period is already closed, only adjustment invoices are allowed — unposting is blocked.