Soldo
Via importPrepaid company cards with a budget per card, receipt capture, spend rules and reporting.
Direct connection planned
How the data gets in
- Google Sheets sync
- Excel import
Soldo and finban – allocated money, planned timeline
Soldo works with prepaid company cards: each card gets a balance and rules, and nothing beyond the allocation can be spent. That reverses the usual order – the money leaves before it is spent, which matters for planning.
Top-ups count differently from card transactions
With a credit card the spend hits your account later. With a prepaid card it hits earlier, at top-up. So in finban the top-ups belong in the cash timeline and the individual transactions in the analysis. Counting both as outflows counts twice.
How Soldo data reaches finban today
Export top-ups and transactions separately, map the columns once, or keep the export in a Google Sheet. A native integration is planned.
What finban is not
finban does not replace Soldo, and it is not bookkeeping or tax advice. It reads; it never writes back.
Frequently asked questions
Is there a direct Soldo integration in finban?
Not yet – it is planned. Today the data comes in by export or a Google Sheet.
Will top-ups and card spend be counted twice?
Only if both are treated as outflows. Keep the transactions in a category that does not feed the cash timeline.
Features
Strengths
- Money is allocated before it is spent
- Budget sits on the card, not in a policy document
- Simple to hand out to teams
Best For
Available in
Soldo's integrations
Related Integrations
Circula
PlannedBerlin-based expense platform for travel expenses, reimbursements, corporate cards and benefits, with a deep DATEV integration.
Moss
PlannedSpend management from Berlin: corporate cards, budgets, incoming invoices and reimbursements in one place, with DATEV export.
Payhawk
PlannedSpend management combining corporate cards in several currencies, international payments, accounts payable and expenses in one system.
Set up once, then one click
Soldo does not connect directly — you bring the file. Column mapping, overwrite rules and error handling are set up once; every import after that is a single click.