Thred
All posts

One agent, many ledgers: mapping accounts, VAT codes and journals across Exact Online, Xero and Moneybird

The same invoice lands differently in Exact Online, Xero and Moneybird. How an agent can book correctly in all three: one model of the booking, translated per administration.

Manoj Tutika7 min read

Working on this yourself? Talk to Mark, our co-founder. We’re here to solve it with you.

Book a demo
On this page

One agent can book correctly across Exact Online, Xero and Moneybird if it decides what a booking means once, in its own terms, and only translates that decision into each ledger's accounts, VAT codes and journals at the very last step. The decision is shared. The translation belongs to each client administration.

This post is for accounting firm partners and managers whose client portfolio is spread over several ledgers, and for controllers in groups where entities run on different software. If your team switches between three systems a day, you already know the problem: the bookkeeping is the same, the buttons and codes are not.

Why does the same invoice look different in three ledgers?

Take one ordinary purchase invoice. A software supplier bills a client €1,000.00 plus €210.00 BTW at 21%, so €1,210.00 in total. Every bookkeeper agrees on what should happen: €1,000.00 to a software or IT costs account, €210.00 to input VAT you can reclaim, €1,210.00 owed to the supplier.

Now book it for three clients.

  • In Exact Online, it becomes a purchase entry in a purchase journal, on a G/L account with that administration's own code, with a VAT code that administration defined itself.
  • In Xero, it becomes a bill (the API calls it an invoice of type ACCPAY), with a line that carries an AccountCode and a TaxType.
  • In Moneybird, it becomes a purchase invoice whose detail rows carry a ledger_account_id and a tax_rate_id.

The accounting is identical. Almost every identifier is different, and none of them can be guessed from the others. Account 4610 in one client's Exact administration and account 463 in another client's Xero organisation might both mean "software", or might not.

What actually changes from one ledger to the next?

Everything below comes from the public API documentation of each ledger. We describe how each one models the parts that matter for booking, because that is what any agent, or any integration, has to respect.

The administration itself

Each ledger scopes data to one company, and each does it differently. Exact Online puts a division number in every request path. Xero identifies the organisation with a tenant header on every call. Moneybird puts an administration_id in the path, and its administration record carries the country, the currency and a period_locked_until date.

For a firm this is the first rule: every map an agent uses belongs to one administration. A mapping learned for one client is never reused for another, even when both run on the same software.

The chart of accounts

All three let you read the chart of accounts, but they classify accounts in different vocabularies.

  • Exact Online's GLAccounts have a unique Code, a Description, a BalanceType (B for balance sheet, W for profit and loss), a BalanceSide (debit or credit) and a numeric Type, such as 22 for accounts payable, 24 for VAT, 27 for accrued expenses and 110 for revenue. An account can be blocked for new entries.
  • Xero's Accounts have a Code of up to 10 alphanumeric characters, a Type from a fixed list (EXPENSE, OVERHEADS, DIRECTCOSTS, CURRLIAB and others), a status that can be ACTIVE or ARCHIVED, and a default TaxType.
  • Moneybird's ledger_accounts have an account_type such as expenses, direct_costs, revenue or current_liabilities, an active flag, and a list of document types they may be used on. A new ledger account created through the API must be linked to a code from RGS, the Dutch reference chart of accounts (Referentie Grootboekschema).

So the agent should never map "by number". It maps by meaning. Internally it decides that this cost is software and IT, an operating expense; then, per administration, it looks up which account carries that meaning, using the account names, the types above and, most of all, how this client's own history was booked. An RGS code, where present, is a helpful extra signal.

VAT codes

VAT is where mapping goes wrong most often, because the same treatment is spelled very differently.

  • In Exact Online, VAT codes are defined per administration. Each has a Type (E for excluding, I for including, N for no VAT, B for 0% base only), percentages with start and end dates, the G/L accounts for VAT to claim and VAT to pay, a flag for whether it may be used on purchases, sales or both, and a setting for how it appears on the EU sales listing (the ICP return). A Charged flag marks transactions such as reverse charge, where Exact creates both a VAT-to-pay and a VAT-to-claim line.
  • In Xero, each line carries a TaxType string chosen from the organisation's tax rates, and a tax rate is built from one or more tax components. Manual journals and invoices also declare whether line amounts are tax exclusive (the default), tax inclusive or without tax.
  • In Moneybird, tax rates are listed per administration and typed by document: a "21% btw" for sales invoices is a different record from the "21% btw" for purchase invoices. The public API documents a list endpoint for tax rates, so an agent picks from what the administration already has rather than creating new ones.

The rule that follows is simple. Decide the VAT treatment first (domestic purchase at the standard rate, EU services with reverse charge, exempt, outside scope), and choose the code second. A code that looks right by its percentage can still be wrong in direction, in date or in how it reports. Check unusual cases with the client's accountant or tax adviser.

