PaidonDue for accountants and bookkeepers
Payments collected through PaidonDue are applied to the matching invoice in your client's ledger automatically, so there is nothing to key in and no bank feed to match by hand. Save the time, and use it to take on more clients.
Reconciled in the client's ledger
Switch on write-back for a client and every payment PaidonDue collects is recorded against its invoice in their ledger, with instalments recorded as part payments. Your client's bank feed then lines up with invoices that are already marked paid.
Failures are flagged, not hidden
If a write-back fails, it is flagged in the needs-attention list and retried automatically, so you are not left wondering whether the books and the bank agree.
Room for more clients
One login covers every client organisation, and collections follow the due dates or schedules your clients' customers agreed to, so there is less chasing and less matching to do for each client.
Collection itself only runs where a client's customer has given valid payment authority and received the required advance notice. Timing and outcomes may vary.
One login, every client
Every client is its own separate workspace — its own ledger connection, its own customers, its own authorisations — but you switch between them from a single login instead of juggling separate accounts per client.
1. Connect clients in one sign-in
Xero, Sage and MYOB connect every organisation you authorise in a single sign-in, each as its own client workspace. QuickBooks, Visma and Fortnox connect one company per sign-in.
2. Set who on your team can act
Grant each team member only what they need on each client: invoices, payment authorities, recovery figures, settings, team management, or nothing at all.
3. Let payments reconcile themselves
In each client's Settings, an owner switches on "Record payments in your ledger" and chooses the bank account. From then on each collected payment is written to that client's ledger against its invoice.
Covers what your clients already use
Your clients don't all use the same ledger. PaidonDue doesn't require them to.
Defensible for every client, not just one
Every authorisation, on every client organisation, is captured with a timestamp, IP address and the exact text the payer agreed to — the same evidence discipline whether you manage one client or fifty.
Read how authorisation is captured→/securityCan I mix clients on different ledgers under one login?
Yes. Each client organisation is independent — one can be on Xero, another on Sage, another on MYOB.
Can I limit what a junior staff member can do on a client?
Yes — permissions are granted per person, per organisation. A staff member with no grants on a client can do nothing on that client's data.
Who pays the subscription — me, or each client?
Either of you can. The subscription is per connected ledger organisation, and it is paid by an owner of that organisation; team members with staff access never pay. If your client subscribes their own organisation, you do not pay for it separately. If you would rather cover it yourself, you subscribe it instead, and an organisation can only have one active subscription.