Getting Started
First Time Setup
Getting Started With Jobs
Getting Started with Ticketing
Setting Sonar up for Billing
Getting Started with Accounts
Getting Started with Inventory
Baseline Configuration
User Specific Resources
Accounts
Account Types: Overview & Example Use Cases
Account Statuses: Overview & Example Use Cases
Account Management View: Overview
Scheduled Events: Overview & Use Cases
Notes & Tasks: Best Practices & Use Cases
Child Accounts: Best Practices & How Tos
Disconnecting an Account
Account List View: Overview
Lead Intake Form Processing
Account Groups: Overview & Example Use Cases
Serviceable Addresses: Overview and Usage
Creating a New Account
Billing
Setting up Bank Account & Credit Card Processors
Billing Settings
Billing Defaults
Taxes Setup
General Ledger Codes: Overview
Services: Overview
Building a Data Service
Building Packages
Delinquency Billing Best Practices
Accounts in Vacation Mode
Batch Payments & Deposit Slips: Overview
Creating Discounts for Services and Packages
Setting Up Payment Methods and Taking Payments
Canadian ACH tool
Printed Invoice Batches: Overview
Delinquency Exclusions: Overview and Use Cases
Multi-Month Billing & Multi-Month Services
How to Take Bank Account Payments
Email Invoice Batch: Overview
Manual Transactions
ACH Batching: Overview
Billing Calculator
Proration Calculator
Usage Based Billing Policies: Overview and Usage
How to: Adding a Service to an Account
Usage Based Billing Policy Free Periods: Overview and Usage
Communication
Setting up an Outbound Email Domain
Triggered Emails: Setup
Call Logs: General Best Practices
Using the Mass Email Tool
Email Messages: Example Content
Email Categories: Overview & Use Cases
Email Variables & Conditions
Trigger Explanations
Companies
Financial
Contract Templates
Invoice Attachment Use Cases & PDF Examples
Invoice Messages: Overview & Use Cases
FCC Form 477: General Overview and Usage
Invoices in Sonar: Examples, Creation & Contents
Integrations
Inventory
Setup of Inventory: Manufacturers, Categories, and Assignees
Inventory List View: Overview
Inventory Model Management: General Overview
Tracking and Using Consumable Inventory
Jobs
Job Types: Best Practices
Setting Up Schedules General Overview
Applying Task Templates to Jobs
Example Jobs & Templates
Scheduling How-to: Creating and Booking a Job
Geofences: Overview
Jobs and Scheduling: Overview
Mapping
Misc.
Monitoring
Building a Monitoring Template
Pollers: General Overview, Deployment Strategy, Build Out & Setup
Building Alerting Rotations
Networking
IP Assignments & Sonar
MikroTik: Setting Up a Sonar Controlled DHCP Server
Setting Up a DHCP Batcher
IPAM: Basic Setup
MikroTik as an Inline Device: Integration With Sonar
MikroTik: Controlling Speeds
MikroTik: Controlling Access
Setting Up CoA Proxy
RADIUS: Building Reply Attributes
Data Usage Available Methods
Pulse, Polling, and PHP
MikroTik: Creating a Self-signed Certificate for use in API-SSL
IPAM: Overview
LTE Integration
Sonar Flow
RADIUS: Build-Out & Integration with Sonar
Network Dashboard: Overview
Being Cloud Native
Building a Device Mapper
Sonar IP Addressing
Automating IP Assignments, Data Rates, and Network Access in Sonar
Network Sites: Management View Overview
Building RADIUS Groups
Building Address Lists
Finding your OIDs
Security
User Role Creation & Best Practices
Removing a Terminated Employee In Sonar
Password Policy In Depth
Application Firewall: General Overview and Best Practices
Users: Overview
Role Creation using GraphiQL
System
How to Best Use Global Search
How Your Data is Backed Up
How To Use GraphiQL to Understand the Sonar API
Frequently Used Terms
Sonar's Rich Text Editor
Mutations in the Sonar API
Notification Preferences
API Calls Using Third Party Applications - Personal Access Tokens
The New Sonar API
A Deeper Dive into the New Sonar API
Consuming the Sonar API
Filtering: Simple vs Advanced
API Wrappers for V1 Compatibility
My Info: Your Personal User Settings
Customizing your Customer Portal
Release Notes
Reporting
Ticketing
Ticketing: Overview
Canned Replies Examples & Templates
Canned Reply Categories
Inbound Mailboxes Example Build
Ticket Categories Best Practices & Example Build
Ticket Groups To Consider
Using Parent Tickets
How to Integrate Inbound Mailboxes with Slack
Advanced Ticketing Features
Accounting with Sonar
Working With the Sonar Team & Additional Resources
Table of Contents
- All Categories
- Billing
- Taxes Setup
Taxes Setup
Updated
by Mitchell Paul-Soumis
Read Time: 2 mins
Tax Creation in Sonar
Tax creation requires 4 fields be filled out: Name, Application, Rate, and Type.
- The name section is what appears on the invoice and on the account
- The application indicates whether it should be a flat rate, or a percentage of the sum which is applied as taxes,
- The rate is the amount (so 5 would be either 5 dollars or 5 percent depending on the application selection) and finally
- The type picker allows you to set if it's global to every customer, or dependent on a certain geographical zone.

Once created, a Global Tax is done here - it's applied to all customer accounts in your instance. Geographical taxes will require additional configuration.
Geographical Taxes Extra configuration
When you create a Geographical Tax in Sonar, you then need to configure a Geo Tax Zone

Configuring a Geo Tax Zone will only tax the residents of that zone, and configuring the actual zone itself is very flexible. The only mandatory fields are the Name and the Rate.
Multiple Service Zone configuration
While Sonar does support integration with Avalara for automated taxation, the software is designed to be robust enough to enable you to create multiple layers of taxation that appear on a line-by-line basis during transactions.
When you provide service to customers in multiple cities, counties, or states, you will need to ensure you have all the layers built. Rate-building occurs on a size basis, starting from the broadest service area to the smallest. As you can see below, the taxes were built in the following order:
- State Tax
- County Tax
- City Tax

The way this system works together allows you to nest multiple Geo Tax Zones within one layer, such as in the case of distinct cities within Colorado:

By nesting these cities under a single Geographical Tax, you minimize not only the number of items, but the number of taxes applied to a service.

Finally, with the taxes configured in this nested manner you and your customers will be able to see all taxes leveraged against the service as it's charged and invoiced.
On the customer's transactions:

Statement Example: