Finance operationsBuilt and run

Money Control

Finance back-office for an import business

A finance back-office: customer balances, multi-currency wallets, debts, invoices and receipts, synced with accounting behind a 2FA admin.

Talk to an engineer
Money Control: how the ledger, wallets, corrections, accounting sync, SDK and reporting connect

The problem

Every service charge, payment and customs payment has to land on the right customer balance, in the right currency, and match the accounting system.

Doing that by hand across spreadsheets and bank exports is where the mistakes come from.

What we built

  1. 01

    Ledger and wallets

    Customer balances, transactions and debts, a wallet per storage location and currency conversion, with money kept as exact amounts, never floats.

  2. 02

    Controlled corrections

    Manual balance corrections, transfers between storages and cancellations are explicit actions a person authorises; nothing changes silently.

  3. 03

    Feeds and accounting sync

    Receipts from point-of-sale and parking machines, and a sync of invoices, payments and contracts with the accounting system.

What runs now

We develop and run it in production for the finance team.

Other systems read it through an SDK and a read-only reporting connection, never its database directly.

Facts

Money
Amounts are stored exactly with moneyphp, never as floats.
Corrections
Balance corrections and cancellations are gated, human-initiated actions.
Wallets
Balances are kept per storage location.

Next step

Tell us where it is. A short call about what you have, what blocks launch and whether we are a fit.

No pitch deck. A straight answer on what's blocking your launch.