ANTE User Manual

Multibook

Once your company is connected to Multibook, this page controls how ANTE behaves for that connection — starting with employee reimbursements. The connection itself (endpoint URL and API keys) stays on Cloud Credentials → Multibook; this page only appears once that connection exists.

Overview

This page is deliberately minimal — just what filing a claim into Multibook needs. It has one section, Employee reimbursement, which decides whether expense claims are filed and approved in ANTE (the default) or pushed straight into Multibook for its own approval, which Multibook document type new claims use, the one fallback Multibook expense type used when nothing else can decide a line, and (under its Departments subsection) the Multibook department sent on every claim.

Employees no longer pick a Multibook expense type or GL account when they file a claim — every line is coded automatically (by AI, by keyword matching, or by the fallback below), and an accountant reviews and can change the coding before the claim is approved. See Account coding in the Reimbursements guide. The AI guideline that teaches ANTE which account to suggest for a line is written on the account itself, under Treasury → Accounting → Chart of Accounts (Edit Account → AI guideline) — it no longer has a separate editor on this page.

More Multibook-driven settings will be added here over time as ANTE integrates further with Multibook.

Getting There

Go to Settings → Multibook.

This menu item only appears once an administrator has connected the company to Multibook under Settings → Cloud Credentials. If you go to the page directly before that, it shows a notice telling you to connect Multibook first.

Page Layout

Connection

A read-only summary of the company's Multibook connection:

FieldDescription
Multibook companyThe Multibook company code the connection posts into
TenantThe Multibook tenant the connection resolves to
Multibook environmentThe hostname of the Multibook environment
AccessRead and write if a write key is configured, otherwise Read only

If Multibook can't be reached to read these details, this card shows the reason instead. A note under the card reminds you that the endpoint and API keys themselves are managed on Settings → Cloud Credentials.

Employee reimbursement

FieldDescription
Filed and approved inANTE (default) or Multibook — see below
Expense document typeThe Multibook document type new claims are filed under. Required when set to Multibook
Fallback expense typeThe Multibook expense type used for a line only when no other coding rule can decide it — neither the AI reading the account guidelines nor keyword matching. Leave unset to allow a line to go uncoded when the other rungs fail

Filed and approved in decides which system runs the approval:

  • ANTE — claims stay in ANTE: the filer's supervisor approves them, and ANTE posts the accounting entries. Nothing is sent to Multibook automatically; an approved claim can still be sent by hand from the claim's Sync to Multibook action. The expense document type set here is only used for that hand sync.
  • Multibook — claims are sent to Multibook the moment an employee files them, and Multibook's own approval route decides them. Multibook posts the accounting entries, so ANTE posts none. Employees must link their own Multibook account (My Profile → Connections) before they can file, and an expense document type is required here so filing has somewhere to go.

Employees never choose the fallback expense type themselves — it only steps in behind the AI and keyword coding described below. See Reimbursements for how both modes look to the people filing and approving claims.

Departments

Every expense claim Multibook receives must carry a Multibook department. ANTE sends the same department, set here, on every claim — nobody picks a department by hand when filing a claim.

FieldDescription
Default departmentThe Multibook department sent on every pushed claim

If this is left unset, no department is sent, and Multibook may reject the claim asking for one.

📌 Pick an actual (leaf) department, not a grouping level. Multibook's department list mixes group headings with the real, postable departments underneath them — Multibook rejects a claim if a grouping level is chosen here.

This subsection only appears once ANTE can read your company's Multibook department list — the same catalog used for the document type and fallback expense type above.

Click Save changes to apply. If you switch to Multibook without choosing an expense document type, ANTE blocks the save and asks you to pick one first.

Common Tasks

Switching reimbursements to Multibook-approved

  1. Go to Settings → Multibook.
  2. Under Employee reimbursement, set Filed and approved in to Multibook.
  3. Choose the Expense document type claims should be filed under.
  4. Optionally set a Fallback expense type as a safety net for lines the AI and keyword matching can't resolve.
  5. Click Save changes.

Setting the fallback expense type

  1. Go to Settings → Multibook.
  2. Under Employee reimbursement, choose a Fallback expense type, or clear it to leave lines uncoded when nothing else resolves them.
  3. Click Save changes.

Setting the default Multibook department

  1. Go to Settings → Multibook.
  2. Under Employee reimbursement → Departments, choose a Default department — this is sent on every pushed claim.
  3. Always pick an actual (leaf) department, never a grouping level — Multibook rejects claims mapped to a grouping level.
  4. Click Save changes.

Writing an AI guideline for an expense account

  1. Go to Treasury → Accounting → Chart of Accounts.
  2. Open the account behind the Multibook expense type and choose Edit.
  3. In AI guideline — when to use this account, describe the kind of spend that belongs to this account (for example, "Taxi, train, and other transport fares employees pay out of pocket").
  4. Click Save.

The guideline is what ANTE's AI reads when it suggests an account for a new claim line, so the more specific it is, the better the AI's suggestions become. An accountant can still change any line's coding by hand — see Account coding.

💡 Note: These settings apply to your whole company. Only administrators should configure them.

← Previous
Cloud Credentials
Next →
Slack Integration