Answer Capsule: Apex Prometheus defines contractor jobsite expense tracking as a controlled chain connecting the original receipt, who paid, why the purchase was made, which project and cost code own it, who approved it, how it settled, where it posted, and whether the accounting destination confirmed the result. A receipt is evidence. OCR is a suggestion. A card swipe is a funding event. None of them is an approved expense by itself.
A foreman buys $438.72 of patching compound, plastic, and sundries at 6:18 a.m. in Staten Island. He uses the company card, stuffs the receipt into the truck console, and splits the material between a Brooklyn repaint and a change order back on the Island. By Friday, the card feed shows one charge, the paper is faded, and the office has no clean answer for which job ate the cost.
That is not a receipt-scanning problem. It is a control problem.
A Receipt, a Card Charge, and an Expense Are Three Different Things
Direct answer: The receipt shows what a merchant says was purchased. The card transaction shows how money moved. The expense record explains the business event and routes it through company control.
Microsoft’s expense documentation separates receipt OCR and matching from expense creation, workflow review, approval, and posting. Ramp likewise treats receipts, memos, accounting fields, categories, reimbursements, and exports as distinct records. QuickBooks separates receipt extraction and matching from project assignment and project reporting. The vendors themselves document separate stages, even when their marketing makes the process look automatic.
The contractor’s system should preserve at least these objects:
- Original receipt or invoice image
- Funding source: company card, employee cash, petty cash, advance, or vendor bill
- Merchant, date, total, tax, tip, currency, and line items
- Business purpose stated by the person closest to the work
- Project, phase, cost code, customer, and billable status
- Policy result, including missing evidence or threshold exceptions
- Submitter attestation and named approval
- Reimbursement, card settlement, or payable status
- Accounting export, posting result, and destination identifier
- Correction, reversal, credit, refund, or adjustment history
If those records are mashed together, the shop cannot tell what the machine extracted, what a worker claimed, what a manager approved, or what accounting actually posted.
Preserve the Original Before the Machine Touches It
Direct answer: Store the original evidence first. Treat every extracted value as a candidate with confidence, source location, and correction history.
OCR can read “$188.40” as “$1,884.00.” It can confuse the transaction date with the print date. It can miss a handwritten tip, drop a line item, or merge two taxes. That does not make OCR useless. It means OCR does not own the truth.
Give each submission a stable identity. Keep the original image. Where appropriate, store a file hash so the system can detect replacement or duplication. Record who submitted it, when it arrived, which transaction it may match, and every correction made afterward. Never overwrite the record just to make the dashboard look clean.
Consider two crew members who each buy exactly $126.54 of supplies on the same morning. Same amount does not mean duplicate. Merchant, time, card identity, receipt content, project, and submitter all matter. A safe system surfaces both candidates and asks for review instead of deleting one.
Separate Every Funding Path
Direct answer: Who paid determines the obligation. A company-card charge, employee reimbursement, cash advance, and vendor bill cannot share the same settlement logic.
If Maria uses a company card for $312.17 of masking material, the company already funded the purchase. If Luis uses his own debit card for the same amount, the company may owe him after review. If a project manager used a $500 cash advance and returns with $421.63 in documented purchases, the workflow must also account for the remaining $78.37.
The receipt does not answer who is owed. The merchant category does not answer whether reimbursement is allowed. AI may propose a match between evidence and funding, but an authorized person must resolve conflicts.
Keep these states explicit:
- Captured
- Matched or unmatched
- Submitted
- Policy exception or ready for review
- Approved or rejected
- Scheduled for settlement
- Paid or card-settled
- Exported
- Posted and confirmed by readback
- Corrected, reversed, or refunded
“Approved” is not “paid.” “Exported” is not “posted.” A successful API response is not proof that the destination ledger accepted the right amount, project, and account.
Job Cost Requires More Than Picking a Category
Direct answer: Project, phase, cost code, ledger account, customer, and billable status are separate decisions. Do not let a merchant name decide all of them.
A $900 purchase at a building supplier might contain $540 of material for a Brooklyn lobby, $240 for a Staten Island punch list, and $120 of shop stock. One swipe needs three expense lines. A flat category called “materials” hides the jobs that consumed the cash.
The workflow should allow split allocation while preserving the original total. Every split needs evidence, an owner, and a reason. If the lines do not add back to $900, the system stops. If the project is closed, the cost code is inactive, or two jobs are plausible, AI abstains and sends the record to the named reviewer.
Here is simple operational math, not a performance claim: suppose a contractor runs 60 field purchases per week. If office staff spend four minutes chasing context on only 20 of them, that is 80 minutes weekly. At a loaded office cost of $42 per hour, the visible handling cost is $56 per week, before counting bad job-cost data, delayed reimbursements, or owner interruptions. The point is not a guaranteed savings number. The point is to measure the current leak before buying another scanner.
Policy Checks Must Not Inherit Money Authority
Direct answer: A rule can flag a condition. It cannot grant itself authority to reimburse, bill a customer, post accounting, decide tax treatment, or punish a worker.
Useful automated checks include:
- Missing receipt or missing memo
- Amount above a review threshold
- Weekend or out-of-area purchase
- Restricted merchant or category
- Duplicate candidates
- Closed project or inactive cost code
- Tip above company policy
- Split allocation that does not equal the source total
- Receipt date outside the card-feed window
The system can request missing information, route an exception, and show the evidence. It should not invent a business purpose because the merchant “usually” sells paint. It should not fabricate a receipt. It should not decide that a purchase is deductible or reimbursable.
IRS recordkeeping guidance helps explain why businesses need records, but it does not turn Apex Prometheus, an AI model, or an expense app into your accountant. Tax, payroll, legal, and reimbursement decisions require authorized review.
Posting Is Not Finished Until the Ledger Talks Back
Direct answer: An export request becomes complete only when the destination confirms what it accepted.
A contractor can receive an HTTP success message while the accounting platform rejects a line later, maps it to a fallback account, or creates a duplicate after a retry. Build destination readback into the workflow. Capture the posted record ID, accepted amount, project, cost code, ledger account, posting date, and any warning returned by the destination.
Then reconcile. If the source says $438.72 and the ledger says $483.72, the record stays open. If a card feed arrives two days late, matching runs again without creating a second expense. If a refund appears next month, it links back to the original purchase rather than erasing history.
Corrections should be additive: adjustment, reversal, replacement, or credit. Clean books do not require a dishonest history.
What AI Can Do Without Taking the Keys
Direct answer: AI can extract, compare, suggest, summarize, flag, and route. It should show uncertainty and refuse to decide when evidence conflicts.
A controlled contractor workflow can use AI to:
- Extract candidate merchant, date, amount, tax, and line items
- Compare receipt data with card-feed transactions
- Suggest project and cost-code candidates from authorized records
- Detect missing fields and conflicting totals
- Summarize the evidence for a reviewer
- Route exceptions to the right project manager, controller, or owner
- Flag likely duplicates without deleting either record
It should display confidence, competing candidates, and the reason for uncertainty. “No safe match” is a valid result. The dangerous system is the one that always produces an answer because the software seller wants a smooth demo.
At Apex Prometheus, the field-first rule is simple: automation does the repetitive handling; named people keep authority over money, customer billing, accounting, tax treatment, discipline, and deletion. Churchill Painting Corp is the proving ground for that build discipline: real crews, real projects, real office pressure, and no permission to hide failure behind software theater.
Build the Control Spine Before Buying Another App
Map the current process on one sheet. Start with a receipt from a real job and follow it through the office. For every state, name the evidence, system of record, owner, approval boundary, exception route, correction method, and destination confirmation.
Run ugly scenarios, not perfect demos: missing receipt, same-amount purchases, split job allocation, employee-paid material, closed project, card-feed delay, rejected export, duplicate retry, partial refund, and a correction after month-end. If the design cannot explain those cases, it is not ready to touch money.
The middlemen make money by making control look like a feature you rent. Contractors win by owning the workflow, the records, the authority map, and the audit trail. The scanner is a tool. The control spine is the business asset.
Frequently Asked Questions
Is a receipt the same as an approved contractor expense?
No. A receipt is supporting evidence. Approval also requires the correct funding source, business purpose, project and cost coding, policy result, and authorized review. Accounting posting is a later state.
Can AI assign every receipt to a job and cost code?
No. AI can propose assignments from authorized project records, but split, shared, unclear, closed-job, or conflicting purchases need a named reviewer. The system should abstain rather than invent certainty.
What happens when a crew member loses a receipt?
Keep the transaction visible as a missing-evidence exception. Follow written company policy for requests, permitted attestations, review, and retention. Do not fabricate evidence or silently clear the exception.
How do I know an expense actually posted to accounting?
Read the result back from the destination. Confirm the destination record ID, amount, project, cost code, ledger account, and posting status. An export click or API success message alone is not final proof.
Should software automatically reimburse an employee after OCR?
No. OCR only proposes data from evidence. Reimbursement requires identity, funding, business purpose, policy review, approval, and an authorized payment path. Payment confirmation must remain separate from approval.
Come see what time it is — apexprometheus.ai