Journals and the shape of an entry

The last difference is in how a manual entry is written. Take a month-end accrual of €2,500.00 for consultancy received in June but not yet invoiced: debit consultancy costs, credit accrued expenses.

  • Exact Online uses typed journals: cash, bank, payment service, sales, purchase and their return variants, and general journals. Entries through the general journal endpoint are of type "Other" and need a journal code; a VAT code on a line only works if that general journal has VAT enabled. The financial year and period must exist in the administration. A Reversal flag lets you write a correction with negative amounts on the same side as the original.
  • Xero's manual journals require a Narration, and each journal line has a LineAmount where debits are positive and credits negative. A journal can be saved as DRAFT or POSTED.
  • Moneybird's general journal documents have separate debit and credit fields per entry row, each pointing at a ledger_account_id.

Signed amounts in one system, debit and credit columns in another. A translation layer that flips a sign once in a while is exactly the kind of bug that produces a balanced but wrong ledger.

How should the mapping be built?

We think about it in three layers.

  1. A booking decision in plain accounting terms. Which economic event, which account meaning, which VAT treatment, which amounts on which side, in whole cents, with the source document attached. This is where the judgement happens, and it is the same for every ledger.
  2. A map per administration. Account meanings to account identifiers, VAT treatments to VAT codes or tax types, entry types to journals. Built from the client's own chart and history, kept up to date as the client adds accounts, and visible to the people who review it.
  3. Validation in the target ledger's own rules, before writing. The checks below run against live data from that administration, every time.

The validation step is where most of the safety comes from.

  • The entry balances in the ledger's own representation, after any sign or column conversion.
  • The period is open. In Moneybird, the date is after period_locked_until. In Exact Online, the financial year and period exist.
  • Every account is usable: not blocked in Exact Online, not archived in Xero, active in Moneybird, and allowed for this kind of document.
  • The VAT code is valid for the direction (purchase or sales), for the date, and for the journal it is used in.
  • Amounts and VAT add up to the source document, to the cent.

If any check fails, the agent does not improvise. It asks a person a specific question, such as which account this client uses for a new kind of cost, and adds the answer to the map so the question is not asked twice.

Where does a person still decide?

Mapping is mechanical once the meaning is clear. Deciding the meaning is not always. A client's first purchase from a supplier in another EU country, an invoice that mixes goods and services, a cost that could be capitalised: these are judgement calls, and the right place for them is with the accountant who knows the client. A good agent makes those cases rare and fast, by turning them into one clear question with the evidence attached.

How Thred works across ledgers

Thred Layer runs finance agents on top of the accounting software a business already uses, including Exact Online, Xero and Moneybird. Thred keeps a full copy of the ledger in sync, the agents do the work in Thred, and finished entries are pushed back, so the accountant keeps working where they always have. You set the rules, approve the work and handle the exceptions, and your rules and policies are stored so the agents apply them as they work.

For firms, that means one layer across all your clients' administrations: your team reviews instead of keying in, and clients keep the software they know.

Want to see one agent booking across your client portfolio? Book a demo.

Frequently asked questions

Can you reuse one account mapping for all clients on the same ledger?

No. Account codes and VAT codes are defined per administration, so code 4610 can mean software for one client and something else for another. Keep a separate map per client, built from that client's own chart and booking history.

How do VAT codes differ between Exact Online, Xero and Moneybird?

Exact Online VAT codes are defined per administration with a type, dated percentages and the accounts for VAT to claim and to pay. Xero lines carry a tax type from the organisation's tax rates. Moneybird lists tax rates per administration, separately for sales invoices, purchase invoices and journal entries.

What is RGS and why does it matter in Moneybird?

RGS (Referentie Grootboekschema) is the Dutch reference chart of accounts. Moneybird links ledger accounts to RGS codes, and its API requires an RGS code when you create a new ledger account, which gives a standard meaning you can map against.

How are debits and credits sent in a manual journal?

It depends on the ledger. Xero manual journal lines use one amount where debits are positive and credits negative. Moneybird general journal documents use separate debit and credit fields. A translation layer must convert carefully and check the balance after converting.

What should be checked before an agent writes an entry into a client's ledger?

That the entry balances in the ledger's own format, the period is open, every account is active and allowed, the VAT code fits the direction and date, and the totals match the source document to the cent. If a check fails, ask a person instead of guessing.

Sources

  1. Exact Online developer documentation
  2. Xero Accounting API, Manual Journals
  3. Moneybird API, ledger accounts
  4. Moneybird API, general journal documents
  5. Referentie Grootboekschema (RGS)

Read next

Where Thred comes in

Thred Layer

Finance agents running on top of your existing ledger. You set the rules, approve the work and handle the exceptions. No migration.

Keep reading

Finance, handled.

Book a demo, or request a callback and we will call you.

Book a demo