A manufacturer or wholesaler with a few hundred dealers ends up running a help desk without meaning to. Dealers call to ask for their ledger. They email for a copy of last month’s invoice. They send a screenshot of a bank transfer and ask why it isn’t showing yet. A sales rep asks accounts for a dealer’s outstanding balance before taking an order. At year end, someone mails out balance confirmations and chases the replies by hand.
None of these questions is hard. The answers are already in your ERP or your accounting package. The problem is that only your staff can see them, so every question costs a person’s time on both sides.
What a dealer portal does
A dealer or distributor portal gives each dealer a secure view of their own account and a few self-service actions:
- Sign-in for each dealer’s staff, with roles such as owner, editor and viewer
- Statement of account and ledger, with opening balance, invoices, receipts, credit notes and the running balance
- Invoice and credit note downloads
- Payment-proof upload, matched against your bank receipts
- Reorders from the dealer’s own price list, with order status read back from your ERP
- Balance confirmations the dealer accepts or disputes in the portal
- An audit trail of who saw, uploaded or changed what
How we would build it
Your ERP stays the system of record
The portal doesn’t keep a second set of books. Ledgers, invoices and orders come from your ERP or accounting package through its API or export, and the portal shows them as read. Orders placed in the portal go back to the ERP as sales orders, where your existing approval and credit checks still apply. If the ERP itself needs work, that is ERP development on its own terms.
Each sync records what it read and when, and the portal shows dealers the “as of” time. A failed sync is reported to your team. It never shows a dealer a balance that looks current but isn’t.
Dealer accounts and staff access
A dealer is one customer with several users. In Lekhavo’s portal, a person gets access to one client as owner, editor or viewer, and the firm can grant or deny individual areas, such as documents or reports, on top of that role. Denials always win. Internal access follows the same idea: Lekhavo staff work only on the clients assigned to them, so a regional sales rep would see only their own dealers.
Payment proofs matched, not assumed
A dealer uploads a transfer receipt. The file is checked: its contents must match its declared type, and the stored name is generated, never taken from the upload. The payment is then matched against your bank receipts.
Lekhavo’s matching engine works in this order: a shared bank reference first, then an exact amount within a short date window, then a person decides. Each match records which method made it. A dealer’s payment would follow the same rules, and anything unmatched goes to a queue for your accounts team. Our reconciliation software page covers the matching design in more detail.
Balance confirmations that compare both sides
Lekhavo already checks one set of books against another. When two entities of the same client owe each other money, it compares each side’s ledger and reports the pair as agreeing, differing by an amount, or missing on one side. A dealer balance confirmation is the same check with the dealer as the second side: the dealer confirms the balance, or disputes it with a reason, and every dispute becomes a work item with both figures.
Money that adds up
Amounts are held as integers in the smallest currency unit, never as floating point. Lekhavo’s Tally export refuses a voucher whose debits and credits differ at all, and we would apply the same rule to anything the portal writes back. Invoices shown in the portal can come from your billing system as they are, or from a new invoicing service; see invoicing software development.
An audit trail for disputes
Lekhavo records every data change with the actor, the record and the fields that changed. It logs every document upload and download with who did it and from which IP address, and every portal sign-in with its method. A dealer portal would carry the same trail, so a dispute about whether an invoice was sent or seen has an answer.
Proof from our own code
We have not shipped a dealer portal. These pieces of a dealer portal already run in production in Lekhavo, our bookkeeping platform for Indian chartered-accountant practices:
- A portal for external users, with owner, editor and viewer roles and per-area permissions
- Party ledgers, where each lender or debtor is listed by name under its balance-sheet head
- Bank-statement reconciliation and transfer matching that records how each match was made
- Export to Tally, with a preview of every ledger renamed to fit Tally’s rules and a balance check on every voucher
- An audit trail of changes, document access and sign-ins
One gap to be clear about: Lekhavo writes to Tally and doesn’t read from it. Pulling ledgers and invoices out of Tally or another ERP is integration work we would scope with you.
What the first version includes
- Dealer sign-in, roles and staff assignments
- Ledger, statement of account and invoice downloads, synced from one source system
- Payment-proof upload with matching and an exceptions queue
- Balance confirmations with disputes
- The audit trail
- Source code, a written spec and runbooks your team owns
Reorders usually come in a second release, once the ledger sync has been trusted for a few cycles.
How the work is run
Tembrant builds with an AI software factory: many agents work in parallel, held to fixed gates. Every change starts from a written spec, tests are written first against samples of your own ledgers and invoices, each change gets independent reviews, and a person signs off before it ships.
If your accounts team spends its day sending ledgers to dealers, tell us which ERP you run and how many dealers you serve.
