Automate expense reports: platform or ERP integration?

This guide is for Finance and Operations teams buying with internal IT. Supplier invoice processing and bank transaction matching have separate capture controls and reconciliation requirements. Here, the unit of work is an employee expense submitted under company policy.

Existing products cover much of this journey. Mendel Argentina describes expense rules, approvals and ERP integration; SAP Concur Mexico offers capture, review and reimbursement. These offers do not establish compatibility with your system version or prove that you need custom development. Sources checked on November 6, 2026.

Start with the remaining work. A platform may be sufficient when its features fit your policy and submission process. Integration makes sense when approved expenses already have a reliable record and the problem is re-entering them into accounting. Custom development needs a specific justification: a rule or user experience that available options cannot cover.

Ask suppliers to demonstrate a representative fictional example: a valid expense, a repeated receipt and a submission returned for correction. If the existing tool can handle these cases and export what your ERP needs, configuration or integration may be enough. Buying one missing part does not require rebuilding the entire process.

Define employee, legal entity, expense date, currency, amount, category, cost center, business purpose, receipt and report reference. Finance specifies required fields and visibility. For multiple currencies, agree on the exchange-rate source and date, retaining the original amount and conversion rule.

Separate business states: draft, submitted, returned, approved, pending accounting, posted and reimbursed. Adapt these names to your process. Approval does not mean the expense has been posted, and posting does not prove that the employee received money. Each transition needs an owner and evidence.

Automated receipt reading can suggest fields; policy rules determine whether a report may proceed. Uncertain extraction, an unknown category or an amount mismatch should remain visible for review. Ask how corrections preserve the original document and history. Reading a receipt does not establish tax deductibility.

Ask which connection method is available for your plan and ERP version, which permissions it needs, what fields it exchanges and how receipt is confirmed. Rindegastos support documents API, web services, FTP and files; API access requires a company account, and some methods involve development work. Platform access does not mean integration is complete.

Define how employees, entities, categories and cost centers map to the destination. An unknown cost center should leave an expense pending with a reason Finance can understand. Retain the accounting entry identifier returned by the ERP so the team can verify what was created and where.

An acceptance response can precede the actual result. HTTP 202 means a request was accepted for processing; it does not confirm completion. If the selected connection works this way, require tracking through to the accounting result and a visible state when confirmation is unavailable. This distinction applies to systems using asynchronous processing; it is not a requirement to choose that design.

Two different failures matter: submitting the same receipt twice and executing the same posting or reimbursement twice. Comparing files can help with the first but does not solve the second. Agree with IT on a stable reference for each expense and operation, and how the destination recognizes an operation already applied.

When a request times out, the record may already exist even though the sender did not receive a response. Before repeating a write, the workflow must check or reconcile its outcome using the destination’s supported mechanism. If it cannot confirm the result, route the case for review. Blind automatic retries are not an acceptable recovery method.

Corrections after approval need a rule too. Changes to amount, currency, recipient or cost center should trigger the review Finance requires and preserve the previous value. Define the response when an expense has already been posted or reimbursed: editing a screen does not reverse an accounting or banking operation.

An employee submits a travel receipt against her department’s cost center. The tool suggests fields, she reviews and submits, and an authorized person approves. The integration attempts to post the expense. This is an illustrative scenario, not a DuoTach customer or measured result.

The ERP receives the operation, but the connection loses its response. The expense stays pending confirmation with its reference retained. The operator checks the destination, finds the record and links it without creating another. It can now be marked posted. Reimbursement remains pending until the authorized payment mechanism provides its own confirmation.

The employee uploads the receipt again. The tool flags a possible duplicate and links the earlier report for review. Acceptance requires no second posting or reimbursement, and an operator must be able to explain the sequence from its history. This is more useful for comparing suppliers than a successful capture demonstration with no exceptions.

Agree on tests before implementation, using fictional receipts or authorized data in a test environment. Finance verifies policy and outcome; IT verifies access, integration and recovery. Approval from both teams prevents accepting a system solely because its interface works.

Include a valid expense, wrong currency, unreadable receipt, repeat submission, unauthorized approver, unknown cost center and unavailable destination. Also test a write that succeeds but loses its response, and a correction after approval. For each case, record the expected state, resolution owner and evidence that the operation is not duplicated.

Check that employees see only records they are entitled to access, and that someone without the required role cannot approve expenses, change policy or inspect another department’s receipts. History should show who approved which version and which system confirmed the result.

Request separate scope items for licenses, policy configuration, any submission interface, ERP connection, exception handling, tests, documentation and support. State exclusions clearly: cards, banking payments, payroll, travel and tax validation may need other vendors, permissions or additional work.

Measure a baseline: submission-to-approval time, returned reports, expenses awaiting posting and resolution time. Compare an equivalent later period with a known volume and case mix. A faster average does not establish savings if difficult cases were excluded.

DuoTach offers workflow automation and system integration. If your expense platform is in place and you need to connect the remaining operational steps, ask about that integration. Include the tool, ERP version, known connection method, approval process and current re-entry point. Scope and feasibility are established before committing to implementation; compatibility with every system and unmeasured financial outcomes are not promised.