Skip to main content
GL mapping is the core of the accounting integration, and the part worth spending setup time on. You do it once, and Vori reuses it for every daily entry and every invoice after that. It works the same way whether you’re connected to QuickBooks Online, QuickBooks Desktop, or Xero. Vori pulls your chart of accounts directly from your accounting system and lets you map those accounts to your Vori data. You’re creating the relationship between what something is called in Vori and the account it belongs to in your books, so you never type an account number from memory.
The store, bookkeeper, or accountant knows these relationships. Vori’s job is to show them where to make each one. If you’re not sure where a line should map, ask whoever closes your books.
Vori refreshes your chart of accounts nightly, so new and renamed accounts are ready to map the next day. You can also refresh on demand from Integrations → Accounting Sync. Mappings are managed under Accounting → GL Code Mapping. There are three types to configure: general accounts, department accounts, and segments.

​
General accounts

Store-level items that don’t belong to any single department, grouped by type: These mappings feed the daily sales journal entry.

​
Department accounts

Every parent department in your store can be mapped to up to four account types: A few important notes:
  • All four are optional. A store that only wants revenue-level detail maps Sales. If you want live department margin tracking and perpetual inventory, map all four.
  • COGS and Inventory go together. Because they’re two sides of the same movement, Vori needs both mapped to post either one. Mapping both is what lets your accounting system show department margin without extra work at period end.
  • Multiple Vori departments can share one account. Many stores have departments that are more granular than their accounting structure. Map those Vori departments to the same account and their activity rolls up together.
Department accounts drive both the daily journal entry and the invoice bills, so purchases and sales settle against the same accounts.

​
Segments

If you run several stores out of one accounting company, Vori tags every line it posts with that store’s segment value, so you can filter reports by store. Assign these under Accounting → GL Code Mapping. What the segment is called depends on your system: A segment value must match one that already exists in your accounting system, or the line posts untagged. Single-store operators generally don’t need this.
If a store’s segment value matches nothing in your accounting system, the entry still posts, but that store’s lines are untagged. Vori flags the mismatch in GL Code Mapping so you can fix it.