An accounts receivable app for finance teams. Record invoices and received payments, review overdue balances, and track collection follow-ups through settlement.

Ledger connects a customer account to its invoices, recorded payments, and follow-up history. Partial payments reduce the outstanding balance; a payment matching the remaining balance marks the invoice Paid. Aging groups open balances by due date so the oldest work stays visible. Payment records are internal bookkeeping entries: the app does not move money or contact customers. The built pilot uses ToolJet Database and fictional records; deployment and download await package and clean-install validation.
Built for Finance and operations coordinators keeping a manual record of invoices, customer payments, and collection follow-ups.
An accounts receivable app for finance teams. Record invoices and received payments, review overdue balances, and track collection follow-ups through settlement.
Review aging bands, oldest open invoices, and next follow-ups. All totals use remaining balances rather than original invoice amounts.
Create a unique invoice linked to a customer. The due date cannot precede the issue date, and amounts use two decimal places.
Add a partial or final received payment, inspect payment history, and log the next customer conversation. Exact settlement marks the invoice Paid.
Create and edit billing contacts, emails, and payment-term notes. Choose a saved customer when entering an invoice.
Review Current, 1–30, 31–60, and 61+ day bands using invoice due dates and recorded partial payments.
Create a unique invoice number with customer, amount in USD, issue and due dates, owner, and description. Customer billing details remain in a separate directory.
Record received payments with amount, date, method, reference, and note. The app blocks overpayment and repeated references within an invoice, and marks exact settlement Paid.
Log a conversation outcome and next follow-up date. Edit open invoice terms, or void and reopen invoices only when they have no recorded payments.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Customers | 4 sample customers | Billing contact, email, and payment-term notes. |
| Invoices | 8 sample invoices | Invoice amount, dates, owner, recorded payments, next follow-up, and internal history. |
The app does not process payments, send collection messages, reconcile bank feeds, issue tax invoices, or calculate exchange rates. Invoice entry is total-based; line items, tax calculation, and credit notes are not included. Amounts are in USD. Payment terms are descriptive customer notes and do not automatically calculate invoice due dates. Recorded payments are retained; no refund or payment-reversal workflow is included. Reopen detail records from the directory after a reload. This English desktop pilot reads up to 1,000 rows per table; larger datasets need pagination. Access policies, package export, and clean installation remain unverified.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
Ledger includes customer accounts, invoice entry, partial payment records, aging, follow-up notes, and settlement status across four pages.
No. It records a payment received through another channel. The app does not connect to a payment processor or bank, transfer funds, or contact the customer.
Outstanding balance is invoice total minus recorded payments. Open balances are grouped by their due date into Current, 1–30, 31–60, and 61+ day bands.
No. The pilot permits voiding or reopening only when no payments have been recorded. It does not include payment reversals or refunds.
Yes. Use the starter prompt or ask the ToolJet AI builder to adapt Ledger with your logo, colors, preferred layout, fields, and workflow. Suggested prompts describe extensions to build and test.
The pilot uses ToolJet Database and fictional sample data. It is in English with light and dark appearances. Other languages and right-to-left layouts need implementation and testing.
Public deployment and download remain disabled until the importable package and clean installation have been validated.