Expense Receipt Reconciler
1. Overview
The Expense Receipt Reconciler process matches scanned receipt images with the corresponding line items in an expense report, assigns each expense to its appropriate budget category, and produces a clear, structured list of the reconciled items together with a summary of the reconciliation.
2. Business Value
- Accuracy – Ensures every receipt is linked to the correct expense line and budget category, reducing errors in financial reporting.
- Compliance – Provides an audit‑ready record of how each expense was validated and categorized.
- Efficiency – Automates the tedious matching step, saving time for the Expense Manager and speeding up month‑end close.
- Transparency – Generates a transparent list showing which receipts were matched, which were not, and why, supporting easy follow‑up on exceptions.
3. Operational Context
- When to run: After all receipts for a reporting period (e.g., monthly, quarterly) have been scanned and the expense report for the same period has been generated.
- Who uses it: Expense Managers, Finance analysts, and anyone responsible for validating employee‑submitted expenses.
- Frequency: Typically once per reporting period (e.g., monthly) but can be run for any ad‑hoc expense review.
4. Inputs
| Name / Label | Type | Details Provided |
|---|
| Scanned Receipts | PDF files (one file per receipt) | Each receipt must be a clear scanned PDF. The file name should include the receipt date (YYYY‑MM‑DD) and the vendor name where possible (e.g., 2023-08-01_Starbucks.pdf). Each file must contain the vendor name, date, and total amount clearly legible. |
| Expense Report | PDF document | The report must cover the same period as the receipts and contain a table of expense line items. Each line must include: Date, Vendor, Amount, Description, and (if available) Budget Category. The layout should be consistent (e.g., column headings appear on each page). |
| Amount Tolerance (optional) | Numeric value (percentage or dollar amount) | The maximum allowed difference between a receipt’s amount and the corresponding expense line amount for a match to be considered valid. If omitted, the default tolerance is 5 % of the larger of the two amounts. |
| (Reference) Budget Category List | (see Appendix C) | A static list of all approved budget categories and their descriptions. This list is provided in Appendix C and is not an input that must be supplied for each run. |
Only the items above are required for a single run of the process.
5. Outputs
| Name / Label | Contents | Formatting Rules |
|---|
| Reconciled Items List | A table where each row shows a matched receipt and expense line: Receipt ID, Expense Line ID, Vendor, Date, Amount, Assigned Budget Category, Match Status (Matched / Unmatched), Notes (e.g., “Amount within tolerance”). | Use plain‑text table format with column headings on the first line, columns separated by a single tab (\t) or a single comma (,). No extra blank lines. |
| Reconciliation Summary | A short summary table: Total Receipts, Total Expense Lines, Matched Items, Unmatched Items, Errors/Flags (count of items flagged for manual review). | Same plain‑text table format, one row per metric, column headings on first line. |
| Unmatched Items List | Two sub‑tables: (a) Receipts without a matching expense line, (b) Expense lines without a matching receipt. Each row lists Identifier (receipt file name or line ID), Vendor, Date, Amount, Reason (e.g., “Amount mismatch”, “Missing vendor”). | Same plain‑text table format. List each category separately with a heading line “--- Unmatched Receipts ---” and “--- Unmatched Expense Lines ---”. |
| Processing Log (optional) | A chronological list of each processing step, any warnings, and the final status (“Completed”, “Error – Missing data”, etc.). | Each log entry on a new line: Timestamp – Step – Message. |
6. Detailed Plan & Execution Steps
- Collect Files – Gather all scanned receipt PDF files and the expense report PDF for the same reporting period. Place them in a single folder for easy access.
- Validate File Names – Verify that each receipt file name includes a date (format
YYYY‑MM‑DD) and the vendor name. If missing, note the file for manual review.
- Open the Expense Report – Locate the table of expense line items. Confirm the table includes the required columns (Date, Vendor, Amount, Description, optional Budget Category).
- Extract Receipt Data – For each receipt:
a. Read the vendor name, date, and total amount.
b. Record the Receipt ID (the file name).
c. If any field is missing or illegible, flag the receipt for manual review and skip matching for that receipt.
- Extract Expense Line Data – For each line in the report:
a. Record Expense Line ID (e.g., row number).
b. Capture Date, Vendor, Amount, Description, and Budget Category (if present).
c. If any required field (date, vendor, amount) is missing, flag the line for manual review.
- Define Tolerance – Use the supplied Amount Tolerance, if provided; otherwise use the default 5 % tolerance. The tolerance is applied to the absolute difference between receipt amount and expense line amount.
- Match Receipts to Expense Lines – For each receipt:
a. Locate all expense lines with the same vendor name (case‑insensitive) and a date that matches exactly (same day).
b. Within those candidates, calculate the absolute amount difference.
c. If the amount difference ≤ tolerance, consider it a potential match.
d. If multiple candidates meet the tolerance, select the one with the smallest amount difference.
e. If no candidate meets the criteria, mark the receipt as Unmatched and note the reason (e.g., “No matching vendor/date”, “Amount difference > tolerance”).
f. Record the match (if any) in the Reconciled Items List. Include the assigned Budget Category from the expense line.
- Identify Unmatched Items – After all matches:
a. Any receipt not linked to a line → list in Unmatched Receipts (part of Unmatched Items List).
b. Any expense line that was never matched to a receipt → list in Unmatched Expense Lines.
- Generate Summary – Count:
- Total number of receipt files processed.
- Total number of expense lines.
- Number of matched items.
- Number of unmatched items (receipts + expense lines).
- Number of flagged errors (missing data, etc.).
Write these counts to the Reconciliation Summary.
- Create Processing Log – Write a line for each major step (e.g., “2025‑08‑11 09:00 – Started reconciliation”, “2025‑08‑11 09:15 – Matched 45 of 50 receipts”, etc.). Include any warnings (e.g., “Receipt 2023‑08‑02_OfficeDepot.pdf – amount mismatch (12 %); flagged for review”).
- Review & Finalize – If any Errors/Flags exist, send the Unmatched Items List and Processing Log to the designated reviewer for manual resolution. Otherwise, mark the process as Completed.
- Output – Deliver the four outputs (Reconciled Items List, Reconciliation Summary, Unmatched Items List, Processing Log) as plain‑text files (or copy‑paste ready) to the Expense Manager.
7. Validation & Quality Checks
- Field Presence – Verify each receipt and each expense line has a non‑empty date, vendor, and amount. If any are missing, the item is flagged for manual review and excluded from matching.
- Amount Tolerance Check – Confirm the absolute difference between receipt amount and matched expense amount does not exceed the defined tolerance. If it does, the item is flagged as “Amount mismatch”.
- Unique Matching – Ensure a receipt is matched to at most one expense line. If a receipt matches more than one line within tolerance, select the one with the smallest amount difference; record a note “Multiple candidates – selected smallest difference”.
- Duplicate Detection – Ensure no receipt or expense line appears more than once in the Reconciled Items List. Duplicate entries trigger a warning in the log.
- Summary Consistency – Verify that the sum of Matched Items plus Unmatched Items equals the total counts for receipts and for expense lines. Discrepancies trigger a “Summary mismatch” flag.
- Log Completeness – The Processing Log must contain a start and end timestamp and an entry for every warning or error.
- Final Review – Any item flagged during validation must appear in the Unmatched Items List with a clear reason, and the process must not generate a “Completed” status until all flagged items have been acknowledged (even if left for manual review).
8. Special Rules / Edge Cases
- Missing Amount – If a receipt lacks an amount, the receipt is automatically placed in the Unmatched Receipts list with reason “Missing amount”. No matching is attempted.
- Missing Vendor – If a receipt or an expense line has no vendor name, flag as “Missing vendor” and move to manual review.
- Date Mismatch – If dates differ (e.g., receipt dated 2023‑08‑01, expense line dated 2023‑08‑02) the items will not match; they appear in the Unmatched Items lists with reason “Date mismatch”.
- Tolerance Override – If a different tolerance is needed for a particular report, the user can supply a custom Amount Tolerance value (e.g.,
$10 or 8 %). The process will use that value for all comparisons in that run.
- Multiple Receipts for One Expense – If two receipts both match the same expense line (e.g., split payment), both are listed in the Reconciled Items List with the same Expense Line ID and the Match Status set to “Matched – Partial”. The Amount column shows each receipt’s amount; the Notes column should note “Partial payment”.
- Multiple Matching Vendors – If the same vendor appears multiple times on the same date (e.g., multiple coffee purchases), the amount tolerance and the closest amount are used to pick the correct line. If the amount is identical for several lines, the first‑encountered line is used and a note “Multiple identical matches – first line used” is added.
- Excessive Unmatched Items – If more than 10 % of receipts or expense lines are unmatched, the process adds a High‑Risk flag to the Processing Log and suggests a deeper audit.
- Unreadable PDF – If the OCR/reading step cannot extract required fields from a PDF, the file is placed in Unmatched Receipts with reason “Unreadable PDF”.
- Budget Category Not in List – If the expense line’s Budget Category is not found in the Budget Category List (Appendix C), the entry is flagged as “Invalid Category”. The item still appears in the Reconciled Items List but with a Note indicating “Category not in master list – needs review”.
- Processing Failure – If the system cannot open either the receipt PDFs or the expense report PDF (e.g., file corrupt), the process stops, logs an Error message, and produces no output tables. The user must fix the files before retrying.
9. Example
Input (for a single run)
-
Scanned Receipts
2023-08-01_Starbucks.pdf – Amount $12.50, Vendor “Starbucks”, Date 2023‑08‑012023-08-02_OfficeDepot.pdf – Amount $45.00, Vendor “Office Depot”, Date 2023‑08‑02
-
Expense Report (PDF) includes a table:
| Line # | Date | Vendor | Amount | Description | Budget Category |
|---|
| 1 | 2023-08-01 | Starbucks | $12.50 | Coffee for client meeting | Travel |
| 2 | 2023-08-02 | Office Depot | $45.00 | Office supplies | Supplies |
- Amount Tolerance – default 5 %
Expected Output
Reconciled Items List
Receipt ID,Expense Line ID,Vendor,Date,Amount,Budget Category,Match Status,Notes
2023-08-01_Starbucks.pdf,1,Starbucks,2023-08-01,$12.50,Travel,Matched,
2023-08-02_OfficeDepot.pdf,2,Office Depot,2023-08-02,$45.00,Supplies,Matched,
Reconciliation Summary
Metric,Count
Total Receipts,2
Total Expense Lines,2
Matched Items,2
Unmatched Items (Receipts),0
Unmatched Items (Expense Lines),0
Errors/Flags,0
Unmatched Items List
--- Unmatched Receipts ---
(Empty)
--- Unmatched Expense Lines ---
(Empty)
Processing Log
2025-08-11 09:00 – Started reconciliation for period 2023‑08‑01 to 2023‑08‑31
2025-08-11 09:01 – Loaded 2 receipt PDFs, 1 expense report PDF
2025-08-11 09:04 – Matched 2 of 2 receipts (100% match)
2025-08-11 09:05 – No unmatched items
2025-08-11 09:06 – Reconciliation summary generated
2025-08-11 09:07 – Process completed successfully
Appendix A – FAQ
Q1: What should I do if a receipt PDF is blurry or unreadable?
A: Move the file to the “Unmatched Receipts” list and note “Unreadable PDF” in the Notes column. The item must be reviewed manually and a clear copy should be obtained.
Q2: How is the amount tolerance applied?
A: The absolute difference between the receipt amount and the expense line amount must be ≤ 5 % of the larger amount (or the custom tolerance you supplied). Example: $10.00 receipt vs. $9.70 expense = 3 % difference → considered a match.
Q3: What if the vendor name is slightly different (e.g., “Starb.” vs “Starbucks”)?
A: The matching logic is case‑insensitive and uses a simple string‑contain check. If “Starb” is a substring of “Starbucks”, it will be considered a match. If the name differs more (e.g., “Star B.”) and does not match, the item is placed in the “Unmatched Receipts” list with reason “Vendor name mismatch”.
Q4: How can I change the tolerance?
A: Provide a numeric value in the “Amount Tolerance” input. Use a percent (e.g., 8%) or a flat amount (e.g., 5 for $5). If omitted, the default is 5 %.
Q5: What if the expense line does not have a Budget Category?
A: The “Category” column can be empty; the process will still reconcile the receipt. In the Reconciled Items List, the Budget Category column will be left blank, and a note “Category missing – review required” will be added.
Q6: How are partial payments handled?
A: If multiple receipts match a single expense line, each is listed as a separate row but with the same Expense Line ID. The Match Status is “Matched – Partial”. The total of the partial amounts should equal the original expense line amount; if not, a note is added for manual review.
Q7: The process flagged many items as “Unmatched”. What should I do?
A: Review the Unmatched Items List. Common reasons are: missing/incorrect dates, mismatched amounts beyond tolerance, or missing vendor names. Correct the source data (e.g., get a clearer receipt) and rerun the process.
Q8: Can I run this process for a different fiscal period?
A: Yes. Ensure you supply the correct set of receipt PDFs and the corresponding expense report for the target period.
Q9: Does this process handle foreign currencies?
A: The process expects all amounts to be in the same currency as shown in the expense report. If receipts are in a different currency, convert them to the reporting currency before running the process.
Q10: What if the total number of receipts exceeds the number of expense lines?
A: The process will match as many as possible based on the criteria. Any extra receipts will appear in the “Unmatched Receipts” list with reason “No matching expense line”.
Q11: What if there are multiple expense lines with the same vendor, date, and amount?
A: The first encountered line will be paired with the receipt; a note “Multiple identical lines – first matched” will be added. Review manually if needed.
Q12: How can I ensure the budget categories are correct?
A: Verify that the Budget Category field in the expense report matches a category listed in Appendix C. If a category is missing from the list, it will be flagged as “Invalid Category”.
Q13: What should I do if the processing logs an “Error – File not found”?
A: Ensure the file paths and names are correct and the files are accessible (no permission issues). Fix the file location and restart the process.
Q14: How do I handle duplicate receipt file names?
A: The system treats the file name as the Receipt ID. If you have duplicate file names, rename the files to include a unique identifier (e.g., add a suffix _1, _2). If duplicates remain, they will be flagged for manual review.
Q15: What if the expense report does not include a Budget Category?
A: The reconciliation will still be performed; the Budget Category column in the output will be empty and a note “Category missing – review required” will be added.
Appendix B – Glossary
| Term | Definition |
|---|
| Receipt | A scanned image of a vendor’s proof of purchase, containing the date, vendor name, and total amount paid. |
| Expense Report | A document (usually PDF) that lists all expense line items submitted for reimbursement, including date, vendor, amount, description, and optionally the budget category. |
| Budget Category | The predefined classification under which an expense is recorded (e.g., Travel, Supplies, Meals). Each category is part of the organization’s budgeting framework. |
| Amount Tolerance | The maximum allowed difference between a receipt amount and an expense line amount for the match to be considered valid. Expressed as a percentage (e.g., 5 %) or a fixed amount (e.g., $5). |
| Matched | An outcome where a receipt is linked to a specific expense line and satisfies all matching criteria (vendor, date, amount within tolerance). |
| Unmatched | An outcome where a receipt or an expense line could not be linked to a counterpart, often due to missing data, mismatched amounts, or missing vendor information. |
| Processing Log | A chronological record of each step performed by the process, including timestamps, actions taken, and any warnings or errors encountered. |
| Reconciled Items List | The primary output: a plain‑text table that shows each receipt linked to its matching expense line, the assigned budget category, and the match status. |
| Reconciliation Summary | A concise summary that provides counts of total items, matches, mismatches, and errors for quick review. |
| Unmatched Items List | Two tables (one for receipts, one for expense lines) that could not be matched and need manual review. |
| Expense Manager | The person responsible for managing and validating employee expense submissions. |
| Fiscal Period | The period (e.g., month, quarter) for which the expense report and receipts are collected. |
| Duplicate | Two or more items (receipts or expense lines) that are identical in all key fields (date, vendor, amount) and may cause ambiguous matching. |
| Partial Match | A scenario where multiple receipts map to a single expense line (e.g., split payment) or vice‑versa. |
| Invalid Category | A budget category that is not listed in the organization's approved category list (Appendix C). |
| Error / Flag | A condition that prevents automatic processing (e.g., missing fields, unreadable file). Requires human intervention. |
Appendix C – Reference Materials & Style Guide
1. Master Budget Category List (Approved)
| Category | Sub‑Category | Description |
|---|
| Travel | Airfare | Costs for airline tickets, including taxes and fees. |
| Travel | Hotel | Accommodation expenses for business trips, including taxes and service fees. |
| Travel | Ground Transportation | Taxis, rideshare, car rental, mileage reimbursement, parking, and tolls. |
| Travel | Meals – Business | Meals consumed while traveling for business, up to the per‑diem limits. |
| Travel | Meals – Office | Meals taken on-site for business purposes, not including entertainment. |
| Supplies | Office Supplies | Pens, paper, printer cartridges, etc. |
| Supplies | IT Equipment | Laptops, monitors, keyboards, mouse, and accessories. |
| Supplies | Software Licenses | Purchased software licenses, renewals, or subscriptions used for business. |
| Marketing | Advertising | Online ads, print ads, promotional materials, and sponsorships. |
| Marketing | Events | Conference registration fees, booth costs, and promotional giveaways. |
| Professional Services | Consulting | External consulting services, legal fees, audit fees, etc. |
| Professional Services | Training | Course fees, certifications, and related material expenses. |
| Utilities | Electricity | Office electricity, water, and heating bills. |
| Utilities | Internet/Phone | Internet service, phone bills, and mobile data used for business. |
| Utilities | Office Supplies | General office consumables not included in Supplies. |
| Miscellaneous | Gifts | Business‑related gifts that comply with the gifting policy. |
| Miscellaneous | Charitable Donations | Contributions to charities approved by the organization, with proper receipts. |
| Payroll | Salaries | Employee wages, payroll taxes, and benefits. |
| Payroll | Bonuses | Employee performance bonuses or incentive payments. |
| Capital | Fixed Assets | Purchase of capital assets (e.g., machinery, furniture). |
| Capital | Depreciation | Depreciation expense for capital assets. |
| Insurance | Liability | Professional liability insurance premiums. |
| Insurance | Health | Employee health insurance contributions. |
| Insurance | Property | Property insurance for office premises. |
| Taxes | Income Tax | Corporate income tax payments. |
| Taxes | Sales Tax | Sales tax collected and remitted. |
| R&D | Research | Costs related to research & development activities. |
| R&D | Prototyping | Materials and services used for creating prototypes. |
| Miscellaneous | Misc. Expenses | Small, infrequent expenses not covered elsewhere; must be justified. |
| Travel | Misc. Travel | Miscellaneous travel costs not fitting other categories (e.g., visas, passport fees). |
| Supplies | Stationery | Pens, pencils, markers, and other stationery items. |
| IT | Cloud Services | Subscriptions to cloud services (e.g., AWS, Azure). |
| IT | Maintenance | Maintenance contracts for hardware and software. |
| Marketing | Digital Marketing | SEO, content marketing, and social media campaigns. |
| Marketing | Print Marketing | Brochures, flyers, and printed marketing collateral. |
| Travel | Meals – Entertainment | Meals with clients where entertainment is a primary purpose; requires prior approval. |
| Travel | Travel Insurance | Travel insurance policy costs for business trips. |
| Legal | Legal Fees | External legal counsel fees, litigation costs. |
| Training | Professional Development | Courses, seminars, or webinars for employee skill development. |
This list is exhaustive for the organization’s current fiscal year. Any new category must be approved by Finance before use.
2. Formatting Guidelines for Output Files
General Guidelines
- Use plain‑text files (e.g.,
.txt) with UTF‑8 encoding.
- No special formatting characters (e.g., tables with borders) – only tab or comma delimiters.
- Each table must have a header row with column titles, followed by one row per record.
- Do not include blank lines at the start or between rows.
- If any field contains a comma or tab, enclose the entire field in double quotes (
").
- Ensure there are no trailing spaces at the end of lines.
Reconciled Items List
- Columns (in order):
Receipt ID, Expense Line ID, Vendor, Date, Amount, Budget Category, Match Status, Notes.
- Use ISO date format (
YYYY‑MM‑DD).
- Amounts should be two‑decimal places (e.g.,
12.50).
- If a field is empty (e.g., missing Budget Category), leave it empty but preserve the column position (e.g.,
,,).
Reconciliation Summary
- Two columns:
Metric, Count.
- Use plain wording for the metric (e.g.,
Total Receipts).
- Provide integer values only; no commas for thousands.
Unmatched Items List
- Header line
--- Unmatched Receipts --- before the first table for receipts.
- Header line
--- Unmatched Expense Lines --- before the second table for expenses.
- Columns for each table:
- Unmatched Receipts:
Receipt ID, Vendor, Date, Amount, Reason.
- Unmatched Expense Lines:
Expense Line ID, Vendor, Date, Amount, Reason.
Processing Log
- One line per event. Format:
YYYY‑MM‑DD HH:MM – Event – Message.
- Example:
2025-08-11 09:05 – Warning – Receipt 2023-08-02_OfficeDepot.pdf – Amount mismatch (12 %); flagged for review.
File Naming Conventions for Inputs
- Receipts:
YYYY-MM-DD_VendorName.pdf (e.g., 2023-08-01_Starbucks.pdf).
- Expense Report:
ExpenseReport_YYYYMM.pdf.pdf (e.g., ExpenseReport_202308.pdf).
Error Handling
- When a required field is missing, write a log entry like:
2025-08-11 09:10 – Error – Receipt file missing amount field – flagged for manual review.
Version Control
- Add a version line at the bottom of each output file:
Version: 1.0 – Generated by Expense Receipt Reconciler SOP.
3. List of Prohibited Items for Expense Reconciliation
| Item Category | Reason for Prohibition |
|---|
| Personal Meals | Not related to business purposes; not reimbursable. |
| Alcohol (unless required for client entertainment, with prior approval) | Typically not reimbursable without pre‑approval. |
| Fines or penalties (e.g., traffic tickets) | Not a legitimate business expense. |
| Personal travel (non‑business) | Not eligible for expense reimbursement. |
| Cash advances not documented with receipts | Lack of supporting documentation. |
| Non‑business related subscriptions (e.g., streaming services) | Not business‑related. |
| Gift cards (unless specifically allowed under Gift policy) | May violate corporate policy. |
| Expenses without a date | Cannot be matched to a reporting period. |
| Receipts without vendor name | Cannot be validated or matched. |
| Expenses that exceed the per‑diem or policy limit without approval | Violates expense policy. |
| Unapproved travel class (e.g., first‑class flight without approval) | Violates travel policy. |
4. Sample Matching Rules (Reference for Users)
- Exact Date Match – The receipt date must exactly match the expense line date. No “close” dates allowed (e.g.,
2023‑08‑01 vs. 2023‑08‑02 is considered a mismatch).
- Vendor Name Matching – A match occurs when the receipt’s vendor name is exactly the same as the expense line’s vendor name, ignoring case and leading/trailing spaces.
- Amount Tolerance – Use the default 5 % tolerance unless a custom value is supplied. The tolerance is applied to the larger of the two amounts (receipt amount vs. expense amount).
- Multiple Matches – If several expense lines satisfy the vendor and date criteria, choose the one with the smallest amount difference. If two are equal, pick the first encountered. Record a note if multiple candidates exist.
- Partial Payments – When multiple receipt amounts sum to the amount in a single expense line, list each receipt with the same Expense Line ID. Add “Partial” to the Match Status.
- Duplicate Receipts – If two receipts share the same file name (i.e., duplicate Receipt ID), they are flagged for manual review.
- Currency Consistency – All amounts must be in the same currency. If different, conversion must happen before processing (outside the scope of this SOP).
5. Sample Data Validation Checks (for Manual Review)
| Check | Description | Action if Fail |
|---|
| Presence of Date | Ensure each receipt and expense line includes a date. | Flag as “Missing date”. |
| Presence of Vendor | Ensure vendor name is present. | Flag as “Missing vendor”. |
| Amount Format | Must be a numeric value with two decimals (e.g., 123.45). | Flag as “Invalid amount format”. |
| Amount Tolerance | Check absolute difference ≤ tolerance. | Flag as “Amount mismatch”. |
| Duplicate Receipt ID | No two receipts should have the same file name. | Flag as “Duplicate receipt”. |
| Invalid Budget Category | Must match a category in Appendix C. | Flag as “Invalid Category”. |
| File Accessibility | Files must be readable. | Flag as “File not readable”. |
6. Frequently Used Terms – Expanded
- ISO Date Format –
YYYY‑MM‑DD, e.g., 2023-08-01.
- Tolerance – The allowed variance between two numeric values (e.g., amounts).
- Plain‑text Table – Textual representation of a table without any special formatting, using delimiters (comma or tab).
- Processing Log – Chronological record of the execution steps.
- Version – The version number of the process output (e.g.,
1.0).
7. Review Checklist for the Expense Manager
- Verify all receipt PDFs are present and named correctly.
- Confirm the expense report PDF contains all required columns.
- Decide if a custom tolerance is needed; otherwise, use the default.
- Ensure the Budget Category List (Appendix C) is up‑to‑date and matches the organization’s chart of accounts.
- Run the process and review the Processing Log for any errors or warnings.
- Inspect the Unmatched Items List for items requiring manual review.
- Confirm that the Reconciliation Summary matches expectations (e.g., total amounts).
- Save all output files in a folder named after the period (e.g.,
Reconciliation_2023_08).
Additional Notes
- Consistency is Key: Keep naming conventions consistent; this reduces mismatches.
- Documentation: Keep a copy of the processed output files for at least the statutory retention period (e.g., 7 years for financial records).
- Audit Trail: The Processing Log serves as an audit trail; do not delete or edit it after the run.
- Escalation: If the Processing Log shows an Error that cannot be resolved by the Expense Manager, forward the log and relevant inputs to the Finance Department for further investigation.
--- (no additional text).
