Cardholders may find other articles in the Expense policy and receipts section to be more applicable.
Overview
Save time closing your books by requiring employees to code their own transactions―many hands make light work, you know. Ramp cardholders can be required to add accounting fields like category, location, vendor, billable, etc. to their own transactions.
Jump to:
- How can I enable this feature for my company?
- Allow employees to split transactions
- Limit fields an employee can see
How can I enable this feature for my company?
Visit the Expense policy section of your Settings. Expense requirements can be set for transactions and reimbursements, and you can implement as many unique policies as you need!
For example, you may need a separate policy for executive cards or for recurring spend with your vendors, create unique policies and apply to specific cards as needed!
Within each policy, you can conditionally set what you would like employees to be responsible for submitting.
Users subject to a particular expense policy will be able to submit receipts, memos, and accounting fields that are required by the relevant policy.
Note: This will only affect transactions made after the policy has been saved (it will not require cardholders to fill in information retroactively when you make a change)
See this article for more: Submission policies
Allow employees to split transactions
Have complex needs for accounting? No problem.
If you'd like employees to be able to split transactions and account for different portions of the charge separately, you can enable this setting by navigating to Settings -> Expense policy -> Global approvals and restrictions and toggling this setting on:
We've written more on splitting in our article: How do I split a transaction or reimbursement?
Limit field options an employee can see
You may want to require a specific accounting field to be filled out, but only show a subset of the options in your chart of accounts that are relevant to the cardholder. Ramp supports this and we've written more in our Conditional filtering article!