Best Practice: Account Codes & Accounting Integration
An account-code mistake is the quietest kind of error MSP Pulse can produce. A wrong price is obvious the moment someone looks at an invoice. A wrong account code isn't. The invoice looks completely normal to the client, the payment comes in, and the only place the mistake shows up is in your accountant's ledger or your own P&L, usually weeks later, usually discovered by someone other than whoever set it up.
This guide covers how to set up MSP Pulse's categories and account mappings so they land on the right accounts in your books, and what genuinely differs between QuickBooks Online and Xero. The two platforms are not interchangeable here, and treating them as though they were is where most of the trouble starts.
1. Know how a line finds its account
Every invoice line records the account it is booked to at the moment the line is created, the same way a rate is frozen when time is logged. MSP Pulse knows what each line is for, because the line carries the labour role or catalogue item it came from, and it picks the account in this order:
- A labour role's account. Each labour role can have its own account, set on the role in Settings → Labour Roles.
- A catalogue item's account. The item's own account wins; otherwise its sub-category's account; otherwise its category's account.
- Your default sales account, set in Settings → Accounting, if nothing above produced an account.
A line with no product behind it, such as a typed credit-note line, an expense, a managed-service fee or a deposit credit, goes to the default sales account. On a draft invoice you can change a line's account yourself.
Everything in this guide follows from that. The account is fixed when the invoice is created, which is why a mapping change doesn't rewrite invoices you've already made, and why the default sales account matters so much (see Section 5).
An account is something you choose from the list MSP Pulse synced from your accounting platform, not something you type. That list is the source of truth, so if the account you want isn't in the dropdown, sync first (Settings → Accounting) rather than looking for a way to enter it by hand.
2. Design the category structure around your real chart of accounts
Catalogue items sit in a two-level structure: a Category, and an optional Sub-category beneath it. Either level can carry an account, and an item can override both. That gives you a sensible default at the top and exceptions underneath.
The sensible approach is to give each Category the account that most of its items belong in, and only set a Sub-category or item account where something genuinely posts elsewhere. Setting an account on every item is the quickest way to end up with a hundred mappings nobody reviews.
Which platform you've connected changes how this plays out:
QuickBooks Online supports parent and sub-accounts. You can organise your income accounts that way in QuickBooks. MSP Pulse doesn't read that nesting, though. It syncs your income accounts as a flat list and you map Categories and Sub-categories to whichever accounts you choose from it. A two-level structure in MSP Pulse and a parent/sub-account structure in QuickBooks can mirror each other, but nothing enforces or checks that they do.
Xero has no sub-accounts by design. Its chart of accounts is a single flat list, and Xero's own approach to grouping and multi-dimensional reporting is tracking categories (up to two, each with a limited number of options). MSP Pulse does not send tracking categories with a push, so anything you want tracked that way has to be applied in Xero after the invoice arrives. In practice: map your top-level Categories to distinct Xero account codes, and don't invent extra account codes just to represent sub-categories. That's the chart-of-accounts bloat Xero's model exists to avoid.
Decide which platform you're mapping to before you design the structure, not after.
3. Choose accounts that mean something in the real ledger
Use your accountant's chart, not your own. The accounts you can pick are the ones synced from your platform, so the numbering is already theirs. The risk is in the choosing: pick the account whose meaning matches the category, not the nearest-sounding one.
Keep category names and account names recognisably aligned. If a Category is "Managed Services", the account it resolves to should be recognisably the same thing in the P&L. A bookkeeper reconciling the two should never have to guess which MSP Pulse category feeds which ledger line.
Remember the sync is income accounts only. MSP Pulse pulls revenue-side accounts (Xero's Revenue class, QuickBooks' Revenue classification). Expense and cost-of-sales accounts are never offered, so MSP Pulse's mapping can't be used to control COGS or expense coding. That limitation is deliberate: it only ever exports sales invoices and credit notes.
4. How the push differs between Xero and QuickBooks
Both connections are live, and what reaches your books looks different on each side.
| QuickBooks Online | Xero | |
|---|---|---|
| What a line is posted against | An Item, found by the line's description or created if there isn't one | An account code, sent directly on the line |
| Where the account comes from | Set on the Item when it's first created; an existing Item keeps its own income account | Resolved fresh from MSP Pulse on every push |
| Client matching | Customer found by name, or created | Contact matched by name |
| Chart of accounts | Parent and sub-accounts supported (MSP Pulse syncs a flat income list) | Flat, no sub-accounts |
| Tax | Tax code matched by the tax rate's name | Tax type set on the tax rate (Settings → Tax Rates) |
| Documents | Invoices and credit memos | Invoices (authorised) and credit notes |
Two consequences matter more than the rest of the table.
On QuickBooks, a line posts against an Item named after the line description, and the Item's income account is fixed when the Item is created. If an Item with that name already exists in QuickBooks, MSP Pulse uses it as it is. Changing a Category's account in MSP Pulse therefore does not move future invoices for descriptions that already have a QuickBooks Item. To change where they post, change the Item's income account in QuickBooks. A description MSP Pulse hasn't pushed before creates a new Item using the current mapping.
On Xero, the code travels with every push, so a mapping change takes effect on the next push. Xero also upserts invoices by number, so MSP Pulse checks for an existing invoice number first and skips it rather than overwrite one.
If QuickBooks has account numbers turned off, which is the default for many companies, MSP Pulse can't match accounts by number and falls back to your default income account. Turn account numbers on, or check what the default account is, before relying on per-category mapping there.
5. Set a default sales account, and treat reaching it as a warning
Xero won't accept an authorised invoice line without an account code, and QuickBooks needs an income account for every Item it creates. The default sales account (Settings → Accounting) is what a line falls back to when nothing more specific matched. Without one, a Xero line goes without a code and a QuickBooks push fails with a clear error rather than posting somewhere unexpected.
That fallback is a safety net, not a plan. A line landing on the default usually means the product or role behind it has no account set at any level (item, sub-category or category), or the line has no product behind it. When you spot-check a pushed invoice (Section 7), look specifically for lines that landed on the default account.
6. Tax is a separate decision from the account
An account says what kind of income a line is. It says nothing about how it's taxed. Each is its own setting, and getting the account right doesn't carry the tax treatment with it.
MSP Pulse applies tax per line, using the tax rate on the line. A tenant flagged as not VAT-registered charges and shows no VAT at all. On a push, each tax rate needs a counterpart on the other side. In Xero that's the Tax type on the rate (a field that appears in Settings → Tax Rates only when the accounting integration is on and Xero is the platform). In QuickBooks it's a tax code with the same name as the rate, so a rate called "Standard 23%" needs a QuickBooks tax code with that exact name.
If a client or product has an unusual tax position, such as reverse charge, a different jurisdiction or an exempt service, that's a tax-rate decision. Don't try to solve it by picking a different account; it won't fix the tax and it will miscode the ledger.
7. Changing a mapping, and what it does to existing invoices
Because each line's account is fixed when the invoice is created, a mapping change only affects invoices created after it. Invoices you already made, drafts included, keep the account they were created with, and nothing already in your accounting platform changes.
- Already pushed: unchanged. A bulk recode of history is a ledger-side job, done in Xero or QuickBooks directly or by your accountant.
- Created but not yet pushed: keeps its old account. If one is wrong, change the account on the draft line, or void and recreate the invoice, before you push.
- New invoices: pick up the new mapping, so make the change before you generate the next batch, not after.
- Renames are harmless. A line follows the product or role it came from, not its name, so renaming a catalogue item or labour role no longer changes where its lines post. (Invoices created before this behaviour was introduced still match by name; the Products guide covers keeping names tidy.)
MSP Pulse keeps no history of mapping changes, so note the date and reason somewhere your future self or your accountant can find it when you change a mapping that's been in active use.
8. Keep the connection healthy, not just set up once
Push is something you do, not something that happens. Invoicing → push sends the sent and paid invoices you select; drafts and voided invoices never go. An invoice you forget to push is simply missing from your books, and the gap compounds quietly. Make pushing a routine, not an occasional clean-up.
Use the reconciliation check. On each client's Statement tab, the "Reconcile with accounting package" card compares MSP Pulse's balances for invoices already pushed against the balances in Xero or QuickBooks and lists any differences, plus invoices not yet pushed. It's the quickest way to find out that something didn't land the way you expected.
Spot-check coded lines, not just totals. Pick a handful of recent invoices and confirm each line landed on the account you expected, paying particular attention to anything on the default account.
Review mappings when your accountant changes the chart. If they retire or restructure an account you're mapped to, nothing in MSP Pulse will tell you. Re-sync after any change and re-check the Categories that pointed at it.
The shape of the chart itself is your accountant's call. Structuring MSP Pulse's categories to match is your job. Deciding what the chart of accounts should look like belongs to whoever is responsible for your books.
Pre-flight checklist for account codes and accounting integration
- [ ] Confirmed which platform is connected before designing the category structure
- [ ] Chart of accounts synced recently, and the accounts you need appear in the dropdown
- [ ] Each Category has a sensible default account; Sub-category and item overrides only where something genuinely posts elsewhere
- [ ] Labour roles have the right income account set
- [ ] On Xero: top-level Categories map to distinct flat account codes, and any tracking is applied in Xero
- [ ] A default sales account is set
- [ ] Category names recognisably match the account names they resolve to
- [ ] Aware the sync offers income accounts only
- [ ] On QuickBooks: account numbers are on, and you know existing Items keep their own income account
- [ ] Every tax rate has its counterpart (Xero tax type, or a same-named QuickBooks tax code)
- [ ] After changing a mapping, new invoices were checked, and any wrong draft lines were corrected before pushing
- [ ] Mapping changes are made before the next push, and dated somewhere
- [ ] Pushing is routine, and the reconciliation card is checked periodically