Policy on the card.[product]What you get
with Rivet
Real-time feed.
Policy checked at authorisation.
Amazon Web ServicesSoftware · Sofia Laurent$412.00
Google AdsAdvertising · Sofia Laurent$2,300.00
FigmaSoftware · Sofia Laurent$45.00
MetaAdvertising · Sofia Laurent$980.00Expense managementReceipts, categories and approvals sit on the charge itself. Policy is checked when the card is used, so month-end is a review rather than a reconstruction.
The cardholder is prompted the moment an authorisation lands, while the receipt is still in their hand, or forwards the emailed receipt and it matches itself by amount, merchant and date.
Blocked categories, per-transaction caps and daily limits are checked when the card is presented. Out-of-policy spend is declined at the terminal, not argued about afterwards.
Spend inside policy clears without anyone being asked. Set a threshold and only what exceeds it routes to an approver, with the merchant, cardholder and note attached.
Merchant data maps to your chart of accounts as the transaction arrives. Export a coded batch as CSV or straight into the accounting system finance already runs.
Policy is checkedat authorisation.
An employee pays on their card, online or in person. Limits, caps and blocked categories are checked when the merchant asks, so anything out of bounds never completes.
Attachedin two taps.
They are prompted in the app when the authorisation lands, or forward the emailed receipt and let it match itself. Anything still missing is flagged on the transaction rather than chased by email.
Against your chartof accounts.
The transaction lands with cardholder, team and merchant on it and the account already set. Any row can be recoded, and the correction sticks for that merchant next time. Only spend above your threshold waits for an approver.
A review,not data entry.
Approved spend exports as a coded batch. What is left to chase is a short list of missing receipts, not a month of reconstruction.
Every control below is applied when the card is presented, not reviewed afterwards.
Per-card limit
A monthly ceiling on each card, set at issuance and changed any time.
Per-transaction cap
Declines a single payment above an amount. Useful on vendor and subscription cards.
Blocked categories
Refuses whole merchant categories outright: cash advances, gambling, whatever you choose.
Note threshold
Requires a reason above an amount you set. The note travels with the transaction.
Approval threshold
Routes spend over an amount to an approver. Everything under it clears without a queue.
Freeze
Stops a card immediately, reversibly. A lost card, or someone leaving on a Friday.
Every transaction carries the cardholder, team, merchant, category and its receipt. Missing receipts are flagged on the line. Spend against budget is visible before the month closes, and the history stays on the account when someone leaves.
Safe by design
Receipts on the charge, policy on the card,
export the way your ledger expects.
Two ways, because people work differently. The cardholder is prompted in the app when the authorisation lands and attaches a photo in a couple of taps; or they forward the emailed receipt and it is matched to the transaction by amount, merchant and date. Anything still missing is flagged on the transaction rather than chased by email.
Policy sits on the card, so every employee, team and vendor card carries its own monthly limit, per-transaction cap, blocked categories and note threshold. A subscription card for one vendor and a travel card for one employee do not have to share rules.
No, and it should not. Set a threshold and spend underneath it clears without anyone being asked. The control that mattered was applied at authorisation. Only what exceeds the threshold routes to an approver, with the merchant, amount, cardholder and note already attached.
CSV for any system, or a direct export into the accounting software your finance team already runs. Every row carries the cardholder, team, merchant, category and its receipt, so the import does not need cleaning up.
Yes. Capture, coding and policy behave the same on digital and physical cards, including ATM withdrawals. That is the point of the spend and the paperwork living in one system rather than two.
Freeze their card and the history stays on the account. Their transactions, receipts and notes remain attached to the company record rather than walking out with the person who spent the money.