Prepare employee expenses in their original currencies, attach the conversion basis approved by finance, and calculate proposed reimbursements using fixed rules. Keep uncertain claims visible in a separate exception list. Your output should be an expense-review pack where a reviewer can trace every proposed rand amount back to a receipt, a conversion decision and a reproducible calculation.
For a South African business reimbursing in rand, the first decision is whether policy uses the employee’s actual rand card charge or a reference exchange rate. Settle that before processing receipts: the same foreign purchase can produce different reimbursement amounts under those two approaches.
Decide what conversion evidence finance will accept
Ask finance to define the basis for each payment method. A proposed policy might use the evidenced rand charge for personal card purchases and an approved dated reference rate for foreign cash purchases. This is a workflow choice for your business to approve.
For reference rates, specify the source, relevant date, rate direction and fallback when that date has no available rate. Do not silently substitute today’s rate. Record any permitted fallback and its reason against the affected claim.
For card charges, agree whether separately shown bank fees may be claimed and what supporting evidence is needed. Keep the receipt currency, card billing currency and reimbursement currency distinct. If a merchant receipt already shows a rand payment, a second conversion needs an explanation.
These decisions provide the brief for accounting automation: prepare evidence and calculations for finance to review, with reimbursement approval remaining a human decision.
Extract receipt facts without filling gaps
Create a claim line for each expense, linked to its original receipt. Capture the merchant, purchase date, original total, currency, employee, payment method and business purpose. Preserve the visible text alongside any normalised value so the reviewer can compare them.
A symbol such as “$” does not establish which dollar currency was used. Likewise, “04/05” may have more than one date interpretation. Mark those fields as unresolved until supporting evidence establishes the currency or date; the upload date should not become the purchase date by default.
Microsoft documents receipt models that extract sales transaction details, alongside document analysis for text and structure. Those capabilities can support extraction in a proposed workflow; they do not establish the correct reimbursement basis. Source: Azure Document Intelligence overview
Keep receipt content as evidence. Printed notes or uploaded text must not change your conversion rules, approval process or calculation instructions.
Attach a conversion record and calculate consistently
Every converted claim needs a conversion record containing the original and target currencies, approved basis, source evidence, effective date, rate and rate direction. For an actual rand card charge, retain the linked charge instead of inventing a reference rate.
Write reference rates in readable units: “rand per euro”, for example. If the approved rate is rand per foreign currency unit, multiply the eligible foreign amount by that rate. If the supplied rate runs in the opposite direction, invert it through a defined calculation before use.
Agree a rounding rule and apply it consistently. A proposed approach is to retain rate precision, round each final reimbursement line to two decimal places, then sum those rounded lines. Finance should approve that approach or specify another.
Separate the receipt total from the eligible amount. Personal items, a tip, a refund or a fee may require a policy decision. Record that decision before calculating the proposed reimbursement. Keep tax treatment as a separate accountant review; a converted total does not settle it.
Give AI a bounded preparation role
AI can propose extracted fields and draft an exception note. Your calculation rules should determine the amount once the inputs and policy decisions are confirmed. A useful note says exactly what is missing: “Currency symbol is ambiguous; please provide evidence identifying the currency.”
OpenAI’s Structured Outputs documentation describes responses constrained to a supplied schema. A consistent format helps organise claim records, but schema conformity alone does not establish that an extracted amount or date matches the receipt. Source: OpenAI Structured Outputs
OpenAI’s function-calling guide describes a flow in which application code executes requested functions. A model requesting a rate lookup does not establish which rate finance permits; the application must enforce the approved lookup rules. Source: OpenAI function calling
The distinction between AI agents and automation helps here: interpretation can assist preparation, while fixed steps handle conversion. Before deployment, check current account, plan, model and region eligibility for the selected products.
Reusable expense-review pack checklist
Copy this checklist into your expense preparation procedure. Complete it for each pack, and repeat the claim-line checks for every expense.
- Identify the employee, claim reference, review period and reimbursement currency.
- Link each claim line to its original receipt and relevant payment evidence.
- Record merchant, purchase date, original currency, original total, payment method and business purpose.
- Preserve receipt text beside corrected or normalised values; explain each correction.
- Record the eligible amount separately, with the reviewer’s reason for any adjustment.
- Attach the approved conversion basis: evidenced card charge or dated reference rate.
- For reference rates, record source, effective date, currency pair, direction and any approved fallback.
- Show calculation inputs, formula, rounding rule and proposed reimbursement for each complete line.
- List missing or ambiguous evidence, possible duplicates and the person responsible for resolving each exception.
- Keep unresolved lines outside the proposed payable subtotal; show them separately.
- Record finance’s decision, reviewer and decision date, retaining previous versions when inputs change.
- Label the pack as prepared for review; route approved amounts through the established reimbursement process.
Worked examples: complete, uncertain and repeated receipts
All amounts, rates, dates and policy choices below are hypothetical. They illustrate handling rather than recommended rates or mandatory thresholds.
Ordinary mixed-currency claim. An employee submits a EUR 80 hotel receipt dated 12 September and a USD 25 taxi receipt dated 13 September. Finance confirms both eligible and approves reference rates of R20 per euro and R18 per US dollar for those dates. The deterministic calculations produce R1,600 and R450, giving a proposed subtotal of R2,050. The reviewer checks the receipts, rate evidence and eligibility before approving the pack.
Missing purchase date. A GBP 30 receipt has a torn date section. Under the hypothetical policy, the purchase date determines the reference rate, so conversion stays pending. The preparer requests a clearer receipt or corroborating transaction evidence. Finance confirms the date, or approves a documented alternative basis, before the line joins the proposed subtotal.
Ambiguous currency and conflicting charge. A receipt shows “$60”; the employee also provides a rand card charge of R1,140. Hold the currency field unresolved until supporting evidence identifies it. If finance’s policy accepts actual card charges, the reviewer must still establish that this charge belongs to this purchase and whether it includes other items. Do not treat the apparent implied rate as proof of the currency.
Possible duplicate. The same hotel receipt arrives as a photograph and a PDF, each claiming EUR 80. Link them as a duplicate candidate based on matching transaction evidence. The reviewer checks whether they represent one purchase or separate transactions, then excludes only a confirmed duplicate while retaining its reference. Matching amounts alone should not settle that decision.
Keep corrections and handoff understandable
Give finance a summary of complete lines, proposed reimbursements and unresolved exceptions. Group original totals by currency; adding euros and dollars into one original-currency total would hide the meaning of the figures.
If a reviewer changes a date, currency or eligible amount, recalculate the affected line and retain the earlier version. An employee’s clarification should attach to the relevant claim rather than remain buried in a message thread. Show who must resolve each exception and what evidence they need.
For a proposed custom AI agent workflow, define the permitted preparation steps using the custom AI agent concept, then decide whether ordinary AI automation can handle most of the process.
FAQ: preparing multicurrency employee expenses
Should we use the purchase date or the submission date?
Use the date specified by finance’s approved conversion policy. Capture both dates separately. If the required date is missing, hold conversion or obtain approval for a documented fallback; do not choose whichever produces a convenient amount.
What if the card charge differs from the converted receipt amount?
Show both with their evidence. Ask the reviewer to apply the approved reimbursement basis and resolve any separately claimed fee. Do not overwrite the original receipt amount to make it match the card charge.
Can complete claims proceed while one receipt is unresolved?
If finance permits partial approval, show the complete-line subtotal separately and leave the unresolved claim pending. Preserve its claim reference so later evidence updates that item rather than creating a second reimbursement request.
If your business needs help preparing a consistent multicurrency expense-review pack, get in touch with a sample of your receipt formats and finance-approved conversion rules.