How to Set Up Expense Reimbursement for New Hires with an AI Company Brain

Do not call a new hire expense-ready because the company brain found the right policy. We recommend a finance-owned readiness record with separate checks for policy, profile, payout destination, card and a test claim, and one rule for the hire: pay for nothing real until a small test expense has been reimbursed. The assistant explains the current rules and shows safe status. Finance systems take the receipts, card data and bank details. Without that split, the assistant can say "ready" while the hire has no profile, no payout route or a card that declines. GitLab's expense handbook shows how the right answer varies: most of its entities reimburse within seven business days, but France and Finland expenses must be submitted by the 6th of the month to reach that month's payroll.
The same question has different answers by entity
GitLab's expense handbook shows how far a correct-sounding answer can drift from the right one. Beyond the entity deadlines above, which also require approval by the 6th if an expense is out of policy, in the Netherlands, home internet costs go through a payroll form, and the same claim in the expense tool is rejected. Payment cannot complete until the hire's bank account is set up in the tool. A policy answer that ignores the employing entity is wrong for part of any multi-entity company, and one that ignores the missing bank account is right but useless.
Track these separately, never as one checkbox called "expense setup complete." GitLab's onboarding handbook shows what a single tick hides: a ticked box in its onboarding issue means either that the task was completed or that it does not apply to that person. A card that is not required and a card that was never issued look the same under one tick, so record card_requirement: not-required explicitly.
What the assistant may hold
The knowledge layer may contain approved expense rules, category definitions, deadlines, support routes and explanations of each state, and every answer should cite a current source with an owner and the population it applies to. Receipts, bank details, card numbers, transactions, report contents and tax treatment stay in the finance systems and out of general search. The onboarding plan sees only a status such as policy-assigned, profile-active, card-not-required, test-report-rejected or reimbursement-verified, plus the owner and the next action. NIST's Privacy Framework page links a repository of implementation resources, and the framework itself is voluntary, so treat what you find there as questions and not as a rule book. For each field, before you connect the systems, ask who needs it, where it goes, who can read it and how long it stays.
One record with states you can test
A state machine keeps a downstream success from hiding an upstream failure, and it gives the assistant an honest answer when a source is unavailable.
employee_id: emp-4821
workflow: expense-readiness
entity: us-parent
worker_type: employee
policy_version: expense-us-2026-07
policy_state: acknowledged
expense_profile: active
reimbursement_destination: verified-by-finance-system
card_requirement: required
card_state: active
spending_controls: accepted
training_state: complete
test_report: approved
payment_verification: confirmed
workflow_state: ready
last_authoritative_check: 2026-08-27T11:15:00Z
restricted_finance_data_present: falseOnly an orchestration service writes this record. The company brain never assembles it from task labels in chat or from elapsed time. Use explicit terminal states: blocked-policy when no applicable policy can be selected, blocked-profile when the finance system rejects or cannot find the employee, blocked-card when a required card is not usable, test-required when setup exists but has not been exercised, exception-open when finance must repair a rejected state, unavailable when the source cannot be checked, and ready only when every required control and the test path pass.
The sequence, system by system
Start from the identity record. Microsoft's lifecycle workflows define a joiner as someone who enters the scope of needing access, and they can fire from user attributes. Start expense setup the same way, not from a recruiter message or a manager's copied checklist. Pass only what selecting the workflow needs: employee identifier, employing entity, country, worker type, manager, cost center, start date and card requirement. Assign an owner for missing or contradictory values, never the model, and make the handler idempotent so a corrected start date updates the same workflow.
Resolve one policy version. A deterministic resolver matches the hire's attributes against approved scope rules and returns one policy identifier, version, owner and effective date. Two matches go to finance, no match returns blocked-policy, and the assistant never picks the rule that sounds closest. Record acknowledgment only when the approved system receives it, because a chat reply of "Got it" is not evidence.
Wait for the expense platform to accept the profile. A successful API call proves delivery, not activation. If the platform rejects the hire for a missing cost center, the assistant shows blocked-profile, names People Operations as the owner and links the support route. It does not ask the hire to choose a cost center. Bank details go straight into the finance or payroll interface, and the company brain only reports whether verification is pending.
Issue a card only when the policy requires one. Stripe Issuing's card documentation covers virtual and physical cards, spending controls such as limits, merchant category restrictions and geographic controls, and simulated test purchases before going live. Those ideas carry over to any issuer. Test both directions: a card that authorizes everything is not ready, and neither is one that declines a permitted category.
Teach substantiation in the real tool, and let the hire practice in the same system that holds real reports. For US employers, IRS Publication 15 says an accountable plan requires employees to substantiate expenses within a reasonable period and return any excess, and it generally treats 60 days after the expense as reasonable. Amounts that miss those rules are treated as wages. Use synthetic evidence or a finance-approved low-risk purchase for the test, never a fabricated receipt that could enter the accounting record as a real transaction, and label the test data so it can be removed.
Verify approval and payment as separate events, because a report can be submitted, approved, exported, paid and received. For the test, require the platform to accept the report, the right approver to act, finance to accept the accounting state, and the hire to confirm that the money arrived. If sending money is not appropriate for a test, finance defines an equivalent check that exercises every integration up to the transfer and validates the destination separately. The company brain says ready only after that rule passes.
Run the test before the first big claim
We recommend making a small test claim, reimbursed to the hire's real account, the gate for any real spending. In GitLab's handbook, new hires get a home-office stipend of 1,500 USD or the local equivalent for their first year. They buy the items with their own money and claim them afterwards, so a broken payout route fails on a claim big enough to hurt. Until the test lands, route early spending through the company: travel booked centrally, or purchases made by finance.
Settle pre-start spending before day one
The first rule for an accountable plan in IRS Publication 15 is that the expense was paid or incurred while performing services as your employee. A monitor bought the week before the start date does not clearly meet it. We recommend that US employers ask their payroll or tax adviser how such claims must be treated, write the answer into the policy the assistant cites, and say it in the offer packet. Otherwise the assistant will tell an eager hire to keep the receipts, and finance will learn about the problem when the claim arrives.
If the money path fails
- If attributes conflict, freeze policy selection and route the issue to People Operations and finance. A newer timestamp is not proof that one source is right.
- If the expense platform is down, return
unavailablewith the last successful check time and a staffed finance contact. Cached readiness is not current readiness. - If a profile request times out, retry with the same idempotency key and reconcile against the finance system before sending another create request.
- If a card shipment or activation fails, keep the hire on the approved fallback route. A suggestion to use a personal card may break policy or cause real hardship.
- If the test report is rejected, keep the reason code in the finance system, show a safe correction instruction and an owner, and do not mark training complete while the test is broken.
- If the entity, manager, role or cost center changes before the start date, rerun policy and approval resolution and update or revoke the old card controls and profile assignments instead of layering new access over old.
- If private finance data reaches chat, stop indexing where possible, restrict the conversation and route cleanup through the incident process. Do not copy the content into a second ticket.
Release rule
Use synthetic employees for every supported entity and worker type, and run both successful and failed routes. Exactly one policy must be selected per supported employee, ambiguous attributes must block, duplicate joiner events must create no duplicate profiles or cards, receipts and bank details must never reach search or analytics, and the finance system, not a checklist, must confirm activation. Cards must allow the approved test and deny a prohibited one, rejected reports must show a safe next action, and a source outage must produce unavailable. Only the end-to-end test may produce ready.
Kipwise's employee onboarding solution provides product context for assigned reading, searchable company guidance, and onboarding progress. Use those capabilities for current policy and safe orchestration status. Keep receipt evidence, card data, account details, approval records, and payment execution in their authoritative systems.
Before you widen the scope past one employing entity, one worker type, one expense platform and one card rule, run a synthetic joiner through a duplicate event, a missing cost center, a card-control failure, a rejected report, a source outage and the successful route. Release the workflow when the hire can find the right rule, submit evidence privately, repair an exception and prove the reimbursement path works.



