How to Map Reimbursement Expenses to the General Ledger

Mapping reimbursement expenses to the general ledger means translating supported employee-paid purchases into the accounts and reporting dimensions used in the organization’s books. The mapping should describe the nature of the purchase, not merely the employee, payment date, or reimbursement batch. A reimbursement payment settles an obligation; it is not a substitute for coding the underlying expense. Exact accounts and dimensions depend on the organization’s chart of accounts, reporting needs, accounting policy, and accountant review.

Define the mapping inputs and decisions

Before assigning an account, identify the item or service purchased, business purpose, date, supporting evidence, and relevant team, project, location, or entity. Set out which field controls each decision. For example, a chart-of-accounts rule may determine the natural expense account, while an approved project reference determines a project dimension. Do not infer a project or department from a cardholder’s current job title when the record supports a different beneficiary.

Create examples for ambiguous categories

Build a short mapping table for common purchase types with the required evidence, default account, applicable dimensions, and escalation owner. Explain boundary cases: a software subscription versus a one-time service, training versus travel, or one receipt containing different types of goods. A merchant name alone may be inconclusive because sellers offer many products. When documentation cannot establish the nature or allocation, return the item for clarification or ask accounting to decide; do not choose a convenient account simply to complete the workflow.

Worked example: one receipt, two expense types

An employee submits a $240 receipt from a general office retailer: $180 of printer supplies and $60 for a desk lamp used by a new team member. The receipt and purpose support the items, but the company’s mapping guide assigns supplies and small equipment to different accounts, with team as a separate dimension. The reviewer splits the record only if the organization’s process allows item-level allocation, preserves the $240 total and source receipt, and applies the supported team dimension. If the receipt only says “miscellaneous items” and the employee cannot explain the purchase, the reviewer requests clarification rather than assigning the entire amount to supplies by merchant name.

Check the posting and settlement path

• Confirm the proposed natural account against the documented purchase and approved mapping.
• Validate required dimensions against evidence and current organizational coding rules.
• Check that split allocations sum to the source amount and preserve the receipt reference.
• Separate the expense posting and employee payable from the later reimbursement payment that clears the payable.
• Route exceptions, restricted account choices, and unusual classifications to the designated accountant.

Govern changes and correct errors transparently

Assign an owner to approve mapping changes, record the effective date, and communicate new examples to submitters and reviewers. Periodically inspect uncategorized items, frequent overrides, and coding corrections for gaps in the guide. If a posted expense was mapped incorrectly, retain the original entry and follow the organization’s adjustment process with a reason and link to supporting evidence. A code suggestion is not proof of the item’s nature, policy eligibility, tax treatment, or proper accounting period; those conclusions require evidence and appropriate review.