Bring the context.
Provide transaction export, receipts and expense claims, expense policy. Choose the systems and documents this team is allowed to read.
Match transactions with receipts and expense rules, then bring the gaps to the finance team.
Illustrative output. Your records and rules shape the workflow.
Bring context from the tools your team already uses. Connect MCP servers and APIs to read records, coordinate actions and keep the evidence together.
Explore the request, the responsibilities and the handoff. Each step keeps the source context attached.
Corin uses the request together with the procedures and records you make available to this workflow.
These example roles show how the work can be divided. Review the proposed team, models, tools and permissions for your process.
Link each transaction to its receipt, claimant and business purpose.
Check amounts, dates and categories against the expense rules.
Assemble unmatched transactions and policy exceptions for the reviewer.
The result includes its source context so the responsible person can review it and decide what happens next.
A new expense batch is ready for review. The team needs transaction export, receipts and expense claims and expense policy to make the next step useful.
Start with the procedure your team already follows. Corin uses that context to propose responsibilities and help coordinate the work across the tools you connect.
Provide transaction export, receipts and expense claims, expense policy. Choose the systems and documents this team is allowed to read.
Use matching agent, policy agent, exception agent as a starting point. Set each role's tools, permissions and approval boundaries.
Run a representative task. Compare the result with your procedure, review its sources and open questions, then refine the team before expanding the workflow.
Give Corin your procedures, connected context and approval rules. Review the agent team, then put it to work.