Moss

Moss and finban – spend management meets cash flow planning

Moss is a spend management platform from Berlin: virtual and physical corporate cards, budgets, approvals, incoming invoices, employee reimbursements and export to accounting, all in one place. Moss shows precisely what was spent and who approved it. What it does not show is whether the money will still be there in four months. That is what finban calculates.

Where Moss ends and planning begins

Moss is good at ordering spend while it happens: every card has a limit, every invoice an approval path, every receipt a place. But a clean set of books does not answer the forward question – a hire in March, VAT due in April, a large customer taking 40 days instead of 14.

How Moss data reaches finban today

• DATEV format – pre-accounted entries with ledger account, VAT rate and cost centre.
• Excel or CSV – card transactions, invoices and reimbursements with every column Moss exports, mapped once in finban's spreadsheet integration.
• Google Sheets – the same data without uploading a file; finban reads the sheet on a schedule.

A native integration over the Moss API is planned. Moss documents its own API, so the work sits on our side.

What you get

A twelve-month forecast, open payables as dated outflows, scenarios, budgets over time, cost centres, and all bank accounts flowing in via PSD2.

What finban is not

finban does not replace Moss, and it is not bookkeeping or tax advice. It reads; it never writes back.

Frequently asked questions

Is there a direct Moss integration in finban?

Not yet – a native integration over the Moss API is planned. Today you bring the data in by export: CSV, DATEV format, or a Google Sheet finban reads.

Which Moss data do I need for cash flow planning?

Card transactions and open incoming invoices, each with date, amount and ideally a cost centre.

What is the difference between Moss and finban?

Moss organises money as it is spent. finban calculates forward: forecast, scenarios, budgets over time.