Invoice-side ingestion (Vendors)
The Vendors page (/vendors) covers spend from the payment side instead of the vendor side.
Rather than connecting each SaaS tool individually, you connect one card feed or accounting
ledger and it covers the whole long tail at once — including tools that have no usage API to
connect to in the first place.
What Plutus imports
Section titled “What Plutus imports”- Charges from a connected card feed or accounting ledger, grouped into one row per vendor (not one row per charge).
How it works
Section titled “How it works”Each new vendor Plutus discovers in the feed lands in a decision queue, pending your review. Until you decide on a vendor, its charges are held out of your account totals. This is deliberate: an undecided vendor is a visible gap with a count next to it, not a guess that quietly inflates (or deflates) a number you’re relying on.
For each pending vendor, you choose one of:
- Accept — count this vendor’s spend toward your totals.
- Ignore — exclude this vendor going forward (for example, a personal charge on a shared card, or a vendor you don’t want tracked).
If Plutus has a suggestion for a vendor — based on a connector already on your account — it shows the suggestion in its own column, separate from your decision. A suggestion is never applied automatically; you still have to accept or override it.
Marking a vendor as covered by a connector
Section titled “Marking a vendor as covered by a connector”If a vendor’s spend is already tracked through one of your cost-source connectors (for example, an AWS charge that also shows up on the card feed), you can mark it as covered by that connector instead of accepting it as invoice-side spend. This requires naming the specific connector and that connector being connected on your account. If either condition isn’t met, the vendor’s spend stays suppressed from totals rather than being counted by neither side or double-counted by both.
Reversing a decision
Section titled “Reversing a decision”Any decision — accepted, ignored, or marked as covered — can be sent back to pending. Reversing a decision removes its effect on totals until you decide again.
- A vendor with no decision yet does not appear in cost totals, even though Plutus has already seen its charges in the feed.
- Marking a vendor as “covered” by a connector that isn’t actually connected doesn’t count the spend from either side — it stays suppressed, with nothing reporting it.