We have run into what looks like a significant defect and want to document it here in case other teams are seeing the same thing.
What we are seeing
Transactions that were fully processed and synced to our accounting system (Sage Intacct) are being modified after the fact. A receipt from a later month gets attached over the receipt that was already on the transaction. The receipt in Ramp then no longer matches what was posted in Intacct, and the transaction and its supporting documentation no longer agree. We have traced instances as far back as 2024.
Why this is a problem
Accounting only moves forward. Once a period is closed and the data has synced, nothing inside it should change. Retroactive edits to closed transactions break the audit trail, create unmatched IDs across the two systems, and leave us unable to show that a given expense was supported by the documentation on file. That is a real problem in an audit and a compliance exposure for us.
Resolution
This is the part we are still working and pushing on. RAMP asked us to upload replacement receipts, but there is a list of issues.
- We do not know the scope across all of our bills/transactions
- Getting receipt going back over 2.5 year will present lots of time and challenges
- The original issue has not been fixed. Therefore, there is risk that it will just revert again.
- We need to reopen each of the “closed” transactions
- This draws MAJOR concern for RAMPs ability to recover data if they cannot produce the receipts
- This is causing issues with our auditors as they are flagging receipts that do not match
Has anyone else run into this, and if so, how did you scope it?