Cash application with a confidence you can check
Remittance advice, payer memory and rules propose the match with a score and a digest, so a person applies in seconds, not hours.
Invoice accurately, collect faster, and keep customer credit under control.
Accounts receivable issues invoices and credit notes with tax worked out per line, applies cash as it arrives from banks, lockboxes and payment links, and tracks what each customer owes. Credit limits and holds protect the business, and collectors work the overdue list by risk with a next action for each customer. Customers can see, pay and dispute their invoices from a portal.
Remittance advice, payer memory and rules propose the match with a score and a digest, so a person applies in seconds, not hours.
Letters are proposals; only a person, or a schedule you approved up to a level you chose, can send them.
An explainable score places a hold automatically; releasing it needs another person.
A dispute stays out of dunning, opens a service case and resolves as a payment, a credit note or a write-off request.
Customers see statements, pay, dispute or promise a date themselves.
Search or filter. Planned items are labelled; everything else is available now.
A customer master with credit limits, an explainable score and holds that need a second person to release.
8 featuresInvoices from orders, plans, schedules or by hand, with tax worked out per line and one document for print and PDF.
14 featuresReceipts arrive from the bank, a lockbox or a payment link and are matched with a confidence you can inspect.
10 featuresWork the overdue list by risk, with letters that are proposals and promises tracked to the day.
13 featuresCustomers see what they owe and act on it without calling you.
4 featuresKnow what is owed, how fast it is collected and what cash to expect.
7 featuresDecisions are separated, AI prepares, and everyday screens work on a phone.
6 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Accounts Receivable.
Write-offs, credit hold releases and dunning exceptions are requests to the shared authority matrix; credit notes are submitted when posted. Another person applies each decision.
Receivables reports and dashboards for collectors, credit managers and the controller.
Datasets
Dashboards
Customer, invoice, receipt and collection resources and events, with a signed machine endpoint for payment provider events.
/v1 resources: customers, invoices, credit notes, receipts, recurring invoices, statements, aging, invoice documents, invoice deliveries, duplicate checks
Events
Connectors
Customers, open invoices and receipts load through Migrate with open items tied by currency, count and aging bucket.
Invoices, receipts, collections, dunning, disputes, aging, customers, write-offs and credit control are phone routes and the page does not widen on a phone. Native phone app comes after the back office.
Orders and quotes create invoices, credit holds and fulfilment status.
Invoices, receipts, refunds and write-offs post to the ledger; open items tie to the control account.
Billing runs create invoices for subscriptions.
Bank receipts and lockbox files reach cash application.
Output tax and e-invoice reporting for each invoice; TDS certificates.
A dispute opens a service case.
A write-off or receipt reversal can claw back incentive.
An accepted order hands off to an invoice.
Write-offs, credit releases and dunning exceptions run on the authority matrix.
Receivables open items tie to the control account in the close.
Only if you allow it. By default every letter is approved by a person. A schedule can auto-approve up to a level you set, and zero means a person approves every letter.
Receipts are matched to open invoices using remittance advice, payer memory and rules, with a confidence and a digest. A person applies the match.
Payment links, signed provider events and receipt creation are built and tested against a fake provider. Live collection needs a payment provider account that is not yet connected.
A request goes to the authority matrix, a second person approves, and a third posts, so no one person can write off a balance.
Yes, from the portal or by a collector. The dispute stays out of dunning, opens a service case and ends in a payment, a draft credit note or a write-off request.
Not yet. The in-app score uses your own receivables data; a bureau feed needs a bureau account.
Yes. Postings are kept here and sent to your existing ledger.
The queue and the document formats are built. Live submission needs provider accounts and credentials and is covered in the tax hub.