SAP Concur Expense to Yardi or MRI · KriyaSync flow

Yardi or MRI sends its properties, entities, and GL accounts to Concur, so employees code against valid values. When a report is approved, KriyaSync maps, splits, and checks it, then posts property-level lines and intercompany entries to the ERP. Reimbursements go to an employee payable or payroll, and anything that can't be mapped goes to the accounting team.

Two rules make the mapping hold up over time. First, the lists flow one way, from the ERP into Concur, so the ERP stays the master. Second, any line that can't be mapped stops at a clear exception instead of posting to a suspense account.

According to the App Center listing, KriyaGo Expense Connect supports Concur Expense Standard and Concur Expense Professional, and is available in North America, Europe, the Middle East, Africa, and Asia Pacific. Its real estate capabilities include:

• Property and entity distribution.

Expenses are distributed to multiple properties or legal entities, "even if the corporate office pays the expense."

• Intercompany entries.

Balanced due-to and due-from entries are created automatically when the payer and the property owner differ.

• Tenant expense chargebacks.

Costs that belong to a tenant are tagged so they can be billed back.

• Corporate card statement distribution.

Each card statement is split by property, so every property's share lands in its own books.

• Payroll reimbursements.

Reimbursements can be initiated through payroll, with the matching ERP accounting entries.

• Real-time data flow.

Lists and postings move between Concur and the ERP as they change, not in month-end batches.

The listing names Yardi Voyager and MRI Platform X among the supported ERPs, along with Procore, Microsoft Dynamics 365, Zoho One, ADP, and others.

Use these steps to plan a Concur Expense integration with Yardi or MRI.

1. Confirm your Concur edition.

Check whether you run Concur Expense Standard or Professional, and which custom fields and connected lists are available.

2. Decide the coding model.

Agree on which Concur fields carry property, entity, job, and recoverability, and whether allocations are allowed on every expense type.

3. Make the ERP the master.

Set up the list sync from Yardi or MRI into Concur for properties, entities, GL accounts, and jobs, and agree on how often it runs.

4. Map expense types to GL accounts.

Build one mapping table, with overrides by property type only where you need them.

5. Define the intercompany rules.

Document which entity pays each card program, which due-to and due-from accounts apply, and how reimbursements are paid.

6. Separate card spend from reimbursements.

Card transactions post to a card clearing account. Out-of-pocket expenses post to an employee payable or flow to payroll.

7. Set exception handling.

Decide who is notified about unmapped values, closed properties, or out-of-balance batches, and how quickly they respond.

8. Run a parallel month.

Post to a test database while the manual process continues, and compare totals by property and entity.

9. Train approvers on coding.

Most rejected lines come from wrong property or entity coding at submission, not from the integration.

10. Review quarterly.

Add new properties, retire sold ones, and refresh mappings as your portfolio changes.