Ramp

Your assistant can pull the full transaction list for a period and open the individual ones that need explaining, which returns the merchant, the accounting codes and whether a receipt is attached. Alongside that it can read your vendor list, which carries spending totals per vendor, so you get the answer by supplier as well as by line item. Nothing is coded, changed or approved by reading.

What you end up with. A written breakdown of last month's card spend by vendor and by category, with the specific transactions behind each number.

Start with it bringing you the information and you deciding.

Never without. Pin the date range and say whether you mean posted or pending. Card transactions settle days after they happen, so the same month read on two different days returns two different totals and neither of them is wrong.

Built on: Get All Transactions / Get Transaction Details / List Vendors / Get Vendor Details

Transaction details include the receipt and the accounting codes, so the assistant can go through the period and hand you the exact list of transactions that are incomplete, grouped by whose card they are on. That is the month-end chase, done in one pass rather than by filtering the interface repeatedly. It can check the memo list at the same time, since a missing explanation is the other thing that stalls a close.

What you end up with. A list, by person, of the transactions that still need a receipt, a code, or a note, ready to send out.

Start with it bringing you the information and you deciding.

Never without. Treat this as a list to work from, not as the close itself. What counts as complete is your accounting policy, and the connector only reports whether the fields are populated.

Built on: Get All Transactions / Get Transaction Details / List Memos / List General Ledger Accounts

The vendor list comes back with spending totals and activity status, and the transaction history shows the recurring charges underneath. That is enough for your assistant to find the same tool bought on two cards, the annual plan that is still billing next to the monthly one, and the subscriptions nobody has touched since somebody left. It reads only, so nothing gets canceled by asking.

What you end up with. A list of duplicated or dormant recurring charges, with what each is costing and which card it sits on.

Start with it bringing you the information and you deciding.

Never without. Check what a charge is actually for before anyone cancels anything. Merchant names on card transactions are often a reseller or a parent company, and two entries that look like the same tool are regularly two different teams' real subscriptions.

Built on: List Vendors / Get Vendor Details / Get All Transactions / Get Transaction Details

Cards are listable across the whole organization with their state, their limits and who holds them, and the user list carries role, status and department. Cross-referencing those two is how you find the card still active in the name of someone who left, or the limit that got raised for one purchase two years ago. This is a read, so the assistant reports what it finds and changes nothing.

What you end up with. A current picture of who holds which card at what limit, with the ones that look stale flagged for you to decide on.

Start with it bringing you the information and you deciding.

Never without. Confirm anything that looks like a departed employee against your own records before acting. A deactivated Ramp user and a departed person are not the same thing, and a card that looks abandoned may be paying for something you still rely on.

Built on: List All Cards / Get Card / List Users / Get User

Memos can be added to transactions, so your assistant can go through the uncoded spend, work out from the merchant and the surrounding context what each charge probably was, and write the note. Where it cannot tell, it should say so rather than guess. Have it draft the whole batch for you to read before any of it is written back.

What you end up with. Transactions carrying real explanations rather than blanks, with the ones it could not explain listed separately for you.

Start with it doing the work and checking with you.

Never without. Read the batch before it is written. A memo is part of the expense record that syncs into your accounting system, so an assistant's guess about what a charge was for becomes the company's stated answer to that question.

Built on: Get All Transactions / Get Transaction Details / Create Transaction Memo / List Memos

Receipts can be uploaded against an existing reimbursement, and a receipt uploaded on its own creates a draft reimbursement by reading the image. Mileage reimbursements can be created directly from the distance, the person and the trip date. Your assistant can also read back the reimbursements already in flight and tell you which ones are stuck waiting on someone.

What you end up with. Out-of-pocket expenses filed with their receipts attached, plus a list of what is still waiting for approval and who is holding it.

Start with it doing the work and checking with you.

Never without. Check the amount and the date against the receipt image before the draft goes for approval. A receipt uploaded on its own is read by character recognition, and a misread figure becomes a claim for company money in somebody's name.

Built on: Submit Reimbursement Receipt / Create Mileage Reimbursement / List Reimbursements / Get Reimbursement Details

Virtual cards can be issued instantly with a limit and restrictions set at creation, and the response comes back with the full card number and the security code. That is the fast path for a single vendor or a one-time purchase, and the same response is the reason to think about where it lands. Physical cards are a separate action and go through a fulfillment step with a shipping address.

What you end up with. A working virtual card with a limit you set, scoped to the purchase it was created for.

Start with it doing the work and checking with you.

Never without. Set the limit at creation, and understand that the full card number and security code come back in the response. That means they pass through your assistant and into whatever transcript or log it keeps, so treat an issued card as a credential that has already been written down somewhere.

Built on: Issue Virtual Card / Get Card / Get Spend Limit / Create Physical Card

Suspending a card locks it and the connector's own note is that suspension can be reverted, which makes it the right first move while you work out whether the card is lost or just misplaced. Termination is also available and it is permanent. Both run as background tasks and return a task ID, so the assistant should check the status rather than assume the lock took effect.

What you end up with. The card locked within a minute of you saying so, and confirmation from Ramp that the lock actually applied.

Start with it doing the work and checking with you.

Never without. Suspend first and terminate only on your explicit say-so. Termination is irreversible, the card number cannot be brought back, and any subscription billing to it fails on the next renewal with no way to restore the original card.

Built on: List All Cards / Get Card / Suspend Card / Terminate Card