Financial Inbox & control

Automatic capture, without automatic trust.

Everything the app captures for you — a bank alert read on your phone, a scanned receipt, a CSV row, a friend naming you as payer — lands in the Financial Inbox as pending. It is not money until you say it is. One tap approves, one tap discards, and nothing moves a balance in between.

Approve or discard, per rowReconcile without rewriting historyYour data, exportable

Everything arrives the same way

What lands in the Inbox

  • Bank alert messagesRead on your phone, Android only, optional and off by default
  • Scanned receiptsText recognised on the device, merchant and total extracted
  • CSV importsA statement export, mapped once and reviewed row by row
  • Shared expensesWhen a friend records you as payer, the row waits for your approval

In short

The Financial Inbox is where every transaction NetWorth+ captures on your behalf waits for approval before it becomes part of your ledger. Bank alert messages read on the device, receipts scanned with on-device text recognition, rows from an imported CSV, and shared expenses a friend recorded naming you as payer all arrive with a pending status. A pending transaction never moves a balance, never appears in totals and never enters analytics; only a confirmed one counts as money. You approve, edit or discard each row, or handle them in bulk. Alongside the Inbox, NetWorth+ provides balance reconciliation that books a visible correction row rather than rewriting your opening balance, full backup and restore to a file you hold, CSV export, read-only account sharing that the other person can never write to, and amount hiding for use in public.

Default state of a capture

Pending, never money

Bulk approve

Yes, with the same rules

Export

CSV and full backup file

Cost

Free, no ads

Why it exists

Automatic capture is only useful if you can trust the ledger

An app that writes straight to your balance is asking you to accept whatever its parser made of a text message.

Bank alert messages are not a structured feed. They are marketing-department prose that changes without notice, in a dozen formats per country, sometimes with the merchant abbreviated past recognition and sometimes with the amount and the available balance in the same sentence. A parser will get most of them right and some of them wrong.

The question is what happens to the ones it gets wrong. If capture writes directly to the ledger, they become silent errors you find weeks later in a total that does not reconcile. If capture writes a pending row, they become a thing you glance at and discard in one tap.

One status is money. The rest are not.

This is the rule the whole app is built on: only a confirmed transaction counts. Balances, income and expense totals, budgets, analytics and the forecast all skip anything that is not confirmed. A pending row is visible and editable and completely inert — it cannot move a figure by accident, because every reader guards against it.

It also gives you a place to fix things

A captured row arrives with whatever the parser could extract. In the Inbox you can correct the merchant, set the right category, point it at a different account, or split it — before any of it is committed. Approving is the moment you take responsibility for the row, and until then the app has made no claim about your money.

Staying in control

Four places the app hands you the wheel

Reconcile without rewriting

When the ledger and your real balance differ, NetWorth+ books the gap as a dated, categorisable row you can see and delete — not as an edit to your opening balance, which would silently restate every past day and quietly change your chart.

Backup and restore

A full backup written to a file you keep, and a restore that puts it back. Not a cloud-only account you cannot get out of — a file, on your device or wherever you choose to move it.

Hide the amounts

One toggle masks every figure on screen for looking at the app on a bus or handing your phone to someone. Input fields are never masked, because typing into a row of dots is how bad data gets entered.

Read-only sharing

Share a specific account with a partner or family member. They can see it and can never write to it, you choose whether it counts toward your net worth, and you can withdraw access at any time.

How a capture becomes a transaction

Four steps, and you are three of them

1

Something arrives

A bank alert is read on the device, a receipt is scanned, a CSV row is mapped, or a friend records a shared expense naming you as payer.

2

It is parsed into a pending row

Amount, date, account and a best guess at the merchant and category. The row is visible immediately and affects nothing at all.

3

You check and correct it

Fix the merchant, choose the category, point it at the right account, split it if it was shared. Or discard it in one tap if the parser was wrong or the message was a duplicate.

4

You approve it

Now it is money. It moves the balance, enters your totals, counts toward budgets, and feeds the forecast. Not a moment before.

Message text never leaves your phone

On Android, reading bank alert messages is optional and off until you switch it on. Only messages from bank and business senders are examined — messages from personal numbers are skipped before anything is read. The text is processed on the device, is never uploaded to our servers, and is never shared with anyone. You can withdraw the permission at any time, and the feature simply stops. There is no equivalent on iOS, because the platform provides no way to read messages, and we will not claim one.

Your data

Getting it out is as easy as getting it in

An app that holds years of your financial history and makes leaving difficult has a business model you should be suspicious of. NetWorth+ has neither ads nor a subscription, so it has no reason to hold your data hostage.

  • A full backup file containing your accounts, transactions, categories, budgets and goals — written where you choose
  • CSV export for taking figures into a spreadsheet, an accountant's software, or anywhere else
  • Account deletion that actually deletes, with the pending window and the exact scope written down
  • No bank credentials to revoke, because none were ever given

Restoring a backup is deliberately careful: writes are batched and chunked so a ledger of any size restores completely rather than half-landing, which is the failure mode that makes a backup worse than none at all.

Where this applies

Across the Gulf, and beyond it

Bank alert formats differ by country and issuer, and the parser is written per region. The approval step is the same everywhere, and it is what makes a regional parser safe to ship.

NetWorth+ also covers India, Singapore, Malaysia, the Philippines, Thailand, Vietnam, the United Kingdom and the United States. Currency handling is not limited to the list above — three-decimal dinars and zero-decimal currencies are treated correctly rather than being forced into two decimal places.

Questions

Good to know

Does a pending transaction affect my balance?
No. Only a confirmed transaction counts as money anywhere in the app — balances, income and expense totals, budgets, analytics and the forecast all skip anything that is not confirmed. A pending row is visible, editable and completely inert.
Can I approve a whole batch at once?
Yes. Bulk approve and bulk discard exist for the case where you have imported a statement or come back to a week of captures. The same rules apply to each row, and large batches are written in chunks so an import of any size lands completely.
What happens if the parser reads a message wrong?
You discard it, or correct it before approving. That is the entire point of the Inbox — a parser that is right most of the time is genuinely useful, and a parser that writes straight to your ledger is not, because you have no way to catch the rest.
Is receipt scanning done in the cloud?
No. Text recognition runs on the device. The extracted merchant and total land in the Inbox like anything else, and the image is yours.
Why does a friend's shared expense need my approval?
Because no client can write into another person's ledger — that is a security boundary, not a workflow choice. When someone records an expense naming you as payer, the group balance updates, and the matching row in your own ledger is created by your device once you approve it.
Can I share an account with my partner?
Yes, read-only and per account. They see the balance and can never write to it, you decide whether their shared accounts count toward your net worth, and access can be withdrawn at any time from Connected Accounts.
Where is my backup stored?
Wherever you put it. It is a file, written through your device's file picker. There is no requirement to keep it in any particular cloud, and no version of the app that can read it that you do not control.

Keep reading

Where else this fits

Automatic where it helps, manual where it matters

Free on Android. Capture is optional, approval is not, and your ledger only ever contains what you put in it.

Android. No bank login. No ads. Message reading is optional and off until you switch it on.