A project manager submits a hotel receipt and a taxi receipt from a site visit. The company paid for the hotel on her corporate card. She paid for the taxi herself. Both are valid business expenses, but under a company-paid card program only the taxi belongs in her reimbursement. Reimburse the hotel too and the company has paid for one room twice.
Expense automation has to get three things right on every line: who paid, whether the charge is allowed, and which balance it clears.
Who paid decides who gets paid
Before a report is routed for approval, every line needs a payer. There are three common arrangements, and each produces different accounting.
| Arrangement | Who pays the vendor | Who the company owes | Typical entry when the report is approved |
|---|---|---|---|
| Company-paid corporate card | The card issuer, billed to the company | The issuer | Debit expense, credit corporate card liability |
| Employee-paid (individual-liability) card | The issuer, billed to the employee | The employee, for approved business charges | Debit expense, credit employee reimbursement payable |
| Out-of-pocket | The employee | The employee | Debit expense, credit employee reimbursement payable |
Check how your card program assigns payment responsibility rather than assuming. Oracle Fusion Expenses, for example, documents several corporate card payment options, including Individual Pay, where the employee pays the issuer (Oracle’s guide to implementing expenses). Verify the configured option for each card program before deciding who gets paid. A company that runs both arrangements, say company-paid cards for site managers and individual cards for sales, needs the payer set by card, not by default.
Capture what each line needs
Keep these on every expense line, not just the report header:
- Receipt image, as submitted
- Payer (company card, individual card, or employee)
- Transaction date and merchant
- Original amount and currency
- Business purpose and attendees where your policy requires them
- Job, project, department, or cost center
- Expense category, which drives the GL account
The job or department field matters more than it looks. For a construction or manufacturing business, a site visit’s hotel and mileage are often job cost. Coded to general travel, they understate the job and overstate overhead, and nobody notices until the job is closed out.
Write policy rules a system can enforce
A policy that lives in a PDF gets enforced inconsistently. Translate it into rules with a clear outcome: pass, flag for reviewer, or block.
| Rule type | Example rule | Outcome when broken |
|---|---|---|
| Receipt requirement | Receipt required above an amount you set | Flag; reviewer can approve a missing-receipt exception |
| Category limits | Nightly lodging cap by city tier; daily meal allowance | Flag the excess, not the whole line |
| Pre-approval | Airfare and conferences need a trip request first | Block until the request is linked |
| Allowable categories | Personal items, upgrades, fines not reimbursable | Block or require a personal split |
| Submission window | Report due within a set number of days of the transaction | Flag late items for manager review |
| Duplicate check | Same merchant, date, and amount already submitted or on a card line | Block pending review |
Set the thresholds to your own policy. If you need your plan to satisfy specific tax substantiation rules, confirm the requirements and thresholds with your tax advisor rather than borrowing numbers from another company’s policy.
Match receipts to the card feed
For card lines, the card feed is the transaction record and the receipt is the support. Match each receipt to a card line by merchant, date, and amount. Leave uncertain matches for a reviewer instead of forcing a pair: hotel folios often post a day after checkout, and restaurants add tips after authorization, so the receipt amount and the settled card amount can legitimately differ.
When a hotel folio includes a personal charge, show the business and personal portions as separate lines. Under a company-paid card, the personal portion becomes an amount the employee owes the company. How you recover it (offset against the next reimbursement, direct repayment, or another method) is a policy decision; if it would involve a payroll deduction, confirm the rules with counsel.
Route exceptions with a specific question
Reviewers approve faster when the system tells them what to look at. Instead of “please review,” send the question.
| Exception | What the reviewer checks |
|---|---|
| Receipt missing | Which expense lacks evidence, and who can approve the exception |
| Same receipt attached twice | Whether it already appears on a card line or a prior reimbursement |
| Expense in another currency | Original amount and currency, converted amount, rate used and its source |
| Expense split between jobs | Allocation basis and who approved it |
| Charge changed after approval | Which fields changed and whether the report goes back for review |
| Personal portion on a company card | Amount the employee owes and how it will be recovered |
| Late submission | Why it’s late and whether it belongs in a closed period |
Give employees the reason when a line comes back. If one line is unresolved, check whether your policy lets the remaining lines proceed; holding a whole report for one missing taxi receipt delays reimbursement and invites workarounds. Save the reviewer’s decision with the version that actually gets paid.
Illustrative example: one report, two balances
The project manager’s report contains:
- Hotel, company-paid card: $612.00, including a $48.00 personal minibar charge
- Taxi, paid out of pocket: $36.00
- Dinner abroad, paid out of pocket: €85.00, converted at 1.08 = $91.80
Card line entry:
| Debit | Credit |
|---|---|
| Lodging expense $564.00 | Corporate card liability $612.00 |
| Employee receivable $48.00 |
Check: $564.00 + $48.00 = $612.00.
Out-of-pocket entry:
| Debit | Credit |
|---|---|
| Ground transport $36.00 | Employee reimbursement payable $127.80 |
| Meals $91.80 |
Check: $36.00 + $91.80 = $127.80.
If policy is to offset the personal charge against the reimbursement: debit employee reimbursement payable $48.00, credit employee receivable $48.00. The net reimbursement paid is $127.80 − $48.00 = $79.80. The card liability is cleared separately when the company pays the issuer’s statement.
A reviewer who only saw “report total $739.80” ($612.00 + $36.00 + $91.80) would have no way to tell that the employee is owed $79.80. Show both numbers on the approval screen.
Reconcile both payment records at month-end
Two balances need to tie out every close.
Corporate card liability. Compare the issuer’s statement to the card charges posted from approved reports. The difference is usually charges not yet submitted or approved.
Illustrative: the statement shows $48,320. Approved reports have posted $44,910 to the card liability account. Unsubmitted card transactions total $3,410. Check: $44,910 + $3,410 = $48,320. Decide by policy whether to accrue the $3,410 to an estimated expense account at month-end or post it to a suspense account until reports arrive, and chase the cardholders either way. Unsubmitted charges that age past a couple of cycles are a control issue, not a timing issue.
Employee reimbursement payable. This should equal approved reports not yet paid. A balance that lingers after a reimbursement run means a payment failed, a report was paid outside the system, or a reimbursement was posted twice. Trace by report.
Test before you switch on
Run these through the new workflow with real (redacted) reports:
- A report with one company-card line and one out-of-pocket line. Confirm accounting records both expenses but reimburses only the out-of-pocket amount.
- A missing receipt, and the same receipt submitted twice across two reports.
- A foreign-currency line, checking that the rate and its source are saved.
- A line edited after approval, which should go back for review.
- A hotel folio with a personal charge on a company card.
Measure the time spent preparing reports, resolving exceptions, and correcting entries after posting. Count corrections after posting separately; they are the expensive ones.
What goes wrong
| Symptom | Likely cause |
|---|---|
| Employee reimbursed for a company-card charge | Payer not captured per line, or card program set up with the wrong payment option |
| Card liability never reconciles to the statement | Unsubmitted charges not tracked, or receipts matched to the wrong card line |
| Job costs light at closeout | Site expenses coded to general travel |
| Reimbursement payable creeps up | Failed payments or off-system reimbursements |
| Same supplier invoice in AP and in an expense report | Vendor bill paid by employee card and also sent to the AP inbox |
The last one crosses into AP. Software subscriptions and supplier deposits are the usual culprits; the SaaS finance guide and duplicate payments guide cover the AP-side checks.
Before the first live expense run
- Confirm the payment option for each card program and require a payer on every line
- Make job or department mandatory on lines that can be job cost
- Agree how personal charges on company cards are recovered
Both reconciliations belong on the month-end close checklist, with evidence kept to the standard in audit trails for automated AP and AR.